Outlook 365 whithout smtp?

I would like to automate my emails for work. My admin has blocked smtp for sending emails.

However they allow the use of one other client (beside O365 online, and outlook app): thunderbird. To allow thunderbird to email stuff, they propose to use “OWL”.

Could this be a way to give non-smtp access to O365?


In principle you can use any SMTP service to send emails on behalf of your company’s domain. But they must set up SPF and/ or DKIM to support the “new” SMTP server.

More explaination:
A SMTP server is a server for sending emails, and you can send emails on behalf of any email address in the world. To reduce the amount of spam in the world most email servers for receiving emails check that the sender server is validated for sending on behalf of the email’s domain name. They check the SPF and DKIM settings in the domain’s DNS.

Or you can set up a new email address: yourname@something.com and use that as the sender email, but with reply to your work email, plus you can forward all emails from yourname@something.com to your work email.

Thunderbird in itself is just an email client (software), and as far as I know it can not be controlled by Activepiece.

many thanks for your reply, very informative.

My admin won’t provide me with access to SMTP servers, it’s simply against their policy.

I mentioned the OWL service, as it “emulates/bypasses” the SMTP issue, if I read their website right. (I did not count on thunderbird :wink: ). I believe my hope were not valid. Thank you for your time and explanations.

Just to clarify:

You don’t need access to their SMTP. What you need is for them to add your own SMTP server to the domains SPF setting in the DNS. That will tell all email receiving servers out there that your SMTP is “allowed to send emails on behalf of” your domain.

If they can add DKIM also that would be even better.

So this has actually nothing to do with having access to their SMTP server, but for your company to add some info to the DNS (which has to do with the domain name) to be allowed to send emails on behalf of the domain name.

This is the same solution that is often used when sending emails from supportsystems that are hosted somewhere else, and they send emails from for instance support@[companyname].com

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.