Link to home
Create AccountLog in
Avatar of jefforamma

asked on

mail delivery issue


I am having some problems sending emails to some domains. i am getting ndr's back when sending to some domains but not others.
i get the following ndr:
Your message did not reach some or all of the intended recipients.
      Subject:      info
      Sent:      03/03/2008 3:08 PM
The following recipient(s) could not be reached:
      **** on 04/03/2008 12:55 AM
            Could not deliver the message in the time limit specified.  Please retry or contact your administrator.
            < #4.4.7>

I am behind a pix but i have esmtp inspection off.
i can telnet from allservers to the server and send a test message from that session with no problems.
another wierd thing is i send emails 2 different ways. my comp hosts a reservation system. i can email that address ** from within the application fine. however when they try to mail from the website, that is when i get the above ndrs.
I send using the exact same email object on all servers so i dont understand why it works on one but not the other?

any insight would be much appreciated. i am banging my head on a wall here

Avatar of jefforamma


i think i know why it is happening but not sure how to fix yet. it looks like the web side is striping out/ignoring the character returns in the templates and only sees the line feeds. so the end user's mail server thinks its in invalid format?
when i send from the app it has all the CR LF's.
Avatar of jefforamma

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Vadim Rapp
in the future, you would want to look into the detailed log of your smtp server. There you would see the conversation between your server and destination server, so you would figure what the latter one did not like so it rejected the message. BTW, I don't think what you described might be the reason , since remote mailserver does not look inside the message during the transmission. It might analyze it after it was already accepted and reject at that point, but then you would receive an ndr from that server, rather than from yours.

i had looked at the logs. most didnt say anything. it was only when i found one response from a particular domain i was trying to send to. it responded with this url in the log. 
that is how we knew it was to do with the CR's. I know it was not their mail server. it would send the data and then disconnect as their server was waiting for the CRLF.CRLF to end the data. it never came so would disconnect/timeout.
once that was figured the cause it was trying to figure out what was stripping the CR's from the templates. Web services was the culprit.