This posting is not a question but more of a timesaving TIP ...
I have a couple of Android apps on the market (developed with B4A) that utilize SMTP to send emails via Google's Gmail server. Recently I was playing with one of them and was dismayed to find out that emails could no longer be sent because Google was rejecting the logins. To make a long story short, the problem was caused by Google going to a more sophisticated authentication procedure in recent(?) months, making simplistic legacy clients like my own apps fail to connect.
Short of redesigning the B4A client to match Gmail's new requirements, a customer can adjust his/her Gmail settings to allow the old authentication procedure and thus allow apps like mine to continue working (though it does make the login less secure). Here are Google's instructions:
Having said that, does anyone have a solution in B4A code that will make an app compatible with Gmail's newer authentication procedures?
I have a couple of Android apps on the market (developed with B4A) that utilize SMTP to send emails via Google's Gmail server. Recently I was playing with one of them and was dismayed to find out that emails could no longer be sent because Google was rejecting the logins. To make a long story short, the problem was caused by Google going to a more sophisticated authentication procedure in recent(?) months, making simplistic legacy clients like my own apps fail to connect.
Short of redesigning the B4A client to match Gmail's new requirements, a customer can adjust his/her Gmail settings to allow the old authentication procedure and thus allow apps like mine to continue working (though it does make the login less secure). Here are Google's instructions:
Having said that, does anyone have a solution in B4A code that will make an app compatible with Gmail's newer authentication procedures?
In fact, the Net library used in those apps was v1.31. UseSSL was the only mode option then. So I have a feeling that upgrading Net and using StartTLSMode might do the trick 
