|
|
|
|
||||||
| comp.mail.sendmail Configuring and using the BSD sendmail agent. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I'm hoping I can find the source of the following problem. As of late
I have more of my users reporting that messages from others are being rejected by our server as being unreachable. This does not appear to be affecting all incoming messages. The only indications I see of errors in our logs is the following: Jan 16 08:47:51 webserver sendmail[8641]: l0GEiMK08641: SYSERR: putoutmsg (service.schwans.com): error on output channel sending "220 mail.netexsw.com ESMTP Sendmail 8.11.6/8.11.6; Tue, 16 Jan 2007 08:47:51 -0600": Connection reset by service.schwans.com Jan 16 08:47:51 webserver sendmail[8641]: NOQUEUE: MAILER-DAEMON@service.schwans.com [205.142.254.199] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA YES, I realize this is a very old version of Sendmail. Right now, unless someone says that that is the definite cause of this problem, I would prefer to ignore that point. Any ideas on what this could mean? Thanks in advance! |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
joe.kang@gmail.com wrote:
> I'm hoping I can find the source of the following problem. As of late > I have more of my users reporting that messages from others are being > rejected by our server as being unreachable. This does not appear to > be affecting all incoming messages. The only indications I see of > errors in our logs is the following: <snip> > YES, I realize this is a very old version of Sendmail. Right now, > unless someone says that that is the definite cause of this problem, I > would prefer to ignore that point. This is not likely your problem, though it is something that should be addressed some time. > Any ideas on what this could mean? You are getting "Connection reset by <hostname>" and "<hostname> did not issue MAIL/EXPN/VRFY/ETRN during connection". If you are receiving a lot of these, I would suspect that you are having a communications issue that is causing your problem with sending email. Also, as of late, ORDB has shut down. If you were referencing it, you may be having DNS timeouts contributing to your apparent communications (timing out) issues. Grant. . . . |
|
![]() |
| Outils de la discussion | |
|
|