Gmail Blocking Email

SUGGESTED

Wondering if anyone can help...just last Monday, our EMAIL is not going through our gmail anymore...looks like it is just not authenticating.

We get ERROR DURING ELECTRONIC DELIVERY.

Unable to login to SMTP connection.
ChilkatLog:
VerifySmtpLogin:
DllDate: Aug 25 2018
ChilkatVersion: 9.5.0.75
UnlockPrefix: SAGECM.CBX112019
Architecture: Little Endian; 32-bit
Language: .NET 4.6 / x86 / VS2017
VerboseLogging: 0
smtpConnectAndAuthenticate:

We have done all the SAGE instructions to allow less secure apps etc.  Please advise if any one is having this issue as well and can help...whats funny is that we have another database in SAGE and that works fine.  Still gmail server, but just different email address.

  • 0 in reply to Kevin M

    Sage 100cloud Standard 2019 (version 6.10.4.0)

  • 0 in reply to Justin Wipeco

    I don't see anything in the release notes... The original start date for this was in June, but I heard rumors of a delay because of COVID work disruptions.

    John, do you know if this was fixed?

  • 0 in reply to Kevin M

    thanks for help on this...just need to figure out what to do now as its broken....can we use a Relay instead?  Does Sage support that way of doing it?

  • 0 in reply to Justin Wipeco

    SMTP relay is a common work-around.  Sage 100 just needs to send to an SMTP server somewhere.  After that it's a matter of email routing / permissions.  Configuring the email stuff is up to you.

  • 0 in reply to Kevin M
    SUGGESTED

    Hi Kevin,  Paperless office and GMAIL oauth requirements are in development.  The rollout was delayed by Google.  Schedule release in FY 2021. 

    https://gsuiteupdates.googleblog.com/2020/03/less-secure-app-turn-off-suspended.html

     Thanks John

  • 0
    SUGGESTED

    I had this happen to a customer using their G-SuiteWorkspace email and I believe what solved it was turning on allow less secure. The other comments are correct that this option to allow less secure is going away but Google has delayed that.

    See support.google.com/.../6260879

  • 0 in reply to Wayne Schulz

    We are still getting this error:

    Unable to login to SMTP connection.
    ChilkatLog: 
    VerifySmtpLogin: 
    DllDate: Aug 25 2018 
    ChilkatVersion: 9.5.0.75 
    UnlockPrefix: SAGECM.CBX112019 
    Architecture: Little Endian; 32-bit 
    Language: .NET 4.6 / x86 / VS2017 
    VerboseLogging: 0 
    smtpConnectAndAuthenticate: 
    smtpConnect: 
    smtpHostname: smtp.gmail.com 
    smtpPort: 587 
    connectionIsReady: 
    Need new SMTP connection 
    --connectionIsReady 
    smtpSocketConnect: 
    socketOptions: 
    SO_SNDBUF: 262144 
    SO_RCVBUF: 4194304 
    TCP_NODELAY: 1 
    SO_KEEPALIVE: 1 
    --socketOptions 
    --smtpSocketConnect 
    smtpGreeting: 
    readSmtpResponse: 
    SmtpCmdResp: 220 smtp.gmail.com ESMTP r67sm2748905oif.43 - gsmtp 
    --readSmtpResponse 
    --smtpGreeting 
    startTLS: 
    sendCmdToSmtp: 
    SmtpCmdSent: EHLO CTC-RDS<CRLF> 
    --sendCmdToSmtp 
    readSmtpResponse: 
    SmtpCmdResp: 250-smtp.gmail.com at your service, [] 
    SmtpCmdResp: 250-SIZE 35882577 
    SmtpCmdResp: 250-8BITMIME 
    SmtpCmdResp: 250-STARTTLS 
    SmtpCmdResp: 250-ENHANCEDSTATUSCODES 
    SmtpCmdResp: 250-PIPELINING 
    SmtpCmdResp: 250-CHUNKING 
    SmtpCmdResp: 250 SMTPUTF8 
    --readSmtpResponse 
    sendCmdToSmtp: 
    SmtpCmdSent: STARTTLS<CRLF> 
    --sendCmdToSmtp 
    readSmtpResponse: 
    SmtpCmdResp: 220 2.0.0 Ready to start TLS 
    --readSmtpResponse 
    TLS connection established. 
    --startTLS 
    ehloCommand: 
    sendCmdToSmtp: 
    SmtpCmdSent: EHLO CTC-RDS<CRLF> 
    --sendCmdToSmtp 
    readSmtpResponse: 
    SmtpCmdResp: 250-smtp.gmail.com at your service, [] 
    SmtpCmdResp: 250-SIZE 35882577 
    SmtpCmdResp: 250-8BITMIME 
    SmtpCmdResp: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH 
    SmtpCmdResp: 250-ENHANCEDSTATUSCODES 
    SmtpCmdResp: 250-PIPELINING 
    SmtpCmdResp: 250-CHUNKING 
    SmtpCmdResp: 250 SMTPUTF8 
    --readSmtpResponse 
    --ehloCommand 
    --smtpConnect 
    smtpAuthenticate: 
    smtp_host: smtp.gmail.com 
    smtp_port: 587 
    domain: www.ctcsupplies.com 
    smtp_user: [email protected] 
    smtpAuthenticate: 
    login_method: LOGIN 
    auth_login: 
    smtpSendGet2: 
    sendCmdToSmtp: 
    SmtpCmdSent: AUTH LOGIN<CRLF> 
    --sendCmdToSmtp 
    readSmtpResponse: 
    SmtpCmdResp: 334 VXNlcm5hbWU6 
    --readSmtpResponse 
    --smtpSendGet2 
    sendCmdToSmtp: 
    SmtpCmdSent: andAY3Rjc3VwcGxpZXMuY29t<CRLF> 
    --sendCmdToSmtp 
    readSmtpResponse: 
    SmtpCmdResp: 334 UGFzc3dvcmQ6 
    --readSmtpResponse 
    sendCmdToSmtp: 
    SmtpCmdSent: {PasswordOrCredentials} 
    --sendCmdToSmtp 
    readSmtpResponse: 
    SmtpCmdResp: 535-5.7.8 Username and Password not accepted. Learn more at 
    SmtpCmdResp: 535 5.7.8 support.google.com/.../ r67sm2748905oif.43 - gsmtp 
    --readSmtpResponse 
    SMTP authentication failed after sending password. 
    Check your username/password or your SMTP server's auth settings 
    --auth_login 
    Failed to login using LOGIN method 
    --smtpAuthenticate 
    ConnectionType: SSL/TLS 
    --smtpAuthenticate 
    --smtpConnectAndAuthenticate 
    Failed. 
    --VerifySmtpLogin 
    --ChilkatLog 

    Is that just because SAGE is not authenticating our GMAIL account we wish to use?  

    Any other suggestions as we have tried all the above?