mail archives

Bruce Dawson jbd at codemeta.com
Mon Jan 31 13:51:02 EST 2005


Kevin D. Clark wrote:

>Bruce Dawson <jbd at codemeta.com> writes:
>
>[snip]
>  
>
>>The problems with python2 have been resolved, and there is a later
>>version of mailman on that system. However, this has exposed a problem
>>with "moving" a list from one version of mailman to a later
>>version. After corrupting the mailman database while trying to move a
>>test list, I decided it couldn't be done in the time I had. I believe
>>I even sent a message to the -org list indicating this and soliciting
>>help. None came.
>>
>>See http://mail.gnhlug.org/mailman/private/gnhlug-org/2004-April/001009.html
>>

>>Unfortunately, I am not subscribed to this mailing list so I can't see
>>the message that you are referring to.  Maybe I'll try to subscribe sometime.
>>    
>>
I would encourage you (and anyone else) to subscribe to the -org list 
for discussions of "things most of the membership doesn't care about".

Here's the text of that message:

On a semi-related note, there are two versions of mailman on that
system. The GNHLUG lists (and others) are using 2.0.13. 2.1.4 is also on
that system and being used by some non-GNHLUG lists.=20

(The "switch" for the two versions is implemented in /etc/aliases).

If someone is brave/foolhardy enough, they can convert the GNHLUG lists
to the new version. But whoever does this has to issue a PLAN (to me at
least), giving step-by-step instructions (and explanation) of how they
intend to do it. Then either I'll do it, or I'll give su privs to the
designated individual

>[snip]
>  
>
>>By the way, could you please provide a link (within the archives) to
>>the message that had your scripts in it?
>>    
>>
>
>It took me a while to find this because...oh, never mind:
>
>http://mail.gnhlug.org/mailman/private/gnhlug-discuss/2005-January/009383.html
>
Ah Ha! I didn't see that (since it was related to a thread I was ignoring).

The first problem I see is that it can't be plugged into mailman without 
modifying mailman (one of those real-world problems involving system 
software upgrades).

Now, before you (or anyone else) goes off on a riposte indicating that 
its a simple matter of stripping off the email address before getting 
passed to mailman...

Mailman needs a valid address to verify that the poster is a list member.

The primary point of interface is in /etc/aliases:

    gnhlug-discuss:          "|/var/mailman/mail/wrapper post 
gnhlug-discuss"

Unfortunately, /var/mailman/mail/wrapper is a binary executable provided 
in the mailman distribution.

Now, after reading the source, one will discover that its mostly a 
"security splice" for some mailman python programs. It is these that 
your perl code has to be called from - probably in the archiving 
interface. Now the archiving interface is something that I have found 
very confusing - especially in the 2.0... version of mailman that we're 
using - so someone who knows better should feel free to correct me - but 
there are at least 4 places where the address is accessed in the archive 
interface - and no telling about pipermail.

So the bottom line is that mailman needs some modification, which I'm 
loathe to do unless its part of the distributed package.

>I'm investigating mail archive services.  Offers by various
>individuals to provide archive services are also welcomed.
>  
>
Thanks for taking up the ball on this.




More information about the gnhlug-discuss mailing list