Hi Geoff:
The difficulty with using OOF for this, is that OOF fires
ONCE per inbound address until it is turned off, then turned back on again.
An actual rule doesn't have this limitation.
From: [email protected] [mailto:[email protected]]
On Behalf Of Orlebeck, Geoffrey
Sent: Monday, December 07, 2015 10:28 AM
To: '[email protected]' <[email protected]>
Subject: RE: [Exchange] RE: Custom NDR:
I was apparently working off poor information. I was under the impression we
had to immediately disable (remove) the user's mailbox. However, we are
allowed to keep the mailbox for up to 14 days with the OOF set. The main
point is to not forward messages to another user, as for
auditing/discoverability purposes this is against policy.
All that said, I did find out what my issue would be even using the custom
NDR-if the sender is using Exchange, it can overwrite the custom NDR. I sent
from non-Exchange environments and the NDR worked as expected, however
sending from a couple test Exchange servers and the NDR was overwritten with
the generic "recipient server rejected the message". It would not be an
acceptable solution if all Exchange users would not get the proper response,
so we set the OOF and will disable/remove in 14 days.
Thank you for the suggestion, though. We may modify from OOF to rule based,
we'll just revisit in a couple months and see how this is working for us.
Thanks again.
-Geoff
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of John Matteson
Sent: Saturday, December 05, 2015 10:54 PM
To: [email protected] <mailto:[email protected]>
Subject: RE: [Exchange] RE: Custom NDR:
Why not create a rule based inside the user's account? Not an OOF, but an
actual rule. You create your template message, let it fire off, and put an
exemption in for auto-responder type messages (so you don't start a ping
pong match).
You need to keep the account/mailbox up for a while to allow your system to
archive, right?
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey
Sent: Friday, December 04, 2015 2:44 PM
To: [email protected] <mailto:[email protected]>
Subject: [Exchange] RE: Custom NDR:
Okay, so I am back as I think I have everything configured, but the behavior
is not what I expect.
I first setup the custom DSN for internal/external:
Then the Transport Rule:
But when I send a message, it doesn't send the enhanced DSN, even though it
references the code 5.7.225:
Am I missing a step or misunderstanding this? It's the first time I've tried
doing this, so hoping for a little guidance.
Thanks,
Geoff
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey
Sent: Friday, December 04, 2015 7:40 AM
To: [email protected] <mailto:[email protected]>
Subject: [Exchange] RE: Custom NDR:
Disregard. Of course as soon as I hit send I see there is an "-internal"
flag. Going to set the Internal parameter to $false and confirm if it starts
working.
Thanks,
Geoff
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey
Sent: Friday, December 04, 2015 7:34 AM
To: [email protected] <mailto:[email protected]>
Subject: [Exchange] Custom NDR:
I am trying to use a Transport Rule to auto-reply with a rejection alerting
senders to redirect email to another address. I was using the below link as
a guide, but does this apply to external recipients as well? Or only
internal senders?
https://technet.microsoft.com/en-us/library/bb123506%28v=exchg.141%29.aspx?f
=255
<https://technet.microsoft.com/en-us/library/bb123506%28v=exchg.141%29.aspx?
f=255&MSPPError=-2147217396> &MSPPError=-2147217396
I setup a custom DSN code and noticed it is marked as 'Internal', so wasn't
sure if that's just a naming convention or if it actually means it is used
only for internal communication (as the example in the above link is
internal staff communication).
We have policies to delete user mailboxes upon termination as we have an
archiving solution that maintains compliance for regulator/discoverable
timelines. We are not allowed to just set an Out of Office for the two
weeks, so I'm curious how others may handle such a scenario?
Thanks.
Confidentiality Notice: This is a transmission from Community Hospital of
the Monterey Peninsula. This message and any attached documents may be
confidential and contain information protected by state and federal medical
privacy statutes. They are intended only for the use of the addressee. If
you are not the intended recipient, any disclosure, copying, or distribution
of this information is strictly prohibited. If you received this
transmission in error, please accept our apologies and notify the sender.
Thank you.
Confidentiality Notice: This is a transmission from Community Hospital of
the Monterey Peninsula. This message and any attached documents may be
confidential and contain information protected by state and federal medical
privacy statutes. They are intended only for the use of the addressee. If
you are not the intended recipient, any disclosure, copying, or distribution
of this information is strictly prohibited. If you received this
transmission in error, please accept our apologies and notify the sender.
Thank you.
Confidentiality Notice: This is a transmission from Community Hospital of
the Monterey Peninsula. This message and any attached documents may be
confidential and contain information protected by state and federal medical
privacy statutes. They are intended only for the use of the addressee. If
you are not the intended recipient, any disclosure, copying, or distribution
of this information is strictly prohibited. If you received this
transmission in error, please accept our apologies and notify the sender.
Thank you.
Confidentiality Notice: This is a transmission from Community Hospital of
the Monterey Peninsula. This message and any attached documents may be
confidential and contain information protected by state and federal medical
privacy statutes. They are intended only for the use of the addressee. If
you are not the intended recipient, any disclosure, copying, or distribution
of this information is strictly prohibited. If you received this
transmission in error, please accept our apologies and notify the sender.
Thank you.
