https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7947
--- Comment #7 from Bill Cole <billc...@apache.org> --- There's still nothing WE can do about this. Other than your provider's statement, I can't even see any evidence that SpamAssassin is involved *IN ANY WAY*. The "Outlook Details" file you attached is incomplete because Outlook makes it very hard to see the full content and headers of such messages, but it does indicate that the intended recipient in this case had a gmail.com address. There is absolutely positively NO WAY for us to address any issues with GMail, because Google does not use SpamAssassin. Your provider sensibly directed you to relevant pages on our Wiki, where there are helpful tips. Their suggestion that you address the issue by addressing the content & structure of your messages is especially apt, because nearly all modern anti-spam tools examine messages in full rather than using simplistic metric like the domain of a sender or a specific single word. -- You are receiving this mail because: You are the assignee for the bug.
