230 likes | 343 Views
> Many of my users send mail to my lists from Netscape. Unfortunately,. > it seems to munge out the hostname from the Sender: header, so that. > "nick@zork.net" would have a "Sender: nick" header. Mailman seems to. > pay undue attention to this header when deciding if the user is.
E N D
> Many of my users send mail to my lists from Netscape. Unfortunately,
> it seems to munge out the hostname from the Sender: header, so that
> "nick@zork.net" would have a "Sender: nick" header. Mailman seems to
> pay undue attention to this header when deciding if the user is
> authorized to post or not. Mailman also won't let me add in any
> address that doesn't have an at sign to the approved posters box in
> the privacy options. As a matter of fact, once it sees an incomplete
This was reported back in August and added to the Jitterbug bug
The only solution that I know of is to preprocess the list with
a procmail recipe that in turn removes the existing Sender: header
if it matches certain criteria, then replaces it with the next
It's a hack, but it may help until this gets fixed. (For what it's
worth, Netscape isn't exactly doing RFC-compliant things either
I have no idea about your question regarding forwarded messages and