Re: [Mailman-Users] Mailman-Users Digest, Vol 63, Issue 53

[Mark Sapiro]

Dave Filchak wrote:
>>   
>Yup ... just sent a test email to a test list we have set up and it 
>seems to be working. It is so weird though ... there is really no way I 
>can think of that these would change even after an unscheduled abrupt 
>shutdown like we had. And the thing is, this server was up and running 
>for two years before that and running mailman with no issues. It is like 
>a ghost in the machine. Very crazy!!


That could explain this. It happens all the time. People make changes
to things which are only effective following a restart of some kind,
but they don't do the restart. Then along comes an unplanned outage
and reboot and all of a sudden things are broken because of changes
that were made and forgotten months before.


>I wan to thank you for hanging in there with me. I really do appreciate it.


You're welcome.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman-Users Digest, Vol 63, Issue 53

[Dave Filchak]

Mark Sapiro wrote:
Dave Filchak 
  
  
  
OK .. well maybe something here. In Defaults.py SMTPHOST is set to 
'localhost' In mm_cfg.py, it is set to the actual public IP of the server.




I'm fairly sure if you just remove the SMTPHOST = 'xx.xx.xx.xx' from
mm_cfg.py and restart Mailman, it will work.

I'm also fairly sure that if you set SMTPHOST to the IP instead of
localhost in the tests that they will fail.

Of course, none of this will explain why it quit after the power
outage, but I'm pretty sure the difference is a DNS issue.

  
Yup ... just sent a test email to a test list we have set up and it 
seems to be working. It is so weird though ... there is really no way I 
can think of that these would change even after an unscheduled abrupt 
shutdown like we had. And the thing is, this server was up and running 
for two years before that and running mailman with no issues. It is like 
a ghost in the machine. Very crazy!!


I wan to thank you for hanging in there with me. I really do appreciate it.

Dave

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman-Users Digest, Vol 63, Issue 53

[Mark Sapiro]

Dave Filchak 
>>   
>OK .. well maybe something here. In Defaults.py SMTPHOST is set to 
>'localhost' In mm_cfg.py, it is set to the actual public IP of the server.


I'm fairly sure if you just remove the SMTPHOST = 'xx.xx.xx.xx' from
mm_cfg.py and restart Mailman, it will work.

I'm also fairly sure that if you set SMTPHOST to the IP instead of
localhost in the tests that they will fail.

Of course, none of this will explain why it quit after the power
outage, but I'm pretty sure the difference is a DNS issue.

-- 
Mark Sapiro 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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9

Re: [Mailman-Users] Mailman-Users Digest, Vol 63, Issue 53

[Dave Filchak]

  
  
OK .. ran both tests as mailman. First one was fine. Second one, while 
it shown no errors initially, I only received the email that was sent as 
a rcpt (secondary email address). The To: email address did not get 
delivered. The smtp-failure logs do not show a specific error for that 
email transaction but it still shows a ton of the same errors, i.e.:


May 29 16:21:04 2009 (6489) Low level smtp error: (-2, 'Name or service 
not known'), msgid: 
May 29 16:21:04 2009 (6489) delivery to some...@domain.org failed with 
code -1: (-2, 'Name or service not known')


Both /etc/resolv.conf and /etc/hosts are world readable. I am truly stumped.




That example won't deliver to any addresses in the message headers. 
Also, it won't log any errors. Error will be written to Python's

stderr (normally the terminal). It sends to the addresses in the rcpts
list as those are the only addresses communicated via SMTP. I.e., the
envelope is sent to the rcpts regardless of what the message inside
the envelope says.

OK. I'm stumped too. Check the definitions of SMTPHOST and SMTPPORT in
Defaults.py and possible overrides in mm_cfg.py to make sure they are
'localhost' and 0 respectively.
  
OK .. well maybe something here. In Defaults.py SMTPHOST is set to 
'localhost' In mm_cfg.py, it is set to the actual public IP of the server.

Also, another thing that occurred to me at one point which I don't
think makes any difference and which looked OK in your prior post of
'ps' output, but make sure that a sendmail process didn't start on
it's own after the power failure.

chkconfig --list sendmail

or however you set these things on your system should show sendmail is
off at all run levels. sendmail should only be run by MailScanner.
  

sendmail is turned off at all levels.

If your python is 2.4.x or later, you can use the technique described
in the FAQ at  to obtain debugging info
from Python's smtplib. The extra information will be written to
Mailman's error log.
  
No such luck. This is an older system running the latest available for 
this system (2.3.4)


I am going to change mm_cfg.py to match Defaults.py or I guess I could 
just comment it out?


Dave


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9