On Mon, Oct 07, 2024 at 11:21:10AM +0200, Benoit Panizzon via mailop wrote: > I usually forward spam mails I receive to Spamcop and similar services > as RFC822 attachments. Those services take the email apart, feed > blacklists train bayes filters and send notifications to the ISP of the > source IP address. > > I also did so with an Office365 account in the past and this worked. > > Not so today. My Office365 account was blocked, because apparently I a, > sending spam. > > Spam, which Microsoft happily forwarded to my inbox, but now that I > forward those spam mails as attachment, my account is getting blocked? > > Somebody please explain.
Somebody (or possibly several somebodies) there must be having a bad day. From a previous brush with that outfit[1] I learned that they prefer hearing about spam originating from their customers via proper reporting channels, aka the address junk at office365 dot micorosoft dot com. Whether or not that would have helped in your case is of course a separate question. - Peter [1] chronicled as https://nxdomain.no/~peter/a_life_lesson_in_mishandling_smtp_sender_verification.html (also prettified and tracked as https://bsdly.blogspot.com/2018/02/a-life-lesson-in-mishandling-smtp.html) -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
