badloop.blogg.se - Email bounce back message no longer

Moving the email address to a catch all mailbox, or assigning it to another person, requires someone to manually inspect and deal with any messages that continue to be received.

And again, this requires that the mailbox still exists.

Configuring an server-side inbox rule introduces the risk of an infinite loop if the auto-reply goes to an address that will also automatically respond.

Out of office messages are also typically not processed by automated email systems that cleanse a database of inactive email addresses so as to avoid continually emailing them.

Configuring an out of office message for the mailbox requires that the mailbox still exists (so it can’t be fully decommissioned), and will only fire once per sender, so there’s a risk that a sender will misinterpret the out of office message as a temporary absence.

There’s a few different approaches that can be taken, each of which has pros and cons. Obviously email is such an important communications channel, and individuals are often situated in critical paths for various matters, that it’s normal to feel concerned about what might happen if someone emails the person after they’ve left the organization.

When a user departs an organization, the Exchange admins are often requested to do something with the departed user’s email address to deal with any emails that continue to be sent to the former staff member.