Sending POs from your own email

Suppliers get your POs from your own address, and a copy stays in your mailbox.

This comes with the Business and Enterprise plans. On other plans, and until it’s set up, Mittral emails your POs from its own sending address, with your company named as the buyer. A workspace admin sets it up under Settings → Integrations → Send from your own email, in one of two ways.

Microsoft 365

Choose Connect Microsoft 365 and sign in with the mailbox POs should come from. Microsoft asks you to allow Mittral to send email as that mailbox; Mittral never sees the password. A test email is sent to you, and POs switch over once it arrives.

To send from a shared mailbox, like purchasing@, enter it under Send as a shared mailbox. The mailbox you signed in with needs “Send as” permission for it.
Many organisations only let their Microsoft 365 administrator approve apps. If Microsoft asks for approval, copy the approval link from the same page and send it to your administrator.
Microsoft 365 takes attachments of up to about 2.75 MB in total this way. A PO whose files are bigger goes out through Mittral’s sending instead, with your company named as the buyer, and the PO says so. Those POs count toward Mittral’s daily limit of 300 supplier emails; if it’s been reached, the PO waits and goes out automatically when the limit allows.
If Microsoft stops accepting the permission (someone removes it, the password changes, or it’s unused for a long time), admins are emailed and POs wait. Choose Connect again and they go out on their own.

SMTP settings

For any other email provider, fill in your mail server’s SMTP settings:

Send POs from: the address suppliers see and reply to, like purchasing@yourcompany.com. Your mail server must allow sending from it.
SMTP server and port: 587, 465, 2525. Port 465 is encrypted from the start; the others switch to encryption before signing in.
The user name and password your mail server uses for sending.

Save and send test email sends a test to you through your server. Your POs start going through it only once that test arrives. If it fails, you see your server’s answer, and POs keep going out as before.

The server must be your provider’s public mail server. Mittral checks where its name points when you save, when you test and before sending each PO, and won’t connect to a private or internal address.

Microsoft 365: smtp.office365.com, port 587. Your IT admin may need to allow SMTP sign-in (SMTP AUTH) for the mailbox.
Google Workspace: smtp.gmail.com, port 587. Use an app password, not the account’s normal password.

What changes

POs come from your address, and a copy stays in your sent items.
Bounces and out-of-office replies go to your mailbox, not to Mittral.
“Sent” on a PO means your email server, or Microsoft 365, accepted it for delivery. It doesn’t mean the supplier got it: if their address bounces, the bounce arrives in your mailbox and the PO still shows Sent, so check that mailbox if a supplier says they didn’t receive a PO.
The daily limit on supplier emails doesn’t apply: your own email’s limits do. (A PO too big for Microsoft 365 goes through Mittral’s sending, which has the limit.)
Connections are always encrypted. Passwords and Microsoft’s permission are stored encrypted and never shown again.
Only one way is on at a time: turning one on turns the other off.

If sending fails

If your email is busy or can’t be reached, Mittral tries again later, as it does with its own sending. If it refuses a PO, for example because a password changed, the PO shows it couldn’t be sent, and admins are emailed.

If the connection drops just after a PO was handed over, Mittral can’t tell whether the supplier got it, so it doesn’t send it again by itself. The PO asks a person to confirm before sending it again.

To stop, choose Stop using it or Disconnect: POs go out through Mittral’s sending again straight away.