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 email@example.com, it was misspelled by the sender and typed in firstname.lastname@example.org, we want it to go in to email@example.com. Of info and the typed firstname.lastname@example.org, we wan to retain that to our email@example.com email address.
We are investigating whether to implement this feature. As mentioned previously, this can be accomplished with a mail flow rule.
We wanted to here from you and have set up an email address to get your feedback instead of having you publicly post them in the comments section.
There is the risk that catch-alls will be turned on by organizations and just become a spam trap that is never looked at but using up large amounts of resources that affect our ability to provide fair use across the service. We are looking for the best solution to meet your needs and still protect our service.
Here are a few questions:
1. What is the type/size of your organization?
2. Why do you want a catch all address?
Is it for just misaddressed emails or emails to common addresses like firstname.lastname@example.org that you do not have a mailbox for? Is it to continue receiving message to former employees? Knowing your scenarios will help us tailor a solution to meet those needs.
3. Does the mail flow rule solution meet you needs but you feel there should be a simpler, native solution for this? Otherwise how is it unable to meet your requirements?
Please email your feedback to email@example.com.
Thank you in advance. We can’t promise that we will implement the feature, but we would like more information before making that decision
I also use on the fly created unique email addresses for all webshops, clubs, maillists etc. which allows me to route and sort my incoming mail (300+ per day) much more efficiently.
Ideally office365 should support emailaddresses containing wildcards - or even better - regular expressions for group names so a group could receive all mails to e.g.
myname-ml-.*@mydomain -> myname # route all maillists to my account
support@.* -> mysupport mailbox # route support of any of my domains to my support account
.*@mydomain -> catcallmailbox # route the rest to a catchup mailbox.
I don't mind using rules for this, if they support proper filtering.
What I DO mind is that I have to fiddle with my domain definition/routing to accomplish this.
1) My organization is my family, we have a half dozen emails. Personal emails.
2) The catch all for me is used to make up email aliases on the fly. Good when shopping online, lets me know who sells my address.
3) The way it works now, I have every email that doesn't match an account come to me. Works well for me.
I would like to see a catchall option for my domain as when people leave my non-profit, it's the best way to handle any and all email that is being sent their way - even 3 years after they've left the organization - especially because I can see who it's being sent to. Also, it's the only way to catch misspellings. Nothing like missing a bill because someone sent the invoice to adimn@ instead of admin@.
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 firstname.lastname@example.org - 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 email@example.com, 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 firstname.lastname@example.org 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