On 1/5/22 9:19 PM, Jered Floyd wrote:
Some of this mail gets forwarded to another organization (also partially under my control) which has a mailhub also running spamassassin.I would like the downstream spamassassin to skip scanning on messages flagged as spam, rather than wrapping in another layer of SA (or deciding that the message is now ham after forwarding). ...Is there a way to do this within Spamassassin config?
I don't know if it would work in your scenario or not, but it might work to have the upstream system send to the downstream mailhub on a different IP+port pair wherein SpamAssassin is not integrated. In Sendmail, this could be as simple as an additional DaemonPort that doesn't include the InputMailFilter (milter) that's interfacing with SpamAssassin.
2) I can get a similar result by having my downstream MTA skip the spamassassin pipeline part for messages from the upstream mailhub (probably by establishing an authenticated alternate delivery port), but this is less ideal as it won't filter messages originating from the upstream organization (and not scanned) and also seems more brittle...
So ... you want /conditional/ filtering between the upstream and downstream mailhub.
Q: Does the upstream MSA not do filtering of inbound messages from clients? I would think that this filtering would cover messages originating from the upstream organization to the downstream organization.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
