Error #806 when using scan to email on I-SENSYS MF742CDW printer

[SimonSVK]

I looked up a guide on how to set it up on canon's website. Did everything but it's not working. I'm using Gmail account for the printer.

Settings:

SMTP Port number - 587

SMTP server: smtp.gmail.com

Email address: ****@gmail.com

✅ SMTP authentication, ✅ Set/Change password

I have App password set up in Google account for the printer 

[Lithoman]

#806 is an invalid username/password response from gmail. Since the app passwords are one time use per machine you may need to delete and recreate. If you are trying to reuse a app password for multiple machines, that won't work. You need to create an app password per machine.

[SimonSVK]

I'm not trying to reuse an existing one. I created that Google account just for that printer.

[Lithoman]

Perfect, I still would delete and recreate. Google gets a bit finicky. Also try port 486 and 25. Yes it sounds odd but have had that work in the past when 587 gives issues like this.

Also, log into the web side for that account. Check the security area and device location. I have seen google lock out the "unknown device" until you accept it. Usually though there is an email in the account inbox stating the security issue. 

[Lithoman]

Let me clarify, sorry. Delete and recreate the app password for that device.

[shadowsports · Accepted solution]

Greetings ,

I'm sure @lithoman meant to type "use port 465".   You cannot use port 486 with Gmail.  

Google only allows SMTP relay on ports 587 or 465, 25 will not work.  

Your settings appear to be correct.

smtp.gmail.com

Username is full @gmail.com address

16-Digit app password (note) be careful if you're using, copy and paste as this can introduce spaces)

My printers are configured to use port 587 

TLS needs to be enabled

[Lithoman]

Correct Rick, good catch. I fat-figured that one. 

[SimonSVK]

Thanks, it's working now. It was either the password (I may had pasted it with the spaces) or that I had TLS disabled.

[shadowsports]

Greetings,

Glad it's working.  @lithoman was on this as much as I was so his posts were as helpful as mine.  😀