Subject: Re: Outlook 2003 timeout problems - msg#00007

Previous Message by Date:

Re: CRLF encoding bugs in imapd and pop3d

This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet software does not support MIME signed messages. The Internet standard for MIME PGP messages, RFC 2015, was published in 1996. To open this message correctly you will need to install E-mail or Usenet software that supports modern Internet standards. Rolf Eike Beer writes: Hi, as I recently found out courier does not check for CRLF sequences at the end of lines. It just blindy inserts CR. In case there's already a CR there it will still insert, Correct. Text files on UNIX/Linux/Posix use LF as end-of-line sequence, so CR gets inserted when the message is transmitted via IMAP. causing invalid IMAP transactions. There is nothing invalid about it. Here is a patch that fixes at least the easy places to correctly send out the mails. Your patch breaks IMAP. You most certainly did not test it at all, or did not test it thoroughly. pgpTyzVHZeJkt.pgp Description: PGP signature

Next Message by Date:

Re: CRLF encoding bugs in imapd and pop3d

Sam Varshavchik wrote: >Rolf Eike Beer writes: >> Hi, >> >> as I recently found out courier does not check for CRLF sequences at the >> end of lines. It just blindy inserts CR. In case there's already a CR >> there it will still insert, > >Correct. Text files on UNIX/Linux/Posix use LF as end-of-line sequence, so >CR gets inserted when the message is transmitted via IMAP. But you can't be sure that there are not CR's in the message. I've seen many of them. Common pitfall is someone inserting mail into qmail using CRLF which will be delivered this way into the mailbox (e.g. by PHP skripts). >> causing invalid IMAP transactions. > >There is nothing invalid about it. Seems I've misread RfC 2060 section 2.2. >> Here is a patch that fixes at least the easy places to correctly send out >> the mails. > >Your patch breaks IMAP. You most certainly did not test it at all, or did >not test it thoroughly. And even the way it is there are some errors in it. Ok, drop that IMAP part. Nevertheless I've seen some clients (especially M$ Outlook) getting heavily confused if there are CRLF in the message store. Maybe it's better to get qmail-queue fixed instead (haha). Eike

Previous Message by Thread:

Re: Outlook 2003 timeout problems

On Wednesday 31 May 2006 14:38, Klaus Zahradnik wrote: > Hello List! > > I have a bit of a problem with Outlook 2003 users. I know that > particular software from Redmond is mostly borken. But I am wondering > wether there is a workaround. > > Thing is that some (not all) users have timeout problems when it comes > to eMails with large attachements. This concerns only IMAP users - POP > works just fine. > As of now I am not able to reproduce this problem. I played with Outlook > for a while and was able to retrieve eMails up to 10 MB just fine. > > Does somebody have a solution for me? M$ Outlook, when it comes to long connections, can open up to 6 simultaneuos connections for single account. Check your settings on authdeamons, deamons and max_per_ip in config files. H.

Next Message by Thread:

Able to authenticate w/ vpopmail but not courier imap

I have gone through the installation a few times.  I can auth using vchkpw and vpopmail fine. However when I login to IMAP the login always fails. The server seems to be working fine, it just says auth failed. I cannot find any other errors. I am using debian. Tried using both the apt-get and built from source. Authlib was built with./configure  --without-authpam --without-authpgsql  --without-authcustom --without-authpipe  --with-mailuser=vpopmail --with-mailgroup=vchkpw courier-imap simply./configure --with-sslIts authlib .58 and courier 4.1.1I have searched a lot and tried about everything I could find online at this point