Re: User receiveing external email, external sender getting repeated NDR
- From: "Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 19:49:50 -0500
rbeck1172@xxxxxxxxx wrote:
I just took over an exchange 2003 cluster running with a Barracuda spam
firewall as an inbound/outbound smtp gateway. We had a user who's
account was deleted (by an incompetent former admin who was fired for
this --- which is why I was given the role)
For deleting a user? It's retty easy to do that. If it wasn't
malicious I don't thin I'd ant to work there. :-(
and recreated and his
email restored from backup. The restored box was put on a different
server as the original, and his client pointed to the restored box and
he now sees all his email/contacts/calendar. His original email box
stayed on the server and showed disabled as it was not connected to an
AD account.
The mailbox was restored to another machine and reconnected to the AD?
This other server is, presumably, in another AD forest?
The original mailbox is still on the "real" Exchange server
(presumably because the Deleted Mailbox Recovery time hasn't expired),
but it hasn't been reconnected to the "new" user? If that's the case,
why restore the mailbox if it's still on the "production" server? Why
not just connect the mailbox to the user and go home?
We now have an issue where an external sender will send him and email,
he'll receive it normally,
Which make it sound like you restored his mailbox into the same
Exchange organization?
but the sender will get repeated NDR's from
the barracuda and it stays in the "IN" queue of the barracuda.
How's this a problem with Exchange?
I did
disable our NDR reporting on the barracuda, and have not heard of the
senders getting NDR's since, but there is still the issue of the
external emails for that particular user getting stuck in the inbound
queue.
Is there an acknowlegdement sent by exchange upon sucessful receipt
that isn't being sent?
Just the regular old "240" status code.
Below is the message the sender would receive. I talked to the folks^
at Barracuda, and they say that they don't see an issue on their end
:Final-Recipient: rfc822; user@xxxxxxxxxxxx
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Spam-Firewall; host 127.0.0.1[127.0.0.1] said: 421
4.3.2
Service shutting down, closing channel (in reply to end of DATA
command)
This is the Spam Firewall at mail.xxxxxxx.com.
|
Is this the Barracuda ----------+
Whatever it is, using address 127.0.0.1 means it's running on the same
machine. Exchange doesn't have a "Spam Firewall".
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: User receiveing external email, external sender getting repeated NDR
- From: rbeck1172@xxxxxxxxx
- Re: User receiveing external email, external sender getting repeated NDR
- References:
- Prev by Date: Re: Exchange logs - owa
- Next by Date: Re: Exchange default server during AD user creation
- Previous by thread: Re: User receiveing external email, external sender getting repeated NDR
- Next by thread: Re: User receiveing external email, external sender getting repeated NDR
- Index(es):
Relevant Pages
|
Loading
