330 likes | 582 Views
> You know, it looks like a LOT of people have this error, from looking at my. > mailbox over the last month or so! I have some ideas about why that is. > Barry wrote that he couldn't reproduce it on his machine, so perhaps they.
E N D
> You know, it looks like a LOT of people have this error, from looking at my
> mailbox over the last month or so! I have some ideas about why that is.
> Barry wrote that he couldn't reproduce it on his machine, so perhaps they
> have turned it off in later versions... I am still on 8.8.7... Anyway, this
> is the Sendmail that comes on the RedHat distribution... I think at least a
It still happens in sendmail 8.9.3 for me, and yes, you are 100% right
> This is further explained on sendmail.org at the following URL:
I personally feel that it's a bug on sendmail's part; according to the
sendmail "bat" book, only aliases that use the 'include:' directive
have the envelope rewritten, yet it appears to happen with *any*
> If the default behavior is left alone, at the very least this info should
> make it into the documentation (under "Troubleshooting" in the "Why doesn't
> member_posting_only work?"). If you go to the trouble of instructing
> people how to turn off the envelope sender option, why not educate them
> I have removed all my owner-* aliases (actually, having learned my lesson
> from the listproc days, I never put them in) and envelope sender works fine.
I'm not contesting that it works for you -- just wanted to get that
clear first. :) However, I have had people send mail to owner-listname
in the past because it's sort of an unofficial standard. Usually they're
people who have heard about the list from somewhere else and want to know
how to subscribe, have a question about archives, or whatever.
I want to know why the sendmail folks are rewriting envelopes anyway... Sounds
like a perfectly acceptable candidate for a sendmail.cf flag (it's not like they
Sorry. I think I'm tired... I just hate making exceptions for software that