Can a shared mailbox be used for SMTP relay?

Mailboxes, Aliases, Shared Mailboxes, and Groups

If your business is in the adoption phase of Office 365 Email, you will want to think about all of the email addresses in your company and how they will be brought in to Office 365. There is a tendency to want to create a mailbox for every email address in your business or, an email address for every employee and aliases if an employee is responsible for an email address other than his or her own. While these options will likely work, and may be the best fit for some businesses, they could also lead to inefficiencies, difficulty making changes later and worst, be an unnecessary expense.

Here’s what you need to know:

A mailbox is usually associated with a single user and requires a license. A mailbox is required for a user to log on to and use Office 365 email.

  • Mailboxes require a paid license
  • Users need a mailbox in order to log in and use email

An Office 365 Email alias is simply another email address attached to your mailbox. You can have multiple email addresses that all come into your inbox. One of those email addresses is your “primary” email address and any email you send will appear to come from your primary email address, even if you reply to an email sent to another of your email addresses.

  • An alias is another email address that a user can be reached at
  • Aliases do not require a license
  • All email sent to an alias goes into the users inbox and must be manually separated if required or separated using rules
  • The primary email address is the address mail sent by the user will appear to come from
  • It is not possible to send an email message and have it appear to come from an alias

A shared mailbox is just that, a mailbox that can be shared with one or more users. Shared mailboxes do not require a license and have all of the features of a normal mailbox; they have an inbox, a calendar, a contact list etc.

  • Shared mailboxes cannot be logged into directly, a user must have their own mailbox to be able to use a shared mailbox
  • Shared mailboxes are not supported on mobile devices
  • Shared mailboxes appear as separate mailboxes in Outlook and Outlook on the web.
  • A user can send email and have the message appear to come from the shared mailbox email address
  • If a user replies to a message in a shared mailbox, the reply appears to come from the shared mailbox email address
  • A user can also (if they have permission to do so) send a message “on behalf of” a shared mailbox. The message will appear to come from “Jane Doe on behalf of
  • Calendars and contact lists in shared mailboxes are fully useable by users having access to the shared mailbox
  • Email sent from a shared mailbox do not by default appear in the sent items of the shared mailbox but rather the sent items of the user sending the email message. This behavior can be changed however
  • Shared mailboxes support subfolders i.e. it is possible to create folders under inbox for example in order to organize email

*

Office 365 Groups have much the same functionality as shared mailboxes. Groups however can have associated SharePoint Team Sites, OneDrive documents, and OneNote notebooks. If collaborating around a mailbox is important to your business, a group may be a better fit than a shared mailbox.

  • Like shared mailboxes, groups cannot be logged into directly
  • Groups are supported on mobile devices
  • Groups appear beneath a users mailbox in Outlook
  • A user can send email and have the message appear to come from the group email address
  • A user can also (if they have permission to do so) send a message “on behalf of” group. The message will appear to come from “Jane Doe on behalf of
  • Email sent as a group email address will not appear in the group Sent Items folder, in fact there is no visible Sent Items folder. This cannot be changed
  • Groups do not support subfolders. Currently, this cannot be changed.

Office 365 Groups vs. Shared Mailboxes

Can a shared mailbox be used for SMTP relay?

Update (November 2022): Read Tony Redmond’s take on this topic five years on after Microsoft has given Outlook Groups a lot more functionality.

I was recently asked for my thoughts on using Office 365 Groups instead of shared mailboxes. Groups in Office 365 have many of the features that Exchange Online shared mailboxes do.

  • Multiple users can access a Group mailbox, just as they would a shared mailbox.
  • A Group mailbox can be used as a single point of email contact for a team or group of users, just as a shared mailbox can be.
  • Users can send-as or send-on-behalf of a Group mailbox, just as they would a shared mailbox.
  • Emails sent to Groups and shared mailboxes are preserved for historical reference, unless deleted by a user.

Office 365 Groups have additional features that shared mailboxes do not.

  • Users (members) can subscribe to receive a copy in their own mailbox of the emails sent to the Group mailbox, which makes Groups work in a similar manner to distribution lists.
  • Groups include additional collaboration apps and resources such as a SharePoint team site, OneNote notebook, Planner, and Teams.
  • Groups have a guest access model for external collaboration that shared mailboxes do not.
  • Groups have connectors for integrating other applications.

However, shared mailboxes have some capabilities that may make them more suitable to teams than Groups.

  • Shared mailboxes can have sub-folders in the mailbox, whereas Group mailboxes can’t.
  • Shared mailboxes have more granular permissions available than Groups do.

There is some demand for Group mailboxes to have sub-folders, as shown in the comments on this Uservoice suggestion. It’s quite common for teams that use a shared mailbox as an inbound communication channel to user sub-folder to sort or file away items that have been actioned. Although I prefer to recommend a proper ticketing/job management system instead, I understand that simpler scenarios don’t warrant setting up a whole separate system and that a shared mailbox with some sub-folders is quite sufficient.

The sub-folders capability is also a problem for anyone considering migrating public folders to Groups. If the public folders have a complex folder hierarchy that needs to be preserved, then you will basically lose that hierarchy due to the lack of sub-folders in Groups.

As it stands right now, the decision to go with Groups or shared mailboxes is a case of “it depends”. Work out which limitations are a showstopper for you, and which capabilities you need the most, and then make your decision based on that. Given the interest that Microsoft has in Groups adoption, perhaps we’ll see the sub-folders capabilities show up in the future.

Photo by Brendan Church on Unsplash

About the Author

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.

Can you use a shared mailbox for SMTP server?

Custom SMTP connections are typically configured using a user's credential for on-prem Exchange shared mailboxes. Once configured successfully, emails sent from that shared mailbox will be delivered through your Exchange servers, but not stored or visible in the sent folder.

Can Office 365 Shared mailbox use SMTP?

Save this answer. Show activity on this post. Office 365 Shared Mailboxes (user without Exhcange licence) do not have SMTP access to Exchange online, which is a bit different from behaviour you might expect when coming from on premise Exchange.

Can a shared mailbox be used to send emails?

A shared mailbox makes it easy for a group of people to monitor and send email from a public email alias like [email protected]. When a person in the group replies to a message sent to the shared mailbox, the email appears to be from the shared address, not from the individual user.

Does Office 365 allow SMTP relay?

SMTP relay lets Microsoft 365 or Office 365 relay emails on your behalf by using a connector that's configured with your public IP address or a TLS certificate.