Is anyone out there experiencing a plethora of these mail routing events:
06/03/2003 08:56:48 AM SMTP Server: 192.189.171.29 connected
06/03/2003 08:56:48 AM SMTP Server: 192.189.171.29 disconnected. 0 message[s] received
06/03/2003 08:57:47 AM SMTP Server: 192.189.171.29 connected
06/03/2003 08:57:47 AM SMTP Server: 192.189.171.29 disconnected. 0 message[s] received
I suspect this might have something to do with spam relay restrictions, but that’s just a wild guess based on a couple of bounce reports that I’d been forwarded. I think one of these non-sending servers reported a “didn’t use HELO protocol” error.
Any thoughts and/or suggestions? Someone mentioned checking firewall settings, but as far as I can tell, we are allowing tcp and udp on port 25 to our box.
Thanks!
Subject: We have a HP Scanner/Digital Sender polls the SMTP server every 5 minutes to see if its alive.
Subject: SMTP inbound, 0 message[s] received
We have the same problem with a W2k machine since migrating from 5.0.11 to 6.0.2cf1.I had the problem 2 weeks ago. I turned off a rule and DNSlookup. After restart the server worked very well. I turned on DNSlookup again and the server worked very well for 2 weeks.
Yesterday I had the same problems without any changes in the configuration. I turned off Domain Name Lookup of the Sender’s Adress in the Configuration document section SMTP inbound control. After server restart it is working again.
I remember a article in MS TechNet concerning DNS cache and how to turn it off. I think I will test it.
Any new experienced anywhere?
Subject: SMTP inbound, 0 message[s] received
A reason for this message could be because you have Internet sites selected in your server doc and you dont have a ‘Default site’ for your server (I’m assuming you have already SMTP inbound doc). Yes, this do not sound very logic but I had this problem. After a couple hours the server started to sending these messages.
To validate if your case is as mine, select temporarily ‘Web server configuration’ and check if you receive mail again (dont forget restart the server after the change, is not enough if you restart the http task only).
Of course, also could be configuration in your firewall, even mail restrictions, but my case was as above. Strange but truth.
Subject: RE: SMTP inbound, 0 message[s] received
Thanks for the reply. We did have similar issues earlier when the SMTP server was rejecting all inbound traffic - setting up appropriate Internet Site (inbound SMTP) documents took care of that.
What we have now is a smaller set of external hosts that do not seem to be rejected by DNS black lists, but still cannot transfer mail.
From what I gather, this might have to do with Cisco PIX settings related to mail guard, but I’m still investigating.
Subject: RE: SMTP inbound, 0 message[s] received
3 suggestions:
-
If a Cisco Pics firewall, turn off SMTP fixup protocol.
-
Disable ESMTP command pipelining.
-
Check out what I wrote earlier (last couple of posts in this thread) - http://tinyurl.com/dct1 - about MTU size:
Subject: RE: SMTP inbound, 0 message[s] received
From what I can tell, we have no PIX upstream of our server. The hosting facility uses a Nortel Shasta, and from speaking with their tech, I gather that the Shasta has no equivalent functionality of the PIX SMTP fixup (and we could be wrong on that, but I’m going on what I’ve been told).
Disabling ESMTP didn’t seem to have an effect, and I’ll have to investigate further on the MTU size adjustment (which, I’m assuming, is done at the NIC configuration level?).
Subject: Re: MTU size adjustment
“which, I’m assuming, is done at the NIC configuration level?”
Yes. There is a rather nice litle utility called Dr TCP from a site called DSLreports.com that will tweak the relevant registry values for you so you don’t have to do a manual registry hack.
http://www.dslreports.com/front/drtcp.html