Re: NDR's generated after server reboot

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Easy now :-)

You don't have to reboot the server, restarting SMTP will do.

Another solution is to send through smarthost, most ISP's offer this service.

Ole Thomsen


Pete wrote:
I just posted the same issue...and found you guys. We are currently
supporting 22 exchange servers...2 of our clients just reported this
to us. This is a potential disaster to clients..especially when they
are emailing potential clients and we cant verify if they were
received. Restarting 22 exchange servers nightly...uh...hellllll no.
Anyone else have any ideas!!!

Peter

"bozzo" wrote:

I am toying with that idea myself.

Microsoft MVPs -- please look into this and help us out here!

"Ole Thomsen" wrote:

Forgot to mention that my "workaround" is a nightly restart of SMTP,
which causes the NDRs to activate.

Ole Thomsen


bozzo wrote:
An Exchange expert on a knowledgebase site referred me here to find
others experiencing the similar difficulties. He also mentioned he
is aware the Microsoft is currently examining the issue, which I
can hope leads to the discovery of what's causing it and a patch
to solve the problem once and for all. I've found at least 5 or 6
instances of others describing this exact same problem so at least
we're not alone.

"Ole Thomsen" wrote:

I had the same experience in two different sites, and it most
certainly
is caused by some implementations of greylisting.

One is a hosted service delivered by Comendo, www.comendo.com.

Unfortunately the error isn't always reproduceable.

By the time I discovered the problem i could find noone else on
the net with the same, so good to see you :-)

Ole Thomsen


bozzo wrote:
Same here, too.

I've had a handful of users approach me about replies to messages
they had originally sent almost a month ago that were apparently
delayed and released when the server restarted this past weekend,
aside from the 4.x.x NDRs generated to internal staff. Right now
I am trying to determine whether or
not this is a bug that is culprit and if recipients of the
delayed messages are currently using greylisting. The idea that
some outgoing mail is disappearing without arriving where
intended is certainly disturbing.


"david@xxxxxxxxxxxxx" wrote:

Same here. I think the SMTP 451 response is often used for
greylisting - legitimate mail servers will retry, spammers might
not. I've looked
up some of the affected in the tracking database, and it shows
multiple "delivered by SMTP to ...". However, in the SMTP log,
I can see that
it actually got a 451, and didn't really send successfully. So,
I'd add to your questions:

c) Why does message tracking show "delivered" when it receives a
451?

We've worked around this by routing outbound mail through our
ISP (smart host). Their server appears to handle 451 responses
correctly.
I'd prefer it worked properly in Exchange though!

David

"Franz Schenk" <franz.schenkNOSPAM@xxxxxxxxxxxxxxxx> wrote in
message news:eA79Je%232GHA.5032@xxxxxxxxxxxxxxxxxxxxxxx
Have a problem with an Exchange 2003 SP2 installation. When
users are sending messages to external recipients that are
hosted on mailservers with greylisting spam support, the
Emails are sometimes not delivered without any notification
from Exchange to the sender. When the Exchangeserver is
restarted once a week, all these users
are finally getting NDR's like "<Exchangeserver> #4.7.1
smtp;451
4.7.1 Please try again "

In my opinion, this should be a temporary error and Exchange
should try resend the message after 10 minutes (with default
settings on
the SMTP virtual server).

Can anyone give me a hint
a.) Why Exchange doesn't try to resend the messages when
getting a 451 4.7.1 answer?
b.) Why Exchange does create the NDR only after a reboot?

Thank you all in advance for any help
Franz

.

Relevant Pages

  • Re: Exchange Server 2003/Greylisting
    ... Zusammenhang mit Greylisting die Rede war, hier auch ein Problem bei mir. ... Das sind die drei Server, ... Der Exchange versucht es dann aber nie wieder. ... aber es scheint mir zumindest ...
    (microsoft.public.de.exchange)
  • Re: Exchange --> Greylisting
    ... exchange 2k3 does not handle this SMTP answer properly and then ... For those who doesn't know - greylisting is used on some mail servers to ... tempfail first attempt of an email, asking the sending server to retry later. ...
    (microsoft.public.exchange.admin)
  • Re: NDRs generated after server reboot
    ... I had the same experience in two different sites, and it most certainly is caused by some implementations of greylisting. ... Their server appears to handle 451 responses ... I'd prefer it worked properly in Exchange though! ... try resend the message after 10 minutes (with default settings on ...
    (microsoft.public.exchange.connectivity)
  • Re: NDRs generated after server reboot
    ... is caused by some implementations of greylisting. ... aside from the 4.x.x NDRs generated to internal staff. ... Their server appears to handle 451 responses ... I'd prefer it worked properly in Exchange though! ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange 2003 Event 952, no mail between servers
    ... > server the mesages are destined for. ... > Restarting SMTP service nor restarting MTA seem to make any difference, ... > Exchange installed on it, I uninstalled this with no effect. ... > Subordinate routing node failed to connect to its master ...
    (microsoft.public.exchange.admin)