Maldua's Zimbra FOSS Builds - Share your feedback

[phoenix]

DNS ERROR resolving MX for meel.halfgaar.net
It is suggested that the domain name have an MX record configured in DNS
Change domain name? [Yes] no
done.
Checking for port conflicts
Port conflict detected: 53 (zimbra-dnscache)
Port conflicts detected! - Press Enter/Return key to continue
Checking ldap status....not running.
Starting ldap...done.
Setting defaults from ldap...done.

Main menu

1) Common Configuration:
+Hostname: meel.halfgaar.net
+Ldap master host: meel.halfgaar.net
+Ldap port: 389
******* +Ldap Admin password: Not Verified
+Store ephemeral attributes outside Ldap: yes
+Value for zimbraEphemeralBackendURL: ldap://default
+Secure interprocess communications: yes
+TimeZone: Europe/Berlin
+IP Mode: ipv4
+Default SSL digest: sha256

2) zimbra-ldap: Enabled
+Create Domain: yes
+Domain to create: halfgaar.net
+Ldap root password: set
+Ldap replication password: set
******* +Ldap postfix password: Not Verified
******* +Ldap amavis password: Not Verified
******* +Ldap nginx password: Not Verified
******* +Ldap Bes Searcher password: Not Verified
[/code]

That MX error seems unrelated, nor do I want an MX record on that subdomain.

That is not a subdomain, it's the FQDN for your mail server and an MX record is required. You should read the Zimbra wiki for details of DNS requirements or:

Code: Select all

https://kb.iu.edu/d/aiuv 

[halfgaar]

I don't see why the FQDN of the server needs to have an MX record. It's not relevant for how the server HELOs itself, or how it's addressable. My FQDN, meel.halfgaar.net, goes into the MX record of domains that I want to use the server for, or domains used in SMTP 'mail from' and 'header from', but the FQDN itself does not need an MX record.

I operate many mail servers, various configurations of Postfix mostly, and I never have that MX record.

Case in point: the MX record of gmail.com points to many SMTP servers, non of which have an MX record.

[phoenix]

I'd suggest you read RFC 1035 which states that the MX record points to an FQDN, this has been shown in the Zimbra wiki article that covers this topic of DNS requirements for your ZCS server. Further information can be found in this search: https://www.startpage.com/do/dsearch?qu ... sion=1.1.7

[adrian.gibanel.btactic]

For the next test step, I tried upgrading my Ubuntu and go from 'zcs-10.1.0_GA_4200000.UBUNTU18_64.20240719155652' to 'zcs-10.1.0_GA_4200000.UBUNTU20_64.20240719155625'. I tried the normal 'install.sh', but also the 'install.sh --software-only' method as described on the wiki, which involves placing back your local config and running '/opt/zimbra/libexec/zmsetup.pl'. Both had the same result, of ldap issues.

Do not use that awful documentation. Use this one instead.

Make sure to replace:

• 8.8.15 to 10.1.0
• 18.04 to 20.04
• 16.04 to 18.04

and you are good to go.

[liverpoolfcfan]

I don't see why the FQDN of the server needs to have an MX record. It's not relevant for how the server HELOs itself, or how it's addressable. My FQDN, meel.halfgaar.net, goes into the MX record of domains that I want to use the server for, or domains used in SMTP 'mail from' and 'header from', but the FQDN itself does not need an MX record.

I operate many mail servers, various configurations of Postfix mostly, and I never have that MX record.

Case in point: the MX record of gmail.com points to many SMTP servers, non of which have an MX record.

The setup is merely pointing out that it cannot find an mx record in DNS for mx.meel.halfgaar.net as it is about to create a domain meel.halfgaar.net in your zimbra server.

It is offering you the opportunity to change the domain name it is about to create. You might for example want to create the email domain halfgaar.net (which has a DNS record - mx.halfgaar.net) running on server meel.halfgaar.net

[halfgaar]

The setup is merely pointing out that it cannot find an mx record in DNS for mx.meel.halfgaar.net as it is about to create a domain meel.halfgaar.net in your zimbra server.

It is offering you the opportunity to change the domain name it is about to create. You might for example want to create the email domain halfgaar.net (which has a DNS record - mx.halfgaar.net) running on server meel.halfgaar.net

This Zimbra mail server has been running for some 10-15 years like this. It's indeed the server named meel.halfgaar.net, serving mail for, among others, halfgaar.net.

It may be related to it being a copy of the original VM. I changed /etc/hosts to make it think meel.halfgaar.net is the new IP. This works for the Ubuntu 18 Zimbra 10.1.0 install, but when I try to install the Ubuntu 20 version after doing do-release-upgrade, it complains about this MX record.

It shouldn't be too much of an issue, as long as it's unrelated to my ldap failures. Probably it's best ignored in this thread, no matter if my setup is wrong or right,, unless it's related to Maldua's builds. I first need to try the different upgrade method he linked to.

[halfgaar]

For the next test step, I tried upgrading my Ubuntu and go from 'zcs-10.1.0_GA_4200000.UBUNTU18_64.20240719155652' to 'zcs-10.1.0_GA_4200000.UBUNTU20_64.20240719155625'. I tried the normal 'install.sh', but also the 'install.sh --software-only' method as described on the wiki, which involves placing back your local config and running '/opt/zimbra/libexec/zmsetup.pl'. Both had the same result, of ldap issues.

Do not use that awful documentation. Use this one instead.

Make sure to replace:

• 8.8.15 to 10.1.0
• 18.04 to 20.04
• 16.04 to 18.04

and you are good to go.

To confirm, that worked. The key was putting the following in /etc/update-manager/release-upgrades.d/allow-thirdparty.cfg:

Code: Select all

[Sources]
AllowThirdParty=yes

That prevents Zimbra packages being removed by 'do-release-upgrade'.

[adrian.gibanel.btactic]

Apparently 10.1.0 FOSS builds have a bug that doesn't enable you to manage storages (new way of saying volumes) because it asks you for a license.

You can find more information at:

• ZimbraAdmin's Storage Management asks for license (Original report at Maldua's zimbra-foss-builder repo)
• ZCS 10.1.0 Foss Build - [BUG] - ZimbraAdmin's Storage Management asks for license (forums.zimbra.org report)

[adrian.gibanel.btactic]

Hello,

Maldua's Zimbra 10.0.9 FOSS Builds have just been released.

Please share your experience when upgrading or installing from scratch.

Versions:

• 10.0.9

Platforms:

• RHEL7 (Red Hat Enterprise Linux 7, Oracle Linux 7, CentOS 7)
• RHEL8 (Red Hat Enterprise Linux 8, Oracle Linux 8, CentOS 8, Rocky Linux 8)
• Ubuntu 18.04
• Ubuntu 20.04

Thank you very much!

Notes:

• These are recent releases. They will become stable releases when after 15 days of being public there has not been any major negative feedback.
• This is not an official Zimbra/Synacor build.

[halfgaar]

Is there a reason to use 10.0.9 vs 10.1.0?