On Fri, Dec 9, 2022 at 9:49 AM Grant Taylor <[email protected]> wrote: > > A slightly less benign case was years ago when I was dealing with an AOL > sender and AOL had no interest in doing anything to stop the sender. So > I configured a forwarder to take messages from the sender, add them as > an attachment to a message that cited the AOL internal case number to > AOL's postmaster. AOL's postmaster had no hand in requesting the forward. > > I consider both to be legitimate, non-spam, forms of forwarding in which > the recipient had no hand in the forward being put in place and likely > couldn't easily change it if they wanted to.
Though your messages might be annoying, each would effectively be a response solicited by an unwanted message being received, resulting in you sending a report to AOL about it. I probably wouldn't call it forwarded if a person sending a spam report (or ISP feedback loop reports) doesn't need to preserve the authentication results of the original sender to be sent. Wrap it up in an attachment, quote in the body, whatever, but the messages (spam or unwanted mail reports) were all clearly coming from you, as far as email authentication goes. You're more likely a sender, not a forwarder. Cheers, Al Iverson -- Al Iverson / Deliverability blogging at www.spamresource.com Subscribe to the weekly newsletter at wombatmail.com/sr.cgi DNS Tools at xnnd.com / (312) 725-0130 / Chicago (Central Time) _______________________________________________ Ietf-dkim mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-dkim
