Re: [Mailman-Users] line feed issue with subscribeack.txt for one-way list
On Fri, Apr 23, 2004 at 01:23:30PM -0400, Jon Quiros wrote: I've been using mailman for several lists very successfully so far, and one of them is a one-way list so I'm using the /var/spool/mailman/lists/mchalertlistnamen/subscribeack.txt file for welcome messages. [...] but when this welcome message is received by a new subscriber, the end of it is all wrapped together, like this: I think the text files are wrapped by default. But another of the defaults is to honor leading whitespace, so you might try prefixing each of the lines you don't want wrapped with a space. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Redirect message from moderated group to unmoderated group
I run a moderated and an unmoderated list which have about a 90% overlap -- the other 10% being those who wish to avoid the flame wars of the unmoderated list. If someone flames the moderated list, I would like to allow it to be posted to the unmoderated list, but not to the moderated list. I would prefer a solution which does not require me to re-implement it on each new release of mailman, but if this is not possible, I would appreciate as detailed as possible a response on what I need to change. -- Chuck -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Getting caught by SPAM Filters because of Mailman handoff
Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server: Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Anything with that format - they are marking as probable SPAM Any thoughts on how to zap? Also, as I mine is an announce only list - it would be nice to be able to zap the other received from headers and show the message as coming directly from the server. One webmail program does it - but it cannot send HTML. Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Received: from mydomain.com ([111.111.11.111]) by mail.python.org with esmtp (Exim 4.22) id 1BH7Ko-0001tP-Ph for [EMAIL PROTECTED]; Fri, 23 Apr 2004 16:31:42 -0400 BTW - usim exim as MTA. Thanks. Lloyd F. Tennison [EMAIL PROTECTED] No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Discarding all held mail
I have let me posted by non-members accumulate over months and now there is quite a bit of it. Can I get rid of it all in one go, or do I need to discard each post individually? -- John -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Re: Messages Not Appearing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 23 Apr 2004 00:28:22 -0600, Space Coyote scribbled down: I am having trouble having anything show up on my lists. I am receiving the mails as forwarded by sendmail, all of the aliases are working. the mail log has none of the typical gid problems. Everything looks like mail is being sent out. Without any logs - nobody knows what's going on. Mailman logs quite comprehensively, so see if you can see the mail being sent out and received by the MTA having been processed by Mailman, see if the mail is actually getting accepted by Mailman. It'd help a great deal if you pinpoint exactly where the mail is getting held up. The following FAQ entries might help you: http://www.python.org/cgi-bin/faqw-mm.py?req=all#1.7 http://www.python.org/cgi-bin/faqw-mm.py?req=all#3.14 Looking at the system log file gate_news is being restarted by cron every five minutes. I cannot find any cron processes running though when I perform a ps -aux | grep cron except the deamon. None of my mailman logs are being populated except the subscribe list. I'm unsure as to what you mean by 'daemon', are Mailman's qrunner processes running? My mm_cfg.py file appears to be empty but my Defaults.py contains what I need it to. What am I missing? You should not use Defaults.py to configure Mailman, instead copy and paste what you need out of Defaults.py into your mm_cfg.py. The reason for this is that if you upgrade your version of Mailman, your site configuration will be completely and irreversibly overwritten. HTH - -- - -jamie [EMAIL PROTECTED] | spamtrap: [EMAIL PROTECTED] w: http://www.silverdream.org | p: [EMAIL PROTECTED] pgp key @ http://silverdream.org/~jps/pub.key 15:30:01 up 4 days, 5:43, 12 users, load average: 1.00, 0.77, 0.67 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAioLfx2omo/Dc/KgRAjTtAKCWZ87nm3sf9lg1wytRnA4e5KzBgACgzIG7 9760JrggS1CuH5zOlXALigU= =I9IC -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Discarding all held mail
John Poltorak wrote: I have let me posted by non-members accumulate over months and now there is quite a bit of it. Can I get rid of it all in one go, or do I need to discard each post individually? If you're using v2.1, the FAQ has the info on how to mass delete pending messages: http://python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.026.htp hth, texas critter -- EL-M FAQ: http://www.emaillist-managers.com/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Getting caught by SPAM Filters because of Mailman handoff
Lloyd F. Tennison wrote on Fri, 23 Apr 2004 18:10:07 -0700: Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server: This is not because of Mailman, this is because they misconfigured their spam filter. We do run SA and others filters and I usually put all mailing lists we receive in the whitelist, but somehow I forgot to do it for this list. It's getting thru as clear ham and doesn't have any standard spam tagging from SA. If it gets a spam hit, then it's because of the body, not the headers and usually it gets BAYES_00 (= ham) for the body. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de http://msie.winware.org -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Getting caught by SPAM Filters because of Mailman handoff
On 24 Apr 2004, at 02:10, Lloyd F. Tennison wrote: Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server: Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Anything with that format - they are marking as probable SPAM Any thoughts on how to zap? Although I run the outgoing MTA and Mailman on the same machine, my Mailman SMTP configuration tells it not to address the MTA using localhost (127.0.0.1) but by the FQDN and IP number which appears in our globally published MX record for that server. Thus the Received: header added by the outbound MTA at this juncture refers to reception form a host (itself) which is resolvable via DNS to an MX record by MTAs which subsequently handle the message. In that respect, it is thus fairly indistinguishable from other Received: headers that precede and follow it. Would this be avoid triggering the approach in anti-spam measures you refer to? Also, as I mine is an announce only list - it would be nice to be able to zap the other received from headers and show the message as coming directly from the server. One webmail program does it - but it cannot send HTML. Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Received: from mydomain.com ([111.111.11.111]) by mail.python.org with esmtp (Exim 4.22) id 1BH7Ko-0001tP-Ph for [EMAIL PROTECTED]; Fri, 23 Apr 2004 16:31:42 -0400 BTW - usim exim as MTA. Thanks. Lloyd F. Tennison [EMAIL PROTECTED] No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] error No template file found: 'archidxentry.html'
I have just migrate my mailman installation 2.1+ to a new server with 2.1.4 and I have problems with a couple of lists that do not process their messages. (I have deleted the list and create again but it continues receive message and do not send it). I have the following error in the logs/error Apr 24 03:56:12 2004 (31159) SHUNTING: 1082664620.461622+ac23d23deec9d0de0b2b78422bfc1fb5c6a6c62f Apr 24 03:56:13 2004 (31159) Uncaught runner exception: [Errno 2] No template file found: 'archidxentry.html' Apr 24 03:56:13 2004 (31159) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 110, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /var/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.close() File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 311, in close self.update_dirty_archives() File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 527, in update_dirty_archives self.update_archive(i) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 1075, in update_archive self.__super_update_archive(archive) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 431, in update_archive self._update_simple_index(hdr, archive, arcdir) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 452, in _update_simple_index self.write_index_entry(article) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 1018, in write_index_entry mlist=self.maillist) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 204, in quick_maketext raw=True, mlist=mlist) File /var/lib/mailman/Mailman/Utils.py, line 485, in findtext raise IOError(errno.ENOENT, 'No template file found', templatefile) IOError: [Errno 2] No template file found: 'archidxentry.html' Apr 24 03:56:13 2004 (31159) SHUNTING: 1082665429.6690519+7a21e9a64c3ff7afd1e8af77fca5162c4ff3d42c I have my system in Spanish. Do you have any suggestion?? -- Rodolfo Pilas Quien los puso a estos tipos donde estan, [EMAIL PROTECTED] Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, Yahoo ID: ysidoritoQuien les paga para que hagan lo que haran ICQ: 17461636 -=# Apocalipsis Now % Cuarteto de Nos #=- GnuPG Public Key: gpg --keyserver www.keyserver.net --recv-key 57153363 Key Fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Getting caught by SPAM Filters because of Mailman handoff
How did you change the configuration to accomplish that, please. Copies to: [EMAIL PROTECTED], [EMAIL PROTECTED] From: Richard Barrett [EMAIL PROTECTED] Subject:Re: [Mailman-Users] Getting caught by SPAM Filters because of Mailman handoff Date sent: Sat, 24 Apr 2004 18:16:55 +0100 To: [EMAIL PROTECTED] On 24 Apr 2004, at 02:10, Lloyd F. Tennison wrote: Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server: Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Anything with that format - they are marking as probable SPAM Any thoughts on how to zap? Although I run the outgoing MTA and Mailman on the same machine, my Mailman SMTP configuration tells it not to address the MTA using localhost (127.0.0.1) but by the FQDN and IP number which appears in our globally published MX record for that server. Thus the Received: header added by the outbound MTA at this juncture refers to reception form a host (itself) which is resolvable via DNS to an MX record by MTAs which subsequently handle the message. In that respect, it is thus fairly indistinguishable from other Received: headers that precede and follow it. Would this be avoid triggering the approach in anti-spam measures you refer to? Also, as I mine is an announce only list - it would be nice to be able to zap the other received from headers and show the message as coming directly from the server. One webmail program does it - but it cannot send HTML. Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 4.22) id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51 -0400 Received: from mydomain.com ([111.111.11.111]) by mail.python.org with esmtp (Exim 4.22) id 1BH7Ko-0001tP-Ph for [EMAIL PROTECTED]; Fri, 23 Apr 2004 16:31:42 -0400 BTW - usim exim as MTA. Thanks. Lloyd F. Tennison [EMAIL PROTECTED] No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced. Thanks. Lloyd F. Tennison [EMAIL PROTECTED] No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] error No template file found: 'archidxentry.html'
Should be in your Mailman/templates folder. If not, put it back in and try again. From: Rodolfo Pilas [EMAIL PROTECTED] To: [EMAIL PROTECTED] Organization: RootWay Date sent: Sat, 24 Apr 2004 14:55:30 -0300 Subject:[Mailman-Users] error No template file found: 'archidxentry.html' I have just migrate my mailman installation 2.1+ to a new server with 2.1.4 and I have problems with a couple of lists that do not process their messages. (I have deleted the list and create again but it continues receive message and do not send it). I have the following error in the logs/error Apr 24 03:56:12 2004 (31159) SHUNTING: 1082664620.461622+ac23d23deec9d0de0b2b78422bfc1fb5c6a6c62f Apr 24 03:56:13 2004 (31159) Uncaught runner exception: [Errno 2] No template file found: 'archidxentry.html' Apr 24 03:56:13 2004 (31159) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 110, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /var/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.close() File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 311, in close self.update_dirty_archives() File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 527, in update_dirty_archives self.update_archive(i) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 1075, in update_archive self.__super_update_archive(archive) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 431, in update_archive self._update_simple_index(hdr, archive, arcdir) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 452, in _update_simple_index self.write_index_entry(article) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 1018, in write_index_entry mlist=self.maillist) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 204, in quick_maketext raw=True, mlist=mlist) File /var/lib/mailman/Mailman/Utils.py, line 485, in findtext raise IOError(errno.ENOENT, 'No template file found', templatefile) IOError: [Errno 2] No template file found: 'archidxentry.html' Apr 24 03:56:13 2004 (31159) SHUNTING: 1082665429.6690519+7a21e9a64c3ff7afd1e8af77fca5162c4ff3d42c I have my system in Spanish. Do you have any suggestion?? -- Rodolfo Pilas Quien los puso a estos tipos donde estan, [EMAIL PROTECTED] Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, Yahoo ID: ysidoritoQuien les paga para que hagan lo que haran ICQ: 17461636 -=# Apocalipsis Now % Cuarteto de Nos #=- GnuPG Public Key: gpg --keyserver www.keyserver.net --recv-key 57153363 Key Fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Thanks. Lloyd F. Tennison [EMAIL PROTECTED] No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Re: Getting caught by SPAM Filters because of Mailman handoff
On 11:00 AM 4/24/2004, [EMAIL PROTECTED] wrote: Companies are now starting to block Mailman lists (among others) because of the way the headers are sent out stating the hand-off to the server: I fear that mail lists will become an increasingly common victim of friendly fire in the war against spam. The better a system is at getting rid of spam, the more false positives it causes. Additionally many spam filters are not configured intelligently, often because the person who installed the system just did it out of the box and walked away. While I am all for the Mailman developers making reasonable efforts to avoid mm lists being caught as spam, the only real solution if for the folks setting up the spam filters, and the folks behind such filters, to get a clue. The responsibility must be on the receiver, not the sender. An example: I just got a message to a moderated list. It an automated message from the spam block system for someone who signed up for the list. The message said: Here's all you have to do: 1. Press Reply. 2. In the body of the reply, type in my AntiSpam Passcode contained in the graphical attachment. 3. Press Send. Right. Like I want to do that. Like I can even get the image in the attachment on a list that strips attachments. The clueless person who signed up for the list will just have to wonder why he is not getting list mail. My suggestion to the developers? Add a reject option to the pending page that reads You will not receive list mail because you are too stupid. Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Getting caught by SPAM Filters because of Mailmanhandoff
Lloyd F. Tennison wrote: How did you change the configuration to accomplish that, please. Me too, please. I don't know if any of my lists are getting blocked by this or not but using a FQDN with resovable MX is always a good idea. hth, texas critter -- EL-M FAQ: http://www.emaillist-managers.com/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] line feed issue with subscribeack.txt for one-way list
Jim Tittsler wrote: I think the text files are wrapped by default. But another of the defaults is to honor leading whitespace, so you might try prefixing each of the lines you don't want wrapped with a space. Thank you! Adding a single whitespace at the beginning of the lines worked. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Mailman 2.1.5 release candidate 2
I've just uploaded Mailman 2.1.5 release candidate 2 (no, you never saw rc1 :). Since there are some fairly significant changes with this version, I felt it was necessary to put out a release candidate to hopefully prompt some additional testing. If you're able to test the new version, that would be great, but please note that: * The file format for on-disk messages in the qrunners has changed. Until now, each queued message was represented by two files, a .msg and a .pck file. With this version, all information is kept in the .pck file. This improves stability and performance. The upgrade script will attempt to convert all your existing .msg/.pck files to the single .pck file, but there may still be lurking problems with this conversion. * The pending database has been changed from a global pickle file living in $prefix/data, to a unique pickle file per mailing list. The upgrade script attempts to determine which list each pending request belongs to, but it isn't always possible to know, so while it does the best it can, there may still be lurking problems with this conversion. If you upgrade you should do so only on a quiet system. I recommend shutting down Mailman, your MTA, and your web server before doing the upgrade. Please note any problems you have with the conversion scripts (you may want to make backups first ;). My thanks for not letting the above discourage you from testing the new version. :) I think the improvements in 2.1.5 are worth it, and based on experiences running python.org, the new version should be quite stable once installed. I plan to release 2.1.5 final sometime next weekend. -Barry signature.asc Description: This is a digitally signed message part -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Senddigests fails with HeaderParseError
Greetings list members,
I thought I had sent this message earlier, but I don't see it in the
archives. Forgive me if you have already seen it.
-- Previous Message -
I did a search of the list on HeaderParseError and didn't find an answer
to this.
I'm running mailman 2.1.4.
I just had senddigests fail due to this From: line:
From: =?Windows-1251?B?wuvg5Ojs6PAgyvDg8e7i8ero6Q?=
[EMAIL PROTECTED]
I deleted the character set specification and the digest was sent
successfully.
Has anyone else seen this? Even if the charset is bogus, mailman
shouldn't bomb.
The error I got was:
Traceback (most recent call last):
File /usr/local/mailman/cron/senddigests, line 94, in ?
main()
File /usr/local/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /usr/local/mailman/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 225, in
send_i18n_digests
addresses = getaddresses([oneline(msg.get('from', ''), lcset)])
File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 389, in
oneline
h = make_header(decode_header(s))
File /usr/local/mailman/pythonlib/email/Header.py, line 113, in
decode_header
raise HeaderParseError
email.Errors.HeaderParseError
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
