[imapfilter-devel] patch for Solstice2.0p12 IMAP4 server
Lefteris Chatzibarbas
lefcha at hellug.gr
Wed Jan 28 22:26:27 EET 2004
On Tue, Jan 27, 2004 at 02:42:12PM +0100, Johannes P?hlmann wrote:
> To contact a Sun Imap Server
> (Banner "* OK XXXXXXXX Solstice (tm) Internet Mail Server (tm) 2.0p12 IMAP4 service ")
> I had to patch response.c at line 123:
>
> - if (!strcasestr(ibuf.data, "IMAP4rev1")) {
> + if (!strcasestr(ibuf.data, "IMAP4")) {
> + puts(ibuf.data); /* Show capabilities the Server offers */
>
> I do not know if there may be Problems with incompatible IMAP4 Versions
> and who os breaking which standard here.
Nobody is breaking any standards... It is just that this server
implements the (obsolete) RFC1730 IMAP4 protocol, while imapfilter works
with RFC3501/RFC2060 IMAP4rev1 protocol servers.
> In fact, imapfilter works with this patch and
> SUN's Solstice (tm) Internet Mail Server (tm) 2.0p12 IMAP4 server.
I don't believe that if this server reports IMAP4 will work with
imapfilter. For example imapfilter uses the IMAP4rev1 STATUS command
(which IMAP4 lacks).
> I think, the keyword "IMAP4rev1" should be made configurable
> as part of the account settings.
No, this isn't a good idea. Imapfilter works with IMAP4rev1 compliant
servers. I don't see what one is aiming to accomplish by sending
IMAP4rev1 commands, to something other than an IMAP4rev1 server.
It would be a good thing to try and make imapfilter work with IMAP4
(besides IMAP4rev1) servers, since there aren't so many differences
between the two protocols, and I plan to look into it some time.
More information about the Imapfilter-devel
mailing list