M5526 and scan to email failure

**Leebs14** · 06-23-2021

so I have been having a battle with one of these machines trying to get it to scan to email, I have done this a thousand times and am sure the settings are correct but it simply will not work!!!

loaded the latest firmware today and still the problem persists.

settings are

STATIC IP ADDRESS
GATEWAY AND DNS ALL CHECK OUT

SMTP Server - mail.smtp2go.com
SMTP PORT - 587
SMTP TIME OUT - 180
AUTHENTICATION - ON
AUTHENTICATION - OTHER
LOG IN USER NAME & PASSWORD ARE CORRECT
SMTP SECURITY - START/TLS

**ntbann** · 06-23-2021

Did you try the ip address for mail.smtp2go.com? You may have a dns issue.

**sparkycivic** · 06-23-2021

what error code is generated upon failure?

**mojorolla** · 06-23-2021

Did you populate the Sender Address under Email Send Settings ?
What is the error code when it fails. This code will indicate the nature of the error (user /password, name resolution, etc...)

You can turn off security and use port 2525 to see if you get the same error.

**Reed** · 06-23-2021

I found another smtp server that I like a little better.

Sendinblue.com

You have to register but it allows you 300 emails a day

Sent from my SM-G955U using Tapatalk

**bsm2** · 06-23-2021

What's the error code?

**Leebs14** · 06-24-2021

Sorry i should have put the error code it is 3102

**Leebs14** · 06-24-2021

Originally Posted by ntbann

Did you try the ip address for mail.smtp2go.com? You may have a dns issue.

I tried another smtp server and got the exact same error - 3102

**mojorolla** · 06-24-2021

Sounds like a DNS issue and it cannot resolve the name. Did you try ip address instead as suggested (47.79.71.155) ?
Go into Command Prompt and run ipconfg /all. This will list the default gateway and DNS server address.
If the ISP DNS settings fail you can also try Google or OpenDNS

**sparkycivic** · 06-24-2021

3102 - error: server response.
generic unhelpful stupid error information, thanks Japan.

I usually encounter this when the server does not allow access for some reason like two-factor auth needed, or device access granted only explicitly per device. In Gmail, one needs to enable access to "less secure devices" before using a scanner.

you might need to wireshark the interface in order to see the server response in plaintext and understand what's really happening.