Configuring Maximo for Use with Microsoft's Office 365 Email Service
PeteHalbeisen 060001VQWA Comments (11) Visits (44249)
[Note: Updated 12/12/2018 to add firewall authentication error to the troubleshooting section.]
Configuring Maximo for use with web- or rather, using the term du jour, cloud-based email services is not appreciably different from service to service. On this blog we've covered configuring Maximo to connect to both Google's GMail and Microsoft's Live.com. We'll cover this for Microsoft's Office 365 Email. This configuration is essential the same as Live.com. Additionally, we'll go over a few things that can go wrong with Maximo email configuration.
Office 365 Email Servers & Settings
Microsoft provides these here. It does not appear that these are configurable by the user.
Take Care of SSL
SSL is handled by the application server. Simple certificate instructions and caveats for BEA are here and Websphere are here. WebSphere has a nice "retrieve from port" mechanism. You should be able to import the certificate using the POP/IMAP server and port. An SSL certificate is typically not available via a STARTTLS port. For Office 365, see this example for obtaining the certificate.
The Three Amigos
We'll need three Office 365 email accounts:
maxadmin - our SENDFROM and SMTP administrator
maxlistener - the account the listener will skulk
maxuser - our intrepid service desk user
Send-side (SMTP) Configuration
Aside from the usual host
Update the SendFrom Field in Communication Templates
It's been our experience that Microsoft Exchange configurations do not allow sending of email in which the from address is outside of its domain.
Add a User for Creating Tickets
Email Listener Configuration
Nothing unusual here. IMAP was used (security and workflow configuration not shown for brevity ... )
Create a Ticket / Receive an Acknowledgement
If Something Bad Happens: A Play in 3 Acts
Hopefully you don't have to read this far ... but if you do, hopefully it's only for informational purposes.
When troubleshooting email related problems, it's always helpful to add or set the JavaMail debug property under System Properties to true. This will show the conversation between that API and your email server.
1) If the mail
2) If the send from address is bogus (i.e. the address does not exist on the Exchange server) something bad will happen:
550 5.7.60 SMTP; Client does not have permissions to send as this sender
3) If the mail.smtp.port is not set to 587, something bad will happen:
DEBUG SMTP: trying to connect to host "smt
4) If you're receiving an authentication error please check with your network administration. Your MXServer host may not have have access to send/receive to/from to the email server / port.
A1 NO AUTHENTICATE failed.
As always, thanks for reading!