At 12/15/2004 03:13 AM -0500, Matt Kettler wrote:
>Of course, there's other arguments too.. Redirectors, forwarding services, etc, but these have their solutions. (Hint: SPF at each stage, and when you remail, use a return path that points at your own servers like a mailing list does. Poof, problem solved.)
Poof, problem created. What am I supposed to do with a message that gets returned to my "remailer" address? Keep track of where it came from just in case? For how long? No mail server I know of does this currently, nor is there any formal spec, RFC, etc. that establishes a precedent. I'm not trying to pick an argument, nor will I respond to one on-list. This discussion has been hacked to death on Postfix list and probably many others.
No need for storage, just use a return path that encodes the original sender in the user name. Lots of legitimate newsletters use this technique so they can unsubscribe bounces.
Heck, even THIS LIST does it for the recipient address: Return-Path: <[EMAIL PROTECTED]>
It would be straightforward to use the same trick to encode the actual return path based on the original sender.
Yes, this does mean implementing it, but no it doesn't create the storage system you suggest, and there's plenty of precedent for this kind of encoding technique.
