New webmail feature is flawed. Please access Gmail properly without forcing users to lower security settings

SOLVED

I was happy to see Sage 50 finally integrated the ability to send emails through "webmail", however this feature is flawed when used with Gmail. Sage 50 attempts to connect to Gmail's SMTP server using Basic Authentication, but Google has had Basic Authentication disabled by default for two years!

This issue occurs when you try to sync to a Gmail account after July 15, 2014 and Basic Authentication has not been enabled for your Gmail account.

Google has increased its security measures to block access to Google accounts after July 15, 2014 if those accounts are being set up or synced in apps and on devices that use Basic Authentication. -https://support.microsoft.com/en-us/kb/2984937

The only way around this is for users to enable "allow access for less secure apps" in their Google security settings, but as a consequence "makes your account more vulnerable".

Google may block sign-in attempts from some apps [Sage 50] or devices that do not use modern security standards. Since these apps and devices are easier to break into, blocking them helps keep your account safe. -https://support.google.com/accounts/answer/6010255?hl=en-GB

Unfortunately I am not going to lower my Gmail security settings just to use the webmail feature. I would hope and urge the Sage 50 developers to access Gmail as most modern apps with similiar functionality have been doing this for a while (eg. Mozilla Thunderbird, Windows 10 Mail, etc). I suspect the following developer docs about the Google/Gmail API platform explain how to access the service properly: https://developers.google.com/+/web/api/rest/oauth#authorization-scopes and https://developers.google.com/gmail/api/auth/about-auth

Looking forward to a future update that fixes this issue.

Parents
  • 0
    This still hasn't been fixed in version 2017.0.

    I am very disappointed that I am still unable to email invoices, receipts, etc from Sage 50 using a Gmail based email address.

    This isn't a hard fix to implement. There are open source email clients on GitHub coded by a lone person that are able to implement proper Gmail security measures, but Sage, whom I am paying hundreds of dollars for their software either cannot or will not do it.

    I am seriously considering other solutions to replace Sage when the license expires.
  • 0 in reply to ivxn
    Hello, please see the 5 steps as described in this post for how to have Gmail allow external programs to connect to it.

    sagecity.na.sage.com/.../what-should-i-do-if-i-am-unable-to-email-from-sage-50-2016-3
  • 0 in reply to Erzsi_I

    Erzsi_I,

    I do not think you have read this thread very carefully because you've posted twice to someone who already described the workaround you're recommending before you posted. Look at the original first post, which also briefly described what the consequence of that workaround is:

    The only way around this is for users to enable "allow access for less secure apps" in their Google security settings, but as a consequence "makes your account more vulnerable".

    Google may block sign-in attempts from some apps [Sage 50] or devices that do not use modern security standards. Since these apps and devices are easier to break into, blocking them helps keep your account safe. -https://support.google.com/accounts/answer/6010255?hl=en-GB

    This is not a good solution, this is workaround that compromises Google account security, and your post that you linked should at the very least caution less tech-savvy users that the workaround does this; it would be irresponsible not to. No IT department worth their salt would recommend doing that, so why would you or Sage Support? This is like telling your clients to disable their software firewall to get around a bug in your software. Yes - it's a bug, because Sage 50 is not accessing Gmail properly. They implemented a deprecated way of doing something in their 2016 release that had been deprecated since about 2014. Unreal.

    A better "workaround" is not to use Sage's webmail feature for Gmail. But to select "use default desktop email program", and install Mozilla Thunderbird [configured with one's Gmail account].

  • 0 in reply to ivxn

    Are you aware there is a second Gmail method which does not require lowering security? Briefly, I have to run, here's a c/p from a ticket I had dealing with a client using Outlook. should work with Sage too. It's yet another cumbersome workaround compared to Sage having native OAuth 2.0 support, but if security is your concern, you don't  mind dealing with the minor inconvenience to get there. You would actually INCREASE your Gmail security by setting it to use 2-step authentication, then you do not need to "allow insecure apps (to use basic auth)" but instead you generate a unique password to be used by each app only.

    "The important point to remember is that for the @gmail.com account, you have a specially-generated second password to use in Outlook. This is because your gmail account has been configured by you for heightened security (2-step authentication). A 2-step login can not be accomplished in Outlook, and gmail views your version of Outlook as an ‘insecure application’. So they rather you not use your master gmail password in it at all.

    If Outlook starts to give password errors FOR THE GMAIL account and it does not resolve on its own after a few hours or after a reboot, then log into Gmail webmail and generate a new app-specific password following these instructions:

         https://support.google.com/accounts/answer/185833?hl=en

    Then enter that new password without spaces into Outlook for the gmail address only"

Reply
  • 0 in reply to ivxn

    Are you aware there is a second Gmail method which does not require lowering security? Briefly, I have to run, here's a c/p from a ticket I had dealing with a client using Outlook. should work with Sage too. It's yet another cumbersome workaround compared to Sage having native OAuth 2.0 support, but if security is your concern, you don't  mind dealing with the minor inconvenience to get there. You would actually INCREASE your Gmail security by setting it to use 2-step authentication, then you do not need to "allow insecure apps (to use basic auth)" but instead you generate a unique password to be used by each app only.

    "The important point to remember is that for the @gmail.com account, you have a specially-generated second password to use in Outlook. This is because your gmail account has been configured by you for heightened security (2-step authentication). A 2-step login can not be accomplished in Outlook, and gmail views your version of Outlook as an ‘insecure application’. So they rather you not use your master gmail password in it at all.

    If Outlook starts to give password errors FOR THE GMAIL account and it does not resolve on its own after a few hours or after a reboot, then log into Gmail webmail and generate a new app-specific password following these instructions:

         https://support.google.com/accounts/answer/185833?hl=en

    Then enter that new password without spaces into Outlook for the gmail address only"

Children
No Data