Eric Evans wrote: >This is very interesting. I took your suggestion and deleted the SMTPHOST >statement from the mm_cfg.py and Mailman immediately started working. I >don't know why this would make a difference. I know that we had this same >SMTPHOST statement in the mm_cfg.py file for quite a long time, years even, >and we never had a problem with it until recently.
You said you had SMTPHOST = '<128.253.175.139>' and I remarked >>Which is probably using sendmail and not trying to connect to an SMTP >>server at <128.253.175.139> (which BTW is if anything, a name and not >>an IP address). I.e '<128.253.175.139>' is not the same as '128.253.175.139'. The latter is an IP address and the former is a name. Maybe something in your DNS or other configuration changed so the name '<128.253.175.139>' could no longer be resolved. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better 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=show&file=faq01.027.htp
