Mailman 3 April 2001 - Mailman-Developers

Re: [Mailman-Developers] Patch: Optionally Suppressing List Headers
by J C Lawrence April 4, 2001

April 4, 2001

On Wed, 4 Apr 2001 19:17:12 -0400 Jay R Ashworth <jra(a)baylink.com> wrote: > On Wed, Apr 04, 2001 at 11:11:54PM +0200, ps(a)psncc.at wrote: >> Note that the patch adds a new attribute to the MailList >> object. This usually breaks existing mailing lists. > That comment troubles me. Isn't the point of object oriented > design pretty precisely to avoid the need for such comments? Yes, except that in this case the relevant objects are streamed to disk and we're talking about changing the object definition (which would therefore change the image streamed to disk). -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

1 0

Re: [Mailman-Developers] patch to remove_member for mass unsubscribes
by Ralph Corderoy April 4, 2001

April 4, 2001

Hi, > Basically it adds a special list name: _alllists_ which does this: > > # time ./remove_members -f /tmp/badmails _alllists_ Perhaps an -option would be better than special-casing a list name. Ralph.

3 2

Headers and footers for MIME messages
by barry＠digicool.com April 3, 2001

April 3, 2001

I've got a bit of a dilemma that I'd like to get your opinion on. In MM2.1, I can be more sane about adding headers and footers to messages that flow through a list, especially when it comes to MIME messages. Here are the cases I've identified: 1. A message comes in that is either text/plain or has no Content-Type. In that case, I can just textually prepend any header and append any footer. This is essentially what MM2.0.x does for all messages. 2. A message comes in that's multipart/mixed. That's easy too, since we can just add the header and footers as additional text/plain subparts. 3. A message comes in that has some other main Content-Type than "multipart", e.g. image/gif. This is a little tricker, but what I think you can do is transform the container message into a multipart/mixed, add the header and footers as subparts, and create a new subpart for the original message payload. You'd need to copy the body of the original message, plus any Content-* headers, into the subpart, but I think you leave all other headers in the container alone. 4. A message comes in that is multipart/* but not multipart/mixed. What to do here? I suppose we could play the same trick as #3, but it seems like an awful lot of work and potentially error prone. Maybe not though. Alternatively, we could add the header and footer to any existing preamble and epilogue, although they'll get hidden by most MIME-aware MUAs. Or we could simply not add headers and footers for #3 and/or #4. Let's assume for the moment <wink> that MM2.1 will have facilities to hold, discard, chop apart, etc. MIME messages and that we're talking about messages that are allowed to go though the list untouched. Any other suggestions? Any preferences? -Barry

5 9

Mailman 2.1.x
by Dan Mick April 2, 2001

April 2, 2001

Any opinions on its stability? I'm setting up a new server, and am contemplating starting off with 2.1. Is it ready for prime-ish time (I can investigate and resolve some problems) yet? I'm also considering taking the Postfix plunge at the same time. I probably need mental help. :)

2 1

patch to remove_member for mass unsubscribes
by Marc MERLIN April 2, 2001

April 2, 2001

I submitted: https://sourceforge.net/tracker/index.php?func=detail&aid=413257&group_id=1… Basically it adds a special list name: _alllists_ which does this: usw-sf-list1:/var/local/mailman/bin# time ./remove_members -f /tmp/badmails _alllists_ User `gb(a)viscomvisual.com' removed from list `berlin-fresco' User `jprice(a)chiinc.com' removed from list `foxgui-announce' User `bmcgroarty(a)high-voltage.com' removed from list `freenet-announce' User `Wilhelm.Pastoors(a)vetmed.uni-giessen.de' removed from list `gump-develop' User `oscu(a)sina.com' removed from list `linux-usb-devel' User `mehdi-laurent.akkar(a)fr.delarue.com' removed from list `madchat-annonces' User `ras(a)colltech.com' removed from list `sendpage-devel' User `mkimball(a)pdi.com' removed from list `utah-glx-cvs' User `mkimball(a)pdi.com' removed from list `utah-glx-dev' User `mkimball(a)pdi.com' removed from list `utah-glx-users' User `brianp(a)pdi.com' removed from list `vacm-develop' User `guido(a)comlog.nl' removed from list `wxwindows-users' User `frekytah(a)jono.com' removed from list `solar-empire-developer' User `dan(a)dar.net' removed from list `xemacs-winnt' real 7m26.294s user 1m9.120s sys 1m10.640s It ran in 7mn on 10,000+ lists, which ain't that bad considering. Hopefully it will make it in the next mailman. Enjoy, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

1 0

Re: [Mailman-Developers] Sender field
by J C Lawrence April 2, 2001

April 2, 2001

On Sun, 01 Apr 2001 23:08:15 +0200 Jesper Jensen <jj-list(a)mail.dk> wrote: > Why is the 'sender' header field set to the list admin address? > E.g.: Sender: mailman-developers-admin(a)python.org I'd imagine its to better handle bounces from broken MTAs. > I probably wouldn't have noticed if it wasn't because Outlook 2000 > (maybe other versions) shows this information as the 'from' > address in the preview pane separator. This is probably a flaw in > Outlook... Minimally it is Broken As Designed -- a characteristic we've all beome very familiar with with Outlook. > Anyway, back to my question, is Mailman doing this to conform with > some rfc, or would it be safe to either remove the 'sender' header > field og simply insert the "correct" 'from' address instead? I'm not aware of an RFC mandate which covers this area. That said its worth realising that Sender is an unreliable header and may be re-written by the first MTA (depends on how the message was delivered). -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

4 3

Re: [Mailman-Users] Any way users can unsubscribe without a password?
by barry＠digicool.com April 2, 2001

April 2, 2001

I've just finished implementing a more general confirmation scheme for Mailman 2.1. There are two aspects to this. When an operation requiring confirmation is performed, a confirmation email message is sent as before. However, the confirmation message will include both a confirming email command and a URL with a unique cookie, and the operation can be performed either by replying to the message or visiting the specified URL. Currently only two confirmable operations are defined: subscribing and removing. The above works regardless of e.g. whether the removal request is coming from cgi or from an email command. This means a user can send the message "unsubscribe" to mylist-request with no address and no password, and they will receive a confirmation message. A reply to that message, or a hit on the URL will remove the user. (Note that if the user actually knows their password, they can include it in the web page or email command for immediate removal.) (Note also that the architecture is general enough that other confirmable operations could be added in the future.) While this isn't exactly password-less accounts, I think it accomplishes basically the same intent. And it strikes a good balance between convenience and security. It means in practice that a user can get removed from a list without having to remember their password (or how to get it!), and the two-step removal in that case isn't too onerous (since most MUAs I suspect would let them click directly on the URL in the mail message). Acks go to Les Niles who implemented a rough cut at this. My implementation was different, but similar in spirit. -Barry

2 3

Sender field
by Jesper Jensen April 1, 2001

April 1, 2001

Why is the 'sender' header field set to the list admin address? E.g.: Sender: mailman-developers-admin(a)python.org I'm asking because I haven't seen this elsewhere. Elsewhere being LISTSERV and eGroups. I probably wouldn't have noticed if it wasn't because Outlook 2000 (maybe other versions) shows this information as the 'from' address in the preview pane separator. This is probably a flaw in Outlook - I don't know - maybe it's on purpose. The "correct" 'from' address is shown elsewhere in the program. Anyway, back to my question, is Mailman doing this to conform with some rfc, or would it be safe to either remove the 'sender' header field og simply insert the "correct" 'from' address instead? All the best, Jesper.

1 0

Re: [Mailman-Developers] Contribution: Procmail mail filter format
by J C Lawrence April 1, 2001

April 1, 2001

On Sun, 01 Apr 2001 21:05:26 +0200 Chris Boot <bootc(a)worldnet.fr> wrote: > Ah, yes, you're right. I don't know how you can take care of > BCC's (they're _meant_ to be hidden, aren't they?), but here's the > fix for the CC problem: <nod> The way to track BCC's (given that you have everything running to a common mailbox) is to have an MTA further up the pipe record the destination address (ie original RCPT_TO value) in one of the headers so that you can then filter off that (this may already be happening). -- J C Lawrence claw(a)kanga.nu ---------(*) http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

1 0

Problem with mailman-2.1a1, syntax error in bin/update : print >> sys.stderr ...
by Patrick Timmons April 1, 2001

April 1, 2001

Hi. This is the error I get when I try to do a ./configure of mailman-2.1a1: Compiling /home/mailm21/Mailman/versions.py ... File "bin/update", line 81 print >> sys.stderr, 'Fixing language templates:', mlist.internal_name() ^ SyntaxError: invalid syntax File "bin/check_perms", line 96 arg.ERRORS += 1 ^ SyntaxError: invalid syntax I tried with python 2.0 and python 2.1b1 and same result. Here is how I made python 2.0: ./configure make make test make altinstall I installed mimelib 0.2 downloaded over the weekend: python2.0 setup.py install And verified the install as per the doc I tried to install mailman-2.1a1 (downloaded today) with: ./configure --prefix=/home/mailm21 --with-username=mailm21 --with-groupname=mailm21 --with-python=/usr/local/bin/python2.0 --with-mail-gid=daemon I tried with and without PYTHONPATH=/usr/local/lib/python2.0 I'm on Linux. -- Patrick Timmons, service informatique

3 5