Re: [Mailman-Users] Mm_cfg.py not setting attribute

2016-05-23 Thread Mark Sapiro 
On 05/23/2016 05:24 PM, Beu, Ed (DOA) wrote:
> 
> We currently have two instances of Mailman running for test purposes. The 
> newlist command along with a customized mm_cfg.py file is producing different 
> results on the two systems.
> 
> Configurations are as follows on these two test systems.
> 
> T1
> Solaris 10
> Mailman 2.1.20 (csw package)
> 
> T2
> CentOS 6.7 (Final)
> Mailman 2.1.12 (yum package)
> 
> On the T1 system I am adding the following statement to the mm_cfg.py file:
> DEFAULT_RESPOND_TO_POST_REQUESTS = No
> 
> Then, when I run "./newlist -q listname 
> my.em...@domain.com 12345678" the list setting is 
> as desired (respond_to_post_request = No).
> 
> On the T2 system using the same scenario above, the "respond_to_post_request" 
> attribute does not change from the Defaults.py setting of Yes.


It should if you spelled it correctly.


> On the T2 system I have tried changing the attribute from  
> DEFAULT_RESPOND_TO_POST_REQUESTS to just RESPOND_TO_POST_REQUESTS, changed No 
> to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A number of 
> combinations, and none work on the CentOS machine.


No, no, 0 and False are all essentially equivalent in mm_cfg.py.

Changing the name is the same as commenting it or leaving it out. Every
setting that Mailman references is defined in Defaults.py. Anything you
set in mm_cfg.py that is not a setting mentioned in Defaults.py is ignored.


> Do you have any suggestions or recommendations? Our goal is to use the CentOS 
> system for production, so getting this worked out will be very helpful.


Exactly what mm_cfg.py file are you editing on CentOS. I *think* the
CentOS package has an mm_cfg.py in /etc/mailman and there is a symlink
from /usr/lib/mailman/Mailman/mm_cfg.py to /etc/mailman/mm_cfg.py, but I
may be mistaken about that which is why you should see the FAQ article
at .

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman suddenly passing through spam from the -bounces addresses

2016-05-23 Thread Mark Sapiro 
On 05/23/2016 01:57 PM, Rusty Newton wrote:
> 
> Recently I started receiving a lot of spam on the mailman-bounces@
> addresses where the From address no longer contains the
> mailman-bounces@ address and instead contains the spammer's address.
> 
> In this case the spam doesn't look like bounce traffic. I'm wondering
> if someone can help me identify why mailman might let it through? From
> reading documentation and the mailman mail archives I get the
> impression that it should be discarding this traffic. However I can't
> identify why it isn't discarding this non-bounce traffic.
> 
> Here is one example of the spam that comes to the owners addresses via
> mailman-bounces:
> 
> http://pastebin.com/u2HyNLw6
>
> The list in question has all three bounce notification options set to *no*.
> 
> That is:
> 
> bounce_unrecognized_goes_to_list_owner
> bounce_notify_owner_on_disable
> bounce_notify_owner_on_removal
> 
> With these three options disabled - should I expect mailman to relay
> spam like this to the list owners through mailman-bounces@ ?


Not unless the mailman-bounces address is set to deliver two 'owner'
instead of 'bounces. Is it?


> Is there a way to tell mailman to not send anything from mailman-bounces?


If you mean not to send anything with envelope from a listname-bounces
address, No.

If you mean not to forward or relay any mail sent to a listname-bounces
address, the settings you have should do it.


> Preferably I'd like to have mailman only pass through legitimate
> bounce messages. If that isn't possible then I'd like to find out how
> to disable the traffic from mailman-bounces completely.
> 
> If I haven't provided enough information, let me know and I'll do my
> best to get it for you. Thanks in advance.


I would like to see what's in Mailman's 'bounce' log from around Tue, 19
Apr 2016 11:57:42 -0700 (PDT). I would also like to see what's in the
MTA log from the arrival of the original to the delivery if the message
to you.

That may not be necessary. Upon closer inspection of the message in the
pastebin, it looks most like a message which was sent to the list-owner
address. You could check your MTA logs and find the incoming message. I
expect you'll find the envelope was to the list-owner address.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] accept_these_nonmembers and Reg Expression

2016-05-23 Thread Mark Sapiro 
On 05/23/2016 05:57 AM, Franck Aerts wrote:
> 
> I added a regular expression to accept_these_nonmembers which goes : 
> 
> ^…@domain\.com$

I'm not sure exactly what you put for this one, but in your email, the
three dots is an elipsis character which won't match any email address.


> and 
> ^.*@asana\.com$


This should match any local part @asana\.com.

I typically use '^.*[@.]asana\.com$' to match x...@subdomain.asana.com as
well as x...@asana.com, but you may not want that.


> but with no success : the emails are still moderated. 


What actually is the first regexp? For what reason are the messages
held? What is the sender of the held message shown in the admindb interface


> Is there an option I should change somewhere that overrule the settings in « 
> accept_these_nonmembers » ??


No.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mm_cfg.py not setting attribute

2016-05-23 Thread Beu, Ed (DOA) 
Hi,

We currently have two instances of Mailman running for test purposes. The 
newlist command along with a customized mm_cfg.py file is producing different 
results on the two systems.

Configurations are as follows on these two test systems.

T1
Solaris 10
Mailman 2.1.20 (csw package)

T2
CentOS 6.7 (Final)
Mailman 2.1.12 (yum package)

On the T1 system I am adding the following statement to the mm_cfg.py file:
DEFAULT_RESPOND_TO_POST_REQUESTS = No

Then, when I run "./newlist -q listname 
my.em...@domain.com 12345678" the list setting is 
as desired (respond_to_post_request = No).

On the T2 system using the same scenario above, the "respond_to_post_request" 
attribute does not change from the Defaults.py setting of Yes.

On the T2 system I have tried changing the attribute from  
DEFAULT_RESPOND_TO_POST_REQUESTS to just RESPOND_TO_POST_REQUESTS, changed No 
to Zero (0) and tried DEFAULT_RESPOND_TO_POST_REQUESTS = 0. A number of 
combinations, and none work on the CentOS machine.

Do you have any suggestions or recommendations? Our goal is to use the CentOS 
system for production, so getting this worked out will be very helpful.

Thx, Ed



Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman suddenly passing through spam from the -bounces addresses

2016-05-23 Thread Rusty Newton 
Hi!

New to the list! I'm the community support manager at the Asterisk project.

We've used mailman for ages and we are on 2.1.14 at the moment. I
rarely get too deep with mailman other than the administration
interface. It mostly works and we don't touch much underneath.

Recently I started receiving a lot of spam on the mailman-bounces@
addresses where the From address no longer contains the
mailman-bounces@ address and instead contains the spammer's address.

In this case the spam doesn't look like bounce traffic. I'm wondering
if someone can help me identify why mailman might let it through? From
reading documentation and the mailman mail archives I get the
impression that it should be discarding this traffic. However I can't
identify why it isn't discarding this non-bounce traffic.

Here is one example of the spam that comes to the owners addresses via
mailman-bounces:

http://pastebin.com/u2HyNLw6

The list in question has all three bounce notification options set to *no*.

That is:

bounce_unrecognized_goes_to_list_owner
bounce_notify_owner_on_disable
bounce_notify_owner_on_removal

With these three options disabled - should I expect mailman to relay
spam like this to the list owners through mailman-bounces@ ?

Is there a way to tell mailman to not send anything from mailman-bounces?

Preferably I'd like to have mailman only pass through legitimate
bounce messages. If that isn't possible then I'd like to find out how
to disable the traffic from mailman-bounces completely.

If I haven't provided enough information, let me know and I'll do my
best to get it for you. Thanks in advance.

-- 
Rusty Newton
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] accept_these_nonmembers and Reg Expression

2016-05-23 Thread Franck Aerts 
Hello everyone,

I am sorry to bother you with this question, but even though the question has 
been asked on this list and a answer has been gaven, it doesn’t work for me.

I want any email coming from a particular domain to be accepted without 
moderation. 

I added a regular expression to accept_these_nonmembers which goes : 

^…@domain\.com$
and 
^.*@asana\.com$


but with no success : the emails are still moderated. 

Is there an option I should change somewhere that overrule the settings in « 
accept_these_nonmembers » ??

The reason i want to have to accept any email from that domain is that the « 
user » part of the email is a token that changes all the time.

Thanks in advance,

Franck
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org