Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jstammi

Pages: [1]
1
Sounds promising: could you please provide what you did exactly?

2
The few times I tried to get support using the forums here, I did not receive any help. So I agree with that statement. I hope someone convinces me of the opposite. As I personally prefer ubuntu  for the same reasons as already said, too.


Concerning the issue: I did not find a good solution for this, it is still an issue for me.

And it is tracked by a bug report, too:

https://tracker.zentyal.org/issues/5257

3
Email and Groupware / masquerade_domains option not configurable
« on: May 10, 2017, 11:40:20 am »
Hi,


AFAIS/AFAIK for my use-case I depend on being able to specify the postfix masquerade_domains option. This is not available directly in zentyal. As workaround I appended such to /usr/share/zentyal/stubs/mail/main.cf.mas and things are working now as expected.

But may be I miss something - perhaps some expert may suggest a different solution?


The setup is as follows:

I run a private mail server for my family, all mails arriving to the various mail accounts are collected bwo fetchmail and made accessible (and archived) there, in our private home LAN.

We own a domain and my families members own a related email addresses (not only my own family but also relatives). For some reasons (mailbox sizes, SPAM filtering, etc) mails to those get forwarded elsewhere only (where they get later fetchmail'ed then for the members of my very own family).

Thus our private LAN mailserver is not the master mail server for that domain, it is not addressed as MX for our domain.

On sending mails all of us use an email address belonging to our domain. The private LAN postfix relays mails sent locally to the provider running our domain at.


Unfortunately it seems impossible to seup zentyal mail/webmail accordingly with standard means.


The solution suggested most (and being documented to be the upgrade path from zentyal 3 to 4 where the masquerade_domains option is said to having been removed) is to configure zentyal mail virtual domain to use our domain: sending emails (using the webmail) locally to my own family's members works as expected. But mails to relatives using also an address of our domain are rejected - they needed to be relay'ed but as my private mail server now feels responsible for the domain they don't get.

Instead I configure zentyal mail virtual domain to use a local domain: sending emails to local recipients works, too. Mails (using the webmail) to relatives and other externals get relay'ed. Unfortunately the domain ISP rejects them as they arrive with my local domain based email address.
This get's solved with configuring the masquerade_domains option.


Is there any other option that I'm not aware of, yet?

4
If there is anybody *not* (yet) having this problem, PLEASE REPORT THE SAMBA PACKAGES' VERSIONS being used, so that I can downgrade.

5
Something seems broken: the journal is filled up with such messages (PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so...) and ldap auth seems no longer working for my everything-up-to-date installation 5.0.7/xenial.

So, please, who has a still working installation? Please report the samba packages installed for you. Perhaps I get it up and running again by downgrading ...

6
Installation and Upgrades / ubuntu+zentyal upgrade to 16.04/5.0
« on: January 06, 2017, 11:20:31 am »
I see the new zentyal version with new ubuntu baseline is available. But I do not find any documentation on upgrading from an existing 14.04/4.2(.2). Just a 1 month old statement in the announcement that some details on this would follow there within the next weeks. Nor did I find some hints or success stories here in the forum.

So did I miss some relevant documentation and/or postings?

I have an up-to-date installation running and just was about to install mail/groupware related stuff. As there is a major change from openchange to sogo I expect prior upgrading would be preferrable ...

7
The other way around to get the module running again initially seemed more difficult to me - but may be I'm wrong with this.

Actually I see a ldap related error on saving any changes related to the domain:

2014/10/29 21:58:31 ERROR> LDAP.pm:196 EBox::Module::LDAP::_connectToSchemaMaster - Error binding to schama master LDAP: An error occurred in C<Net::LDAP>
 at Error binding to schama master LDAP: An error occurred in C<Net::LDAP>
 at /usr/share/perl5/EBox/Module/LDAP.pm line 196

8
No, sorry, this is not what I meant: on re-installing the module then, all settings having done still remain. And the module still will not come up without errors.

So I need to know: what do I have to delete
 - files
 - directories
 - software packages
to have a "clean" system again. So that none of the settings having made previously remain. And hopefully re-installing the service succeeds then ...

9
Does no one have an idea of what I have to remove/modify (directories, software packages, files, ...) to re-start the AD server installation?

10
I'm struggling with problems of the samba service on starting the "Users, Computers and File Sharing".

As this service is IMHO in an completely undefined (configuration) state and as the domain controller was not yet "productive" prior to upgrading the server from 3.3 to 3.4 and finally 3.5, I would like to re-install such completely from scratch.

So what do I have to delete, de-install, ... to achieve this?

I already spent some hours now on try-and-error with removing directories and packages related to samba, ldap and sss - but up to now no success on starting the service finally (with the server to become a dc).

Pages: [1]