Hey there Fedex, You've got a problem with users on google phishing from your domain:
=== Feedback-Type: auth-failure Version: 1 X-Mailer: OpenDMARC-Filter/rel-opendmarc-1-4-2-268-ge0cbd49 Auth-Failure: dmarc Identity-Alignment: dkim,spf Authentication-Results: prime.gushi.org; dmarc=fail header.from=fedex.com Original-Envelope-Id: 6AA0Nn4d031320 Original-Mail-From: [email protected] Arrival-Date: Tue, 10 Nov 2026 00:23:51 +0000 (UTC) Delivery-Result: delivered Source-IP: 35.237.135.155 (155.135.237.35.bc.googleusercontent.com) Reported-Domain: fedex.com <http://fedex.com/> Maybe report it to google's famously responsive abuse@ box where it's super easy to reach a human who will swiftly act on it? === But also, Your _dmarc.fedex.com <http://dmarc.fedex.com/> TXT record is broken: From: <[email protected]> To: <[email protected]> ... Delivery has failed to these recipients or groups: [email protected]<mailto:[email protected]> The recipient's mailbox is full and can't accept messages now. Please try r= esending your message later, or contact the recipient directly. (The latter is what this email purports to do.) === Specifies an RUF= address, which means you want a report for *every* *single* *email* received, and bounces those reports when we send them. Hosted by microsoft who can't figure out that maybe they should do a lookup on a hosted domain's _dmarc record and perhaps apply special handling to internal dmarc RUA/RUF addresses (like, I dunno...bring it to an admin's attention, or not generate bounces, or don't apply usage limits). Instead, another case of "someone used some online guide to generate a _dmarc record and then forgot about it." -Dan Cranky Sysadmin _______________________________________________ mailop mailing list -- [email protected] To unsubscribe send an email to [email protected]
