Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Mark Sapiro
On 01/16/2016 05:13 PM, Perry E. Metzger wrote: > On Sat, 16 Jan 2016 16:52:29 -0800 Mark Sapiro > wrote: >> >> Please provide some examples. If there is any discernable pattern, >> it might be blockable without impacting real subscribers. > > I don't have a lot of examples (haven't been saving t

Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Perry E. Metzger
On Sat, 16 Jan 2016 16:52:29 -0800 Mark Sapiro wrote: > On 01/16/2016 04:02 PM, Perry E. Metzger wrote: > > > > I have direct evidence that the asshats are now using "+" strings > > after the main address that are not strictly numeric. They seem to > > have responded to the simple ways of stoppin

Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Mark Sapiro
On 01/16/2016 04:52 PM, Mark Sapiro wrote: > > Based on the one above getting through, I wrote the script at > (mirrored at > ) to 'erase' an address from > all lists. Note, this script uses the Python argparse m

Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Mark Sapiro
On 01/16/2016 04:51 PM, Perry E. Metzger wrote: > > Oh, and by the way, the documentation for SUBSCRIBE_FORM_SECRET (such > as it is) does not mention that it needs to be set to a string. I > only figured that out when setting it to True and 1 both failed > spectacularly and reading the traceback.

Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Mark Sapiro
On 01/16/2016 04:02 PM, Perry E. Metzger wrote: > > I have direct evidence that the asshats are now using "+" strings > after the main address that are not strictly numeric. They seem to > have responded to the simple ways of stopping them. I haven't seen any like that yet. The regexp I use is ^

Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Perry E. Metzger
On Sat, 16 Jan 2016 19:02:58 -0500 "Perry E. Metzger" wrote: > On Thu, 14 Jan 2016 08:55:21 -0600 "Gibbs, David" > wrote: > > On 1/12/2016 11:54 AM, Mark Sapiro wrote: > > > > > There are threads on this in the archives of this list. See > > > threads containing the posts > > >

Re: [Mailman-Users] Handling bogus subscribe requests

2016-01-16 Thread Perry E. Metzger
On Thu, 14 Jan 2016 08:55:21 -0600 "Gibbs, David" wrote: > On 1/12/2016 11:54 AM, Mark Sapiro wrote: > > > There are threads on this in the archives of this list. See > > threads containing the posts > > > > I can confi

Re: [Mailman-Users] IOError reading list extension: [Errno 20] Not a directory

2016-01-16 Thread Mark Sapiro
On 01/15/2016 08:13 AM, Web Analysts wrote: > My mail server is delivering a post to mailman but it is not being > distributed. The mailman error log shows > > > > IOError reading list extension: [Errno 20] Not a directory: > '/usr/lib/mailman/archives/private/listname.mbox/listname.mbox/extend

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2016-01-16 Thread Mark Sapiro
On 01/16/2016 06:24 AM, Eva Isaksson wrote: > > To cut the long story short, the script worked without any problems. > Taking backups took more time than running the script and doing the > package upgrade. I'm glad the script worked for you. I have mentioned this issue to the Debian people who

[Mailman-Users] IOError reading list extension: [Errno 20] Not a directory

2016-01-16 Thread Web Analysts
My mail server is delivering a post to mailman but it is not being distributed. The mailman error log shows IOError reading list extension: [Errno 20] Not a directory: '/usr/lib/mailman/archives/private/listname.mbox/listname.mbox/extend.py' I have checked perms, the db and restarted mailma

Re: [Mailman-Users] Encoding problem with 2.15 to 2.18 upgrade with Finnish

2016-01-16 Thread Eva Isaksson
I did the 2.1.18 upgrade this weekend, after some weighing of the options. In the long run, using the Debian package is less work intensive, so in the end my choice was the utf-8 conversion. > The script is at (mirrored > at