Re: [vchkpw] indirect reasons for 5.7.1? - behavior confirmed
On Fri, Apr 02, 2004 at 10:14:26PM -0800, Kurt Bigler wrote: Thanks for your help, which lead to the resolution. Still a mystery to me why a default SMTP answerer would respond with 5.7.1. I inquired about that but got no reply yet. Just a wild guess, but perhaps because the recipient addresses in question were not being handled by the SMTP server in question. Peace, david -- David H. Wolfskill [EMAIL PROTECTED]
Re: [vchkpw] indirect reasons for 5.7.1? - behavior confirmed
Kurt Bigler wrote: snip The plot thickens. sockstat produced no output, apparently a limitation of the virtual server implementation. Inquiring into this, the parent server apparently had default processes answering (stupidly) when virtual server email servers were not running. The administrator fixed this with a quick configuration change, and now everything behaves as expected. Thanks for your help, which lead to the resolution. Still a mystery to me why a default SMTP answerer would respond with 5.7.1. I inquired about that but got no reply yet. -Kurt Well, that is an easy one, if they are running qmail as well, it would answer with a 5.7.1 meaning your domain is not in their rcpthosts. X-Istence
Re: [vchkpw] indirect reasons for 5.7.1? - behavior confirmed
on 4/2/04 1:15 PM, Kurt Bigler [EMAIL PROTECTED] wrote: This is regarding qmail + vpopmail 5.3.12 running under tcpserver, on FreeBSD 4.6.1. My server was bouncing *everything* with 5.7.1, that is including stuff that should have been delivered to domains hosted by my server. I panicked and just rebooted my server (because reboot is very quick and it is the most reliable way to fix a bunch of things quickly without having to take time to identify a problem), and thus lost some of the evidence. But I am suspicious based on previous expeirences that if a certain process dies that some process starts responding to all smtp requests with 5.7.1. Or is there any other obvious reason why qmail might go into a permanent 5.7.1 mode? Thanks for any thoughts, and sorry to be so lacking in info. I did do a quick ps when I discovered the problem and I'm pretty sure that the tcpserver process involving qmail-smtpd was probably not there. I only remembered it should have been there after rebooting and doing another ps. Is there some default mode for smtp connections that takes over under such a circumstance? Thanks, Kurt Bigler I confirmed that if I kill this process (line from ps output): qmaild86243 0.0 0.1 904 360 ?? SNJ 3:05PM 0:00.09 tcpserver -v -H -R -lvps.breathsense.com -x /var/vpopmail/etc/tcp.smtp.cdb -c200 -u1003 -g1001 0 25 fixcrio /var/qmail/bin/qmail-smtpd that incoming SMTP attempts are greeted by a 5.7.1 error. Does anyone understand how this happens? Thanks, Kurt Bigler
Re: [vchkpw] indirect reasons for 5.7.1? - behavior confirmed
Kurt Bigler wrote: snip I confirmed that if I kill this process (line from ps output): qmaild86243 0.0 0.1 904 360 ?? SNJ 3:05PM 0:00.09 tcpserver -v -H -R -lvps.breathsense.com -x /var/vpopmail/etc/tcp.smtp.cdb -c200 -u1003 -g1001 0 25 fixcrio /var/qmail/bin/qmail-smtpd that incoming SMTP attempts are greeted by a 5.7.1 error. Does anyone understand how this happens? Thanks, Kurt Bigler Well, considering that is your SMTP service, it looks like another server on the same system is taking over, or you configured something wrong. since its freebsd, take a look at: sockstat -4, and look for port 25 and what process has it in use if you kill that process you mentioned. X-Istence
Re: [vchkpw] indirect reasons for 5.7.1? - behavior confirmed
on 4/2/04 6:24 PM, X-Istence [EMAIL PROTECTED] wrote: Kurt Bigler wrote: snip I confirmed that if I kill this process (line from ps output): qmaild86243 0.0 0.1 904 360 ?? SNJ 3:05PM 0:00.09 tcpserver -v -H -R -lvps.breathsense.com -x /var/vpopmail/etc/tcp.smtp.cdb -c200 -u1003 -g1001 0 25 fixcrio /var/qmail/bin/qmail-smtpd that incoming SMTP attempts are greeted by a 5.7.1 error. Does anyone understand how this happens? Thanks, Kurt Bigler Well, considering that is your SMTP service, it looks like another server on the same system is taking over, or you configured something wrong. since its freebsd, take a look at: sockstat -4, and look for port 25 and what process has it in use if you kill that process you mentioned. The plot thickens. sockstat produced no output, apparently a limitation of the virtual server implementation. Inquiring into this, the parent server apparently had default processes answering (stupidly) when virtual server email servers were not running. The administrator fixed this with a quick configuration change, and now everything behaves as expected. Thanks for your help, which lead to the resolution. Still a mystery to me why a default SMTP answerer would respond with 5.7.1. I inquired about that but got no reply yet. -Kurt
