Zimbra Forums

hi guys, we as probably everybody are annoyed by spam. Using the hints in https://wiki.zimbra.com/wiki/Anti-spam_Strategies and implementing a few RBL resulted in too many false positives, so we do not see this as good first barrier against spam. i hoped that spamassassin would actually learn if we ...

If all better methods fail imapsync is your friend

Gesendet von meinem SM-N910F mit Tapatalk

thank you jorge for your feedback. the topic internal fqdn/domain names vs external is usually solved by using application delivery controllers/load balancers like netscaler, kemp loadmaster, bigip f5 and so on which do rewrite the client requests target name to the proper internal domain. The issue...

the thing with the documentation like https://wiki.zimbra.com/wiki/Split_DNS for example is, that you there is no notion of internal domain names and it seems as if you expect the server host name and FQDN to be the same as the public FQDN host name that will be used to access zimbra externally. one...

since re-installing zimbra just because some hosts file was not proper at the time of install is not really an option, wouldn't it be better to have a documentation about the configuration values that should be in place when using the common split dns scenario ? so basically what the output of zmloc...

even though you say that you disables anti spam and anti virus you could try to set the verbose level of those components to a higher level and then check the zimbra.log for the messages and what rating those messages get before they get put into spam. Use following command to raise the verbose leve...

hey andre,

the webmail port is the default https port (443), so just open a browser and navigate to your server with HTTPS

Did you try SMTP via StartTLS with Port 5xx( don't remember by heart). That is what works for me by default.

Gesendet von meinem SM-N910F mit Tapatalk

What protocol do you use? By default zimbra does not allow authentication over unencrypted protocols. So if you use Port 25 for the smtp connection your are doing it wrong

Gesendet von meinem SM-N910F mit Tapatalk

Just as a little Note and warning: if you use the steps described in the Wiki and your Hostname Fqdn does not match the public domain name (which is pretty much always the case) after deployment of the lets encrypt certificates the ldap Server will fail to connect, since it somehow expects the local...