| I had a major issue with spam on FM and after some back and forth with support, I got some understanding of their system: 1. The bayesian filter updates only when you actually delete emails from the Spam folder. 2. There is a global and a personal spam filter. The personal one kicks in after 200 spam emails have been ingested/deleted. You need to break it in, like a pair of leather shoes. 3. Before this 200 email threshold, make use of automated rules to just mark stuff as Spam automatically, if like me, they have all a similar pattern. When your personal filter kicks in, you're golden and works as expected. I don't have any spam issue anymore and I don't think I've ever seen a false positive either. So now it's smooth sailing. I wish Fastmail documented this process, which was explained to me by their support after a dozen exchanges. Funny aside: all the spam overwhelmingly comes from gmail.com accounts. Seems like Google needs to work on their terrible outgoing spam issue. They're the biggest spam sender now that no one runs open mail servers on the Internet anymore. |
Report it to google, and make the world a better place.
But, first check the first received header that was added by your mail provider's servers to make sure the spam really is coming from gmail's servers-- oldest received headers are at the bottom, newer as you go up (e.g., view message source, view headers, or some such option in your client; look for received: from...).
Add a short blurb at the top of your message about spam received from their domain, include the message with full headers as text at the end of the email message body (some clients like MS outlook break mail, so this may be the only way the recipient will be able to view the headers if the sender is using one of these broken clients. Also attach the original spam message as an attachment (this will provide something useful to the recipient when sent by most ?all? non-Microsoft mail clients).
Send it to abuse@gmail.com
Report the stuff your spam filter catches too.
At past jobs, we took these reports very seriously. They were usually an indication that a user's account was compromised.