Mailman 3 August 2007 - Mailman-Users

Re: [Mailman-Users] Fw: problem in Makefile for mailman
by Barry Finkel Aug. 4, 2007

Aug. 4, 2007

>Yep, it's a FreeBSD port. While I run both free and open bsd, I've >found that there are a few things better installed from original >source. Mailman is one of them. Look at the changes that FreeBSD has made. You will probably find some that you do not understand. I did the same with Ubuntu, and most of the changes were not documented, so I had no idea why they were made. ---------------------------------------------------------------------- Barry S. Finkel Computing and … [View More]

5 4

antispam patch, and private archives not found
by BobLaJolla＠aol.com Aug. 3, 2007

Aug. 3, 2007

Hi - I've been working on the anti-spam harvest patch to dynamically X out the addresses in the mailman archives via the private.py script, but have been running across an error. After putting in the httpd.conf rewrite rule, I get the error: Private archive file not found This is generated from the patched portion of the private.py script, so it looks like I have the patch applied properly, but the private script can't for some reason locate the archive. Checking the /… [View More]

1 0

customizing pages
by Wes Aug. 3, 2007

Aug. 3, 2007

I'm trying to figure out how to customize all the pages that an end user will see when interfacing with the mailman system. I want a one way list, so I want to have the fewest options available to the user. I'd like them to just: 1. subscribe on a web form 2. confirm via a link in their email client 3. unsubscribe if necessary following instructions at the bottom of each email 4. unsub/resub if they want to change their email delivery address In other words, I don't care to let them see … [View More]

2 1

Weird problem data format error. Command output Mailbox does'nt exist
by carconni Aug. 3, 2007

Aug. 3, 2007

HI, I have an odd problem. I have over a hundred lists and all but one is working properly. The initial support call was a complaint that the mail server was bouncing back the emails sent to the list claiming that there was no such user (list-name). I thought it was odd, so I rmlist -a and recreated it using newlist. I tested the list, mail went to the user and everyone was happy. Oddly, the mailserver bounced that night (we aren't sure why) but the next day I got another call … [View More]about the same list. I thought that it was a fluke, maybe some weird setting had been reverted when the server bounced, so again I removed the list (rmlist but without removing the archives) and recreated the list using newlist. I tested the list by sending an email and everyone (except the administrator who now had to repopulate the list was happy) It is day 3. I got phone call today. The same list is broken again. All the other lists work fine but this one seems to be unrecognized by the system: Aug 2 13:36:36 mail postfix/smtpd[5008]: NOQUEUE: reject: RCPT from sjc.mailserver.com[63.80.14.252]: 550 <qvc- requests(a)mail.mailserver.com>: Recipient address rejected: User unknown in local recipient table; from=<carconni(a)mailserver.com> to=<qvc-requests(a)mail.mailserver.com> proto=ESMTP helo=<[172.16.246.5]> Aug 2 13:42:02 mail postfix/smtpd[5066]: NOQUEUE: reject: RCPT from sjc.mailserver.com[63.80.14.252]: 550 <qvc- requests(a)mail.mailserver.com>: Recipient address rejected: User unknown in local recipient table; from=<carconni(a)mailserver.com> to=<qvc-requests(a)mail.mailserver.com> proto=ESMTP helo=<[172.16.246.5]> Aug 2 13:45:31 mail postfix/pipe[6401]: 9E219166485D: to=<qvc- requests(a)mailserver.com>, relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) Aug 2 13:57:17 corp-admin2 postfix/pipe[7594]: 222591665614: to=<qvc- requests(a)mailserver.com>, relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) Aug 2 14:05:45 mail postfix/pipe[7722]: 34A081666003: to=<qvc- requests(a)mailserver.com>, relay=cyrus, delay=0, status=bounced (data format error. Command output: qvc-requests: Mailbox does not exist ) I have spent the better part of 6 hours looking for a reason. I've checked permissions, not just with checkperms but manually, step by step, directory by directory comparing the broken list to a list that is known to be working. /private/var/mailman/archives/private/qvc-requests/database "other" perms must be 000 (fixing) drwxrwsr-x 3 root mailman 102 Jun 18 13:30 production drwxrwsr-x 2 root mailman 68 Jun 18 13:30 production.mbox drwxrwsr-x 10 root mailman 340 Aug 1 11:18 qvc-requests drwxrwsr-x 3 root mailman 102 Jul 26 09:02 qvc-requests.mbox /var/mailman/lists root# ls -l qvc-requests total 56 -rw-rw---- 1 mailman mailman 3777 Aug 2 11:25 config.pck -rw-rw---- 1 mailman mailman 3778 Aug 2 11:24 config.pck.last -rw-rw---- 1 mailman mailman 11089 Aug 1 14:16 digest.mbox -rw-rw---- 1 mailman mailman 131 Aug 1 10:24 pending.pck -rw-rw-r-- 1 www mailman 24 Aug 1 11:18 request.pck /var/mailman/archives/private/qvc-requests root# ls -l total 160 drwxrwsr-x 10 mailman mailman 340 Aug 1 14:16 2007-August -rw-rw-r-- 1 mailman mailman 2476 Aug 1 14:16 2007-August.txt drwxrwsr-x 28 mailman mailman 952 Jul 31 15:08 2007-July -rw-rw-r-- 1 mailman mailman 66954 Jul 31 15:08 2007-July.txt drwxrwsr-x 7 root mailman 238 Aug 1 11:59 attachments drwxrwx--- 12 mailman mailman 408 Aug 1 14:16 database -rw-rw-r-- 1 root mailman 1465 Aug 1 14:16 index.html -rw-rw---- 1 mailman mailman 892 Aug 1 14:16 pipermail.pck I've checked the alias file in /var/mailman/data/aliases: (Everything looks ok) # STANZA START: qvc-requests # CREATED: Wed Aug 1 09:09:12 2007 qvc-requests: "|/usr/share/mailman/mail/mailman post qvc- requests" qvc-requests-admin: "|/usr/share/mailman/mail/mailman admin qvc- requests" qvc-requests-bounces: "|/usr/share/mailman/mail/mailman bounces qvc-requests" qvc-requests-confirm: "|/usr/share/mailman/mail/mailman confirm qvc-requests" qvc-requests-join: "|/usr/share/mailman/mail/mailman join qvc- requests" qvc-requests-leave: "|/usr/share/mailman/mail/mailman leave qvc- requests" qvc-requests-owner: "|/usr/share/mailman/mail/mailman owner qvc- requests" qvc-requests-request: "|/usr/share/mailman/mail/mailman request qvc-requests" qvc-requests-subscribe: "|/usr/share/mailman/mail/mailman subscribe qvc-requests" qvc-requests-unsubscribe: "|/usr/share/mailman/mail/mailman unsubscribe qvc-requests" # STANZA END: qvc-requests I've checked locks: - nothing regarding this list there. main.cf shows: alias_maps = hash:/etc/postfix/lmail/ company.aliases,hash:/var/mailman/data/aliases Where else can I check? Thank you [View Less]

2 6

Duplicate messages and unpickling errors on Mailman lists after upgrading Mac OS X Server
by Alan Sill Aug. 3, 2007

Aug. 3, 2007

After applying the most recent Security Update to our Mac OS X Server 10.4.10 installation, we are encountering the following two problems with Mailman lists hosted on this server that were working fine earlier: 1) Each message sent to any of our Mailman-based e-mail lists appears to be sent in duplicate to each member of the list 2) Under some conditions we encounter an "unpickling error" that from Googling around would appear to be a python error, as follows: Aug 03 01:22:25 2007 (… [View More]

2 1

Quick Question...
by Jason Pruim Aug. 3, 2007

Aug. 3, 2007

I have seen people complaining about mailman hosts limiting their outgoing messages to X per hour/day... Is that something that the host puts in? Or is there something with mailman that's limiting? I think I know the answer I just want to double check :) -- Jason Pruim Raoset Inc. Technology Manager MQC Specialist 3251 132nd ave Holland, MI, 49424 www.raoset.com japruim(a)raoset.com

3 3

Any way to prevent password reminders from being set at a server level?
by Pat Riehecky Aug. 3, 2007

Aug. 3, 2007

I am in the process of configuring a secondary mailman system for use as a hotspare. I noticed just a few days ago that both the primary and the backup system sent out list password reminders. There really is no reason to send out both reminders as they contain the exact same text. Is there a way to tell the server not to send those out. I know each user can set this up on a per list basis, but since the backup does an rsync of the list data from the primary any such change in the list … [View More]

2 1

How to change xxx-bounces@mydomain.com address in mailman
by BugsBunny Aug. 3, 2007

Aug. 3, 2007

Hi,I installed mailman 2.1.9 on fedora core 5. My host name was originally set as mydomain.net. Everything seemed working fine. Then I changed my host name to mydomain.com. (from .net to .com).I changed this from /etc/sysconfigure/network.I also checked my mm_cfg.py and default.py to make sure no "mydomain.net" specified. But whenever I get mailing list email, the email header still says it comes from "mydomain.net" instead of "mydoamin.com". This caused my email going into spam folder … [View More]

2 1

Sanity-checking individual lists for health?
by Chris Waltham Aug. 3, 2007

Aug. 3, 2007

Hi folks, I have been tasked with moving a Mailman 2.0.12 installation from a Solaris (SPARC) server to a Linux (x86) server. The Linux server will be receiving a copy of Mailman 2.1.9, so obviously I am making the 2.0.x -> 2.1.x jump in there. Also, on Solaris, Mailman lives in / home/mailman but on Linux I will be putting it in /blender/mailman (and thus using move_list to update archives, fix_url, etc.) What makes this migration slightly tricky is that the server hosts around … [View More]

2 3

Re: [Mailman-Users] Digest not being sent
by Christopher Adams Aug. 3, 2007

Aug. 3, 2007

Actually, I have read the FAQ, but didn't seem to reap any useful information in this regard. I did find something in my search of the mailman-users list that talks about a corrupt digest.mbox file. Before I had a chance to check that out, the digest was sent. Odd. So, what controls the time that the daily digest is sent out if the threshold hasn't been reached? There is a 'senddigests' script in the /mailman/cron directory, but I am at a loss as to when it is fired off. I can generate … [View More]

3 3