Recently it seems that Google have modified the way that their server responds to the LOGIN command, they now return a list of capabilities after LOGIN before returning the OK authenticated message.
We had code that had been working fine using your library but within the last week or so it just started breaking, without any changes from ourselves.
I've had a look through your source and found a fix to get around this problem.
In the ImapAuthenticate.cs file, at line 195 just after
result = Connection.Read();
Add the following
if (result.StartsWith("* CAPABILITY")) // Gmail seems to send capabilities after login
{
result = Connection.Read();
}
The second read gets the OK authenticated message from gmail.
Hope that helps.
Great work with the library by the way, really useful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Recently it seems that Google have modified the way that their server responds to the LOGIN command, they now return a list of capabilities after LOGIN before returning the OK authenticated message.
We had code that had been working fine using your library but within the last week or so it just started breaking, without any changes from ourselves.
I've had a look through your source and found a fix to get around this problem.
In the ImapAuthenticate.cs file, at line 195 just after
result = Connection.Read();
Add the following
if (result.StartsWith("* CAPABILITY")) // Gmail seems to send capabilities after login
{
result = Connection.Read();
}
The second read gets the OK authenticated message from gmail.
Hope that helps.
Great work with the library by the way, really useful.
Thanks for posting the fix.
I was just about to look at it myself and then decided to check the forum first. Always nice when that happens :o)
Vin
Good catch i swear Google didn't do this before but I have this in the update I am working on. ;P
IMAP is such a jacked up protocol cause everyone does it different it seems.