I guess it depends on which domain the OP was trying to report, asalesforce.com<http://asalesforce.com> does exist and it seems a bit dodgy so it could be a typo, or could be the actual spammer.
From: mailop <[email protected]> On Behalf Of Frost The Fox via mailop Sent: Monday, April 3, 2023 2:50 PM To: Jay Hennigan <[email protected]> Cc: mailop <[email protected]> Subject: [EXT] - Re: [mailop] Salesforce abuse bounces Typo, or am I missing something? You've got asalesforce.com<http://asalesforce.com> instead of salesforce.com<http://salesforce.com> there, and indeed smtp.secureserver.net<http://smtp.secureserver.net> is the MX for that domain. Actual SF has Proofpoint MXs. On Mon, Apr 3, 2023 at 2:45 PM Jay Hennigan via mailop <[email protected]<mailto:[email protected]>> wrote: Trying to report spam from their network, got this: Reporting-MTA: dns; speedy.sb.west.net<http://speedy.sb.west.net> X-Postfix-Queue-ID: 4PqzpV4cYJz6N6gs X-Postfix-Sender: rfc822; [me] Arrival-Date: Mon, 3 Apr 2023 11:25:22 -0700 (PDT) Final-Recipient: rfc822; [email protected]<mailto:[email protected]> Original-Recipient: rfc822;[email protected]<mailto:rfc822%[email protected]> Action: failed Status: 5.1.1 Remote-MTA: dns; smtp.secureserver.net<http://smtp.secureserver.net> Diagnostic-Code: smtp; 550 5.1.1 <[email protected]<mailto:[email protected]>> Recipient not found. <http://x.co/irbounce> -- Jay Hennigan - [email protected]<mailto:[email protected]> Network Engineering - CCIE #7880 503 897-8550 - WB6RDV _______________________________________________ mailop mailing list [email protected]<mailto:[email protected]> https://list.mailop.org/listinfo/mailop
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
