-
ok here is some nice info.. hopefully its not too huge :)
scroll down to about 1/3 of the site. Starting from Section 6 it explains the list of commands and the responses to expect.
http://www.packetizer.com/rfc/rfc3501/
also there is this one of the extensions that have been made to IMAP. Though you will see that most of them are prefixed with OK|NO|BAD etc, which is good...
2009-12-17 01:02:49 UTC in Koolwired.Imap
-
yeah , i guess that would work fine. though either way you would need to compile a list of possible responses from the IMAP server to make sure there is nothing missing. I'll see if i can find a list somewhere that you can use.
2009-12-17 00:40:43 UTC in Koolwired.Imap
-
sorry, all those br tags were for formatting, but i guess the Preview doesn't correctly reflect how it will look :P. removed and reAdded code below
bool IsResponseEnd(string response) { return (Regex.IsMatch(response, OKCOMPLETE) || Regex.IsMatch(response, FETCHNOTOK) || Regex.IsMatch(response, OKSUCCESS) || Regex.IsMatch(response, OK_CREATE)); }.
2009-12-08 07:57:09 UTC in Koolwired.Imap
-
Cheers for adding that in.
I'll see if I can explain what i meant with OK CREATE and I'll add the code below to fix the problem.
firstly, you need to declare the new RegEx string in ImapCommand.cs (probably at the top with the other ones)
const string OK_CREATE = @"kw\d+\WOK [Cc][Rr][Ee][Aa][Tt][Ee]";
then you need to update the IsResponseEnd() function like...
2009-12-08 07:50:24 UTC in Koolwired.Imap
-
I've noticed that both the ImapCommand.Create() and ImapCommand.Delete functions are creating the command line without the "\r\n" suffix. This would cause the command to not be executed.
also, ImapCommand.IsRespondEnd() does not cater for all possible positive response from the imap server. eg. should include Regex.IsMatch(response, OK _CREATE) as well. (i haven't tested completely...
2009-10-28 06:14:34 UTC in Koolwired.Imap
