Re: [Mailman-Users] Confirmation and sent messages not
The esteemed Mark Sapiro has said: Jason Luck wrote: Why is the default in DaemonPortOptions set for 127.0.0.1 as opposed to a broader range? It would seem most folks would want to be able to external mail through their box and from what I'm learning would require the 127.0.0.1 to be changed. Also by changing this...does one open themselve up to security issues? These are good questions, but they are Sendmail questions. There are whole books (e.g. the 'bat' book) devoted to Sendmail, and I haven't read any of them. The important thing is to not be an open relay - i.e. only accept mail from outside for local delivery; do not accept mail from outside to be relayed to another outside location; only accept 'outside delivery' mail from the localhost. I would think that the default Sendmail configuration would not be an open relay, but I don't know. There are various services, e.g., http://www.abuse.net/relay.html, that will test to see if your server is an open relay. Speaking from the vantage point of a sendmail user, I think virtually all of the issues involving sendmail+Mailman are basic sendmail configuration issues. In short, that means that if sendmail+Mailman are not working properly, odds are that sendmail is not working properly with a simple MUA like elm or mutt. Test your configuration for both incoming mail from the Internet backbone and outgoing mail to it. If your Mailman installation is going to take mail to [EMAIL PROTECTED], then set up a local user account as [EMAIL PROTECTED] and use it to check out your sendmail installation. Once you have your sendmail working properly, Mailman is a very simple drop-in. The defaults in the distribution Defaults.py are correct for a simple sendmail configuration; you don't have to override anything in mm_cfg.py. One step that you do have to perform, that I do not see in Barry Warsaw's otherwise-excellent Mailman build-install manual is the need to add the Mailman address pipes to the sendmail aliases file, and run newaliases. This has to be done for each list. The aliases list that Mailman generates when you create a list is correct for sendmail; just copy it into the aliases file and run newaliases. Barry's manual does include a comprehensive and clear how-to on adding smrsh (sendmail restricted shell) for Mailman. However, you also have to add FEATURE(smrsh, /usr/lib/smrsh)dnl to your main.mc file and recompile. Don't try to manage sendmail by editing the .cf files. Use the .mc (and .m4) files for everything. You absolutly need to have the O'Reilly book Sendmail, commonly referred to as the bat book because it has a picture of a bat on the cover. The recent O'Reilly Sendmail 8.13 Companion is another must-have, and is valuable not only for the 8.13 references, but for a lot of information that clarifies thing about sendmail in general. The bat book is 1200 pages of information and nothing if not comprehensive. Additional resources are the Sendmail FAQ and the Usenet newsgroup comp.mail.sendmail. You'll get answers there AFTER you summarize your researches in the bat book and the FAQ. On relaying: the distribution sendmail sources should compile with all relaying disabled. If you are running a Solaris system with the Sun sendmail distribution, you have to change the DOMAIN statements in both main.mc and subsidiary.mc to DOMAIN(`solaris-antispam')dnl For reasons known only to $DEITIES, Sun distributes sendmail with relaying enabled. On any other installation, the bat book has a comprehensive section (several pages) on relaying, and it will tell you exactly what to check and how to turn on the relaying you need, if any. Virtually everything I've covered above is covered in the sendmail literature in copious detail. One additional comment that I haven't seen clearly outlined in any documentation, except perhaps the O'Reilly book DNS and BIND 5th edition (2006) is that sendmail is DNS-intensive. If you are running Mailman lists, you should have, at minimum, a caching DNS server on your local network. This is both a performance and a netiquette issue. In short, don't flood somebody else's DNS with your Mailman lookups, flood your own. For best performance, put a DNS server of some sort on the same box that is running Mailman. Hank -- 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] Confirmation and sent messages not
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 25, 2007, at 10:37 PM, [EMAIL PROTECTED] wrote: One step that you do have to perform, that I do not see in Barry Warsaw's otherwise-excellent Mailman build-install manual is the need to add the Mailman address pipes to the sendmail aliases file, and run newaliases. This has to be done for each list. The aliases list that Mailman generates when you create a list is correct for sendmail; just copy it into the aliases file and run newaliases. Thanks Hank. I haven't used Sendmail in 20 years, so if there is some specific text you'd like to see added (or preferably a patch to the latex file), please feel free to send it directly to me and I'll push up a doc update. Thanks, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBReJk/3EjvBPtnXfVAQK+TQQAuAc+w8c6aq1XcODoVjRPDPKJKimBITrU 0naOycJZRwC92a7IEiUymQexUHGoKMY39b8YwfdkioNis0I+xK1+ePZLCyFmX30+ h4ogtjbhHSbZqvnJWM+38iTINd6kbRHbe+P0gWAyKMxYcCUvv6dEDI/1V6kBNZqN Au9xQ9RDtxM= =Twl7 -END PGP SIGNATURE- -- 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] Confirmation and sent messages not
Jason Luck wrote: Why is the default in DaemonPortOptions set for 127.0.0.1 as opposed to a broader range? It would seem most folks would want to be able to external mail through their box and from what I'm learning would require the 127.0.0.1 to be changed. Also by changing this...does one open themselve up to security issues? These are good questions, but they are Sendmail questions. There are whole books (e.g. the 'bat' book) devoted to Sendmail, and I haven't read any of them. The important thing is to not be an open relay - i.e. only accept mail from outside for local delivery; do not accept mail from outside to be relayed to another outside location; only accept 'outside delivery' mail from the localhost. I would think that the default Sendmail configuration would not be an open relay, but I don't know. There are various services, e.g., http://www.abuse.net/relay.html, that will test to see if your server is an open relay. -- 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] Confirmation and sent messages not reaching end-user
SMTPHOST...in mm_cfg.py...no info on DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' If the above are actually indented, this is bad. They shouldn't be. Is this from mm_cfg.py or Defaults.py? Actually the text listed above on SMTP which was in section 4 of 3.14 FAQ is not listed in my mm_cfg.py...not there at all. Is this a problem? 6) Locks Can't find any locks folder under a mailman directory It's somewhere? Is there a setting for LOCK_DIR in mm_cfg.py? There is no setting for LOCK_DIR in the mm_cfg.py. I perform a locate on either LOCK or LOCK_DIR and the only LOCK I can find deal with items in an selinux area. Within the Mailman directory there is a LockFile.py, LockFile.pyc and LockFile.pyo 7) Logs more post Feb 21 18:30:00 2007 (6645) post to test from [EMAIL PROTECTED], size=1492, message-id=mailman.0.1172099747.6557.test @falconfootball.org, 1 failures And most important, what's in the smtp-failure log? Here is what the smtp-failure log is saying... more smtp-failure Feb 21 18:30:00 2007 (6645) Low level smtp error: (-2, 'Name or service not known'), msgid: [EMAIL PROTECTED] Feb 21 18:30:00 2007 (6645) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Feb 21 18:30:00 2007 (6645) Low level smtp error: (-2, 'Name or service not known'), msgid: [EMAIL PROTECTED] Feb 21 18:30:00 2007 (6645) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Feb 21 18:30:01 2007 (6645) Low level smtp error: (-2, 'Name or service not known'), msgid: [EMAIL PROTECTED] Feb 21 18:30:01 2007 (6645) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Feb 21 18:45:00 2007 (6645) Low level smtp error: (-2, 'Name or service not known'), msgid: [EMAIL PROTECTED] Feb 21 18:45:00 2007 (6645) delivery to [EMAIL PROTECTED] failed with code -1: (-2, 'Name or service not known') Feb 21 18:45:00 2007 (6645) Low level smtp error: (-2, 'Name or service not known'), msgid: [EMAIL PROTECTED] This goes on and on and on. To recap...I've created two lists to-date. mailman and test. I have not received confirmation emails about starting either list. Also, I joined the list *test* via the web-interface. I have not as the administrator of this list been given a notification to approve my acceptance to the list via the admin pending area. Also, I sent a message via my business email to the *test* list and have not received that message and the message is not showing up in the mailman provided *test* list archive. As an aside...and I know this is a bit out-there, and I'm not looking for help on this through this group but will bring it up as it may have some connection. I am also unable to view any usage statistics via webalizer either remotely or from the localhost. I've checked all of the normal FAQ/info from lists on this and am continually getting the following. Forbidden...You don't have permission to access /usage/ on this server. ... Apache/2.2.0 (Fedora) Server at www.*.org Port 80 Now here is why I bring it up...about two years ago when I set both the site up and mailman lists I (a) had no problem with viewing the usage characteristics and (b) had no problem with confirmation emails (although I did have initial issues with remote users getting and receiving emails). That system went down due to a blown power supply and I've since been attempting to rebuild. The new installation of Linux is as listed in the initial message and it is my understanding that SELINUX sometimes plays some tricks behind the scenes from a security perspective...could this be the root of both of my issues? Just a thought to throw out there. -- 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] Confirmation and sent messages not reaching end-user
Also...I just found a discussion on the mailman archives of... Low level smtp error. I have a different error than this individual had, the error they listed was... an 16 17:12:32 2007 (9353) Low level smtp error: (111, 'Connection refused'), msgid: [EMAIL PROTECTED] Jan 16 17:12:32 2007 (9353) Low level smtp error: please run connect() first, msgid: [EMAIL PROTECTED] Jan 16 17:12:32 2007 (9353) delivery to [EMAIL PROTECTED] failed with code -1: please run connect() first Jan 16 17:12:32 2007 (9353) delivery to [EMAIL PROTECTED] failed with code -1: (111, 'Connection refused') ...and folks suggested trying telnet localhost 25 ...from the mailman box. I just tried that command from the mailman box and received the following...which I'm guessing is potentially a source of my problem. localhost/25: Name or service not known -- 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] Confirmation and sent messages not reaching end-user
On Thu, 22 Feb 2007, Mark Sapiro wrote: Jason Luck SMTPHOST...in mm_cfg.py...no info on DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' If the above are actually indented, this is bad. They shouldn't be. Is this from mm_cfg.py or Defaults.py? A bit confused on this...as I mentioned earlier, this was not in the mm_cfg.py file, but in looking through the Defaults.py file I have the following. DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' I did notice in the Defaults.py file the following comment... # SMTP host and port, when DELIVERY_MODULE is 'SMTPDirect'. Make sure the # host exists and is resolvable (i.e., if it's the default of localhost be # sure there's a localhost entry in your /etc/hosts file!) When I look in my /etc/hosts file...I have no entries. So I just added... 127.0.0.1 localhost ...and restarted the network. -- 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] Confirmation and sent messages not reaching end-user
In my set-up...mm_cfg.py is located... /etc/mailman/mm_cfg.py /usr/lib/mailman/Mailman/mm_cfg.py ...and Defaults.py is located... /usr/lib/mailman/Mailman/Defaults.py On Fri, 23 Feb 2007, Baris Basar wrote: Can i ask you something? Where's mm_cfg.py?? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Luck Sent: Friday, February 23, 2007 4:43 PM To: Mark Sapiro Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Confirmation and sent messages not reaching end-user On Thu, 22 Feb 2007, Mark Sapiro wrote: Jason Luck SMTPHOST...in mm_cfg.py...no info on DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' If the above are actually indented, this is bad. They shouldn't be. Is this from mm_cfg.py or Defaults.py? A bit confused on this...as I mentioned earlier, this was not in the mm_cfg.py file, but in looking through the Defaults.py file I have the following. DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' I did notice in the Defaults.py file the following comment... # SMTP host and port, when DELIVERY_MODULE is 'SMTPDirect'. Make sure the # host exists and is resolvable (i.e., if it's the default of localhost be # sure there's a localhost entry in your /etc/hosts file!) When I look in my /etc/hosts file...I have no entries. So I just added... 127.0.0.1 localhost ...and restarted the network. -- 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/baris%40mobilnet.com.tr 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: SMTPHOST...in mm_cfg.py...no info on DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' If the above are actually indented, this is bad. They shouldn't be. Is this from mm_cfg.py or Defaults.py? Actually the text listed above on SMTP which was in section 4 of 3.14 FAQ is not listed in my mm_cfg.py...not there at all. Is this a problem? No. That bit in the FAQ is just a listing of the defaults from Defaults.py and these should be OK. 6) Locks Can't find any locks folder under a mailman directory It's somewhere? Is there a setting for LOCK_DIR in mm_cfg.py? There is no setting for LOCK_DIR in the mm_cfg.py. I perform a locate on either LOCK or LOCK_DIR and the only LOCK I can find deal with items in an selinux area. LOCK_DIR is not a directory, it is a Python name set in Defaults.py and possibly overridden in mm_cfg.py. Thus, you won't find it with locate, but you might find it with grep. If this is a RedHat FHS compliant installation, you will probably find them in /var/locks/, but if you check the setting for LOCK_DIR in Defaults.py (since it isn't in mm_cfg.py) you should find it. See http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html for more on RedHat FHS. Within the Mailman directory there is a LockFile.py, LockFile.pyc and LockFile.pyo This is the Mailman module that deals with locking and locks. It is not the locks themselves, but locks aren't your problem anyway. Here is what the smtp-failure log is saying... more smtp-failure Feb 21 18:30:00 2007 (6645) Low level smtp error: (-2, 'Name or service not known'), msgid: [EMAIL PROTECTED] See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.014.htp and http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.073.htp. -- 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: Also...I just found a discussion on the mailman archives of... Low level smtp error. And I wonder why you didn't find FAQ 6.14 which addresses your problem specifically. telnet localhost 25 ...from the mailman box. I just tried that command from the mailman box and received the following...which I'm guessing is potentially a source of my problem. localhost/25: Name or service not known Yes, it is the problem. You can't resolve the name 'localhost'. -- 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: When I look in my /etc/hosts file...I have no entries. So I just added... 127.0.0.1 localhost ...and restarted the network. That should help. -- 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] Confirmation and sent messages not reaching end-user
Baris Basar wrote: I'm using xp pro op. Sys. Are you running Mailman on this? If so, and if you have anything to add to http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq05.002.htp, let us know. Jason Luck wrote: In my set-up...mm_cfg.py is located... /etc/mailman/mm_cfg.py /usr/lib/mailman/Mailman/mm_cfg.py ...and Defaults.py is located... /usr/lib/mailman/Mailman/Defaults.py And in general, mm_cfg.py and Defaults.py are located with all the other Mailman modules in the Mailman/ directory in the Mailman installation, wherever that is. And in RedHat FHS Mailman, /etc/mailman/mm_cfg.py is a symlink to usr/lib/mailman/Mailman/mm_cfg.py. -- 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] Confirmation and sent messages not reachingend-user
On Fri, 23 Feb 2007, Mark Sapiro wrote: Jason Luck wrote: Also...I just found a discussion on the mailman archives of... Low level smtp error. And I wonder why you didn't find FAQ 6.14 which addresses your problem specifically. I didn't know enough to look into the specific log files that gave me the information until I had started this thread. 6.14 looks helpful. But I looked in resolv.conf and have the following: ; generated by /sbin/dhclient-script search localdomain nameserver 24.25.5.60 nameserver 24.25.5.61 ...the nameserver info is for my domain...is the search localdomain the issue? -- 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: I didn't know enough to look into the specific log files that gave me the information until I had started this thread. 6.14 looks helpful. But I looked in resolv.conf and have the following: ; generated by /sbin/dhclient-script search localdomain nameserver 24.25.5.60 nameserver 24.25.5.61 ...the nameserver info is for my domain...is the search localdomain the issue? I think the issue was the lack of a 'localhost' entry in /etc/hosts. When you added that, did anything change? Can you now 'telnet localhost 25'? If Mailman still can't send, have the log messages changed in smtp-failure? -- 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] Confirmation and sent messages not reachingend-user
On Fri, 23 Feb 2007, Mark Sapiro wrote: Jason Luck wrote: I didn't know enough to look into the specific log files that gave me the information until I had started this thread. 6.14 looks helpful. But I looked in resolv.conf and have the following: ; generated by /sbin/dhclient-script search localdomain nameserver 24.25.5.60 nameserver 24.25.5.61 ...the nameserver info is for my domain...is the search localdomain the issue? I think the issue was the lack of a 'localhost' entry in /etc/hosts. When you added that, did anything change? Can you now 'telnet localhost 25'? yes. I can telnet to localhost 25. If Mailman still can't send, have the log messages changed in smtp-failure? I just checked my mail and both confirmations, one for the mailman list and one for the test list have hit my external business mailbox. Also, the subscription request for the test list has also hit my mailbox. 6.14 has seemingly helped out a bit. I've changed a few things and to be honest am not completely sure at what time things started flowing. I used python for the first time...and did the following and got the following result import smtplib connection = smtplib.SMTP() Traceback (most recent call last): File stdin, line 1, in ? File /usr/local/lib/python2.4/smtplib.py, line 255, in __init__ addr = socket.gethostbyname(socket.gethostname()) socket.gaierror: (-2, 'Name or service not known') I suppose no surprise...I then checked the resolv.conf and that was the previous message. Then I did the following per 6.14... import socket x = socket.gethostname() print x (response) y = socket.gethostbyname(x) print y (response) ...In my reponses, for x I obtained what I had been locally calling my machine, but not what my static IP is known as to the outside world. When I attempted the *y=* line I received no response. After making the appropriate hostname changes the above python routine connected the IP to the name of the machine. Another problem though...it looks like I am... (a) able to create lists (b) receive notification emails about the creation of lists (c) able to subscribe to lists (d) receive notification about subscribing to a lists ...but...I'm not able to... (a) receive any email when posted to a list I'm subscribed to. (b) and there is not record in the archives of these messages. (c) I've checked the following logs...maillog, smtp, smtp-failure and they are not posting anything. It seems as though the messages may have left my external email, but never reached my local MTA or mailman? Listed below is a message I received from my business email side... The original message was received at Fri, 23 Feb 2007 12:34:05 -0500 from localhost.localdomain [127.0.0.1] - Transcript of session follows - [EMAIL PROTECTED]... Deferred: Connection refused by falconfootball.org. Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old [ Part 2: Delivery Status ] Reporting-MTA: dns; [business email] Arrival-Date: Fri, 23 Feb 2007 12:34:05 -0500 Final-Recipient: RFC822; [EMAIL PROTECTED] Action: delayed Status: 4.4.1 Remote-MTA: DNS; falconfootball.org Last-Attempt-Date: Fri, 23 Feb 2007 16:35:54 -0500 Any ideas...I've looked through all of the titles on the FAQs and don't see anything about not receiving emails and also not having anything in the log files. Also, per the initial messages that started this discussion, I've run through all of the 3.14 FAQs and all seems to be working as best as I can decipher working means by the info in the FAQ. Thanks. -- 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: ...but...I'm not able to... (a) receive any email when posted to a list I'm subscribed to. (b) and there is not record in the archives of these messages. (c) I've checked the following logs...maillog, smtp, smtp-failure and they are not posting anything. It seems as though the messages may have left my external email, but never reached my local MTA or mailman? That's right. The delay notice below says it was unable to connect to an SMTP server at falconfootball.org. Is your MTA at falconfootball.org listening for connects on port 25 from the outside? Listed below is a message I received from my business email side... The original message was received at Fri, 23 Feb 2007 12:34:05 -0500 from localhost.localdomain [127.0.0.1] - Transcript of session follows - [EMAIL PROTECTED]... Deferred: Connection refused by falconfootball.org. Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old snip -- 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] Confirmation and sent messages not reachingend-user
That's right. The delay notice below says it was unable to connect to an SMTP server at falconfootball.org. Is your MTA at falconfootball.org listening for connects on port 25 from the outside? grep Port sendmail.cf O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA #O ClientPortOptions=Family=inet, Address=0.0.0.0 netstat -na |grep :25 tcp0 0 127.0.0.1:250.0.0.0:* LISTEN and in the etc/hosts file IPAddress Hosts Alias 127.0.0.1 localhost [##.###.##.##]falconfootball.org Listed below is a message I received from my business email side... The original message was received at Fri, 23 Feb 2007 12:34:05 -0500 from localhost.localdomain [127.0.0.1] - Transcript of session follows - [EMAIL PROTECTED]... Deferred: Connection refused by falconfootball.org. Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old snip -- 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: grep Port sendmail.cf O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA #O ClientPortOptions=Family=inet, Address=0.0.0.0 I don't know sendmail configuration, but it seems you've only told it to listen on the local loopback port 127.0.0.1 netstat -na |grep :25 tcp0 0 127.0.0.1:250.0.0.0:* LISTEN And netstat confirms that. You should also see something like tcp0 0 0.0.0.0:250.0.0.0:*LISTEN You should be able to telnet to port 25 of this host from outside. You can't (or at least I can't - I get a refusal to my connect negotiation). and in the etc/hosts file IPAddress Hosts Alias 127.0.0.1 localhost [##.###.##.##]falconfootball.org Not relevant. This only directs connects to falconfootball.org from this machine to the given IP address. It has no effect on what's listening on this machine for connects from the outside. -- 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] Confirmation and sent messages not reachingend-user
Thanks for the response, unfortunately my limited knowledge on these matters leaves me at a dead end. Not sure how to change any of these items or where to go from here. On Fri, 23 Feb 2007, Mark Sapiro wrote: Jason Luck wrote: grep Port sendmail.cf O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA #O ClientPortOptions=Family=inet, Address=0.0.0.0 I don't know sendmail configuration, but it seems you've only told it to listen on the local loopback port 127.0.0.1 netstat -na |grep :25 tcp0 0 127.0.0.1:250.0.0.0:* LISTEN And netstat confirms that. You should also see something like tcp0 0 0.0.0.0:250.0.0.0:*LISTEN You should be able to telnet to port 25 of this host from outside. You can't (or at least I can't - I get a refusal to my connect negotiation). and in the etc/hosts file IPAddress Hosts Alias 127.0.0.1 localhost [##.###.##.##]falconfootball.org Not relevant. This only directs connects to falconfootball.org from this machine to the given IP address. It has no effect on what's listening on this machine for connects from the outside. -- 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] Confirmation and sent messages not reachingend-user
Jason Luck wrote: Thanks for the response, unfortunately my limited knowledge on these matters leaves me at a dead end. Not sure how to change any of these items or where to go from here. You fix it in your sendmail configuration by telling sendmail to listen for port 25 connects from anywhere. I can't tell you how to do that because I don't know. Perhaps you can read some sendmail documentation or ask on a sendmail list. -- 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] Confirmation and sent messages not
The esteemed Mark Sapiro has said: Jason Luck wrote: Thanks for the response, unfortunately my limited knowledge on these matters leaves me at a dead end. Not sure how to change any of these items or where to go from here. You fix it in your sendmail configuration by telling sendmail to listen for port 25 connects from anywhere. I can't tell you how to do that because I don't know. Perhaps you can read some sendmail documentation or ask on a sendmail list. I'll chime in with some quick observations (I run sendmail 8.13.8 on Solaris 9). The two first places I'd look are: 1. The tcp-ip services file (/etc/inet/services on Solaris) needs a line that says: smtp 25/tcp mail 2. There needs to be a sendmail -bd daemon running. That is the one that listens for incoming smtp. I don't see anything specific to port 25 in the .cf files. I would also check any router/firewall between your sendmail client machine to make sure that incoming port 25 traffic is not being blocked; also any ipfilter setup. Hank -- 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] Confirmation and sent messages not
On Fri, 23 Feb 2007 [EMAIL PROTECTED] wrote: The esteemed Mark Sapiro has said: Jason Luck wrote: Thanks for the response, unfortunately my limited knowledge on these matters leaves me at a dead end. Not sure how to change any of these items or where to go from here. You fix it in your sendmail configuration by telling sendmail to listen for port 25 connects from anywhere. I can't tell you how to do that because I don't know. Perhaps you can read some sendmail documentation or ask on a sendmail list. I'll chime in with some quick observations (I run sendmail 8.13.8 on Solaris 9). The two first places I'd look are: 1. The tcp-ip services file (/etc/inet/services on Solaris) needs a line that says: smtp 25/tcp mail 2. There needs to be a sendmail -bd daemon running. That is the one that listens for incoming smtp. I don't see anything specific to port 25 in the .cf files. I would also check any router/firewall between your sendmail client machine to make sure that incoming port 25 traffic is not being blocked; also any ipfilter setup. Hank Looks like I have it up and working. Just received one of my first test messages all the way through. I think there were a number of things wrong, not the least of which was that I had the DaemonPortOptions set for the loopback and so it was in no way looking for external mail as I understand it now. I made the changes listed in some sendmail lists and although the changes took affect seemingly in the files based on time stamp changes when I ran netstat I saw no difference in what sendmail was listening to. I did all of the restarts on the networking and mailman but it didn't seem like it was working. So...I did a full shutdown and restart of the entire system. And...all is working seemingly. In fact as I type this message it looks like two test messages from earlier today have just hit. Why is the default in DaemonPortOptions set for 127.0.0.1 as opposed to a broader range? It would seem most folks would want to be able to external mail through their box and from what I'm learning would require the 127.0.0.1 to be changed. Also by changing this...does one open themselve up to security issues? Mark and Hank, thanks for all of the help! -- 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] Confirmation and sent messages not reaching end-user
- Mailman 2.1.7 - RPM - Redhat Fedora Linux version 2.6.15-1.2054_FC5 - Sendmail Question: I'm setting up a Mailman system and have hit a roadblock that looks to deal with sending and receiving messages. What I know: I've looked through the FAQ and specfically FAQ 3.14, and am able to get a number of the items requested, but don't know enough to be able to decipher what the outputs are saying. I can seemingly create lists...both at the command prompt using newlist and through the web-interface, but do not receive any confirmation emails once those lists are created. Additionally, I subscribed to one of the lists and tried to send a message to the list and did not receive the message. Also, the archives do not show the message. I've listed below a few of the responses from the outputs of the FAQ and can provide additional log file info if it will be helpful. Thanks. FAQ3.14 3) yes uses smrsh, grep smrsh sendmail.cf output: # $Id: smrsh.m4,v 8.14 1999/11/18 05:06:23 ca Exp $ # Mprog, P=/usr/sbin/smrsh, F=lsDFMoqeu9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, D=$z:/, A=smrsh -c $u ls -l smrsh output: total 4lrwxrwxrwx 1 root mailman 29 Sep 16 05:18 mailman - /usr/lib/mailman/mail/mailman 4) Interface grep Port sendmail.cf O DaemonPortOptions=Port=smtp,Addr=127.0.0.1, Name=MTA #O ClientPortOptions=Family=inet, Address=0.0.0.0 netstat -na |grep :25 output: tcp0 0 127.0.0.1:250.0.0.0:* LISTEN a bit shady here... /etc/hosts has nothing in it. SMTPHOST...in mm_cfg.py...no info on DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' 5) qrunner is running 6) Locks Can't find any locks folder under a mailman directory 7) Logs more post Feb 21 18:30:00 2007 (6645) post to test from [EMAIL PROTECTED], size=1492, message-id=mailman.0.1172099747.6557.test @falconfootball.org, 1 failures Feb 21 18:30:00 2007 (6645) post to test from [EMAIL PROTECTED], size=1845, message-id=[EMAIL PROTECTED], 1 failures Feb 21 18:30:01 2007 (6645) post to mailman from [EMAIL PROTECTED], size=1876, message-id=[EMAIL PROTECTED], 1 failures Feb 21 18:45:00 2007 (6645) post to test from [EMAIL PROTECTED], size=1492, message-id=[EMAIL PROTECTED], 1 failures Feb 21 18:45:00 2007 (6645) post to test from [EMAIL PROTECTED], size=1845, message-id=[EMAIL PROTECTED], 1 failures Feb 21 18:45:00 2007 (6645) post to mailman from [EMAIL PROTECTED], size=1876, message-id=[EMAIL PROTECTED], 1 failures Feb 21 18:58:02 2007 (6645) post to test from [EMAIL PROTECTED], size=1636, message-id=[EMAIL PROTECTED], 1 failures -- 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] Confirmation and sent messages not reaching end-user
Jason Luck SMTPHOST...in mm_cfg.py...no info on DELIVERY_MODULE = 'SMTPDirect' MTA = 'Manual' SMTPHOST = 'localhost' SMTPPORT = 0 # default from smtplib SENDMAIL_CMD = '/usr/lib/sendmail' If the above are actually indented, this is bad. They shouldn't be. Is this from mm_cfg.py or Defaults.py? 6) Locks Can't find any locks folder under a mailman directory It's somewhere? Is there a setting for LOCK_DIR in mm_cfg.py? 7) Logs more post Feb 21 18:30:00 2007 (6645) post to test from [EMAIL PROTECTED], size=1492, message-id=mailman.0.1172099747.6557.test @falconfootball.org, 1 failures And most important, what's in the smtp-failure log? -- 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
