Mailman 3 May 2004 - Mailman-Developers

Where to start Implement this?
by Martin Häcker 16 May '04

16 May '04

Hi there, Could you please give me some advice about where to start implement this? I want to create an option that allows my users to have the mailinglist set a reply-to header to itself in their e-mails. (Please no discussion about wether this is bad or not - I've read <http://www.unicom.com/pw/reply-to-harmful.html> and <http://www.metasystema.net/essays/reply-to.mhtml> and also had a look at the archive of the mailman-users list) Though I want it - and I want it so badly I'm going to implement it myself. As far as a quick investigation has shown I will need to add the preference in MemberAdoptor.py and some of it's subclasses (which?) and then change Decorator.py to write the Reply-To if the user whiches for it. Would this be the right way to do it? And is there any other place I need to change to make this work? Thanks a lot cu Martin -- dont.wanna.tell [ot]coder - hehe

4 8

suggestion for Full Customization [Mailman-Developers]
by James Ralston 16 May '04

16 May '04

Mailman 2.1.4, Mailman/Handlers/CookHeaders.py, line 138: # The To field normally contains the list posting address. However # when messages are fully personalized, that header will get # overwritten with the address of the recipient. We need to get the # posting address in one of the recipient headers or they won't be # able to reply back to the list. It's possible the posting address # was munged into the Reply-To header, but if not, we'll add it to a # Cc header. BAW: should we force it into a Reply-To header in the # above code? if mlist.personalize == 2 and mlist.reply_goes_to_list <> 1: # Watch out for existing Cc headers, merge, and remove dups. Note # that RFC 2822 says only zero or one Cc header is allowed. new = [] d = {} for pair in getaddresses(msg.get_all('cc', [])): add(pair) i18ndesc = uheader(mlist, mlist.description) add((str(i18ndesc), mlist.GetListEmail())) del msg['Cc'] msg['Cc'] = COMMASPACE.join([formataddr(pair) for pair in new]) Question: why was this done? If I have set the "personalize" option to "Full Personalization", a very likely reason why I have done so is because I don't *WANT* the recipient to reply back to the list--or, for that matter, even realize that the message was sent through a mailing list at all. I want the recipient to see an individual message that looked like it was sent *from* an individual person *to* an individual person. Adding the list address to the CC header perfectly defeats this. While I can address this locally simply by excising the above code snippet, I'd rather see this issue addressed upstream. Would it make sense to split the "Full Personalization" setting into its own option? Meaning, make the existing personalize Option a yes/no toggle, and create another option to specify how to customize the headers: - To: header is listname; recipient address does not appear (default) - To: header is recipient; CC: header is listname - To: header is recipient; listname does not appear If someone would be willing to double-check my Python code (and proofread my documentation), I'd be willing to implement a patch to perform the above split. Thoughts? -- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA

5 7

Changing member options via command line
by Felix Kipping 16 May '04

16 May '04

hello, i have to change the member options (Mail delivery, Set Digest Mode, Get MIME or Plain Text Digests?, Receive your own posts to the list?, Receive acknowledgement mail when you send mail to the list?) via the command line. i figured out that this is possible by using the withlist command and execute a own python programm. in the mailman faq i found the following programm to change the member password via withlist. --- from Mailman.Errors import NotAMemberError def changeuserpw(mlist, addr, newpasswd): try: mlist.setMemberPassword(addr, newpasswd) mlist.Save() except NotAMemberError: print 'No address matched:', addr --- i wanted to use this technique to change the above mentiones member options. i looked into the file /Mailman/Cgi/options.py and found the function call "setDeliveryStatus(user, newval)". i changed the programm for changing the password into the following. --- from Mailman.Errors import NotAMemberError def changeuseroptions(mlist, email, delivery): try: mlist.setDeliveryStatus(email, delivery) mlist.Save() except NotAMemberError: print 'No address matched:', addr ---- but this causes the following error when executing. --- Traceback (most recent call last): File "./withlist", line 275, in ? main() File "./withlist", line 256, in main r = do_list(listname, args, func) File "./withlist", line 189, in do_list return func(m, *args) File "./changeuseroptions.py", line 6, in changeuseroptions mlist.setDeliveryStatus(email, delivery) File "/var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/OldStyleMemberships.py ", line 331, in setDeliveryStatus AssertionError --- does anybody know what i've done wrong and can give me a hint how i can write such a python programm, inorder to change the member options (Mail delivery, Set Digest Mode, Get MIME or Plain Text Digests?, Receive your own posts to the list?, Receive acknowledgement mail when you send mail to the list?). or is there a python programm for download anywhere which accomplishes this task? Felix Kipping

2 1

Split anonymous from harvester-proof (bug 940497)
by Pierre Abbat 11 May '04

11 May '04

I'm on a list which a few weeks ago enabled the anonymous feature to prevent a spammer from lurking on the list and harvesting addresses. This made it impossible to sort messages by sender, and several members have complained about this. The list is not intended to be anonymous. I propose splitting this feature in two: Anonymous: Anything that looks like an email address in the headers and is not a message-ID is replaced with the list address. The entire From: header is replaced with the list address. The incoming Received: headers are deleted (if the sender has a static IP, they identify him). Harvester-proof: Anything that looks like an email address in the headers and is not a message-ID is replaced with the list address. The rest of the From: header (usually the sender's name) is left alone. The Received: headers are left in. phma -- li fi'u vu'u fi'u fi'u du li pa

1 0

Re: suggestion for Full Customization [Mailman-Developers]
by James Ralston 11 May '04

11 May '04

Brad, On 2004-05-06 at 10:26:05+02 Brad Knowles <brad.knowles(a)skynet.be> wrote: > At 7:03 PM -0400 2004/05/05, James Ralston wrote: > > > If I have set the "personalize" option to "Full Personalization", > > a very likely reason why I have done so is because I don't *WANT* > > the recipient to reply back to the list--or, for that matter, even > > realize that the message was sent through a mailing list at all. > > I want the recipient to see an individual message that looked like > > it was sent *from* an individual person *to* an individual person. > > > > Adding the list address to the CC header perfectly defeats this. > > This is a mailing list. Mailman is a mailing list manager. It is > not a "hidden address so you can spam" manager. We're not trying to > hide anything here, and I doubt that anyone is going to be > interested to see code in the mainstream package that would try to > address this "problem". I've been lurking on these lists for a few months now. In that time, I've seen you generally act friendly and helpful towards others. So, I'm going to give you the benefit of the doubt and assume that your rude and unprofessional reply was a result of a really bad mood, a complete misinterpretation of what I was suggesting, or both. Given these two points: 1. Mailman already allows list owners to configure their lists so that only a few select people are permitted to post. The typical case in which a list owner would want to do this is the situation where a single person wants to send "announcement" -type messages to a non-trivial number of recipients. 2. Mailman already has personalization features, so that messages can be customized on a per-user basis. One of the personalization features is the ability to customize the "To:" header for each recipient, and move the list address to the "CC:" header. ...why would you even *want* to have the listname for an announcement list exposed in the To and/or CC header of messages sent through the list? If a recipient replies to the list, it's just going to go to the moderators, right? In most cases, the person who is sending the messages will *be* the moderator. Why not just bypass this indirection and have the replies go directly to the sender (i.e., the moderator)? One counter-argument would be that if a list had multiple moderators, you would probably want people to reply to the list (instead of one of the moderators individually), so that all of the moderators could possibly act upon the reply. But that's actually an argument for permitting the list owners to decide where they want the list address to appear (if at all). Which is what I not only suggested, but *volunteered to contribute*. Are the specifics of what I'm suggesting clearer now?

4 5

Can moderator edit subject line and body of message?
by prodos＠prodos.com 08 May '04

08 May '04

From: Prodos (Melbourne, Australia) Good afternoon. [Part of this post was recently sent to the mailman-users list but didn't get a response. So I'm taking the liberty of posting it to the mailman-developers list. I hope that's okay. Thanks.] I coordinate a whole lot of non-profit projects (promoting free trade and related issues) and for years have been using YahooGroups/eGroups. I currently have about 200 lists set up with YahooGroups (each city involved in the campaigns has its own local discussion list, hence the quantity of lists.) For a couple of months now I've been "shopping about" for an alternative list service and I really like Mailman. However, the main problem I have with it is: It doesn't allow the subject line and the body of the message to be edited by the moderator before the message is sent through to members. YahooGroups allows this to be done very easily. Searching the mailman-user archives I've come across the following patch: "[ 644129 ] Edit held message header/body" available @ https://sourceforge.net/tracker/index.php?func=detail&aid=644129&group_id=1… The description says this patch allows "full editing of headers and bodies of messages being held for approval in Mailman 2.1" >From the description it seems this patch *does* make it possible to edit the body of a post. But I'm not sure, does it also allow editing of the subject line? i.e. Does "header" mean the same thing as "subject line"? Questions: Is it simple/easy/straightforward to do the required editing once this patch is installed? Is there a better patch available for the job? Is it a well tested patch? Why isn't such editing a standard part of Mailman? Is it because Mailman's developers think such editing is wrong? Or is it because there's not much call for such a function? Thank you for any assistance or suggestions on the above! =]:-) Best Wishes, PRODOS http://prodos.com "Discover the power. Of ideas!" -

1 0

Feature Request: Jerk Mode
by Bill Moseley 08 May '04

08 May '04

I'm a 2.0.11 user. I did look through the NEWS file; apologies if I missed something new. I'd like a subscription mode where someone will receive all messages, but when they post their message is only delivered back to them. I run a few lists where we have trollers and trouble makers. Unsubscribing or moderating them doesn't help because they re-subscribe with a new email address. Moderation of subscriptions and posts is not practical on some lists. These people just post to get a reaction out of other list members. The best solution is to have people ignore them, but that's hard on a list that is constantly changing. So, this mode would allow a way for the list owner to enforce people to ignore the posts. I realize that it's not a perfect solution -- these people can still re-subscribe with a new email address, but for many they may not realize that they are the only one seeing their own messages. Thanks, -- Bill Moseley moseley(a)hank.org

4 4

upgrade 2.0 -> 2.1: heldmsgs?
by Zoran Dzelajlija 08 May '04

08 May '04

Hi. I have both Mailman 2.0 and 2.1 installed on a machine, and wish to migrate a number of lists from Mailman 2.0.13 to the latest 2.1 version. However, I don't want to lose any of our customers data and make it as transparent as possible, so I'd like to convert everything, including all the stuff from the data/ directory, heldmsg-* and the pending subscriptions. Is there a script to convert the 2.0 heldmsg-*.txt to current heldmsg-*.pck style, or if I am to write one, where should I start from? What about pending subscriptions? Zoran

1 0

Allowing post just if a header is present
by Paulo Eduardo Neves 07 May '04

07 May '04

I've tried to have a list open, manually approving the messages of non-subscribers, but due to the amount of spam and virus, I can't handle the workload any more. I want to allow posting of non-subscribers just if they use a form in my webpage (no direct emailing to the list address). It looks like that it isn't possible to automatically approve a message just if a header is present. Any tips on how to implement it? regards, -- Paulo Eduardo Neves Agenda do Samba & Choro, o boteco virtual do samba e choro http://www.samba-choro.com.br

1 0

Re: [Mailman-Developers] Maybe you guys can help me
by J C Lawrence 07 May '04

07 May '04

On Tue, 4 May 2004 07:03:26 -0400 Paul Tomblin <ptomblin(a)xcski.com> wrote: > I do have some control over the MTA. But it does seem a little > ridiculous to filter out warnings (but not errors) just because > mailman insists on treating warnings as errors. Reliably distinguishing is non-trivial. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

9 13