fwiw, if they just remove "LITERAL+" from the capabilities line, it
might just work. although in the same place imap allows you to send a
normal literal anyway, so if they dotn support either some other
operations could fail.
On Tue, 2002-08-20 at 23:38, Not Zed wrote:
> On Wed, 2002-08-21 at 12:11, Richard Zach wrote:
> > >
> > >
> > >get them to fix their proxy, its not the first uni to fuck up like this.
> > >
> > >
> > Well, I'll try. But it would be easier if I understood what's going on
> > and what would have to be fixed (roughly). A workaround would be nice,
> > too, since they'll probably just tell me "Sorry, we only support
> > Netscape and Outlook."
>
> it was reported in the other mail. your proxy is saying it supports
> LITERAL+, but it doesn't.
>
> > >are you using 1.1? i thought htat had patches to get aroudn broken
> > >proxies like this, but maybe it doesnt handle this case.
> > >
> > Yes, using 1.1 snapshots.
> >
> > >theres
> > >absolutely no reason "" should be sent as a literal anyway.
> > >
> > Can you briefly explain to me what's going on? Doesn't the LIST
> > command require the reference name (ie, "") AND the mailbox name (eg, *)
> > as arguments? That's what RFC 2060 seems to me to be saying. Why is Evo
> > only sending only the ""? And is there a reason to use LITERAL+ in this
> > case? I mean, why not just send LIST "" * ?
>
> if you see the log it is sending two arguments. the proxy doesn't
> udnerstand literal+ so the login line is being taken as the 1 line with
> no extra argument and failing there.
>
> the first arugm3ent is:
> '{0+}
> '
>
> which is in literal+ format, saying 'take the next 0 bytes as the
> argument'.
>
> the second is
> '""'
>
> which shows up a little later in the log.
>
> they will have problems with certain passwords (e.g. a password that
> contains control characters) if they dont fix their literal handling
> (the other uni just made everyone not use those kinds of passwords).
>
> > >
> > >On Wed, 2002-08-21 at 05:52, Richard Zach wrtote:
> > >
> > >
> > >>Hey,
> > >>
> > >>My school has changed the IMAP config, and now I can't login to get my
> > >>mail. The log's below. Looks like Evo is inserting a CRLF in the LIST
> > >>command where it shouldn't.
> > >>
> > >>-RZ
> > >>
> > >>received: * OK IMAP4 Ready iproxy1.acs.ucalgary.ca
> > >>sending : A00000 CAPABILITY
> > >>received: * CAPABILITY IMAP4 IMAP4REV1 LITERAL+
> > >>received: A00000 OK CAPABILITY
> > >>sending : A00001 LOGIN xxx xxx
> > >>received: A00001 OK You are so in
> > >>sending : A00002 LIST {0+}
> > >> ""
> > >>received: A00002 BAD Missing required argument to LIST
> > >>
> > >>camel-imap-provider-WARNING **: Unexpected response from IMAP server:
> > >>A00002 BAD Missing required argument to LIST
> > >>sending : A00003 LOGOUT
> > >>received: "" BAD Missing command
> > >>
> > >>camel-imap-provider-WARNING **: Unexpected response from IMAP server: ""
> > >>BAD Missing command
> > >>
> > >>
> > >>_______________________________________________
> > >>evolution maillist - [EMAIL PROTECTED]
> > >>http://lists.ximian.com/mailman/listinfo/evolution
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> >
>
>
> _______________________________________________
> evolution maillist - [EMAIL PROTECTED]
> http://lists.ximian.com/mailman/listinfo/evolution
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution
