With the development of cloud based services, customer are moving to hosted email services like Office 365 hosted Exchange server.
EveryeonePrint Email print feature requires a dedicated Inbox to receive email print job requests, this can be setup using Office 365 Exchange.
Configuring Everyoneprint incoming email settings to work with Microsoft Office 365:
- Mail server type: Exchange Web Services (recommended)
- Mail server address: include full URL like: https://outlook.office365.com
- Mail domain name: leave the "mail domain name" empty
- Incoming Mail Account Settings: enter the required credentials
Office 365 and ADFS authentication:
Starting with EveryonePrint 4.2 we've added support for customers using hosted Microsoft Office 365 Exchange with AD FS single-sign-on authentication. Same setup as above applies.
Warning: Due to the nature of cloud based solutions and the need to provide new features or for technical and security reasons, there might be changes over time on the Microsoft side that can have an impact on the ability to connect and/or retrieve emails correctly.
If you do experience any unusual behavior or have trouble making the feature work,please contact our Customer Support.
Advanced Threat Protection:
For enhanced security reason real time Advanced Threat Protection (ATP) may have been enabled on Office 365 Email Print incoming mailbox.
What this means is that received attachments are scanned before being accepted in the inbox. However, the email body is almost immediately released and available, while the attachments, depending on their size, could be held whilst the scan is taking place.
The consequence is that in some occasion, Office 365 will not deliver the attachment itself but a separate download link to the attachment, which would be impossible for EveryonePrint to access.
Do not enable Advanced Threat Protection (ATP) on the Email print inbox.
Note: If you're using the EveryonePrint Built-in conversion engine, there is practically no risk with even harmful Word documents, since the conversions don't take place inside of MS-Office, but inside a virtual memory space in a Java process, so even if a document was attempting things, which would break something, it would only "crash" within the memory space, and there would be no harm.