SMTP Mail on webserver not reaching internal email addresses.

I have a web applications that uses the SMPT server on the webserver to send out email notifications to people outside of our network as well as to people inside our network.  This has worked for several years, but suddenly, it has stopped working for mail recipients inside our network.

1) the undelivered messages are stuck in the queue on the webserver (Intepub/mailroot/queue)
2)  The message I see in the BadMail folder is "Unable to deliver message to the following recipients, due to being unable to connect successfully to the destination mail server."

I need help to get this to start working again.  And, I'm a novice at this.
LVL 1
varesourcesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

varesourcesAuthor Commented:
I've reviewed many of the posts on experts exchange looking for ways to solve my problem.  In one I found directions on how to telnet into my mail server and test the flow of mail.  1) I am able to telnet into the server on port 25.  2) I can Helo the mail server from the web server.  3) the mail server DOES accept messages from the webserver.  4) the email addresses the web server is sending to are getting the following result:   Unable to deliver this message because the follow error was encountered:

"This message is a delivery status notification that cannot be delivered.".

The specific error code was 0xC00402C7.


The message sender was <>.


The message was intended for the following recipients.
      onlineapp@computerlease.com


To me it looks like the webserver is not sending the HELO message correctly.  Since nothing has changed on the webserver, could a setting on the Exchange server be set incorrectly?  

I have my external mail filtered by an outside company.  They filter the mail for me and then forward to my mail server.  All my incoming mail is filtered by that service before it arrives.

The mail from the webserver does not look as if it is flowing out and trying to come back in through the filtering service.  It is not getting caught in their filter - I can check that.
0
meverestCommented:
Hi,

>> I have my external mail filtered by an outside company.

do they know that you are sending mail from this web application?  try asking if they will add the web server IP address as a 'known sender'.

>> the email addresses the web server is sending to are getting the following result

what does that mean?  did you get that error message from the destination mail /server/?  Looks more like the web application does not set the sender email address properly.  That is one reason why the recipient system is not accepting the messages.

>> To me it looks like the webserver is not sending the HELO message correctly.

I don't think so.  More likely to be the sender address is missing - but I'm not exactly sure what you mean by your comment (4)

>> Since nothing has changed on the webserver, could a setting on the Exchange server be set incorrectly?  

Perhaps, or more likely that something is set CORRECTLY on the exchange server ;-)  You probably don't want to accept mail that has a blank sender address.

Does the smtp service on the web server send mail *direct* to your exchange server, or to that intermediary service?  You can make it go direct by adding a new domain of type 'remote' and set your exchange server as the 'smart host' for the new domain.

The fact that mail is showing up in the queue on that server indicates that the web application is working OK and the smtp service is running.  The question you need to be asking yourself is "why does our mail server (or the third party mail forwarder) refuse to accept mail from this system"

cheers.


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cj_1969Commented:
Given the blank reply to address and the error message I would agree with meverest ... Exchange is configured correctly, I think your outgoing email is missing a header field, the sender email address.

Check your email configuration on the sending application and make sure that there is a reply to email address and a sender address.
0
varesourcesAuthor Commented:
We fixed the problem.  It was an internal DNS MX record that needed to be set.  Thank you so much for your help in resolving this issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.