Alright. We're running 2000 server (SBS) with exchange 2000 (SP3). Everything _seems_ to be working fine until lately i've seem to run into a reoccuring problem.
We use exchange for SMTP/connector. Here's the problem:
With certain mx/hosts (not all) sending email, it times out in the queue and keeps retrying until it fails.
Here's what I've found out using a sniffer. Any email that's sent out to *certain hosts* does NOT get sent if it's sent out in more than one packet, yes, you heard me. So comcast.net, and about 5-10 other emails are getting constantly stuck in the queue because we all use outlook/html when sending emails. How did test this theory you ask? Well, if i send out an email thats plaintext, or a multipart email thats ONE packet, it sends fine. Any plaintext works fine because it seems to all be sent in one packet, but anything else creates a multipart email thats split into several packets.
Here's the retarded thing, all the data is right, and it works to MOST hosts/mx, just some it doesn't, but i can't brush it off or ask my boss and supervisor to use plaintext sometimes. I mean it sends all the proper data, gets all the proper responses, but doesn't get the 250 OK after it sends the "." escape character after the message DATA. (so it hangs, no ok, no QUIT). I'm stumped. watching the packets everything looks okay from my home computer, all the data looks the same, i just DONT GET IT!!
Any suggestions are welcome
We use exchange for SMTP/connector. Here's the problem:
With certain mx/hosts (not all) sending email, it times out in the queue and keeps retrying until it fails.
Here's what I've found out using a sniffer. Any email that's sent out to *certain hosts* does NOT get sent if it's sent out in more than one packet, yes, you heard me. So comcast.net, and about 5-10 other emails are getting constantly stuck in the queue because we all use outlook/html when sending emails. How did test this theory you ask? Well, if i send out an email thats plaintext, or a multipart email thats ONE packet, it sends fine. Any plaintext works fine because it seems to all be sent in one packet, but anything else creates a multipart email thats split into several packets.
Here's the retarded thing, all the data is right, and it works to MOST hosts/mx, just some it doesn't, but i can't brush it off or ask my boss and supervisor to use plaintext sometimes. I mean it sends all the proper data, gets all the proper responses, but doesn't get the 250 OK after it sends the "." escape character after the message DATA. (so it hangs, no ok, no QUIT). I'm stumped. watching the packets everything looks okay from my home computer, all the data looks the same, i just DONT GET IT!!
Any suggestions are welcome
Facebook
Twitter