-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason R. Mastaler wrote: > "Robert P. Thille" <[EMAIL PROTECTED]> writes: > >>> As an aside, I notice that TMDA's tmda-sendmail script (intended as a >>> drop-in replacement for /usr/sbin/sendmail) completely ignores the -f >>> option... >> That seems broken. If you're going to accept a bounce address over SMTP >> (the envelope sender), or via the command line, then throw it away, how >> can the bounces get back to their intended sender? Is it intended >> simply as an anti-forgery mechanism? > > There was a specific and good reason why I chose to just 'pass' on > tmda-sendmail -f, but I can't recall what it is at the moment. Keep > in mind though that it's been that way for 5 years and no one has had > a problem with it, so I don't think it's a bug.
I'm guessing it's because tmda-sendmail is mostly used by system users, and therefore it's easy to determine what the appropriate value is? Alternatively, perhaps it's because the envelope sender is typically(?) (or just often) overridden to e.g. a dated address in the outgoing filter, so the feature wasn't necessary. Or, perhaps, it's just to disallow system users from forging mail as if it was from another system user? Many possibilities:-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWkDfhk3bo0lNTrURApJWAKCAWjAfkW+ywpG76BB8yLxURd+MYACfagYC ouHJPUBcE9Ll6rGUvaW6vGM= =RSd1 -----END PGP SIGNATURE----- _________________________________________________ tmda-workers mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-workers
