Scan to email - vanishing emails

Forums › IT Pro and developers › Scan to email - vanishing emails

1 | 2

SirHumphreyAppleby

2939 posts

Uber Geek
+1 received by user: 1862

#2897736 6-Apr-2022 17:27

nztim:TBH All printers should now be using modern authentication to talk to azure and NOT imap/smtp and if the printer doesn't support it then the printer should be replaced

Rubbish. These 'modern' authentication schemes have zero to do with security. They're all about control.

OAuth2 adds a dependency on HTTPS as there is no token exchange mechanism within SMTP itself. While this likely isn't a big deal for most uses, there is a need to reauthenticate applications periodically, including after a password change in the case of Google. For a tool which is designed to send notification e-mails without user interaction, this is problematic as it will eventually fail, silently. Further, OAuth2 also puts users at the mercy of the service provider, who may rate limit access to their API (Google does this) and could at any time decide that an application doesn't meet their standards, breaking it for everybody.

SATTV

1670 posts

Uber Geek
+1 received by user: 658

ID Verified

#2897814 6-Apr-2022 20:26

Make sure the DNS is set correctly over even use 8.8.8.8

I typically only use the exchange connector, dont have huge problems. ( you just need to approve the static IP address )

If you are using a P1 account with Auth it should just work, make sure you can use TSL 587 as I dont think M365 can use SSL 465 for some reason.

I have had to use SMTP2Go on a couple of occasions and works very well.

John

I know enough to be dangerous

SepticSceptic

2263 posts

Uber Geek
+1 received by user: 779

Trusted

#2897859 6-Apr-2022 22:45

If no error on the MFD, then as far as it is concerned, the email has been sent.
Been there, done that, seen the movie.

Past experience shows that it's been caught at the mail server side, and not forwarded on for some reason.

Though do check both the device and administrator email addresses are the same as the smtp login account email address.

They will be under the maintenance tab or similar. One of the two tabs in from the left.

O365 scanning is a bit hit n miss at times.

SepticSceptic

2263 posts

Uber Geek
+1 received by user: 779

Trusted

#2897861 6-Apr-2022 22:49

Additionally, is there any copy print management control ? Papercut? Ysoft? Etc

engedib

254 posts

Ultimate Geek
+1 received by user: 93

#2897877 7-Apr-2022 01:07

nztim:

cyril7:

Ahh, should point out in my case it was using a P1 account and authenticating, I still find it odd that the customers domain related SMTP entry (ie xxxxx-co-nz.mail.protection.outlook.com did not work, yet had previosuly, I am keeping an eye on it.

Cyril

to use xxxxx-co-nz.mail.protection.outlook.com you can only send to your own domain, AND your external IP must be in the SPF record

@xpd another thing is has someone in your org created a conditional access policy to disable legacy authentication?

TBH All printers should now be using modern authentication to talk to azure and NOT imap/smtp and if the printer doesn't support it then the printer should be replaced

This is not true, you need to configure a connector in Exchange online, add the public IP of the site. Then you can use unauthenticated SMTP on the MX record.

1 | 2