Search results

the only way, I see to avoid this is to provide different priority to your MX records. abc.com IN MX 10 pmg1.abc.com abc.com IN MX 20 pmg2.abc.com abc.com IN MX 30 pmg3.abc.com It has its own "cons", but may speedup mail delivery in your case.

Thank you very much! everything with default config works as expected now!

I did not applied any workarrounds described in this thread. only apt upgrade to new pmg-api via web console. do I ubderstand correctly, tnan: smtputf8_enable = no is now an defaul option in automatically generated postfix main.cf, and I do not need to edit anything. btw i cant find it in my...

I just updated to pmg 7.2-4. so do I need to edit main.cf manually?

received an update to 7.2-4. what config should I edit to have it working?

that will not break my cluster, especially after official patch will be enabled.

have the same issue. pmg last update + ms exchange 2016. it there any nondestructive workaround? Jan 18 12:24:45 mx5 postfix/smtpd[49268]: connect from relay.sender.tld[xxx.xx.xxx.x] Jan 18 12:24:47 mx5 postfix/smtpd[49268]: NOQUEUE: client=relay.sender.tld[xxx.xx.xxx.x] Jan 18 12:24:47 mx5...

DKIM is musthave feature for modern MTA...