This is why you shouldn’t include the whole spam sample, but instead, just include the headers. The headers include enough info for them to find the mail in their systems.
When it comes to outgoing respective incoming, what I know they have higher thresholds for outgoing mail, because once they detect a user as a spammer, they will terminate the user. So they, what I know of, never block outgoing spam, but instead, terminate users that are detected sending spam. Från: Hans-Martin Mosner via mailop <[email protected]> Skickat: den 13 december 2025 12:00 Till: [email protected] Ämne: [mailop] Google knows that its spam, they recognize it when its incoming, just not when theyre sendi Response to an abuse report (which naturally contains a spam sample): <mailto:[email protected]> <[email protected]>: host smtp.google.com[192.178.156.26] said: 550-5.7.1 [xx.xx.xx.xx 12] Gmail has detected that this message is 550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail, 550-5.7.1 this message has been blocked. For more information, go to 550 5.7.1 https://support.google.com/mail/?p=UnsolicitedMessageError xxx-xxx-xxx.186 - gsmtp (in reply to end of DATA command) Guess I will need to skip the reporting step and proceed to outright blocking from the start. Cheers, Hans-Martin
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
