Feedback by UserVoice

Office 365 Admin

We have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

Welcome to the Office365 Admin UserVoice forum. If you’ve got ideas on how to improve the tenant admin features in the service, such as the Admin Console, Service Health Dashboard, and Message Center, you’ve come to the right place.

If you have feedback for SharePoint admin features, please submit your ideas here SharePoint Administration

Thanks for joining our community and helping improve the tenant admininistration features in Office 365!

Need Tech Support? Please see the Manage Office365 forum in the O365 Community.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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 richie@domain.com, it was misspelled by the sender and typed in richee@domain.com, we want it to go in to catchall@domain.com. Of info and the typed ifno@domain.com, we wan to retain that to our catchall@domain.com email address.

    Thank you.

    296 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →

    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, catchall@domain.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…

  2. Allow redirect rules to work even if forwarding is enabled.

    Allow redirect rules to work even if forwarding is enabled in the Inbox Rules and vice versa.

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →

    If your redirection is set to Store and Forward, then the copy of the messages that is still delivered to the mailbox will have Inbox Rules applied to it.

    Redirection happens before Inbox Rules are applied so if redirection is set to Forward only, Inbox Rules will not be applied. This is by design and not something we will consider changing at this time.

  3. Increase Recipient Rate Limit of 10K for sending using SMTP

    When using SMTP through Office365, there is Recipient rate limit of 10,000 recipients per day, It's not enough. I suggest to raise the value.
    If the mailbox that sending the mail through the SMTP server is reach the limit, The SMTP sever will not send mail through the mailbox for 24 hours.

    Sami Yehezkel

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    try this instead  ·  6 comments  ·  Exchange Admin  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base