[Mailman-Users] Address matching behavior

2003-10-23 Thread Vijay G. Bharadwaj
Hi all,

I've been running a bunch of mailman lists for about two years now, and 
a couple of months ago I upgraded to version 2.1 from 2.0. Since the 
change, every message sent to any one of our members-only lists is being 
held for approval.

The problem appears to be a change in mailman's address matching 
behavior. Previously, if [EMAIL PROTECTED] was subscribed, email from 
[EMAIL PROTECTED] would be accepted as well. The new mailman, 
however, doesn't think [EMAIL PROTECTED] is a member, and so holds 
the message for approval.

This is a huge pain. Is there a way I can get back the old behavior? I 
searched all over google and Usenet, and it seems like no one else has 
commented on this before...

Thanks,

--
-Vijay


--
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] Address matching behavior

2003-10-23 Thread Richard Barrett
On Thursday, October 23, 2003, at 08:50  pm, Vijay G. Bharadwaj wrote:

Hi all,

I've been running a bunch of mailman lists for about two years now, 
and a couple of months ago I upgraded to version 2.1 from 2.0. Since 
the change, every message sent to any one of our members-only lists is 
being held for approval.

The problem appears to be a change in mailman's address matching 
behavior.
See:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg11701.html

Previously, if [EMAIL PROTECTED] was subscribed, email from 
[EMAIL PROTECTED] would be accepted as well. The new mailman, 
however, doesn't think [EMAIL PROTECTED] is a member, and so holds 
the message for approval.

This is a huge pain. Is there a way I can get back the old behavior? I 
searched all over google and Usenet, and it seems like no one else has 
commented on this before...

Thanks,

--
-Vijay
---
Richard Barrett   http://www.openinfo.co.uk
--
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] Address matching behavior

2003-10-23 Thread Ed Wilts
On Thu, Oct 23, 2003 at 03:50:44PM -0400, Vijay G. Bharadwaj wrote:
 I've been running a bunch of mailman lists for about two years now, and 
 a couple of months ago I upgraded to version 2.1 from 2.0. Since the 
 change, every message sent to any one of our members-only lists is being 
 held for approval.
 
 The problem appears to be a change in mailman's address matching 
 behavior. Previously, if [EMAIL PROTECTED] was subscribed, email from 
 [EMAIL PROTECTED] would be accepted as well. The new mailman, 
 however, doesn't think [EMAIL PROTECTED] is a member, and so holds 
 the message for approval.

I believe that this is the intended behavior.  You need to determine if
you want outgoing mail to be [EMAIL PROTECTED] or [EMAIL PROTECTED] -
you should not use both.  The 2 e-mail addresses are different, and I
think you need to fix the outgoing mail to masquerade
[EMAIL PROTECTED] to [EMAIL PROTECTED]

I would think the 2.0 behavior, as you specified, is a bug.  How would
you expect it to work if [EMAIL PROTECTED] and [EMAIL PROTECTED]
are different users?  From an outsider's point of view, the most
certainly are.  [EMAIL PROTECTED] is also different than
[EMAIL PROTECTED] - in some cases at my site, they are (root for example).

IMO, 2.1 is doing the right thing and you need to fix your outgoing mail
behavior.

-- 
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] Address matching behavior

2003-10-23 Thread Vijay G. Bharadwaj
Thanks for the replies.

I realize that adding the host name is not-so-desirable behavior (which 
is why you won't see hostnames in my outgoing email :)). It is, however, 
very common, and I don't have any control over the large number of users 
and mail servers that would need to be fixed in order for it to go away.

Ed - the 2.0 behavior was a config option, not a bug. I know that 
someone who controls a host can give themselves any username they want - 
this is just one of the many easy ways to forge a from address. However, 
most users don't do this, and many are either unable or not knowledgable 
enough to fix their clients or servers to canonicalize the outgoing 
address. As such, SMART_MATCH provided a useful service to some of us 
harrowed admins.

I think I will take a closer look at the membership adapter. It doesn't 
seem that hard to hack the functionality back in at first glance, and it 
sure beats having to nag at all the (mostly external) users who have the 
problem.

--
-Vijay


--
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