Hi, I'm having a problem with bounce messages being tagged as spam. What is the proper way to handle legitimate bounce messages these days? Is it safe to bypass scanning DSN bounce messages and route them directly with postfix?
I've created some rules over the years which attempt to identify spoofed bounce messages (mailer-daemon@...), but the rule hit this message when it shouldn't have. We have a mail system that allows user forwarding. The user with an account on our system sent a message from their gmail address (bfg38...@gmail.com) with the envelope-from being the account on our system (38...@example.com). The DSN was sent back to the 38137 user, where spamassassin tagged it as spam incorrectly. https://pastebin.com/HBTx7Cqw I realize this is convoluted, and forwarding is problematic for many reasons. That's a separate issue. I'm trying to figure out how I can better configure bounce message management on my system in general, particularly as it relates to preventing legitimate messages from being marked as spam. Is the solution here to use the whitelist_bounce_relays? Or does it not apply here since the mail originated at gmail? Thanks for any ideas.
