Release spam without whitelist 127.0.0.1 default
Posted: 13 Jul 2018 12:52
I've been playing around with EFA (latest) for the past few weeks, and plan to deploy it in production soon. I like it.
My final set-up is a bit weird. It has another MTA in front of postfix.
So myMTA listens on 25, receives, passes on to postfix (listening on 2525) on the same box, Maiscanner does stuff, then on to finalMTA.
This works very well, and allows me to have myMTA do address validation at FinalMTA before accepting. There are more motivations for having myMTA in stead of postfix in front, but this is certainly an important one.
Only 1 caveat/hurdle is left: I can't whitelist 127.0.0.1 default, as all mail now reaches postfix from 127.0.0.1.
Without this whitelist, releasing a spam triggers Mailscanner on the released message, which then get tagged as spam, and sent to quarantine again.
So I'm looking for a - here comes the word - workaround here: avoid scanning a released message, without the required 127.0.0.1 default whitelist.
Patrick Sneyers
BE
My final set-up is a bit weird. It has another MTA in front of postfix.
So myMTA listens on 25, receives, passes on to postfix (listening on 2525) on the same box, Maiscanner does stuff, then on to finalMTA.
This works very well, and allows me to have myMTA do address validation at FinalMTA before accepting. There are more motivations for having myMTA in stead of postfix in front, but this is certainly an important one.
Only 1 caveat/hurdle is left: I can't whitelist 127.0.0.1 default, as all mail now reaches postfix from 127.0.0.1.
Without this whitelist, releasing a spam triggers Mailscanner on the released message, which then get tagged as spam, and sent to quarantine again.
So I'm looking for a - here comes the word - workaround here: avoid scanning a released message, without the required 127.0.0.1 default whitelist.
Patrick Sneyers
BE