[Mailman-Users] Confirmation logging

2013-07-02 Thread Stephen J. Turnbull
Kip Warner writes: > Apparently Mailman doesn't handle opt-in confirmations in a way that is > compliant with it. Specifically, it doesn't log new subscriptions or the > IP addresses of the confirmation. Is this correct? Each step of a subscription is logged. IP addresses of web requests are

Re: [Mailman-Users] Confirmation logging

2013-07-02 Thread Mark Sapiro
On 07/02/2013 04:14 PM, Kip Warner wrote: > Greetings, > > I'd like to setup a project announcement mailing list on my DreamHost > server using Mailman, however DreamHost has informed me that Mailman is > allegedly not compliant with their Anti-Spam policy. > >

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Mark Sapiro
On 07/02/2013 03:09 PM, Chris Nulk wrote: > > Thank you for the help. Hopefully a last question. In the > do_discard_globalban function, how can I send the discard message to > mailman list? Or should I? As it stands now, each list owner/admin > would be getting the message for their list. I

[Mailman-Users] Confirmation logging

2013-07-02 Thread Kip Warner
Greetings, I'd like to setup a project announcement mailing list on my DreamHost server using Mailman, however DreamHost has informed me that Mailman is allegedly not compliant with their Anti-Spam policy. Apparently Mailman doesn't handle opt-in

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Chris Nulk
On 7/2/2013 2:37 PM, Mark Sapiro wrote: If you raise some exception other than the Mailman.Errors exceptions DiscardMessage, HoldMessage or RejectMessage, it will be the same as if you didn't catch the exception, i.e., the exception will be logged in the 'error' log with a traceback and the mess

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Mark Sapiro
On 07/02/2013 01:49 PM, Chris Nulk wrote: > > On 7/2/2013 12:17 PM, Mark Sapiro wrote: >> On 07/02/2013 11:38 AM, Chris Nulk wrote: >>> except: >>> # unspecified error >>> # log it and continue with the next pipeline handler >>> syslog('error', >>>

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Chris Nulk
On 7/2/2013 12:17 PM, Mark Sapiro wrote: On 07/02/2013 11:38 AM, Chris Nulk wrote: I did forget about some of my other questions. I plan on writing another custom handler for a list-specific issue. Where would I look if I wanted to intercept messages related to subscribing, unsubscribing, an

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Mark Sapiro
On 07/02/2013 11:38 AM, Chris Nulk wrote: > > > I did forget about some of my other questions. I plan on writing > another custom handler for a list-specific issue. Where would I look if > I wanted to intercept messages related to subscribing, unsubscribing, > and options processing? These ar

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Chris Nulk
On 7/2/2013 10:16 AM, Mark Sapiro wrote: On 07/02/2013 08:48 AM, Chris Nulk wrote: You could change your code as follows: 1) Make the banlist global by putting # First, initialize the banlist banlist = [] ahead of def process(mlist, msg, msgdata): and remove that from the process() defini

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Mark Sapiro
On 07/02/2013 08:48 AM, Chris Nulk wrote: > On 7/1/2013 3:35 PM, Mark Sapiro wrote: >> On 7/1/2013 10:24 AM, Chris Nulk wrote: >>> >>> # Go through possible senders. Check if any of them are >>> # on the global ban list >>> for sender in msg.get_senders(): >>> if sender.

Re: [Mailman-Users] Writing a custom handler

2013-07-02 Thread Chris Nulk
Thank you Mark for your time. I went through and made the syslog change, removed the usenet bit, and correct my typing error. On 7/1/2013 3:35 PM, Mark Sapiro wrote: On 7/1/2013 10:24 AM, Chris Nulk wrote: Hello user, I am writing a custom handler to globally ban email address from sending