At many client locations, we have shadowprotect and other apps that want to send status reports / mail from a client machine. We've set up firstname.lastname@example.org in our pop / smtp mail server on a shared hosting web server that each client sends from using SMTP. That way we can see what client it comes in from. And there's no extra cost for all these extra sending addresses (incoming mail like bounces and spam redirect to our general business address so these addresses get no mail).
I don't want to have a common mailbox across all locations / clients. If a machine gets compromised and that email@example.com email and password gets out, we have to touch each client machine to change the password.
Moving to office 365, there;s a cost for each mailbox / user that you want to send out FROM (yes, you can have loads of email addresses / aliases at no extra cost for incoming mail. But if you want to send out with different credentials like firstname.lastname@example.org and email@example.com, that will take 2 different office 365 licenses, right? I was thinking that would be $4 / client / month... but now seeing kiosk offerings for $2 / month. That kiosk plan lets you send out via smtp?
Is that the cheapest way to have different machines sending out under different email addresses / passwords? Or some other alternative you'd suggest?
Another way I was thinking is to keep 1 of our other domains we have on the shared hosting email server for the ability to create free pop / smtp accounts.
So rather than firstname.lastname@example.org, we would set up email@example.com (we bought the same domain for our business with .com and .net TLDs). The .net website redirects to the 'real' .com website. And we aren't using any .net email addresses). But keeping that .net domain on the shared email server will save us that $2 / client / month?