Let users send as another mailbox
A Microsoft 365 sending account sends newsletters through the mailbox of the person who signed in when it was added to
JungleMail 365. To send from another address, for example the shared mailbox news@enovapoint.com, that person needs
one of two Exchange Online permissions on it:
- Send as: the newsletter comes from the shared mailbox alone.
- Send on behalf: recipients see that it was sent by the person on behalf of the shared mailbox, for example “Daniel Okafor on behalf of EnovaPoint News”.
JungleMail uses whichever the person has, and Send As when they have both. Full Access alone doesn’t let anyone send.
Give Send as on a shared mailbox for a site’s regular newsletters: readers see one sender whoever wrote the issue, and replies reach everyone who reads the mailbox. Give Send on behalf only when readers should see who sent the newsletter, such as an assistant sending for a manager.
Newsletters sent through Bird Cloud Email Service or the JungleMail mail server don’t go through your Exchange and need no permission; to use your own domain with them, see Send from your own domain.
Before you begin
Section titled “Before you begin”- You need permission to manage mailbox permissions in Exchange Online, for example the Exchange Administrator role.
- You need to know whose mailbox sends: the account that signed in when the Microsoft 365 sending account was added. A JungleMail site administrator can tell you.
Give Send As permission
Section titled “Give Send As permission”- In the Exchange admin center, go to Recipients > Mailboxes.
- Select the shared mailbox, for example EnovaPoint News.
- On the Delegation tab, under Send as, select Edit.
- Select Add members, choose the person whose mailbox sends, for example Daniel Okafor, and select Save, then Confirm. Add Send As alone: the person needs Full Access only if they also read the mailbox.
Or in Exchange Online PowerShell:
Add-RecipientPermission -Identity news@enovapoint.com -Trustee daniel.okafor@enovapoint.com -AccessRights SendAsFor Send on Behalf on a shared mailbox, use PowerShell; the Exchange admin center doesn’t offer it for shared mailboxes:
Set-Mailbox -Identity news@enovapoint.com -GrantSendOnBehalfTo @{Add="daniel.okafor@enovapoint.com"}Microsoft describes both permissions in Manage permissions for recipients in Exchange Online.
Then in JungleMail
Section titled “Then in JungleMail”A JungleMail site administrator sets the sending address’s From to Specified email address and enters
news@enovapoint.com (Add and manage sending addresses). When the
address is saved, JungleMail sends a test email through the mailbox and refuses the address if Exchange rejects it.
A new permission doesn’t apply at once: if the test fails right after you granted it, wait a while and try again.
Microsoft says this can take about an hour
(About shared mailboxes in Microsoft 365).
- Send from a shared mailbox, not a person’s. A shared mailbox needs no license of its own up to 50 GB and isn’t tied to anyone’s job. Keep sign-in blocked for its own account, as Microsoft says: the person with Send As signs in to JungleMail, never the shared mailbox (About shared mailboxes in Microsoft 365).
- Give the permission to an account that stays. When that account loses Send As, or leaves, newsletters pause with Paused (sending account error – Send As permission denied) (Newsletters stop sending after a password change). Before you remove either, tell the site’s administrators, so that they first add the shared mailbox through another account with Send As (Add a Microsoft 365 sending account).
- Have someone read the shared mailbox. Replies and out-of-office answers to a newsletter for all 2,412 EnovaPoint employees arrive there. A shared mailbox that reaches its storage limit can no longer send, so its newsletters stop too (About shared mailboxes in Microsoft 365).

