Mailman 3 October 2006 - Mailman-Users

How does mailman/mail/wrapper get created?
by Jon Ferraiolo 03 Nov '06

03 Nov '06

I am working with my ISP to get Mailman installed on a private domain. I believe we have followed all of the Mailman setup instructions correctly. We are at the point where we mail lists with subscribers. However, when attempted to send email to one of the lists (e.g., foo(a)bar.com), we are now getting an error message that says: sh: line 1: /home/bar/mailman/mail/wrapper: No such file or directory Looking at my installation, there is no mail/main/wrapper file. Should there be one? Should it have been created by "make install" or is this something that needs to be created manually? Thanks. Jon Ferraiolo <jferrai(a)us.ibm.com>

2 1

Interesting Goings ons...
by Adam Morehead 03 Nov '06

03 Nov '06

We have mailman setup on our server... Everything is working fine except one thing, all the approved emails are going to the recipients, all denied are getting denied.. only one thing is bugging me... if theres a pending request, we used to get a email letting us know that we have email waiting for approval.. its not happening anymore. I went through aliases and made sure it is 'mailman' not 'wrappers' (Since we used to have the older version. made sure that the aliases file is being called. and even the email addy is in the admin and moderator spot on the webform... what am I missing? Please let it be simple? lol. Adam

3 7

Unexpected Listname When Creating New List
by Jon Forrest 03 Nov '06

03 Nov '06

(Mailman 2.1.9 Fedora 5) newlist --help says: "Note that listnames are forced to lowercase". That doesn't seem to be true. I just ran bin/newlist test but my listinfo web page shows this as "Test". It also shows up as "Test" in the General Options web page. If I look at the "Details for real name" information, it says: "Email addresses are not case sensitive..." I learned in Email 101 that this is not true on the left side of "@" signs. Was my teacher playing a cruel joke on me? In any case, I can change "Test" to "test" and all appears well. What's a mother to do? Cordially, -- Jon Forrest forrest(a)ce.berkeley.edu Computer Resources Manager Civil and Environmental Engineering Dept. 305 Davis Hall Univ. of Calif., Berkeley Berkeley, CA 94720-1710 510-642-0904

3 6

Re: [Mailman-Users] reviving broken mailman ???
by Patrick Bogen 01 Nov '06

01 Nov '06

On 10/31/06, Dr. Scott S. Jones <scott(a)fyrenice.com> wrote: > Broken, in that it won't send out through my MTA, which in my case is Exim4, > or in another who's had trouble with mailman on debian, through Postfix. It > seems that when he moved his data files, and purged mailman and then > reinstalled it. He claims it works now.... Well, my point was, if your mailman is broken because something is wrong with your list config files, keeping the list config files and reinstalling everything else won't help anything. :) > My question then is which files does one move out of the way of the wrecking > ball, a la apt-get --purge mailman etc.... so that one doesn't have to > recreate the list after reinstallation? If you aren't concerned about list archives, I believe you only need the files in (on Debian) /var/lib/mailman/lists/* Each list should have its own directory, with a config.pck, possibly config.pck.last, and (possibly?) a request.pck. Archives are in /var/lib/mailman/archives; they can be regenerated from some subset of the files in this hierarchy (I believe its those under listname.mbox/), but I'm not sure if that's all that's required. If you can read bash script, FAQ 4.18 <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.018.htp> might help you figure all this out. P.s., Please CC the list on all replies, so that more well-versed folk can chime in when I might not know the answer. -- - Patrick Bogen

3 3

Emails Not Being Delivered to All on List
by Bruce E. Breeding 01 Nov '06

01 Nov '06

Symptom: some list recipients are not receiving their emails from the list [Four resulting questions below] In attempting to determine WHY the above symptom is occurring, I contacted my web service provider. We're getting to know each other well due to frequency of communication. ;) He seems to be trying hard to help me out. Here is his latest helpful hint: **** Web service provider's suggestions start here ... "I happened to catch some of your mailing lists trying to deliver a little while ago and caught an example of why you sometimes have problems. This is a good example of a list doing a partial delivery because it stalls at a bad address which causes delays etc for other addresses that are on the same list and this particular address you have on for lists currently unable to finish delivery....................... Getting MX record for <domainname>.org (from local DNS server, may be cached)... Received a SERVER FAILURE response. This should be treated as an ERROR (per RFC974), and the E-mail delivery should PROBABLY be retried later. Here is what has been delivered so far, anything with a "Y" has been delivered, anything without is stalled because of the bad email address which doesn't allow the mailserver to continue. <and here, he inserted a list of email addresses from the list, each prefaced with either YY, YN, NY, or NN> <I presume he's getting this from (hopefully appropriate) log.> <He even suggested I check email addresses at http://www.dnsreport.com (which I have, although I had already checked one by one to be sure the addresses were correctly entered. I have most of them in a contact list and so there was little doubt in my mind of their accuracy.)> **** Web service provider's suggestions end here ... So, my Question(1): Is it normal to expect a substantial amount of non-delivery to valid email addresses? I would presume, "No." But, in case I'm really missing the obvious, here, please enlighten me. Question (2): Is it normal for Mailman to "stall", or "stop" processing the rest of a list because of one bad email? (I'm asking that somewhat rhetorically, expecting an emphatic "NO" answer.) Question (3): Please explain the YY, YN, NY, and NN indicators [preceding the email addresses] from the above referenced log. I understand that YY means the email was delivered to the recipient, and NN means the email was NOT delivered to the recipient. But, YN and NY? maybe yes, maybe no? Question (4): Do you have further suggestions as to troubleshooting the reason that some of these addresses did not receive the email? Are there specific places (other logs in mailman) I should ask him to look that could give further information? Thank you for you help. Bruce

4 9

Re: [Mailman-Users] undelivered mail, but only to some
by D. Alan Stewart 01 Nov '06

01 Nov '06

Responding to Mark Sapiro: > If the sendmail log says the post is sent to the user in question, > Mailman delivered it to sendmail for the user, and it's not Mailman's > problem. I agree, it's not clear whether this is a sendmail or a Mailman problem. However, I have never, AFAIK, failed to receive an email from my provider's domain, unless that email originated from this specific Mailman list. That seems suspicious, doesn't it? Of course, I may be missing other emails that I am not aware of. Not getting something you did not know to expect is not an easy problem to trap. Since I now know that I am not receiving all emails from this list, possibly the problem is common but not often detected because the severity varies, list by list. > Mailman's 'smtp' log. This will tell you how many recipients the post > was sent to. My provider has checked Mailman's smtp log. It shows emails were sent to all subscribers. > Also check if the list is personalized. You may not even have > personalization options on your Non-digest options page which means > that OWNERS_CAN_ENABLE_PERSONALIZATION is not set to Yes in mm_cfg.py > and delivery is almost certainly not personailzed. I'm not certain, but I think this answers your question: the list does have digest options available to the users. > Check the settings of VERP_DELIVERY_INTERVAL and SMTP_MAX_RCPTS if any > in mm_cfg.py I looked, there are no settings for these in Mailman/mm_cfg.py. There don't appear to be any site-specific settings here. > You should also see this in the sendmail log, i.e. that the mail was > delivered to sendmail in one transaction. The provider has given me sendmail logs that I have analyzed. I was able to identify entries in the sendmail log that correspond with mailing list transmissions that were not received by the subscriber (me). > Sendmail claims it sent the mail to the users who didn't get it. I > recognize the symptoms say that Mailman is somehow involved, but I > don't see how. I recognize the difficulty of this particular problem. Thanks, Alan

2 1

IOError: Broken pipe on long mails
by Dan Young 31 Oct '06

31 Oct '06

Python version: python-2.3.4-14.3 Mailman version: mailman-2.1.5.1-34.rhel4.5 I've been getting a broken pipe error when sending log mails (usually triggered by those with attachments) through SMTPDirect (DELIVERY_MODULE = 'Sendmail' delivers, but obviously is not preferred): Oct 30 12:59:13 2006 (25556) Low level smtp error: [Errno 32] Broken pipe, msgid: <4546679E.5030804(a)mesd.k12.or.us> Watching the local MTA, I can see the connection time out 300 seconds after the connection is opened. I'm able to trigger a similar broken pipe error trying to unpickle the queued message (/root/test.pck is a copy of a pickled message): # /usr/lib/mailman/bin/show_qfiles /root/test.pck | head ====================> /root/test.pck Return-Path: <dyoung(a)mesd.k12.or.us> X-Original-To: xxxxxxx(a)xxxxxxxx.k12.or.us Delivered-To: xxxxxxx(a)xxxxxxxx.k12.or.us Received: from mrelay-i2.mesd.k12.or.us (mrelay-i2.mesd.k12.or.us [198.236.68.99]) by xxxx.xxxxxxxxx.k12.or.us (Postfix) with ESMTP id 205A370C0AF for <xxxxxxx(a)xxxxxxxx.k12.or.us>; Thu, 26 Oct 2006 15:29:39 -0700 (PDT) Traceback (most recent call last): File "/usr/lib/mailman/bin/show_qfiles", line 74, in ? main() File "/usr/lib/mailman/bin/show_qfiles", line 69, in main sys.stdout.write(fp.read()) IOError: [Errno 32] Broken pipe I can suppress the IOError by patching show_qfiles: 21a22,24 > import signal > signal.signal(signal.SIGPIPE, signal.SIG_DFL) > Any way I can get mailman to close the connection to the MTA, short of "pass"ing on except IOError? -- Dan Young <dyoung(a)mesd.k12.or.us> Multnomah ESD - Technology Services 503-257-1562

1 0

Re: [Mailman-Users] rename mailman hostname
by mardin＠comcast.net 31 Oct '06

31 Oct '06

Mark , In my Defaults.py: $ more Defaults.py DEFAULT_EMAIL_HOST = 'mailman_server1.admin.net' DEFAULT_URL_HOST = 'mailman_server1.admin.net' Since I need to rename hostname to mailman_server2.admin.net, I have to change it in mm_cfg.py. Thanks for your explanation, I will add these two lines to mm_cfg.py as follows: DEFAULT_EMAIL_HOST = 'mailman_server2.admin.net' DEFAULT_URL_HOST = 'mailman_server2.admin.net' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_URL_PATTERN = 'https://%s/mailman/' Thanks for your help! Mardin -------------- Original message ---------------------- From: Mark Sapiro <msapiro(a)value.net> > mardin(a)comcast.net wrote: > > > >My question is how to use the following two lines: > > > >VIRTUAL_HOSTS.clear() > >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > > > >For our case, is it necessary to add the above two lines? When I did a quick > test, the mailman server was working without adding these two lines. > > It depends on what you're doing and what's in Defaults.py. If the > settings in Defaults.py for DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST > are correct, then you don't need the two lines in mm_cfg.py (and you > also don't need to set DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in > mm_cfg.py). > > If the settings in Defaults.py for DEFAULT_URL_HOST and/or > DEFAULT_EMAIL_HOST need changing in mm_cfg.py, then you also need the > two above lines. This affects mostly creation of new lists, but also > fix_url and the domain of the site email address on the listinfo pages > and some other places. > > -- > Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

1 0

Re: [Mailman-Users] rename mailman hostname
by mardin＠comcast.net 31 Oct '06

31 Oct '06

Mark, You are great! It works now! If renaming the mailman (2.1.5) hostname from mailman_server1.admin.net to mailman_server2.admin.net, I know that I have to modify and add the following three lines: # vi mm_cfg.py DEFAULT_EMAIL_HOST = 'mailman_server2.admin.net' DEFAULT_URL_HOST = 'mailman_server2.admin.net' DEFAULT_URL_PATTERN = 'https://%s/mailman/' My question is how to use the following two lines: VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) For our case, is it necessary to add the above two lines? When I did a quick test, the mailman server was working without adding these two lines. Thanks, Mardin -------------- Original message ---------------------- From: Mark Sapiro <msapiro(a)value.net> > mardin(a)comcast.net wrote: > > > >After I used URL of https://mailman_server2.admin.net/mailman/admin/, I could > log in the list successfully. But I could not modify the contents of > configurations and do other administration work. When I tried to submit the > changes, I got the following message: > > > >"Although this page is encrypted, the information you have entered is to be > sent over an unencrypted connection and could easily be read by a third party. > >Are you sure you want to continue sending this information? -> Continue" > > > >After I clicked the Continue Botton, nothing changed about the list. > > > >I did add the "DEFAULT_URL_PATTERN = 'http://%s/mailman/'" to mm_cfg.py and > restart mailman. Did I miss some steps for renaming the mailman hostname? > > If you want to use SSL, you should set > > DEFAULT_URL_PATTERN = 'https://%s/mailman/' > > and then run fix_url again. Also see > <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.045.htp>. > > -- > Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

2 1

sendigest error
by Kory Wheatley 31 Oct '06

31 Oct '06

I receive the following error when the below cron job is ran, or just running it from the command line. Any suggestion on what would fix this issue? Do I have a bad digest.mbox somewhere? /usr/local/bin/python -S /home/mailman/cron/senddigests Traceback (most recent call last): File "/home/mailman/cron/senddigests", line 94, in ? main() File "/home/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/home/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 315, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 299, in process url = save_attachment(mlist, part, dir) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 411, in save_attachment filename = Utils.oneline(msg.get_filename(''), lcset) File "/home/mailman/pythonlib/email/Message.py", line 724, in get_filename filename = self.get_param('filename', missing, 'content-disposition') File "/home/mailman/pythonlib/email/Message.py", line 607, in get_param for k, v in self._get_params_preserve(failobj, header): File "/home/mailman/pythonlib/email/Message.py", line 554, in _get_params_preserve params = Utils.decode_params(params) File "/home/mailman/pythonlib/email/Utils.py", line 337, in decode_params charset, language, value = decode_rfc2231(EMPTYSTRING.join(value)) File "/home/mailman/pythonlib/email/Utils.py", line 284, in decode_rfc2231 charset, language, s = parts ValueError: unpack list of wrong size

2 1