Re: [Mailman-Users] Variations of email addresses
On Thu, Sep 18, 2003 at 02:22:13PM -0500, Rob Day wrote: Hi, My organization just made the switch from Majordomo to Mailman. I am most pleased with Mailman to say the least. I am, however, having one problem. A user will subscribe to the list with the address [EMAIL PROTECTED], but their address will actually be [EMAIL PROTECTED] Mail sent to the expanded address (some.name) will be received, but the person will be unable to post to the list because the message comes from [EMAIL PROTECTED] Does that make sense? No, this doesn't make sense. How are the users subscribing to the list? Via e-mail or web? It sounds to me like the user's MUA is misconfigured - either your e-mail address is [EMAIL PROTECTED] or it's [EMAIL PROTECTED] You can't have it both ways - mailman should correctly treat those as separate people since there is absolutely no way for it to know the difference. If you're subscribed with some.name, then post from some.name. If you want to allow posting from other e-mail addresses, then configure mailman so that non-list members are allowed to post. If you restrict posting to list members, then the client must be configured to post from some.name. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Variations of email addresses
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, September 18, 2003 3:06 PM To: Rob Day Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Variations of email addresses On Thu, Sep 18, 2003 at 02:22:13PM -0500, Rob Day wrote: Hi, My organization just made the switch from Majordomo to Mailman. I am most pleased with Mailman to say the least. I am, however, having one problem. A user will subscribe to the list with the address [EMAIL PROTECTED], but their address will actually be [EMAIL PROTECTED] Mail sent to the expanded address (some.name) will be received, but the person will be unable to post to the list because the message comes from [EMAIL PROTECTED] Does that make sense? No, this doesn't make sense. How are the users subscribing to the list? Via e-mail or web? It sounds to me like the user's MUA is misconfigured - either your e-mail address is [EMAIL PROTECTED] or it's [EMAIL PROTECTED] You can't have it both ways - mailman should correctly treat those as separate people since there is absolutely no way for it to know the difference. If you're subscribed with some.name, then post from some.name. If you want to allow posting from other e-mail addresses, then configure mailman so that non-list members are allowed to post. If you restrict posting to list members, then the client must be configured to post from some.name. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] -- Actually, it makes perfect sense. [EMAIL PROTECTED] is an alias. SuSE OpenExchange creates such aliases by default for users. The simple way around this (for the admin) is to explicitly allow [EMAIL PROTECTED] to post to the list. This way, you don't open the whole list up to spammers. You could also unsub some.user@ and then subscribe sname@ Hopefully, it would be a rare occasion that you'd have to do this. Mike -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Variations of email addresses
On Thu, Sep 18, 2003 at 03:58:59PM -0500, Mike Kercher wrote: Actually, it makes perfect sense. [EMAIL PROTECTED] is an alias. SuSE OpenExchange creates such aliases by default for users. The simple way around this (for the admin) is to explicitly allow [EMAIL PROTECTED] to post to the list. This way, you don't open the whole list up to spammers. You could also unsub some.user@ and then subscribe sname@ Hopefully, it would be a rare occasion that you'd have to do this. The proper approach to this is to rewrite the From address on the outbound address as well as aliasing the inbound. If the outbound e-mail is some.user@, then all will work properly. Allowing e-mail into the box to be consistently different than e-mail out of the box is a misconfiguration to me. There is no way for Mailman to know that the 2 addresses are equivalent unless somebody goes in there and manually updates the permissions list. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Variations of email addresses
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, September 18, 2003 6:19 PM To: Mike Kercher Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Variations of email addresses On Thu, Sep 18, 2003 at 03:58:59PM -0500, Mike Kercher wrote: Actually, it makes perfect sense. [EMAIL PROTECTED] is an alias. SuSE OpenExchange creates such aliases by default for users. The simple way around this (for the admin) is to explicitly allow [EMAIL PROTECTED] to post to the list. This way, you don't open the whole list up to spammers. You could also unsub some.user@ and then subscribe sname@ Hopefully, it would be a rare occasion that you'd have to do this. The proper approach to this is to rewrite the From address on the outbound address as well as aliasing the inbound.If the outbound e-mail is some.user@, then all will work properly. Allowing e-mail into the box to be consistently different than e-mail out of the box is a misconfiguration to me. There is no way for Mailman to know that the 2 addresses are equivalent unless somebody goes in there and manuallyupdates the permissions list. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] I disagree on your first point. I don't see it as being a misconfiguration. I see it a method of NOT exposing a username. I have many servers with email aliases that eventually get routed to me, but I don't have an email account anywhere named [EMAIL PROTECTED] That doesn't mean I can't reply to an email sent to that address...but any reply would not come from postmaster@ I do agree with your second statement...there is no way for Mailman to know, which is why I said to make one of the suggested changes above. Mike -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
