it's also a mistake that makes a lot of sense in the historical context of the
email network - DSNs against misconfigured or unpatched email servers were
often used for backscatter spam (which was thankfully prevented here by
rejection during SMTP), so it made sense to treat them as regular messages or
worse for filtering's sake.
On 19 November 2022 17:27:23 UTC, Jaroslaw Rafa via mailop <mailop@mailop.org>
wrote:
>Dnia 19.11.2022 o godz. 10:41:32 Chris Adams via mailop pisze:
>> I have a Gmail address - I don't give it out, the only legit mail I get
>> to it is generally Google account related stuff (bills and such). I
>> have a forward set up on it to send everything to my personal server.
>>
>> This morning, there was some spam that got through Gmail's filters sent
>> to it. Gmail tried to forward it, but my server's spam filters rejected
>> the message (reject during SMTP, no bounce generated from my server).
>> Gmail generated a delivery status notification message... and sent that
>> directly to the Gmail spam folder.
>>
>> Oops... :)
>
>Probably because the DSN contained a part of the spam message that was
>rejected. It's a common mistake of spam filtering systems (not only Gmail's)
>that they don't treat DSNs (even their own) specially and often classify
>DSNs for spam messages as spam.
>--
>Regards,
> Jaroslaw Rafa
> r...@rafa.eu.org
>--
>"In a million years, when kids go to school, they're gonna know: once there
>was a Hushpuppy, and she lived with her daddy in the Bathtub."
>_______________________________________________
>mailop mailing list
>mailop@mailop.org
>https://list.mailop.org/listinfo/mailop
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
