[ mailman-Bugs-1667570 ] RegExp not working in 2.1.5

SourceForge.net noreply at sourceforge.net
Sat Feb 24 03:48:43 CET 2007


Bugs item #1667570, was opened at 2007-02-23 16:07
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: security/privacy
Group: 2.1 (stable)
Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Michael O (qchrontech)
Assigned to: Nobody/Anonymous (nobody)
Summary: RegExp not working in 2.1.5

Initial Comment:
Under "accept_these_nonmembers (privacy): List of non-member addresses whose postings should be automatically accepted." I have the following RegExp's and I still continue to receive notices as the admin to approve the email from addresses listed below. I tested the RegExp to make sure that the e-mail addresses are successfully matched and they are. I believe in 2.1.2 this was working fine with the same RegExp. 

List of non-member addresses whose postings should be automatically accepted.
^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$
^[^@]+@(.*\.)?nyc\.gov$

post from emeeks at comptroller.nyc.gov requires approval
post from ahutchi at comptroller.nyc.gov requires approval
post from jsimmon at comptroller.nyc.gov requires approval

I saw no previous bug reports on this and am unsure if this is fixed in 2.1.9 so I submitted it.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-02-23 18:48

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Re: your followup.

You have several choices, but adding ^[^@]+@(.*\.)?nyc\.gov$ to acceptable
aliases isn't one of them.

The post was held because it wasn't explicitly addressed To: (or Cc:) the
list. I.e. the canonical list posting address, say listname at example.com,
was not in To: or Cc:. Maybe it was a Bcc: to the list. Maybe the post was
addressed to listname at mail.example.com.

If the former, and you can't convince to poster to explicitly address the
list, then you have to turn off require_explicit_destination. If the
latter, you can add listname at mail.example.com to acceptable aliases.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-02-23 18:40

Message:
Logged In: YES 
user_id=1123998
Originator: NO

So the message is held for implicit destination which means two things:

1) It passed your accept_these_nonmembers test.

2) It was held because Privacy Options...->Recipient
filters->require_explicit_destination is Yes and the list posting address
or another address in the acceptable_aliases list was not found in any To:
or Cc: header of the post.

----------------------------------------------------------------------

Comment By: Michael O (qchrontech)
Date: 2007-02-23 18:39

Message:
Logged In: YES 
user_id=1631912
Originator: YES

ok so i looked this up. Does this mean I should turn off
require_explicit_destination OR should i add ^[^@]+@(.*\.)?nyc\.gov$ to
the acceptable_aliases?

----------------------------------------------------------------------

Comment By: Michael O (qchrontech)
Date: 2007-02-23 18:30

Message:
Logged In: YES 
user_id=1631912
Originator: YES

Vetta log
Feb 13 12:57:25 2007 (13626) Editors post from emeeks at comptroller.nyc.gov
held,
message-id=<9634B41B9ED66B44AAC9674F95755AAB035518AE at smex03.comptroller.nycnet>:
Message has implicit destination


----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-02-23 17:03

Message:
Logged In: YES 
user_id=1123998
Originator: NO

It works for me in current mailman, and the only changes to
Mailman/Handlers/Moderate since 2.1.3 have to do with allowing a list
specified nonmember_rejection_notice. The only other change since 2.1.2
was to accept posts from the news->mail gateway.

Are you sure these posts aren't being held for some other reason. What
does Mailman's vette log give as the hold reason.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&group_id=103


More information about the Mailman-coders mailing list