Postfix Backup MX
-
Thank you for your reply. The link you posted is one of the general examples.
The default configuration of the pfSense Postfix package will not hold messages if the mail server goes down. Somebody else asked a similar question on these forums, and the gist of the discussion was that it should be possible. I was just wondering if somebody already has a working recipe.
I will dig into this today and post my findings.
-
@G.D.:
The default configuration of the pfSense Postfix package will not hold messages if the mail server goes down.
It will hold messages and will work as an mx backup.
Just configure general and domain tabs. For an extra config for valid recipients, check recipient tab.
-
You are probably right, but it looks like something needs tweaking
.
What is causing the following messages, when the primary MX is down?450 4.1.1 Recipient address rejected: unverified address: Address verification in progressIs Postfix trying to query the main MX if the recipient is valid? Obviously that will not work when the main MX is down.
-
@G.D.:
Is Postfix trying to query the main MX if the recipient is valid? Obviously that will not work when the main MX is down.
At least using ldap perl script on AD, if the MX is offline, it uses current list until a new one is fetched.
-
No LDAP on this setup, just a hard-coded list of valid recipients.
I switched the Header verification from Strong to Basic, and “Address verification in progress” rejections stopped.
Maybe, in the future, it would be nice to have more granular control over header verification options, where individual ones could be checked on and off; perhaps with ones that require server verification grouped together, for easier configuration of backup mail exchanges.
Thank you.
-
FYI- In theory / on paper this sounds good but in practice you might find, as I have, that spammers tend to hit your backup MX harder than the primary since backup mail servers tend to have less stringent spam controls.
Not saying it's a bad idea to have a backup MX, it's a great idea, but be forewarned / prepared for what may come.
-
Sorry to revive an old topic but I am actually curious about this setup.
-
A high priority mail server - the main MX - and a lower priority server, the backup MX - have exactly the same setup from a "pfSense point of view".
-
I know how that works, but I was just wondering if it was possible to do it with pfsense should my main server be down briefly.
-
I'm using myself a "3 € a month" small dedicated VPS system as my backup MX, running postfix.
As Jimp said above, this server backup MX gets hit rather often (mine does), because many spammers do not send mail to to main MX, but directly to the back MX.
This means that all mail filtering, present on your main MX should also be present on your backup MX.This means for me :
fail2ban,
grey listing,
amavis (spamassassin and clamav and their boatload of plugins
which implies full MySQL supportThe thing is : all these kind of programs just don't belong on a firewall.
Btw : many voices just state : "do not use a MX backup, you don't need it" because the defition of the mail protocol says : "if the destination server can't be reached, the mail should be queued for a day or so …" which means that if things go bad, you have a day "click it to work".
-
The only downside of not having a backup MX is having to wait hours (4+) for retries to come through, or longer if it's a prolonged outage. It's not the end of the world, though, messages will be resent.
If you botch the backup MX config then it could be worse. You could accidentally reject mail and never receive it, or let even more spam through on a continuing basis.
The best backup MX is an exact duplicate of your primary mail server hosted off-site.
