[Mailman-Users] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
Hi, I'm currently having a problem with Mailman 2.1.8 and Exim 4.62 on the 64-bit version of Fedora Core 5. Exim is set up as per the Exim+Mailman FAQ on www.exim.org, and everything appears to be working fine from Exim's point of view: Jun 22 14:59:37 shinobu exim[15144]: 2006-06-22 14:59:37 1FtPib-0003wG-Eo = [EMAIL PROTECTED] H=mail-gw2.york.ac.uk [144.32.128.247] P=esmtp S=1062 [EMAIL PROTECTED] Jun 22 14:59:37 shinobu exim[15145]: 2006-06-22 14:59:37 1FtPib-0003wG-Eo = alcuinstycs [EMAIL PROTECTED] R=mailman_router T=mailman_transport Jun 22 14:59:37 shinobu exim[15145]: 2006-06-22 14:59:37 1FtPib-0003wG-Eo Completed Mailman also appears to receive the message (it appears in the archive), but then the message appears to disappear, it doesn't get forwarded to any of the list members, it doesn't appear in the mod queue, and none of the logfiles show anything regarding that message at all. I have a feeling I'm missing something obvious here. I can't see anything in the list archives or in the documentation/FAQs that describes this situation. Any advice would be fantastic! :) Thanks, Chris Northwood. -- 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] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
On 6/22/06, Chris Northwood [EMAIL PROTECTED] wrote: I have a feeling I'm missing something obvious here. I can't see anything in the list archives or in the documentation/FAQs that describes this situation. Any advice would be fantastic! :) The FAQ in question is pretty simplistic. In particular, it doesn't seem to cover configuring Mailman's outgoing SMTP settings. Can you double-check your configuration (and post it to the list)? The relevent settings are: DELIVERY_MODULE = 'SMTPDirect' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib (these are the defaults, I believe, which ought to work as long as Exim is configured to accept mail on SMTP from localhost.) If these settings seem sane, something else is the problem. Please see: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp -- - Patrick Bogen -- 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] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
-Original Message- From: Patrick Bogen [mailto:[EMAIL PROTECTED] Sent: 22 June 2006 17:23 To: Chris Northwood Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails? On 6/22/06, Chris Northwood [EMAIL PROTECTED] wrote: I have a feeling I'm missing something obvious here. I can't see anything in the list archives or in the documentation/FAQs that describes this situation. Any advice would be fantastic! :) The FAQ in question is pretty simplistic. In particular, it doesn't seem to cover configuring Mailman's outgoing SMTP settings. Can you double-check your configuration (and post it to the list)? The relevent settings are: DELIVERY_MODULE = 'SMTPDirect' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib These settings weren't set in mm_cfg.py, but in Defaults.py. I've put them in mm_cfg.py too, but no luck. (these are the defaults, I believe, which ought to work as long as Exim is configured to accept mail on SMTP from localhost.) If these settings seem sane, something else is the problem. Please see: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp I've already seen that page, and other than flagging up some incorrect permissions, nothing solved it. I live in the If you get no posts but you do get some notifications camp, so Mailman must be communicating with Exim somehow. I'm at a total loss as to what's going wrong, especially as the logs are showing nothing, but Exim is saying completed. -- - Patrick Bogen Thanks again, Chris Northwood. -- 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] Mailman and Exim on Fedora Core 5 doesn'tappear to deliver mails?
Chris Northwood wrote: These settings weren't set in mm_cfg.py, but in Defaults.py. I've put them in mm_cfg.py too, but no luck. If you put the same setting from Defaults.py into mm_cfg.py, it doesn't make any difference as you are just redefing something with the same value it already had. I'm at a total loss as to what's going wrong, especially as the logs are showing nothing, but Exim is saying completed. The posts get to Mailman and past any moderation or other holds because they're in the archive. You need to look in the Mailman log files error, smtp and smtp-failure for more information. -- 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] Mailman and Exim on Fedora Core 5 doesn'tappear to deliver mails?
Chris Northwood I've looked in these files, but they're not giving me any information whatsoever, just errors occuring at totally different times and unrelated to the mail message. Most of the errors are due to a misconfiguration when setting up my initial mail list. And just so you don't think I'm being thick, yes, Mailman is running. Well, posts are getting to the archive so IncomingRunner and ArchRunner must be running, but what about OutgoingRunner? The messages must still be queued in Mailman somewhere. What's in the queues? (qfiles/*). -- 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] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
On 6/22/06, Chris Northwood [EMAIL PROTECTED] wrote: I live in the If you get no posts but you do get some notifications camp, so Mailman must be communicating with Exim somehow. I'm at a total loss as to what's going wrong, especially as the logs are showing nothing, but Exim is saying completed. Is delivery enabled on all your users? What do the Mailman logs say? (How many deliveries attempted? How many does it think were successful?) Could this be filtering, somewhere? (Your end, on the destination's end?) -- - Patrick Bogen -- 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] Mailman and Exim on Fedora Core 5 doesn'tappear to deliver mails?
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: 22 June 2006 18:47 To: Chris Northwood; 'Mark Sapiro' Cc: Mailman Users Subject: RE: [Mailman-Users] Mailman and Exim on Fedora Core 5 doesn'tappear to deliver mails? Chris Northwood I've looked in these files, but they're not giving me any information whatsoever, just errors occuring at totally different times and unrelated to the mail message. Most of the errors are due to a misconfiguration when setting up my initial mail list. And just so you don't think I'm being thick, yes, Mailman is running. Well, posts are getting to the archive so IncomingRunner and ArchRunner must be running, but what about OutgoingRunner? $ ps aux | grep qrunner mailman 19022 0.0 1.6 106984 8324 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 19023 0.0 1.1 104828 5880 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 19024 0.0 1.2 104776 6268 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 19025 0.0 1.4 105112 7136 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 19026 0.0 1.5 104788 7568 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 19027 0.0 1.5 104988 7696 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 19028 0.0 1.3 104820 6624 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 19029 0.0 1.2 104824 6332 ?S15:29 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s Which seems to be everything The messages must still be queued in Mailman somewhere. What's in the queues? (qfiles/*). There appears to be absolutely nothing. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Chris Northwood. -- 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] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: 22 June 2006 21:40 To: Chris Northwood Cc: 'Mailman Users' Subject: RE: [Mailman-Users] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails? *snip* Yes, that's all the runners. So let me confirm: You send a post. It gets archived. It does not get sent to list members. All the qfiles/*/ directories are empty. There's nothing relevant in Mailman's error, smtp or smtp-failure logs. If this is correct, and if you are looking at the correct logs, the only thing that can cause this are there are no list members who are eligible to receive this post, because They are digest subscribers, Those that aren't are the poster with 'not metoo' checked or are direct To: or Cc: recipients with 'no dups' checked or are not subscribed to the Topic that this post matches or haven't selected 'receive messages that do not match any topic'. Other possibilities are that you are mistaken about nothing relevant in the logs or you are not looking at the logs that Mailman is actually writing (check LOG_DIR in mm_cfg.py/Defaults.py) If the message reached the archive and if DELIVERY_MODULE is 'SMTPDirect' (the default) and if the default SMTP_LOG_* settings haven't been overridden, and if the message is not in the 'out' queue, there has to be an entry in the post log and one in the smtp log unless the message had no recepients. Heh, I knew it'd be something simple. Instead of disabling the ability for people to be able to sign up to digests, I disabled the ability to be able to sign up to non-digests, hence everyone was put on digest mode. Ah well, cheers for the help everyone! -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Chris Northwood. -- 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] Mailman and Exim on Fedora Core 5 doesn't appear to deliver mails?
On 6/22/06 9:51 AM, Chris Northwood [EMAIL PROTECTED] wrote: I'm at a total loss as to what's going wrong, especially as the logs are showing nothing, but Exim is saying completed. You've solved the problem, and the completed wasn't related to the problem, so this is just a note. Exim's completed doesn't necessarily mean I've delivered this. It means I've done everything I'm ever going to do with this. --John -- 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] mailman (+vexim +exim) -- web interface uses absolute urls... to elsewhere
my original missive should've been more thorough. i can see that now. :) On 5/9/06, Richard Barrett [EMAIL PROTECTED] wrote: On 9 May 2006, at 04:16, will trillich wrote: On 5/8/06, Patrick Bogen [EMAIL PROTECTED] wrote: Check your setting in DEFAULT_URL_PATTERN. See FAQ 4.29: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp thanks for the pointer. turns out, ours is set exactly right. it's perfectly fine. according to http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp we can plop 'https://%s/mailman' into DEFAULT_URL_PATTERN and it'll determine where the links go when creating those cursed (and unnecessarily) absolute urls. but it's still not cooperating. it's IGNORING that variable. during execution, that variable is parsed, because if we take out the %s it dies a painful python death. but so long as it has %s then the rest of the string does not matter, and we get redirected to our alternative virtual site no matter what. since DEFAULT_URL_HOST didn't appear to be used in the final analysis, we tried DEFAULT_URL instead (with the short-circuit approach, it would override). alas, no luck. DEFAULT_URL_HOST is definitely NOT what determines the links we're having trouble with. If you want https for everything then follow the link from: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp apache is serving up secure https just fine. we've got that part covered. okay, just to be sure that DEFAULT_URL_PATTERN is referenced SOMEWHERE, we changed it to 'bad-url-pattern' and sure enough, it bombs out with a serious python error (no %s in the string for the argument passed to the '%' operator). so we changed it to 'where%s the beef?' and then everything worked just fine. all links STILL pointed to the other (wrong) virtual site, without secure https. plus, forms are also sent in the clear, to the wrong site. NO absolute links should be working at all in that case, right? IF the variable were being used, that is. it's clearly NOT being used in generating these links. i'm very new to python (coupla hours, now) -- so following library and module calls is quite alien to me. any chance i could munge the href-generator algorithm to generate relative links? absolute links are handy when taking cross-site jumps into account as a possibility -- but with cookies and authentication that would be counter productive anyway. links should look like ../../other/path NOT http://proper.server.name/on/a/good/day/other/path at the very least, if we're going to insist on an absolute website for the html doc, it should be placed in the base tag, and then all the other links should STILL be relative. If you diligently follow _all_ the instructions in the FAQ entries, including the comments regarding virtual hosts, the VIRTUAL_HOSTS Python dictionary, restarting mailmanctl and judicious use of is it simple to dump the virtual_hosts dictionary? maybe there's something in there that we don't want. better, would be to massage the href-generator routine. fix_url for existing lists you will get a consistent set of appropriate URLs produced on the MM web GUI. You also need to read the bin/newlist usage to understand the way that you can assign new lists to web and email hosts when creating them which again links to the understanding and setup of VIRTUAL_HOSTS Python dictionary in mm_cfg.py. Also, if you find yourself fooling with the list's host_name attribute through the admin GUI Host name this list prefers for email option then it is probably time to stop and review you mm_cfg entries etc. don't mean to sound too grumpy, but i think i've been pretty diligent. and we don't have any existing lists yet, as we're still trying to get this bad boy to straighten up and fly right. if we can have DEFAULT_URL_PATTERN set to ?x:%s:z! and the site still works, then there's something very very wrong under the hood. (could be MY hood, sure, but the point stands. :) your talking from the perspective that it's working sanely. my debian setup is currently not aligned with your paradigm, but i'd love it if it were. :) -- will trillich Their is five errers in this sentance. -- 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] mailman (+vexim +exim) -- absolute links are per LIST, not per SERVER -- SOLVED
On 5/10/06, Richard Barrett [EMAIL PROTECTED] wrote: You can examine a list's attributes by running the bin/withlist script from the command line as follows: [mailman!/mailman/solaris-run/mailman]:bin/withlist -i rbtesth Loading list rbtesth (unlocked) The variable `m' is the rbtesth MailList instance print m.web_page_url snip i got it to work like this, instead: # bin/withlist -l -r bin/fix_url.fix_url test Importing bin/fix_url... Running bin/fix_url.fix_url()... Loading list test (locked) Saving list Finalizing # bin/withlist -i test Loading list test (unlocked) The variable `m' is the test MailList instance print m.web_page_url https://emailadmin.mysite.com/ so even tho grrwe've got absolute urls/grr, i think they'll be pointing to the right place. thanks for your sisyphean attention to detail and for putting up with my inane ignorance! i'll go away now and leave you to get back to more intelligent questions. :) -- will trillich Their is five errers in this sentance. -- 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] mailman (+vexim +exim) -- absolute urls, stored WITH THE LIST
On 5/10/06, Michael Best [EMAIL PROTECTED] wrote: I'm using vexim + exim and I'm using DEFAULT_URL_PATTERN = 'https://%s/mailman/' in my mm_cfg.py and I'm not haivng any problems. finally got it figured out, thanks to the unrelenting patience of R.B. -- i had been thinking that DEFAULT_URL_PATTERN was a server-specific setting, but it's not. it gets copied into the list config, so that if you change the value later, the list still has its previous value, and mailman enforces it ruthlessly! caught me off guard, i was expecting either the apache daemon or the mailman daemon to have the server setting. i'm feeling much better now. :) probably drove Richard to drink. -- will trillich Their is five errers in this sentance. -- 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] mailman (+vexim +exim) -- absolute urls, stored WITH THE LIST
At 4:36 PM -0500 2006-05-10, will trillich wrote: i'm feeling much better now. :) probably drove Richard to drink. Since this issue is fresh in your mind, it would probably be a good idea to capture your experience in the FAQ Wizard on this subject. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- 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] mailman (+vexim +exim) -- web interface uses absolute urls... to elsewhere
On 9 May 2006, at 04:16, will trillich wrote: On 5/8/06, Patrick Bogen [EMAIL PROTECTED] wrote: On 5/7/06, will trillich [EMAIL PROTECTED] wrote: any ideas? Check your setting in DEFAULT_URL_PATTERN. See FAQ 4.29: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp thanks for the pointer. turns out, ours is set exactly right. it's perfectly fine. even so, check out Mailman/MailList.py, inside InitVars (and mentioned in /usr/lib/mailman/Mailman/Defaults.py): self.web_page_url = ( mm_cfg.DEFAULT_URL or mm_cfg.DEFAULT_URL_PATTERN % mm_cfg.DEFAULT_URL_HOST) This is a red herring because the value assigned in InitVars is only transient while the object is being created. Shortly after this assignment it is replaced with the stored value recovered from the list's config-stored-on-disk for an existing lists or by assignment when a new list is being created, per the comment Assign default values - some will be overriden by stored state at the head of InitVars. since DEFAULT_URL_HOST didn't appear to be used in the final analysis, we tried DEFAULT_URL instead (with the short-circuit approach, it would override). alas, no luck. all links from site/cgi-bin/mailman/admin/list are absolute links, pointing to another virtual host we've got on this server. there's GOT to be a way to make them relative -- we don't want to submit POST forms via insecure http (to the wrong site) from our secure https page! Looking back at your original posting, you were setting DEFAULT_HOST_NAME and DEFAULT_URL both of which are obsolete, only honoured for legacy/update installations, and should have the value None (the default in Defaults.py). Stop fooling with them, it is only confusing the issue. btw: If your are trying to have a mix of http URLs for non-admin GUI and and https for admin GUI then you are wasting your time, it is all or nothing, one or the other. Same rule applies regarding which host is used for a list admin or no-admin web GUI, same one for all. If you want https for everything then follow the link from: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp to: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.027.htp e.g. site for mail is 'mail.myexample.not'. that's where the MX points for smtp, and that's where webmail will be hosted for user pick-up (or imaps or pop3s). to administer this puppy, we've got 'emailadmin.myexample.not' which has vexim and mailman running on it. but ALL links on the admin pages -- including form actions -- hop from 'https://emailadmin.myexample.not' to 'http://mail.myexample.not'. it's maddening! If you diligently follow _all_ the instructions in the FAQ entries, including the comments regarding virtual hosts, the VIRTUAL_HOSTS Python dictionary, restarting mailmanctl and judicious use of fix_url for existing lists you will get a consistent set of appropriate URLs produced on the MM web GUI. You also need to read the bin/newlist usage to understand the way that you can assign new lists to web and email hosts when creating them which again links to the understanding and setup of VIRTUAL_HOSTS Python dictionary in mm_cfg.py. Also, if you find yourself fooling with the list's host_name attribute through the admin GUI Host name this list prefers for email option then it is probably time to stop and review you mm_cfg entries etc. -- will trillich Their is five errers in this sentance. -- 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/ r.barrett%40openinfo.co.uk Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? req=showamp;file=faq01.027.htp -- 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] mailman (+vexim +exim) -- web interface uses absolute urls... to elsewhere
On 5/9/06, Richard Barrett [EMAIL PROTECTED] wrote: btw: If your are trying to have a mix of http URLs for non-admin GUI and and https for admin GUI then you are wasting your time, it is all or nothing, one or the other. Same rule applies regarding which host is used for a list admin or no-admin web GUI, same one for all. ah. If you want https for everything then follow the link from: http://www.python.org/cgi-bin/faqw-mm.py?req=3Dshowfile=3Dfaq04.029.htp to: http://www.python.org/cgi-bin/faqw-mm.py?req=3Dshowfile=3Dfaq04.027.htp e.g. site for mail is 'mail.myexample.not'. that's where the MX points for smtp, and that's where webmail will be hosted for user pick-up (or imaps or pop3s). to administer this puppy, we've got 'emailadmin.myexample.not' which has vexim and mailman running on it. but ALL links on the admin pages -- including form actions -- hop from 'https://emailadmin.myexample.not' to 'http://mail.myexample.not'. it's maddening! If you diligently follow _all_ the instructions in the FAQ entries, including the comments regarding virtual hosts, the VIRTUAL_HOSTS Python dictionary, restarting mailmanctl and judicious use of fix_url for existing lists you will get a consistent set of appropriate URLs produced on the MM web GUI. You also need to read the bin/newlist usage to understand the way that you can assign new lists to web and email hosts when creating them which again links to the understanding and setup of VIRTUAL_HOSTS Python dictionary in mm_cfg.py. Also, if you find yourself fooling with the list's host_name attribute through the admin GUI Host name this list prefers for email option then it is probably time to stop and review you mm_cfg entries etc. thanks for the pointers. got lots to chew on, thanks! -- will trillich Their is five errers in this sentance. -- 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] mailman (+vexim +exim) -- web interface uses absolute urls... to elsewhere
On 5/7/06, will trillich [EMAIL PROTECTED] wrote: any ideas? Check your setting in DEFAULT_URL_PATTERN. See FAQ 4.29: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp -- - Patrick Bogen -- 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] mailman (+vexim +exim) -- web interface uses absolute urls... to elsewhere
after many, many iterations and googling left and right, we've finally made some progress on our email setup -- but mailman's web interface keeps generating absolute links off-site! including the form submits... not good! - debian (testing/unstable) - exim4-daemon-heavy (4.61-1 via apt-get) - mailman (2.1.7-2.1.8rc1-1 via apt-get) - vexim (downloaded installed 2.0.1) all's well EXCEPT... within the web interface for mailman (http://site.name/cgi-bin/mailman/*) ALL admin links are absolute, and point to a DIFFERENT virtual host on the same server. it's all written in python, and from what i can tell the culprit is in ScriptURL inside Mailman/Utils.py: in particular, when viewing https://site.name/cgi-bin/mailman/admin/test to administer the TEST list, all links are absolute, pointing to http://other.site/cgi-bin/mailman/admin/test/* -- no https, and on to a different web server. things we tried, to make the URLs link relative to the current host, current protocol, and current request-path: we added DEFAULT_HOST_NAME = 'site.name' DEFAULT_URL = 'https://site.name' to /etc/mailman/mm_cfg.py (after seeing the comments in /usr/lib/mailman/Mailman/Default.py and confirming it in MailList.py) to no effect. [maybe the python files aren't being recompiled? timestamps indicate .pyc are being recompiled from the .py files.] we ran 'hostname site.name' to fix it in ram, and then restarted mailman, exim, and apache. no good. we reset /etc/hostname and rebooted the computer, no good. it's almost as if the other site name is hard-wired into the code, but of course that's ludicrous, as it's another virtual host on the same machine. how do we get relative links? any ideas? -- 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] mailman (+vexim +exim) -- web interface uses absolute urls... to elsewhere
On 5/8/06, Patrick Bogen [EMAIL PROTECTED] wrote: On 5/7/06, will trillich [EMAIL PROTECTED] wrote: any ideas? Check your setting in DEFAULT_URL_PATTERN. See FAQ 4.29: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp thanks for the pointer. turns out, ours is set exactly right. it's perfectly fine. even so, check out Mailman/MailList.py, inside InitVars (and mentioned in /usr/lib/mailman/Mailman/Defaults.py): self.web_page_url = ( mm_cfg.DEFAULT_URL or mm_cfg.DEFAULT_URL_PATTERN % mm_cfg.DEFAULT_URL_HOST) since DEFAULT_URL_HOST didn't appear to be used in the final analysis, we tried DEFAULT_URL instead (with the short-circuit approach, it would override). alas, no luck. all links from site/cgi-bin/mailman/admin/list are absolute links, pointing to another virtual host we've got on this server. there's GOT to be a way to make them relative -- we don't want to submit POST forms via insecure http (to the wrong site) from our secure https page! e.g. site for mail is 'mail.myexample.not'. that's where the MX points for smtp, and that's where webmail will be hosted for user pick-up (or imaps or pop3s). to administer this puppy, we've got 'emailadmin.myexample.not' which has vexim and mailman running on it. but ALL links on the admin pages -- including form actions -- hop from 'https://emailadmin.myexample.not' to 'http://mail.myexample.not'. it's maddening! -- will trillich Their is five errers in this sentance. -- 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] mailman wrappen+exim 4.22
hello. i have installed mailman 2.0.11-1woody8 from debian. MM working under exim
4.22, and working correctly except one thing.
i got a message from wrapper with error code 6, and message in syslog listed below
Mailman mail-wrapper: Illegal command: admin
this message appears, when coming mail to '[EMAIL PROTECTED]'.
exim debug show, that wrapper run with following arguments:
14:58:36 10644 direct command after expansion:
14:58:36 10644 argv[0] = /var/lib/mailman/mail/wrapper
14:58:36 10644 argv[1] = admin
14:58:36 10644 argv[2] = news
so, this something like wrapper admin news. this configuration i got from internet,
and do not sure in it cleaness. so, what i need to seng via arguments to wrapper, when
mail to listname-admin received? may be i dont need to route mail to admins via
mailman router?
configuration:
-
MAILMAN_HOME=/var/lib/mailman
# wrapper script for mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper
# user and group for mailman
MAILMAN_USER=list
MAILMAN_GROUP=daemon
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.db
local_part_suffix_optional
local_part_suffix = -bounces : -bounces+* : -confirm+* : -join : -leave : -owner :
-request: -admin
transport = mailman_transport
mailman_transport:
driver = pipe
command = MAILMAN_WRAP '${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} {post}}' $local_part
current_directory = MAILMAN_HOME
home_directory = MAILMAN_HOME
user = MAILMAN_USER
group = MAILMAN_GROUP
--
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] mailman wrappen+exim 4.22
At 3:24 PM +0400 2004-06-08, vlad f halilow wrote: hello. i have installed mailman 2.0.11-1woody8 from debian. MM working under exim 4.22, and working correctly except one thing. Hmm. Have you seen the pages linked from http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.019.htp? My understanding is that the documentation at exim.org assumes you're using Mailman 2.1.x with Exim 4.x, or Mailman 2.0.x with Exim 3.x. I don't know if they've got anything for people using an older version of Mailman with the recent version of Exim. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. SAGE member since 1995. See http://www.sage.org/ for more info. -- 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 wrapper + exim 4.22
hello. i have installed mailman 2.0.11-1woody8 from debian. MM working under exim
4.22, and working correctly except one thing.
i got a message from wrapper with error code 6, and message in syslog listed below
Mailman mail-wrapper: Illegal command: admin
this message appears, when coming mail to '[EMAIL PROTECTED]'.
exim debug show, that wrapper run with following arguments:
14:58:36 10644 direct command after expansion:
14:58:36 10644 argv[0] = /var/lib/mailman/mail/wrapper
14:58:36 10644 argv[1] = admin
14:58:36 10644 argv[2] = news
so, this something like wrapper admin news. this configuration i got from internet,
and do not sure in it cleaness. so, what i need to seng via arguments to wrapper, when
mail to listname-admin received? may be i dont need to route mail to admins via
mailman router?
configuration:
-
MAILMAN_HOME=/var/lib/mailman
# wrapper script for mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper
# user and group for mailman
MAILMAN_USER=list
MAILMAN_GROUP=daemon
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.db
local_part_suffix_optional
local_part_suffix = -bounces : -bounces+* : -confirm+* : -join : -leave : -owner :
-request: -admin
transport = mailman_transport
mailman_transport:
driver = pipe
command = MAILMAN_WRAP '${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} {post}}' $local_part
current_directory = MAILMAN_HOME
home_directory = MAILMAN_HOME
user = MAILMAN_USER
group = MAILMAN_GROUP
--
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 and Exim Problems!
Is anyone else have trouble with MailMan and Exim? I cannot get the headers or footers to be sent with the email? I have a longer list of issues, but I thought I would see if anyone has these same problems? Thank You, Chad McCan Blue Virtual Webhosting www.BlueVirtual.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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman and exim problem (relay trouble)
I wrote re: qrunner not delivering on 24 October 01: Jon Carnes wrote on 24 October 01: In you ~mailman/Mailman/mm_cfg.py and Defaults.py what is the value of your Delivery defaults? They aren't declared in mm_cfg.py, and the Defaults.py are, as I've been instructed, untouched. I changed SMTPHOST to 'lithchat.com' and now it seems to be delivering--oops, except now I'm having relaying problems. Now this is perplexing me, too, and I thought I'd ask here before I moved on to the exim mailing list. In my exim.conf, I have this: local_domains = 192.168.0.6:127.0.0.1:lithchat.com relay_domains = *.lithchat.com Now, here is the error I get in ~mailman/logs/smtp-failure: Oct 26 17:48:58 2001 (2789) delivery to [EMAIL PROTECTED] failed with code 550: 5.7.1 [EMAIL PROTECTED]... Relaying denied. IP name lookup failed [192.168.0.6] I've been getting this error forever, and cannot figure out why on earth it simply refuses to relay for mailman *only* ideas? I know I'm not the only person on this list who uses exim... --m -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim problem (qrunner not delivering)?
I've since upgraded to 2.1a3, to see if that would fix things. First, the README.EXIM has to be changed to look for config.pck instead of config.db (or else messages won't even get out the starting gate)--at least, that's what I had to do. Next, I'm still getting the same problems as before--messages get into the qfiles directory and then just sit there. Oct 24 02:54:33 2001 (28401) delivery to [EMAIL PROTECTED] failed with code -1: ignore is an example of the line I get in smtp-failure. Any hints? thanks, --m -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim problem (qrunner not delivering)?
Next, I'm still getting the same problems as before--messages get into the qfiles directory and then just sit there. Oct 24 02:54:33 2001 (28401) delivery to [EMAIL PROTECTED] failed with code -1: ignore is an example of the line I get in smtp-failure. In you ~mailman/Mailman/mm_cfg.py and Defaults.py what is the value of your Delivery defaults? === # # Delivery defaults # # Delivery module for the message pipeline. See # Mailman/Handlers/HandlerAPI.py for details. Unless overridden specifically # in that module, this handler is used for message delivery to the list, and # to an individual user. This value must be a string naming a module in the # Mailman.Handlers package. # # SECURITY WARNING: The Sendmail module is not secure! Please read the # comments in Mailman/Handlers/Sendmail.py for details. Use at your own # risk. # #DELIVERY_MODULE = 'Sendmail' DELIVERY_MODULE = 'SMTPDirect' # Ceiling on the number of recipients that can be specified in a single SMTP # transaction. Set to 0 to submit the entire recipient list in one # transaction. Only used with the SMTPDirect DELIVERY_MODULE. SMTP_MAX_RCPTS = 500 # Maximum number of simulatenous subthreads that will be used for SMTP # delivery. After the recipients list is chunked according to SMTP_MAX_RCPTS, # each chunk is handed off to the smptd by a separate such thread. If your # Python interpreter was not built for threads, this feature is disabled. You # can explicitly disable it in all cases by setting MAX_DELIVERY_THREADS to # 0. This feature is only supported with the SMTPDirect DELIVERY_MODULE. # # NOTE: This is an experimental feature and limited testing shows that it may # in fact degrade performance, possibly due to Python's global interpreter # lock. Use with caution. MAX_DELIVERY_THREADS = 0 # SMTP host and port, when DELIVERY_MODULE is 'SMTPDirect' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib # Command for direct command pipe delivery to sendmail compatible program, # when DELIVERY_MODULE is 'Sendmail'. SENDMAIL_CMD = '/usr/lib/sendmail' # Allow for handling of MTA-specific features (i.e. aliases). Most MTAs use # sendmail (including Sendmail, Postfix, and Exim). Qmail uses the qmail # style. MTA_ALIASES_STYLE = 'sendmail' -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim problem (qrunner not delivering)?
Jon Carnes wrote on 24 October 01: In you ~mailman/Mailman/mm_cfg.py and Defaults.py what is the value of your Delivery defaults? They aren't declared in mm_cfg.py, and the Defaults.py are, as I've been instructed, untouched. I changed SMTPHOST to 'lithchat.com' and now it seems to be delivering--oops, except now I'm having relaying problems. --m -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim problem (qrunner not delivering)?
M == Moacir [EMAIL PROTECTED] writes: M First, the README.EXIM has to be changed to look for config.pck M instead of config.db (or else messages won't even get out the M starting gate)--at least, that's what I had to do. Ah thanks, I've updated README.EXIM in cvs. M Next, I'm still getting the same problems as before--messages M get into the qfiles directory and then just sit there. M Oct 24 02:54:33 2001 (28401) delivery to M [EMAIL PROTECTED] failed with code -1: ignore M is an example of the line I get in smtp-failure. M Any hints? Looking at SMTPDirect.py gives a clue: if your smtp connection failed because of a low-level socket error, or any kind of SMTPException other than SMTPRecipientsRefused, we can't dig an smtp error code out of the exception, so we log it as error -1. I suspect that Mailman can't complete the socket connection to your MTA. -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Mailman and exim problem (qrunner not delivering)?
I somehow had this problem and posted about it several months ago. Back then, a complete reinstallation of mailman fixed the problem. This time, the reinstallation hasn't fixed anything. What follows will be a bunch of info from log files trying to follow a specific message. I don't know if this is an exim problem (I have also removed exim and reinstalled it) or a mailman problem. Elsewhere people seem to have the same problem with other MTAs (that I've found in web searches), and the response is always look in the MTA logs--well, I've included the full bulk of the MTA logs pertaining to the message I follow. So please let me know if there's anywhere else I can dig around for information to try and get down to the center of the problem Thanks, --m On a different machine, I do this: zuikis.uchicago.edu -20:22:57- ~ echo hi | mail [EMAIL PROTECTED] The following are commands run on the mailman server (and there was nothing appropriate in mailman/logs/error) lithchat.com:/mailman/logs# ../bin/version Using Mailman version 2.0.6 lithchat.com:/mailman/logs# uname -a Linux nida 2.2.19 #1 SMP An Rgp 14 21:36:28 CDT 2001 i586 unknown lithchat.com:/mailman/logs# exim -bV Exim version 3.32 #1 built 15-Aug-2001 00:13:26 Copyright (c) University of Cambridge 2001 lithchat.com:/mailman/logs# tail -2 /var/log/exim/mainlog 2001-10-22 20:22:32 15vqH2-0002FP-00 = [EMAIL PROTECTED] H=zuikis.uchicago.edu [128.135.57.157] P=esmtp S=490 [EMAIL PROTECTED] 2001-10-22 20:22:33 15vqH2-0002FP-00 = test [EMAIL PROTECTED] D=list_director T=list_transport 2001-10-22 20:22:33 15vqH2-0002FP-00 Completed lithchat.com:/mailman/logs# tail -1 post Oct 22 20:25:02 2001 (8668) post to test from [EMAIL PROTECTED], size=138, 1 failures lithchat.com:/mailman/logs# tail -1 smtp-failure Oct 22 20:25:02 2001 (8668) -1 [EMAIL PROTECTED] (ignore) lithchat.com:/mailman/logs# tail -2 smtp Oct 22 20:25:02 2001 (8668) All recipients refused: host not found Oct 22 20:25:02 2001 (8668) smtp for 1 recips, completed in 0.089 seconds lithchat.com:/mailman/logs# tail subscribe Oct 22 02:32:57 2001 (2363) test: new [EMAIL PROTECTED] lithchat.com:/mailman/logs# python -S ../cron/qrunner lithchat.com:/mailman/logs# tail -1 smtp-failure Oct 22 20:36:01 2001 (8744) -1 [EMAIL PROTECTED] (ignore) lithchat.com:/mailman/logs# tail -2 smtp Oct 22 20:36:01 2001 (8744) All recipients refused: host not found Oct 22 20:36:01 2001 (8744) smtp for 1 recips, completed in 0.086 seconds lithchat.com:/mailman/logs# tail -7 /var/log/exim/mainlog 2001-10-22 20:22:32 15vqH2-0002FP-00 = [EMAIL PROTECTED] H=zuikis.uchicago.edu [128.135.57.157] P=esmtp S=490 [EMAIL PROTECTED] 2001-10-22 20:22:33 15vqH2-0002FP-00 = test [EMAIL PROTECTED] D=list_director T=list_transport 2001-10-22 20:22:33 15vqH2-0002FP-00 Completed 2001-10-22 20:23:01 Start queue run: pid=8653 2001-10-22 20:23:01 End queue run: pid=8653 2001-10-22 20:38:01 Start queue run: pid=8757 2001-10-22 20:38:01 End queue run: pid=8757 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim problem (qrunner not delivering)?
Jon Carnes wrote on 22 October 01: Your DNS is improperly setup. There is no MX record for zuikis.uchicago.edu. Could be. Yet it worked before--and it wasn't a new version of mailman that caused the problem. I tried again using [EMAIL PROTECTED] as the sending address, and the errors are identical. It seems like DNS can't be the problem if a midway.uchicago.edu address works fine. (2001-10-22 22:33:53 15vsK9-0002Uj-00 = [EMAIL PROTECTED] H=midway.uchicago.edu [128.135.12.12] P=esmtp S=701 [EMAIL PROTECTED] 2001-10-22 22:33:54 15vsK9-0002Uj-00 = test [EMAIL PROTECTED] D=list_director T=list_transport 2001-10-22 22:33:54 15vsK9-0002Uj-00 Completed) nslookup Default Server: ns2.uchicago.edu Address: 128.135.12.73 set query=mx midway.uchicago.edu Server: ns2.uchicago.edu Address: 128.135.12.73 midway.uchicago.edu preference = 0, mail exchanger = midway.uchicago.edu [etc.] --m -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim problem (qrunner not delivering)?
Can't argue with that! Here's a long shot... On the Privacy Options page of the web Admin, try putting in the complete name of the mailing list into the field: Alias names (regexps) which qualify as explicit to or cc destination names for this list From the example below [EMAIL PROTECTED] It doesn't make any sense, but then neither does the error... On Monday 22 October 2001 23:42, Moacir wrote: Jon Carnes wrote on 22 October 01: Your DNS is improperly setup. There is no MX record for zuikis.uchicago.edu. Could be. Yet it worked before--and it wasn't a new version of mailman that caused the problem. I tried again using [EMAIL PROTECTED] as the sending address, and the errors are identical. It seems like DNS can't be the problem if a midway.uchicago.edu address works fine. (2001-10-22 22:33:53 15vsK9-0002Uj-00 = [EMAIL PROTECTED] H=midway.uchicago.edu [128.135.12.12] P=esmtp S=701 [EMAIL PROTECTED] 2001-10-22 22:33:54 15vsK9-0002Uj-00 = test [EMAIL PROTECTED] D=list_director T=list_transport 2001-10-22 22:33:54 15vsK9-0002Uj-00 Completed) nslookup Default Server: ns2.uchicago.edu Address: 128.135.12.73 set query=mx midway.uchicago.edu Server: ns2.uchicago.edu Address: 128.135.12.73 midway.uchicago.edu preference = 0, mail exchanger = midway.uchicago.edu [etc.] --m -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman and exim
[EMAIL PROTECTED] said: I'm installing mailman (from tarball) on a debian woody system running exim. I'm running into the "mail-gid" problem - exim complains that "Neither the system_aliases director nor the address_pipe transport set a uid for local delivery of..." I'm not a total exim newbie - I've mostly used sendmail. What gid should I use for this setup? Besides knowing that exim won't let you use root, there's no guidance I can find for the group to use. Its the gid you specified on the ./configure line - ie if you did ./configure --with-mail-gid=exim --with-cgi-gid=www then the gid you want is "exim" That then needs attaching to the aliases director, or alternative skip that stuff and go to http://www.exim.org/howto/mailman.html Nigel. -- [ Nigel Metheringham [EMAIL PROTECTED] ] [ Phone: +44 1423 85 Fax +44 1423 858866 ] [ - Comments in this message are my own and not ITO opinion/policy - ] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
