X-DMARC-Info: pass=pass; dmarc-policy=reject; s=r1; d=r1; pdomain=mydomain.org
(Where "mydomain.org" is my actual personal domain from which I replied when I had HME setup to forward to [email protected].) message size 67539976 exceeds size limit 28311552 of
server mx01.mail.icloud.com[17.57.154.33]
I tried various approaches. They all bounce at the edge: Reporting-MTA: dns; mailfout.phl.internal
X-Postfix-Queue-ID: 13B6AEC00E7
X-Postfix-Sender: rfc822; [email protected]
Arrival-Date: Thu, 2 Jul 2026 18:28:38 -0400 (EDT)
Final-Recipient: rfc822; [email protected]
Original-Recipient: rfc822;[email protected]
Action: failed
Status: 5.0.0
Remote-MTA: dns; mx02.mail.icloud.com
Diagnostic-Code: smtp; 550 We are unable to send your email as one or more of its attachments may be corrupted or may contain malicious content.
So the theory now has to be that possible to sneak something past the edge SMTP server, past the point where the system rewrites the HME address, then bouncing, and in sending the bounce, failing to properly rewrite something on the way back out, thus disclosing the real address. I remain skeptical that's what's happening.