Mailman 3 October 2002 - Mailman-Users

Re: OFFTOPIC Re: [Mailman-Users] Archive URL in postings (2.1b3)
by Jay Sekora 31 Oct '02

31 Oct '02

> > What that means to me is that Chuq Von Rospach knows me, knows my email > > address, deliberately decided to send this mail to me specifically, > um, interesting philosophy. I don't buy it. Not for a moment. Well, obviously I can tell in this context that it isn't true, but that's what the semantics of seing my address in a To: or a Cc: header are for me. What do *you* think the connotations should be? If there weren't any destination headers at all in RFC822 messages, and the only information end-users got about source or recipient were the envelope information, the situation would be different, but we *do* use To: and Cc: to mean different things. Whatever the merits of your arguments about what headers I should be using to filter which lists, the fact is that taking something the original composer of the mail entered in the To: field and moving it to the Cc: field, and taking something the original composer didn't specify at all and putting it in the To: field is losing information. I can imagine situations where you want to lose that piece of information, but not very typical ones. FWIW, Jay

3 2

Help!
by Director 31 Oct '02

31 Oct '02

Hi my list is down, it's been down since Monday evening...this happened once before. Nothing has changed, just stopped working. Any ideas? Sharon S. E. Schlossenberg Director - My Woman2Woman Network, LLC http://www.mywoman2woman.com director(a)mywoman2woman.com (800) 216-0549

2 1

Help! "All recipients refused"
by Leewei 31 Oct '02

31 Oct '02

Hello all, I installed Mailman RPM package on my Red Hat 7.2. But the list can not relay any e-mail! I can read all sent mails in list archives on web but none of list members can get the mail! In /var/log/mailman/smtp file, it goes like this: ... Oct 30 18:03:00 2002 (10101) All recipients refused: (111, 'Connection refused') Oct 30 18:03:00 2002 (10101) All recipients refused: (111, 'Connection refused') Oct 30 18:03:00 2002 (10101) smtp for 5 recips, completed in 0.005 seconds Oct 30 18:04:00 2002 (10106) All recipients refused: (111, 'Connection refused') Oct 30 18:04:00 2002 (10106) All recipients refused: (111, 'Connection refused') Oct 30 18:04:00 2002 (10106) smtp for 5 recips, completed in 0.005 seconds ... In /var/log/mailman/smtp-failure file, it goes like this: ... Oct 30 18:03:00 2002 (10101) -1 user1(a)hotmail.com (ignore) Oct 30 18:03:00 2002 (10101) -1 user2(a)hotmail.com (ignore) Oct 30 18:03:00 2002 (10101) -1 user3(a)hotmail.com (ignore) ... Could someone please tell me why? Thank you very much! -- Best regards, Leewei mailto:leewei@163.net

2 1

problems view archives (again you say)
by James Quiring 31 Oct '02

31 Oct '02

I an running mailman on freebsd with apache and sendmail. All works as expected except that I cant view the archives for public lists (lists with private archives work fine). The error is the usuall 403 don't have permission to access /pipermail/listname/ I have not errors logged in the httpd-error.log my httpd.conf includes: Alias /pipermail/ "/usr/local/mailman/archives/public/" </Directory "usr/local/mailman/archives/public"> Allow overide none Options FollowSymLinks </Directory> and as I said - if I mark it as private it works. uid and gid are mailman for files in the lists archive directory apache runs as www Any help would be appreciated. Regards James Quiring Mailman newbie.

2 1

Integrating LDAP and Mailman 2.1b4
by Gedaliah Wolosh 31 Oct '02

31 Oct '02

Hi folks, I have spent the last several hours looking for documentation on how to integrate LDAP with mailman. What I need to be able to do is create a list where the membership is based on certain criteria fed to an LDAP server. Is this possible?? If anyone has done something like this I would appreciate explicit instructions on how to do this. --Gedaliah

1 0

B4 changed the To: line?
by Danny Terweij 31 Oct '02

31 Oct '02

Hi all, I do not know if this is the same as discussed now on the users list about "List Id". But all my users from all lists are complaining since i upgraded to B4/B4+ . The Short list description is placed at every outgoing mail at the TO: field. If the short list desciption is: "Welcome at this fine list" (You can see this at the /listinfo/ web page) Then all mail looks like this: >From : Danny Terweij To: Welcome at this fine list How to stop this or how to get back what it was before B4 version? Danny Terweij.

5 4

Problem with 2.1 beta 4
by Miller Brett 31 Oct '02

31 Oct '02

Hello mailman users, I just upgraded to Mailman beta 4 and I am receiving this error when a mailman cron job runs. Has anyone seen this error and does anyone know how to fix it. Thank you for your time. Traceback (most recent call last): File "/usr/local/mailman/cron/checkdbs", line 26, in ? from email.Charset import Charset ImportError: No module named email.Charset Brett Miller Booz | Allen | Hamilton E-mail: miller_brett(a)bah.com Office: (410)684-6468

4 5

Re: OFFTOPIC Re: [Mailman-Users] Archive URL in postings (2.1b3)
by Jay Sekora 31 Oct '02

31 Oct '02

> > The problem with personalization in the To: header is that I can't > > tell if email is to me or just to the list. > Be careful here in distinguishing limitations and models of your MUA as > problems with external systems. The fact that you MUA exposes specific > features and the manner you take advantage of them is something between > you and your MUA and has little to do with Mailman. So if Mailman decides to change the Subject: header to "What this message is about:", transcribe the addresses in the To:, Cc:, and From: fields into EBCDIC and reverse the local part and the domain, and put all the headers at the bottom of the message instead of the top, would my beef be with my mail reader for not displaying that properly? -j.

2 1

Re: OFFTOPIC Re: [Mailman-Users] Archive URL in postings (2.1b3)
by Jay Sekora 31 Oct '02

31 Oct '02

> No, it's not. Not a bit. One of the things my organization does is > manage the email systems for our corporation (not a small one). and we > set policy on email clients quite simply: "here are the ones we > support. If you use something else, we wish you luck. If it doesn't > work right, we hope you can fix it". That's an excellent strategy for managing support staff's workload, and it's a strategy we use at my job as well. It's a terrible strategy to get a software project taken seriously around the world. Imagine if Python could only build on HP/UX, IRIX, and SCO Unix, using a particular version of GCC that had the quirks that Guido liked and didn't have the quirks he didn't like. Would anybody be using it? -j. PS - Admittedly, Mailman is *already* taken seriously around the world. But I don't think it has sufficient monopoly power yet that it can impose this sort of a paradigm shift on email. Actually, it's going to have a hard time doing that as long as anybody also gets non-mailing-list-mail. If it were a newsreader or a weblogging system, it would have a better chance, because people don't see their news or their blogs alongside their personal email, so it's not going to bother them as much if the semantics are different.

1 0

Re: OFFTOPIC Re: [Mailman-Users] Archive URL in postings (2.1b3)
by J C Lawrence 31 Oct '02

31 Oct '02

On Tue, 29 Oct 2002 10:56:39 -0800 (PST) alex wetmore <alex(a)phred.org> wrote: > 1) You are using an email system which removes duplicates (based on > the Message-Id header). Microsoft Exchange 2000 is one such system. > If Mailman is changing the headers so much perhaps it should stick a > new Message-Id on the message though. We should start out admitting that such mail systems are broken and then decide how far we want to cater to such broken systems. > 2) You want replies to your messages to show up in your mailman-users > folder (or whatever), but colored in a different manner. I do this. > If I'm away for a while and want to catch up on a folder I just scan > for cyan messages. I don't want public replies to messages that I > posted on a mailing list to end up in my private inbox. There are multiple ways to achieve this. Parsing To: is one of the more fragile ways. Far more effective and near-guaranteed to be correct (except for the standard broken software case as above) is tracking In-Reply-To: from your original post(s). -- 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.

3 2