Zimbra Forums

If you Google like “Ubuntu Server Stub Resolver port conflict” you will find actionable info and several choices for how to solve this problem. I’m not trying to be cryptic nor coy; it’s a complex Ubuntu configuration you’ll need to understand fully to avoid issues going forward, like when patching.

Thanks for your kind words! Please prepend the subject of your first post with “[SOLVED]” and that will take care of that. No way to star a specific post as a solution here to my knowledge. As for your own emails being marked as spam, the same header analysis technique should help you identify the r...

If you look up all of the tests in the "X-Spam-Status" field, you will see exactly why your IP camera's messages are getting flagged. All of those tests are in either ~/data/spamassassin/rules or ~/data/spamassassin/localrules, so if you do like: zimbra@mail2:~$ grep FORGED_MUA_OUTLOOK ~/d...

Having a single LDAP MMR server is not an issue technically.

Yes, it will get lonely and pine away in the logs for its partner, but the Rolling Upgrade docs include a cron job to prune those entries from zimbra.log.

And, you can always dump LDAP, do zmldapinit, and import LDAP to get rid of MMR.

So first, 8.8.15 is past end of General Support and should be updated to at least Zimbra 9 if not Zimbra 10. Second, why those emails are being flagged as spam will be revealed by the email header. Right click on the email in the web client, choose “Show Original” and paste the headers here up throu...

The only changes to the existing Production server during a Rolling Upgrade comprise: - Turning on LDAP MMR - Changing the zimbraServiceEnabled attribute to turn off (in stages) LDAP, Proxy and MTA services and restarting Zimbra. These are all low-risk operations; the zimbraServiceEnabled changes ar...

I would use, and have used successfully, the documented Rolling Upgrade method.

And once you are on the latest patch, you'll want to plan your move to a newer version of Zimbra, as 8.8.15 was End of General Support on 31 December 2023.

You need to enter the selector manually in the Dmarcian DKIM tester; without sending an email to Dmarcian there is no way for them to know what your selector is.

You would be better off configuring the destination Gmail mailbox to fetch emails from Zimbra rather than Zimbra trying to pump everything to Gmail.

Mass, blind forwarding like that can result in your Zimbra server’s IP and domain getting throttled/blocklisted by the destination provider.