Office 365 Problems with Scan to email using WorkCenters 3315 & 3325 to

[NikosTopsis]

There is a video because the driver understood but did not help me

[Joe Arseneau]

MS killed that server about a year ago, and it is long since not needed as the latest firmware fixed the issue that made it necessary to use it. Since you did not post what model or settings or anything relevant I cannot proivide you with the latest firmware.

"Does not work" is not enough to even begin to help you.

[XeroxAdvisicon]

Does not work

[Joe Arseneau · Accepted solution]

If you can't email to one person the machine is not the problem, the mail server makes the decision once it receives the email, not the printer.

If that user is on another domain, it is likely that you are setup without a relay server side so you can only email from the MFP to your internal domain.

As for the SSL/TLS issue, just don't bother with it, MS has done things right with their system and created virtual servers for their users so authentication is not even required.

Smtp server: [domain].mail.eo.outlook.com

Outgoing port: 25

No encryption, no authentication.

Example:

So if Xerox.com was your domain  xerox-com.mail.eo.outlook.com
would be the SMTP server (That hyphen is not a misprint, you replace . with -)

[Berggren1975]

Similar issue with a Xerox 3635.  When we set up office 365, we successfully configured the Phaser to scan to emails in hosted exchange.  Recently we've added a new user, but cannot get scan to email to work for the new email.

What needs to be done?

[AXA1GA · Accepted solution]

1. Obtain the public IP address you’re using. A dynamic IP address isn’t supported or allowed. You can share the IP with other devices and users, but you shouldn’t be sharing the IP with anyone outside of your company. Make note of this IP address for later.

2. Log on to the Office 365 Portal.

3. Select Domains. Highlight one of your domains and use the wizard to obtain your MX record. The MX record will look similar to contoso.com.mail.protection.outlook.com. Make a note of the MX record for later.

4. Make certain that the domains that the application or device is sending as have been properly verified. If the domain is not verified, emails could be lost and you won’t be able to track them through Office 365 using Message Trace.

5. In the upper right, select Admin and then select Exchange from the drop down. If you have Small Business, then see the instructions here.

6. In the Exchange Admin Center, select Mail Flow > Connectors.

7. If no inbound connector exists, create one.

8. Give the connector a name.

9. Select On-Premises for the Connector Type.

10. Under Domains, add a single asterisk (*). This will allow sending to any domain. Other values in this field will limit the domains that you can send mail to.

11. In the IP Addresses section, add the IP address from Step 1.

12. Leave all the other fields with their default values and select Save.

13. In the DNS for your domain, we suggest that you modify your SPF record to include the IP address from Step 1. The finished string should look similar to this: v=spf1 ip4:10.1.2.3 include:spf.protection.outlook.com ~all where 10.1.2.3 is your public IP address. Skipping this step could cause email to be sent to recipients’ junk mail folders.

14. In the device’s settings, specify a Smart Host value equal to the MX record value you recorded in Step 3.

[RickVB11104-XAD]

I meant TLS 2.0

[RickVB11104-XAD]

I believe the device needs to be TSL 2.0 to work with office 365 smtp server. I had to create my own smtp server internally to use the scan to email on HP and Xerox devices.

[JoeTudisco]

My company has just migrated over to Office 365 and I can't get the scan to email to work. I have used smpt.office365.com with ports 587 and 25. I have also tried fioranotile-com.mail.protection.outlook.com with ports 587 and 25. when I click on the smptn config test, it just times out. I have 3 units and tried everything on all 3 with no luck. Help !!!!