Support a Catch All email address
Looking to get a catch all email address feature. When we were with godaddy, they had this feature to catch all emails. Example, if email is addressed to firstname.lastname@example.org, it was misspelled by the sender and typed in email@example.com, we want it to go in to firstname.lastname@example.org. Of info and the typed email@example.com, we wan to retain that to our firstname.lastname@example.org email address.
Use of a catch all is strongly discouraged. It is better to provide a bounce back to the sender letting senders know their message could not be delivered as addressed so they can take action. You can also limit the monitored mailbox to only catch formerly valid email addresses.
Any catch all mailbox will receive a good deal of spam and may eventually fill if not closely monitored. (There are receiving limits.)
If you decide to proceed, follow these steps:
1. Create a Dynamic Distribution Group & include “All Recipient Types.”
2. Create a dedicated Mailbox to catch emails, for example, email@example.com.
3. For the specific domain, set the DomainType to “InternalRelay”. If you later remove the catch all, be sure to set the domain back to Authoritative.
4. Create a Mailflow Transport Rule as follows:
- If the Sender is “Outside the Organization”
- Redirect the message to Catchall@domain.com
- Except if the recipient is a member of firstname.lastname@example.org (Distribution Group contains all members)
- Ensure to validate that new mailboxes are added into the Dynamic Distribution Group
I am a one-man shop and was dismayed to learn that catch-all isn't a feature. I use it for authentication security. I have a different address for every online account, something that's recommended by security experts. That way, if Netflix is hacked, for example, the hackers have email@example.com - so, a unique username and password. That won't get them too far.
Also, when I get spam or a cyber-threat, I can see from the "To" line who might have sold my email address or was hacked.
This is very important! Please!
@scott: please do not tell people what they need or tell them that "this or that is a bad idea because..." - That simply does not add value. I NEED a "catch all" functionality - point! And yes, I am an it-professional. I know that there are many aspects of a catch all email account that are bad for many people, but there are use cases where there is no alternative. And currently, because of these use cases, I need to do some fancy settings with an additional group, changing the domain type and adding transport rules instead of just selecting an existing post box to receive all "other" emails.
@scott I think you are completely missing the point here.
We have a system that supports incoming emails that are sent to our customers, like firstname.lastname@example.org, this is so we can identify which customer needs to get which email.
And no, we are not changing this behaviour because it's the domain we are sending out with. At the moment we have 1 mailbox that has over 1000 aliases to support our customers, not scalable.
We are switching out email away from O365 for this reason.
We really need to make sure we can catch all email sent to our @domain.com that do not have a valid email setup. We need the ability to select the email(s) to forward them too so we can make sure they are being handled.
Microsoft are a bunch of morons! It ****** me off that they have this "you don't need this feature" attitude. Just switched to office 365. That plus numerous other features are missing compared to my previous hosting which cost $50 for the entire company per year. Now it costs over $3,000 and they jack features. Infuriating!
Desired by enough that you can merge these:
Upi Struzak commented
This is a very important feature. I just spent 1/2 hour with support implementing the work-around (switch server role to Internal Relay, create a dynamic distro group with all email addresses in it, create a flow rule to send all external email - except if recipient in the dynamic group - to dedicated shared mailbox), and it should not be that difficult...
William Hamilton commented
I have a basic catch-all mailflow rule set up to fwd misdirected email to 2 users in my organization. For some reason, email to 1 of my several Office365 Groups refuses to play along with the stated mailflow rules, despite other technically identical Office365 Groups functioning correctly, and is caught by the catch-all rule. I have spent over a dozen hours on the phone with Office 365 support Reps to eventually be told that they simply don't support catch-all rules and to post my request here. PLEASE provide official support for basic Catch-All rules!
Kamran Marzbani commented
The Catchall possibility to see all emails sent to a non existing email on our domain.
It is very important to have a catch all emails option in the O365 like most of the other main service providers.
Having catch all address for only domain itself is sensible approach to have. Like this, having one that catches all doesn't use fully what Office 365 has to offer with adding multiple domains to manage, but what is it good for if you cant have catch all address and setup bounce processing.
Or, for example xyz.org and erg.org are added as domains, if catchall is xyz, it will catch erg mails for accounts that don't exist, which loses the point of having it on office, even postfix have simple solution.
This is an important feature that is easily implemented in many other email solutions. Depending on the business is it very important that one can capture emails that have been sent from clients or prospective clients to ask for product or service but somehow mistyped the email address. These emails should still be able to be delivered so that appropriate action can be taken.
Same problem here! Hope so we got this feature for Office 365. Google have this option on their G Suite... Normal users don't need this feature, but advanced users need (this is very important feature)!
Henry Yei commented
Current Office 365 rules are not complex enough to imitate a catchall inbox for non-existing mailboxes within the organization. Please implement one that will collect mail going into the organization domain that cannot be delivered. As it is, rules are insufficient and have a lot of quirks, and corner cases where it doesn't apply, or catches much more email that it should not (like grabbing emails from mailbox forwarding to external domains)
Ali Kasim commented
Back before we had O365, we had our email through GoDaddy. It was a pain in the neck, but it had one useful feature that I don’t believe we have anymore. We had a “catch-all” email function, that sent any email directed to email@example.com where xxxx was not a valid address, to a designated “good email address. and we could figure out if the email needed to be forwarded to someone else on our team. We will need to add function like this in Office 365
Hakan UZUN commented
Please add a "catch-all" email address to handle misspellings and emails for former employees that may be important. At my current e-mail provider I get all of them, spam is filtered very well, and I get the rest in my inbox.
Matthew Steeples commented
This sounds to me like a request for a catch-all mailbox (adding this comment so that hopefully it turns up in search results)
There are many cases, when sender writes a wrong email-address.
The common mailbox for those letters will help to company not to lose them