On 6/11/2024 4:05 AM, Gilgongo via Postfix-users wrote:
On Tue, 11 Jun 2024 at 05:17, Noel Jones via Postfix-users
<postfix-users@postfix.org <mailto:postfix-users@postfix.org>> wrote:
You should remove permit_mx_backup.
This feature is intended for ISP-scale users that may not have a
complete list of domains that use their server as a backup MX. In
this case, permit_mx_backup_networks would define the ISP's
customer
network space.
I've just tried that, but the mail queue filled up
with double-bounce messages being sent to postmaster. This is partly
the reason why I'd like to sort out my configs, as there's clearly
some stuff going on that I don't understand.
BTW in the meantime, if I add this (where mx2.mydomain.com
<http://mx2.mydomain.com> is our secondary MX hostname), I take it
that would be a good idea:
permit_mx_backup_networks = $mynetworks mx2. mydomain.com
<http://mydomain.com>
or is there a way of replacing address verification (if that's
what is going on) with something better?
Thanks for your help BTW.
If you need permit_mx_backup, that means postfix doesn't have a
clear idea of domains it is responsible for.
Please read and study:
http://www.postfix.org/BASIC_CONFIGURATION_README.html
mydestination should contain domains that are delivered locally by
postfix on the same machine.
relay_domains should contain a list of all domains that are passed
further downstream for final delivery outside of "this" postfix,
such as to another process on the same server, or to a different server.
It shouldn't be that hard to tell postfix what domains it is
responsible for.
-- Noel Jones
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
