https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7686
--- Comment #3 from Jordan <[email protected]> --- Something I'm still not clear on: In the example provided we happen to operate both the RainLoop webmail system that the message was sent *from* and the *receiving* server. The spamassassin headers and PBL checks were done on the *receiving* server. Therefore its on the *receiving* server that I would need to set msa_networks. Great, this would solve things for when our servers happen to be the receiving server. But configuring msa_networks in Spamassassin does absolutely nothing when someone sends a message to some server using Spamassassin that's out of our control. So I think I'm back to square one with the options being: 1. Disable the x-originating-ip header in RainLoop and simply do without its diagnostic aid 2. Compile my own latest version of Spamassassin and deal with the binary package differences, then hope that this *was* a bug which was fixed between 3.4.0 and 3.4.2 -- You are receiving this mail because: You are the assignee for the bug.
