You're missing the larger issue of having abuse and postmaster flooded with spam.
Aloha, Michael. -- Michael J Wise Microsoft Corporation| Spam Analysis "Your Spam Specimen Has Been Processed." Got the Junk Mail Reporting Tool ? -----Original Message----- From: Philip Paeps [mailto:phi...@trouble.is] Sent: Monday, April 10, 2017 11:51 AM To: Michael Wise <michael.w...@microsoft.com> Cc: Laura Atkins <la...@wordtothewise.com>; Anne P. Mitchell, Esq. <amitch...@isipp.com>; mailop@mailop.org Subject: Re: [mailop] Do we need a new list for reporting spam? (Was Re: Admin: This is not a place to report Spam. ) On 2017-04-10 17:15:38 (+0000), Michael Wise via mailop <mailop@mailop.org> wrote: >And a way to establish contacts automatically. What's wrong with the well-known abuse@ address? Or postmaster@? If abuse@ bounces, I try postmaster@. If that bounces, I'm not interested in receiving mail from that network. Quoth RFC 5321: "Any system that includes an SMTP server supporting mail relaying or delivery MUST support the reserved mailbox "postmaster" as a case- insensitive local name." "SMTP systems are expected to make every reasonable effort to accept mail directed to Postmaster from any other system on the Internet." I find this list quite helpful in prodding ESPs out of band when abuse@ seems to be defective in some way. If abuse@ isn't so much 'defective' as 'hopeless' ... tough? Philip -- Philip Paeps Senior Reality Engineer Ministry of Information _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
