Mail from: shows internal server name in mail header and fails

Here is a background on our setup: we have one server that is setup as an
SMTP relay that has an MX record configured and a FQDN. We have another
application server creating messages via Adobe Central Pro and relaying them
through this SMTP server. During the HELO to the internal SMTP server, the
internal application server is "lying" to our internal SMTP server by saying
HELO SMTPSERVERINTERNALIP during the communications as opposed to saying HELO
MYINTERNALSERVERIP. This relaying has worked without a problem, and looking
at successful mail headers we can see the following line:

Received: From SMTPINTERNALIP {ADOBESERVERINTERNALIP} by
mail.externaldns.com etc.

Now we have added another application server to do some of this message
creating. Initially it was configured to send this HELO command when
connecting to the SMTP server:

HELO NEWINTERNALSERVERNAME

And looking at the mail header for this new server:

from NEWINTERNALSERVERNAME ([NEWINTERNALSERVERNAMEIPADDRESS]) by
mail.externaldns.com etc

So now since it is sending the servername in the HELO command many of our
clients are not receiving emails from us from the new server. The old server
configuration works fine still. Now our developers are changing the new
application to match the existing one but I still wonder why on Earth
messages using the INTERNALSERVERDNSNAME would stop working. For these
addresses using the INTERNALSERVERDNSNAME we are receiving several delay
notifications before sending the failure notification with a status of 4.4.7
action failed. Here is the failure notification message:

This is an automatically generated Delivery Status Notification.

Unable to deliver message to the following recipients, due to being unable
to connect successfully to the destination mail server.

Can anyone provide any insight as to why this would occur?

.

Relevant Pages

  • Re: Default SMTP virtual server "Current Connections" Stuck
    ... That is how SMTP works, ... I don't have a 5.5 server handy to telnet to. ... RFC-compliant and isn't going to issue a HELO command (EHLO isn't ...
    (microsoft.public.exchange.admin)
  • Re: Default SMTP virtual server "Current Connections" Stuck
    ... That is how SMTP works, ... I don't have a 5.5 server handy to telnet to. ... RFC-compliant and isn't going to issue a HELO command (EHLO isn't ...
    (microsoft.public.exchange.admin)
  • Re: Default SMTP virtual server "Current Connections" Stuck
    ... Whether it is true or not has nothing to do with why it works with Exchange ... That is how SMTP works, ... I don't have a 5.5 server handy to telnet to. ... RFC-compliant and isn't going to issue a HELO command (EHLO isn't ...
    (microsoft.public.exchange.admin)
  • Re: 554 5.6.1 Body type not supported by Remote Host
    ... I went ahead and created the domain document on the ISA IIS SMTP ... server and I get the same error message except it says HELO. ... the e-mail was being delivered using a Domino SMTP relay server ... Relay server which forwards all outbound e-mails to our external ISA SMTP ...
    (microsoft.public.exchange.admin)
  • RE: SMTP Server remote queue length alert
    ... Thank you for posting in the SBS newsgroup. ... automatically creates a SMTP connector for outgoing messages. ... bridgehead defines the Exchange server which can use this SMTP connector to ... What method is used to send outgoing email (DNS route or ISP ...
    (microsoft.public.windows.server.sbs)
Loading