No more mail with google

As we already know, Google has disabled these days the simple user-pass email authentication.

Workaround with i.e. Outlook is to enable 2 factor authentication into google account and create a app-specific password.

I tried the same with routerboard with no success :

18:02:02 e-mail,debug recv: 250-smtp.gmail.com at your service, [185.234.165.29] 
18:02:02 e-mail,debug recv: 250-SIZE 35882577 
18:02:02 e-mail,debug recv: 250-8BITMIME 
18:02:02 e-mail,debug recv: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH 
18:02:02 e-mail,debug recv: 250-ENHANCEDSTATUSCODES 
18:02:02 e-mail,debug recv: 250-PIPELINING 
18:02:02 e-mail,debug recv: 250-CHUNKING 
18:02:02 e-mail,debug recv: 250 SMTPUTF8 
18:02:02 e-mail,debug send AUTH PLAIN AGtrb3JhbG10cEBnbWFpbC5jb20mNvbQBrb3JhbGxvc210cEBnbWFpbC5jb20= 
18:02:02 e-mail,debug recv: 535-5.7.8 Username and Password not accepted. Learn more at 
18:02:02 e-mail,debug recv: 535 5.7.8  https://support.google.com/mail/?p=BadCredentials q12-20020a056402248c00b0042def6cd141sm5188233eda.30 - gsmtp 
18:02:02 e-mail,error Error sending e-mail <Test>: AUTH failed 
18:02:02 e-mail,debug send RSET

Is this because google app-password uses Oauth2 unsupported by routerOS ??

Any workaround other than choose another smtp service provider ?

http://forum.mikrotik.com/t/posts-not-strictly-related-to-v7-3-and-v7-3-1-stable/158547/9

i had to activate second factor auth in google account and then enable application password on google account

now i use that password for email tool on routeros

That’s what I’ve done….
But I get the shown error.

Please provide export from /tool/e-mail (hide public info such as account and password)

I have this an it works (password is provided in script)

/tool e-mail
set address=142.251.5.108 from=my.name@gmail.com port=587 tls=starttls user=my.name@gmail.com

EDIT:
password is not shown in normal export. It’s there when using show-sensitive.

/tool e-mail
set address=142.251.5.108 from=my.name@gmail.com password=<supersecret> port=587 tls=starttls user=\
    my.name@gmail.com

@ik3umt
On AUTH PLAIN is base64 encoded your addres and password hash… kk*****tp@gmail.com / *******…

Better if you delete that line and change that password everywhere, your routerbord included…

E sarà maglio che fai in fretta :wink:
Spero non sia la stessa password su …ir3ip.net…

Ciao. (IU5)

In my case it was Monday night that stuff stopped being able to use several different G-Mail accounts (as opposed to 30 May). However, yesterday added 2 factor authentication to three different G-Mail accounts and added app specific passwords (make sure you select Email on the google account security page). Then updated almost 20 devices (including three Mikrotik routers) to use the appropriate app specific password, and they are all working just fine.

/tool e-mail
set address=smtp.gmail.com from=RB750r2-2 password=redacted port=587 \
    start-tls=yes user=redacted@gmail.com

i use it in this way

/tool e-mail
set address=smtp.gmail.com from="Router" password=pwdpwdpwdpwd port=587 start-tls=yes user=router@gmail.com

i use routeros v6 :open_mouth:

I should have said, mine is also 6.49.6 (all three routers).

I don’t recall anymore when it was but there was a point where dns name could not be used (or my config was wrong then :laughing: ).
So I used the IP address instead.

Just tested again with ROS7, works as well using smtp.gmail.com.

It Works, Thanks

I had a related issue recently – I was dealing with a ‘Cannot Verify Email Existence’ problem, which was a nightmare since I use email daily. After some digging, I found that the first step is to double-check your email address for errors. Also, if there’s a delivery error message, verifying the recipient’s email address is crucial. For Gmail users, following Gmail Help’s instructions is a good idea. Checking your mail server settings and DNS entries is vital for smooth email operations. Contacting your email provider’s support can sometimes clear up any configuration issues.

I stumbled upon a helpful article providing straightforward steps to tackle these email issues. If you’re interested, you can see it here.