On Sun, 20 Oct 2019 21:36:49 +0100, MArtin
 declaimed the following:


>         250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER
>XOAUTH

>
>it is then not accepting the username and password. which used to be
>valid and are still valid when i log in to google directly.
>

 I still don't believe that direct Google log-in success means much --
other than to verify you do have a valid account.

 What character encoding is being used by the direct log-in vs that
being used by exim4? If your password has some special characters that have
different values in different encodings then the password could be seen as
different on the server end. Does the password only use characters in the
7-bit ASCII set? (That should be safe for ASCII, ISO-Latin-1, and UTF8
encodings).

 Unfortunately, I suspect having those items sent after the STARTTLS
command means WireShark won't capture legible packets, and sense each
session should have negotiated a different key-pair you can't rely upon
matching up packets between sessions.


--
 Wulfraed                 Dennis Lee Bieber         AF6VN
 wlfraed@ix.netcom.com    http://wlfraed.microdiversity.freeddns.org/

--- SoupGate-Win32 v1.05