Mailman 3 February 2002 - Mailman-Developers

Re: [Mailman-Developers] Protecting email addresses from spam harvesters
by Dan Mick Feb. 27, 2002

Feb. 27, 2002

> On Wed, Feb 27, 2002 at 10:42:36AM -0800, Dan Mick wrote: > > > On Tue, Feb 26, 2002 at 05:07:41PM -0800, Marc MERLIN wrote: > > > > Not that it is a big deal to me, but out of curiosity: what part > > > > of mailman cares that it's a list and not a mail alias? > > > > > > The *user*, when the list machinery breaks completely, and there's > > > no obvious target address to complain to. > > > > While this might be a good point, it's wrong and unhelpful to Marc's > > question. > > Well, either I have misunderstood Barry these last 48 hours, or you > have. We're talking about the *server* admin address. Right. And currently that admin address is "mailman-admin" or "mailman-owner", and both are tied to a list. Marc asked what about the Mailman **SOFTWARE** cares that it's a list. I answered him, correctly. > > IIRC, Marc, there's a bunch of stuff that does things like "get > > the Owner address for the list named mm_cfg.<site-list-name>". Not > > that that couldn't be found and changed, but...that's how it works > > currently. Also, that way bounce handling happens for those sorts of > > notification messages in the "normal" way. > > Yup, we're talking about different things. Only when you bring up the user, which has no bearing on the question *at all*.

1 0

Re: [Mailman-Developers] Protecting email addresses from spam harvesters
by Dan Mick Feb. 27, 2002

Feb. 27, 2002

> At 10:55 -0800 2/27/2002, Dan Mick wrote: > >"wrong" was misstated; what I meant to say was "the user is not > >part of Mailman". > > But the user is part of the mailing list system. Usually the most > troublesome part. That's as may be, but Marc asked a specific question that had nothing at all to do with the user part of the holistic system. The weather is part of everything, but discussing it doesn't really solve specific software problems.

3 3

Re: [Mailman-Developers] Protecting email addresses from spam harvesters
by Dan Mick Feb. 27, 2002

Feb. 27, 2002

> > > Not that it is a big deal to me, but out of curiosity: what part of mailman > > > cares that it's a list and not a mail alias? > > > > The *user*, when the list machinery breaks completely, and there's no > > obvious target address to complain to. > > While this might be a good point, it's wrong and unhelpful to Marc's > question. "wrong" was misstated; what I meant to say was "the user is not part of Mailman".

3 2

Re: [Mailman-Developers] Can't approve/discard/reject subscriptions in 2.1a4
by Joel Lord Feb. 27, 2002

Feb. 27, 2002

My experience is that this is more than just subscribtion requests - any moderator request at all will maintain like this. I now have three domains worth of the daily nags hitting me - two of them were subscription requests, two moderated posts (the posts went through, but the daily nag doesn't get cleared). I posted a bug report on sourceforge for this one... Brett Delmage wrote: > > Problem: I can't clear pending subscription requests by processing them. > I applied the patch to 2.1a4 below but it doesn't work for me. > > The steps to duplicate the problem are listed below and are very simple. > > I created a new list. > > I subscribed to the list using email, not the web form, using the list > defaults. The subscription was activated without incident. > > Using Konquerer (2.2.1) as my browser, I modified the subcribe_policy to > "Require approval" then subscribed to it using a different email address. > > I received the "Your subscription request has been forwarded to the list > administrator" message as expected, as well as the list-owner > notification. > > I went to the Administrative requests for mailing list: form > and confirmed that the pending subscribe request was shown. > > I selected the Discard radio button end entered a reason, then the submit > button. > > I confirmed that the rejection notice was mailed to the subscriber. > > However the subscriber was still shown as a subscription request. > > I tried resubmitting the form with the Approve radio button selected. The > subscriber was sent a welcome message, but still appeared on the form as a > pending subscription request. > > I selected the Reject radio button end entered a reason, then the submit > button. The subscriber (supposedly already subscribed!) was mailed a > rejection notice. And still appeared on the form as a pending request. > Some users just won't go away ;-) > > If left in this state, the daily oustanding moderations nag is mailed to > the list owner. > > I've looked at the code but am just learning python (part of my reason for > using mailman, I figured it was a great 'real world' project to help me > learn python.) But I couldn't see the problem. Maybe in a month or two... > > I hope the steps to reproduce the problem are helpful. Really, you can't > help but encounter it. > > Thanks to all those working on Mailman. It's a really impressive list > manager despite this bug, which doesn't affect the actual list operation > in any way. > -- Joel Lord Systems Architect Information Management Group

1 0

System to tie Hypermail archiving to Mailman
by Ben Gertzfield Feb. 27, 2002

Feb. 27, 2002

Here's a simple system I whipped up to automatically generate Hypermail configuration files based on each Mailman list's preferences and a few template files. The default template files I supply are for Japanese, but you can just remove the iso-2022-jp related lines and the Japanese comments from the html templates if you don't need that. http://nausicaa.interq.or.jp/mailman/hypermail-conf/ The meat is in hypermail-conf, a script to be run occasionally from cron to generate the per-list config files and create or rename hypermail archives for lists that do/don't want archiving. The do-hypermail script simply loops over all config files in /etc/hypermail/ created by hypermail-conf and runs hypermail on them. hypermail-conf.cron is an example crontab to run these. Comments, complaints, etc. are all appreciated. Ben -- Brought to you by the letters W and H and the number 12. "What's green and sits in the corner? ... A naughty frog!" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/

1 0

At least some of my problems...
by Dan Mick Feb. 27, 2002

Feb. 27, 2002

....with messages that get corrupted in an I18N-ish way, are due to the fact that I'd written a Handler module to reject messages held for ImplicitDestination reasons (because I was tired of them). Um...but I didn't I18N-ize it. Oops. Sorry Ben, and thanks for the help. :)

1 0

Can't approve/discard/reject subscriptions in 2.1a4
by Brett Delmage Feb. 27, 2002

Feb. 27, 2002

Problem: I can't clear pending subscription requests by processing them. I applied the patch to 2.1a4 below but it doesn't work for me. The steps to duplicate the problem are listed below and are very simple. I created a new list. I subscribed to the list using email, not the web form, using the list defaults. The subscription was activated without incident. Using Konquerer (2.2.1) as my browser, I modified the subcribe_policy to "Require approval" then subscribed to it using a different email address. I received the "Your subscription request has been forwarded to the list administrator" message as expected, as well as the list-owner notification. I went to the Administrative requests for mailing list: form and confirmed that the pending subscribe request was shown. I selected the Discard radio button end entered a reason, then the submit button. I confirmed that the rejection notice was mailed to the subscriber. However the subscriber was still shown as a subscription request. I tried resubmitting the form with the Approve radio button selected. The subscriber was sent a welcome message, but still appeared on the form as a pending subscription request. I selected the Reject radio button end entered a reason, then the submit button. The subscriber (supposedly already subscribed!) was mailed a rejection notice. And still appeared on the form as a pending request. Some users just won't go away ;-) If left in this state, the daily oustanding moderations nag is mailed to the list owner. I've looked at the code but am just learning python (part of my reason for using mailman, I figured it was a great 'real world' project to help me learn python.) But I couldn't see the problem. Maybe in a month or two... I hope the steps to reproduce the problem are helpful. Really, you can't help but encounter it. Thanks to all those working on Mailman. It's a really impressive list manager despite this bug, which doesn't affect the actual list operation in any way. Brett ------------------------------------------------------ On Thu, 24 Jan 2002, Les Niles wrote: > (Apologies if this has already been reported. I don't remember > it.) Approval of pending subscriptions via the admindb web page is > ignored in 2.1a4. Here's a patch that fixes this. > > ------------------------------------------------------------- > *** Mailman/Cgi/admindb.py.~1~ Sun Jan 6 23:04:02 2002 > --- Mailman/Cgi/admindb.py Thu Jan 24 21:56:59 2002 > *************** > *** 630,635 **** > --- 630,636 ---- > except ValueError: > continue > if v not in (mm_cfg.DEFER, mm_cfg.APPROVE, > + mm_cfg.SUBSCRIBE, mm_cfg.UNSUBSCRIBE, > mm_cfg.REJECT, mm_cfg.DISCARD): > continue > # Get the action comment and reasons if present. > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers >

1 0

Can't approve subscriptions in 2.1a4
by Les Niles Feb. 27, 2002

Feb. 27, 2002

(Apologies if this has already been reported. I don't remember it.) Approval of pending subscriptions via the admindb web page is ignored in 2.1a4. Here's a patch that fixes this. ------------------------------------------------------------- *** Mailman/Cgi/admindb.py.~1~ Sun Jan 6 23:04:02 2002 --- Mailman/Cgi/admindb.py Thu Jan 24 21:56:59 2002 *************** *** 630,635 **** --- 630,636 ---- except ValueError: continue if v not in (mm_cfg.DEFER, mm_cfg.APPROVE, + mm_cfg.SUBSCRIBE, mm_cfg.UNSUBSCRIBE, mm_cfg.REJECT, mm_cfg.DISCARD): continue # Get the action comment and reasons if present.

2 1

Re: [Mailman-Developers] Can't get VERP to do much
by Dan Mick Feb. 26, 2002

Feb. 26, 2002

> On Mon, Feb 25, 2002 at 02:25:14PM -0800, Dan Mick wrote: > > > > > File "/var/local/mailman/Mailman/Queue/BounceRunner.py", line 112, in > > __verpbounce > > > if bmailbox <> mo.group('bounces'): > > > IndexError: no such group > > > > Are you sure Defaults.py is up-to-date? Specifically, > > VERP_FORMAT and VERP_REGEXP? > > root@gandalf:/var/local/mailman/Mailman# grep VERP_ mm_cfg.py > VERP_FORMAT = '%(bounces)s+%(mailbox)s=%(host)s' > VERP_REGEXP = r'^[^+]+?\+(?P<mailbox>[^=]+)=(?P<host>[^@]+)@.*$' > VERP_PASSWORD_REMINDERS = 1 > VERP_PERSONALIZED_DELIVERIES = 1 > VERP_DELIVERY_INTERVAL = 1 > > I left the defaults Those aren't current. # Note that your MTA /must/ be configured to deliver such an addressed message # to mylist-bounces! VERP_FORMAT = '%(bounces)s+%(mailbox)s=%(host)s' # The second describes a regular expression to unambiguously decode such an # address, which will be placed in the To: header of the bounce message by the # bouncing MTA. Getting this right is critical -- and tricky. Learn your # Python regular expressions. It must define exactly three named groups, # bounces, mailbox and host, with the same definition as above. It will be # compiled case-insensitively. VERP_REGEXP = r'^(?P<bounces>[^+]+?)\+(?P<mailbox>[^=]+)=(?P<host>[^@]+)@.*$'

2 1

More building the snapshot....
by Ron Jarrell Feb. 26, 2002

Feb. 26, 2002

Mailman/pythonlib/Makefile needs to get registered, so the cvs will realize it can delete it, and the pythonlib tree..

2 2