Re: Mail from: shows internal server name in mail header and fails
- From: "skyline" <skyline@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 Sep 2005 05:59:02 -0700
The SMTP server generated the NDR. Both servers are allowed to relay through
the SMTP server and many clients get the emails from the new application
server but some do not.
We are investigating the following link as this may relate to the problem:
http://www.dylanbeattie.net/docs/iis6_bare_linefeed.html
Although we did not upgrade the version of IIS the new application server is
running a .NET app different from the Adobe application on the first app
server to generate the emails and I have the sneaking suspesion they
programmed it incorrectly.
Thanks for the reply and if you have any other thoughts please let me know.
"Al Mulnick" wrote:
> Which server generated the NDR?
> Likely a relay restriction, but it would be helpful to know which MTA
> created the NDR.
>
> Al
>
>
> "skyline" <skyline@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:325196A5-27FC-4883-8394-87C217F21AD0@xxxxxxxxxxxxxxxx
> > 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?
> >
>
>
>
.
- Follow-Ups:
- Re: Mail from: shows internal server name in mail header and fails
- From: Al Mulnick
- Re: Mail from: shows internal server name in mail header and fails
- References:
- Mail from: shows internal server name in mail header and fails
- From: skyline
- Re: Mail from: shows internal server name in mail header and fails
- From: Al Mulnick
- Mail from: shows internal server name in mail header and fails
- Prev by Date: Re: Can IIS due multiple smarthosts ?
- Next by Date: Re: Mail from: shows internal server name in mail header and fails
- Previous by thread: Re: Mail from: shows internal server name in mail header and fails
- Next by thread: Re: Mail from: shows internal server name in mail header and fails
- Index(es):
Relevant Pages
|
Loading
