Re: [Mailman-Users] Preventing Cross Posting
Thanks Mark for the good suggestions. I didn't think there was an easy solution besides the clue-by-four. I guess I be reading and contemplating a custom handler. -- Bryan Carbonnell - [EMAIL PROTECTED] Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting What a great ride! -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] senddigests cron error.
Folks,
Has anyone seen this error before? I just started receiving this error
message on my list server. This is only happening to one of my lists and
keeping users from receiving mail. All mails sent to the list is queued
in the list/digest.mbox file. I will appreciate any feedback on this issue.
Daniel.
Subject: Cron [EMAIL PROTECTED] /usr/lib/mailman/cron/senddigests
To: [EMAIL PROTECTED]
Traceback (most recent call last):
File /usr/lib/mailman/cron/senddigests, line 94, in ?
main()
File /usr/lib/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /usr/lib/mailman/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 306, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /usr/lib/mailman/Mailman/Handlers/Scrubber.py, line 265, in process
url = save_attachment(mlist, part, dir)
File /usr/lib/mailman/Mailman/Handlers/Scrubber.py, line 359, in
save_attachment
fnext = os.path.splitext(msg.get_filename(''))[1]
File /usr/lib/mailman/pythonlib/email/Message.py, line 731, in get_filename
return unicode(newvalue[2], newvalue[0] or 'us-ascii')
LookupError: unknown encoding: -86400-[ERROR:_getenv_
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Uncaught bounce notification - Out-of-Office
I, as co-owner of a Mailman 2.1.9 list, received this message: Subject: Uncaught bounce notification The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it. This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s). ... From: [EMAIL PROTECTED] ... I will be out of my office from Monday July 23 till Wednesday July 25. I will get back to you as soon as possible. Are there plans for Mailman to be able to intercept out-of-office replies and ignore them? Or is the format of the text too variable to be able to parse the OOO message? The text says or no member addresses could be extracted from it, but the recipient's address is clearly in the From: line of the mail sent back to LISTNAME-bounces. These OOO messages should not increase the recipient's bounce score. Thanks. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Uncaught bounce notification - Out-of-Office
On Tue, 2007-07-24 at 08:12 -0500, Barry Finkel wrote: Or is the format of the text too variable to be able to parse the OOO message? Bingo! No Standard, and even if there was one most wouldn't follow it. The 2 biggest offenders I see are Outlook/Exchange and Lotus Notes, of which neither tries to implement any OoO standard. -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Uncaught bounce notification - Out-of-Office
Barry Finkel writes: The attached message was received as a bounce, but either the bounce format was not recognized, This is the relevant case here. If the message doesn't look like an MTA bounce, it's probably a bad idea to treat it as a bounce. ML admin addresses get a fair amount of spam, and often enough the spam will contain member addresses. or no member addresses could be extracted from it. Are there plans for Mailman to be able to intercept out-of-office replies and ignore them? Not worth the effort because of the variability of format, and the high probability of false positives of the form P.S. I'll be out of the office next week. in a post with real content. If you have users who use vacation programs, you probably have the best idea of what their messages look like, and you should just catch them in your filters with the other spam du jour. The text says or no member addresses could be extracted from it, but the recipient's address is clearly in the From: line of the mail sent back to LISTNAME-bounces. These OOO messages should not increase the recipient's bounce score. They don't. But if there was a setting to immediately unsubscribe and ban users who send OOO messages to my lists, I'd use it.0.5 wink -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Uncaught bounce notification - Out-of-Office
On Tue, 24 Jul 2007, Barry Finkel wrote: Are there plans for Mailman to be able to intercept out-of-office replies and ignore them? Or is the format of the text too variable to be able to parse the OOO message? I've solved this problem locally using a procmail rule, and I think the method could be implemented in mailman itself if others thought it worthwhile. I only send on to mailman messages that match procmail's FROM_MAILER check, anything else is sent directly to a human. My theory is if the message isn't from a mailer-daemon, than it probably isn't a bounce. For those not familiar with procmail, FROM_MAILER expands to a faily complicated regex designed to catch mail from any mailer-daemon. `(^(((Resent-)?(From|Sender)|X-Envelope-From): |?From )([^]*[^([EMAIL PROTECTED])?(Post(ma(st(er)?|n)|office) |(send)?Mail(er)?|daemon|mmdf|n?uucp|ops|r(esponse|oot) |(bbs\.)?smtp(error)?|s(erv(ices?|er)|ystem) |A(dmin(istrator)?|MMGR))(([^).!:a-z0-9][-_a-z0-9]*)?[%@\t ][^)]*(\(.*\).*)?)?$([^]|$))' The aliases entry looks like this: listname-bounces: \ |/usr/local/bin/procmail -m /etc/mail/listname-bounces.rc listname-bounces.mc has: # Only send stuff from the mailer to mailman :0 * ^FROM_MAILER | /home/mailman/mail/mailman bounces listname #Everything else to a human :0 [EMAIL PROTECTED] == Chris Candreva -- [EMAIL PROTECTED] -- (914) 948-3162 WestNet Internet Services of Westchester http://www.westnet.com/ -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Sanity-checking individual lists for health?
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 840 lists. Therefore, going through each list pre- and post- migration by hand would be a little time-consuming for me, so I want to avoid that where possible :-)I noticed that, when doing a make update when installing 2.1.9, a couple of lists from 2.0.12 failed the update process and I had to Control-C them for the process to continue. I'm not sure what the exact problem was, hence I'm wondering if there is any kind of check that I can run in a FOR loop to verify a list's integrity. And, yes, I've run check_db and check_perms and neither report problems, this just seems to be a handful of lists out of the 800-odd that seem a little flaky. Thanks, Chris -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Unmoderated Posts Not Allowed
I have run into an odd problem with one mailing list belonging to a client. The client has many lists but we have not seen this behavior before. I have also set up a test list with them and have duplicated their settings and cannot reproduce the behavior. Details: Mailman ver. 2.1.5. Installation unknown, probably source. OS version is RHEL 4.0, 2.6.9-42.0.2.ELsmp. MTA is postfix. The list is set up to make announcements, so all members are moderated except the one making announcements. The announcer and one other list member are set up as administrators and moderators. First time the announcer tried to post to the list, her post needed approval. The issue was looked at and it became clear that at that time she was not a list member, even though she was an administrator and a moderator. She was added to the list membership and set to not be moderated. The issue was thought resolved. Recently she made another announcement post to the list and it was again held for approval. We have looked through the settings in the admin panel and can find no reason why it would be held for approval. The announcer was still unmoderated and emergency moderation had not been enabled. The email did have a Word doc attached. I tested with my test list and Word doc attachments did go through, so I don't think it is blocking all Word docs. I also used my test list to try a settings change which I thought might help. I set all members to be moderated and made a few posts with Approved: [admin password] in either the subject line or the first line of the email, but these emails were all held for approval. I am hoping you can give me a lead where to look for fixing the moderated posts problem. -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] senddigests cron error.
Daniel Ojo wrote:
Has anyone seen this error before? I just started receiving this error
message on my list server. This is only happening to one of my lists and
keeping users from receiving mail. All mails sent to the list is queued
in the list/digest.mbox file. I will appreciate any feedback on this issue.
Daniel.
Subject: Cron [EMAIL PROTECTED] /usr/lib/mailman/cron/senddigests
To: [EMAIL PROTECTED]
Traceback (most recent call last):
File /usr/lib/mailman/cron/senddigests, line 94, in ?
main()
File /usr/lib/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /usr/lib/mailman/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 306, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /usr/lib/mailman/Mailman/Handlers/Scrubber.py, line 265, in process
url = save_attachment(mlist, part, dir)
File /usr/lib/mailman/Mailman/Handlers/Scrubber.py, line 359, in
save_attachment
fnext = os.path.splitext(msg.get_filename(''))[1]
File /usr/lib/mailman/pythonlib/email/Message.py, line 731, in get_filename
return unicode(newvalue[2], newvalue[0] or 'us-ascii')
LookupError: unknown encoding: -86400-[ERROR:_getenv_
There is probably also a similar errer for each post in Mailman's error
log.
The underlying problem may be a malformed message in the list's
digest.mbox file, but there is also a bug in some versions of the
email library having to do with decoding RFC 2231 encoded headers that
is more likely the issue.
Examine the list's digest.mbox file. I believe you will find a a
message with an attachment with a Content-Disposition: header with a
RFC 2231 encoded filename parameter and an apostrophe (') in the name.
Something like
Content-Disposition: attachment;
filename*0*=us-ascii'en'first part of name
filename*1*=some more of name
with one or more apostrophes in the name text.
If you edit this name to remove the apostrophe(s) from the name, but
not the ones delimiting the character set and language parameters, the
next post to the list will trigger a digest on size and the error will
not occur.
You can then run bin/unshunt to deliver the messages that were shunted
because of this error, but first examine the *.pck files in
qfiles/shunt to be sure there aren't any old, stale ones you don't
want, and remove any unwanted ones before runing unshunt. You can
examine the contents of these files with bin/show_qfiles or bin/dumpdb.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
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/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unmoderated Posts Not Allowed
Janis Neville wrote: Recently she made another announcement post to the list and it was again held for approval. We have looked through the settings in the admin panel and can find no reason why it would be held for approval. So why don't you look at the held message in the admindb interface or the email notice to the moderator or Mailman's vette log and see why Mailman says it was held? That should give you a clue. The email did have a Word doc attached. I tested with my test list and Word doc attachments did go through, so I don't think it is blocking all Word docs. Content filtering may or may not remove this attachment, but it doesn't hold messages. However the message may have been held because it was too big (but I am only guessing - Mailman told you if this was the reason). I also used my test list to try a settings change which I thought might help. I set all members to be moderated and made a few posts with Approved: [admin password] in either the subject line or the first line of the email, but these emails were all held for approval. Approved: password does not work in the Subject: header. It works best if it is an actual message header, but it also works if it is the first non-blank line in the first text/plain part of the post, but in Mailman 2.1.5, it won't be removed from other alternatives if the first part is multipart/alternative and the code that removes it from the text/plain part also removes the line following it so it needs to be followed by an empty or other non-significant line. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Sanity-checking individual lists for health?
Chris Waltham wrote: 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 840 lists. Therefore, going through each list pre- and post- migration by hand would be a little time-consuming for me, so I want to avoid that where possible :-)I noticed that, when doing a make update when installing 2.1.9, a couple of lists from 2.0.12 failed the update process and I had to Control-C them for the process to continue. I'm not sure what the exact problem was, hence I'm wondering if there is any kind of check that I can run in a FOR loop to verify a list's integrity. And, yes, I've run check_db and check_perms and neither report problems, this just seems to be a handful of lists out of the 800-odd that seem a little flaky. There is little you can do to verify the integrity of a list other than trying to instantiate it which will also update it if necessary (and possible). check_perms only checks permissions (and it has a bug regarding archives/private). check_db only checks that list data can be loaded from lists/listname/config.* files. It doesn't sanity check the result. Do you know which lists failed in bin/update (run by make update)? If so do these lists have lists/listname/config.pck files which are converted from the config.db files and indicate the conversion of the list data was probably successful. In any case, are there any lists that don't have lists/listname/config.pck files? These would be the problem lists. One way to do a better sanity check or problem detection on these (or even on all) lists is bin/config_list -i /dev/null listname This will attempt to instantiate the list and if it's a 2.0.12 list convert the data in config.db and save as config.pck. One bit of advice. Once the lists are all converted, remove the config.db and config.db.last files from the lists/listname/ directories. If you don't do this, it is possible that at some future time, the config.pck and config.pck.last files could become corrupt and cause Mailman to fall back to the then ancient config.db. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
