[ mailman-Bugs-1449048 ] non-member post failuer

[SourceForge.net]

Bugs item #1449048, was opened at 2006-03-13 13:18
Message generated for change (Comment added) made by llbetts
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1449048&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Linda Betts (llbetts)
Assigned to: Nobody/Anonymous (nobody)
Summary: non-member post failuer

Initial Comment:
Running Mailman 2.1.5 on Red Hat Linux 3.  Have list
configured to discard posts from non-members. 
Non-member sent in auto reply containing my address has
changed information that actually came from the new
address which was not registered.  List server sent
this auto-reply from non-member to the list.

Can't find similar problem reported or bug fix.

Output list configuration, pertinent info below:

# legal values are:
#    0 = "Accept"
#    1 = "Hold"
#    2 = "Reject"
#    3 = "Discard"
generic_nonmember_action = 3

Please advise.

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

>Comment By: Linda Betts (llbetts)
Date: 2006-03-13 20:10

Message:
Logged In: YES 
user_id=1063268

According to the output from config_list these 2 items are
set to:

accept_these_nonmembers = []
generic_nonmember_action = 3

I have attached the complete output from the config_list output.

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-03-13 19:31

Message:
Logged In: YES 
user_id=1123998

Is there anything in accept_these_nonmembers?

What is generic_nonmember_action?

If one or the other of these settings don't explain the
issue, then I'm afraid that without specific information as
to the headers of the post as received by Mailman and
specific list configuration information, we aren't going to
be able to understand what happened or if there is a bug
involved.

In any case, I am moving this from 'patches' to 'bugs' for
the interim as it clearly isn't a patch.


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

Comment By: Linda Betts (llbetts)
Date: 2006-03-13 18:26

Message:
Logged In: YES 
user_id=1063268

Although I agree with the comments that if any of the
headers contains the real members email address it will be
processed as a member, the real member is moderated and all
posts from moderated members are configured to be discarded.
 Therefore, in this configuration it should not matter who
sent the reply. Only the list owner is allowed to send
messages to the list and the reply should have been discarded.

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

Comment By: Mark Sapiro (msapiro)
Date: 2006-03-13 16:00

Message:
Logged In: YES 
user_id=1123998

In a default installation, post will be determined to be
from a list member if the envelope sender or any of the
From:, Reply-To: or Sender: headers contain a member address.

You could send an off list message to the old address and
inspect the returned message to see if Return-Path: (the
envelope sender), From:, Reply-To: or Sender: contain the
old address. If so, accepting this would be expected behavior.

Note that in a situation like this, it may be preferable to
discuss the issue on mailman-users at python.org before
submitting a bug report.

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

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