[Mailman-Users] Multiple users' properties set/unset

2009-05-13 Thread Denis Yurashkou
Hello All! Do you know any way to set/unset properties of subscribers such as Receive as text? We have 2500+ users... and... you understand... ) -- with Best regards, Denis A. Yurashkou -- Mailman-Users mailing list Mailman-Users@python.org

Re: [Mailman-Users] Patch for use of Postfix VERP support

2009-05-13 Thread Fil
Hi, the VERP system is good to detect bounces, but it has issues when lots of subscribers are on the same server: (delivery temporarily suspended: connect to smtp..xxx.xxx[x]: Connection timed out) (host mx01..xxx[x] refused to talk to me: 421 4.3.2 Connection rate limit

Re: [Mailman-Users] Multiple users' properties set/unset

2009-05-13 Thread Mark Sapiro
Denis Yurashkou wrote: Do you know any way to set/unset properties of subscribers such as Receive as text? We have 2500+ users... and... you understand... ) Go to http://www.msapiro.net/scripts/ and look at the scripts set_*.py for examples. In particular, the script set_mod.py can be changed

Re: [Mailman-Users] Mailing list + message filter problem

2009-05-13 Thread Mark Sapiro
Filipe Daros wrote: For example: My main e-mail address is t...@test.com and I created a list: l...@test.com. I also created a message filter that forwards any e-mail sent to t...@test.com and has the word hello on it's subject to the list l...@test.com. I tried changing

Re: [Mailman-Users] Patch for use of Postfix VERP support

2009-05-13 Thread Brad Knowles
Fil wrote: As the emails are sent one by one the connection rate to these systems can get very high, and we get delayed. Ideas? Having postfix do your VERP'ing for you isn't going to help. Mailman needs to know what VERP was used going out, so that it can match that when the bounce comes

Re: [Mailman-Users] Mailing list + message filter problem

2009-05-13 Thread Mark Sapiro
Filipe Zanluca DarĂ³s wrote: The address t...@test.com is not a list. It is just a pop3 email account. They do appear in the archives at l...@test.com! Does 'l...@test.com' have any eligible recipients (non-digest members with delivery enabled and in some cases not an explicit addressee and