similar to: 0.99.10.1 released

Available from http://dovecot.fi/rc/ While still waiting for .11 with index file rewrites to stabilize, here's a release candidate for 0.99.10.1 which is basically 0.99.10 patched with most of the simple bugfixes from CVS. Some bugfixes such as LIST's children-flags were done with larger rewrites so I didn't try to apply them. All the changes are listed in ChangeLog. The

Just ran into a problem[1]. It seems to have been introduced by changeset 224 [2], a fix for ticket 126 [3]. The root is the number of CRLFs Camping puts between the headers and the body of the response. This has changed at least 3 times; right now we''re back to 1. (ie. every header ends in a CRLF, and then there''s the body) The HTTP RFC[4], the CGI spec[5] and the FastCGI

One of the recent 1.0 commits relating to CRLF handling (maybe 2006-06-24) has changed the behaviour of APPEND when using mbox files with ordinary plain text emails. When a client stores a new message using an APPEND command (eg. saving a draft or copy of a sent message), it uses CRLF consistently as a line-ending throughout the literal data block over the wire - both for the header and the

Right, my understanding is that files that specifically need CRLF should say so via .gitattributes somewhere. autocrlf=false ought to work if your Windows editor doesn’t (or can be persuaded not to) introduce CRLFs. I’ve observed that the Visual Studio editor will detect the line-ending style of the file you’re editing, and imitate it. This works great until you create a new file. 😝 So I’ve

Hi, could somebody apply the below patch to contrib/cygwin/ssh-host-config? The patch solves a problem with the way, the Windows pendant of the /etc/services file is used. This file has (obviously) CRLF line endings. The ssh-host-config file tries to accomodate that when adding the ssh service entries but I never reviewed this functionality in the light of some major changes in the Cygwin DLL.

Again rc, just in case I broke something. Or maybe I should just start creating nightly CVS snapshots. Anyway, fixes the few bugs people have reported lately: - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a

Dovecot-2.2.1 does not appear to support URLs specified via non-synchronizing literals (RFC 2088 LITERAL+), and also does not read and discard the literal+ input after reporting the error. This results in the literal+ input being interpreted as IMAP commands, which could alter the user's mail store in unexpected ways and/or lead to the abrupt disconnection of the client for exceeding the

Hi. I've made a strange observation. When having Dovecot (at least) with maildir and moving (via IMAP) mail received by some client (Evolution 3.4) into it the following happens: Regardless of whether the mail was originally(!) set with CRLF or LF (i.e. when I use netcat to submit the plain SMTP to the relaying MTA). When the client (Evolution) had received the mail via POP3 before moving

Hi all, I've configured "quota_exceeded_message" in dovecot 1.2, but I have two questions: - Can I use "CRLF" in it? I'd like have two messages: english and spanish. - If char character set in dovecot.conf is ASCII, How do I set special characters (spanish)? The email received is in UTF-8 Thanks you -- Antonio Casado Rodr?guez Administrador de Servicios de Red y

I go back and forth between windows and linux, and find myself running into problem with line endings. Is there a way to control the line ending conversion when writing files, such as write and cat? More explicitly I want to be able to write files with LF line endings rather than CRLF line ending on windows; and CRLF line endings instead of LF on linux, and I want to be able to control when the

Several bugfixes since 0.99.6rc3. Here's again the change summary since 0.99.5: v0.99.6 2003-01-13 Timo Sirainen <tss at iki.fi> + THREAD=REFERENCES extension support. ORDEREDSUBJECT would be easy to add, but I think it's pretty useless. + SORT is much faster now. + mbox: If ~/mail directory isn't found, create it. + Log login usernames * Some coding style changes

Am 30.10.18 um 13:37 schrieb Stephan Bosch: > > > Op 28-10-2018 om 23:28 schreef Peter Nabbefeld: >> Hello, >> >> cannot fetch mails from an IMAP folder because of the error in the >> subject - fetching always stops with SIGABRT. >> >> Could anybody help me, please? > > We need more information than that: > > - Your configuration and

I've read about one month back this list's messages. I've still 216 messages from this year marked as "unread" which I should look into more (+258 older ones). Also I've 180 "unread" messages in my INBOX also which might contain something useful. So those messages could still contain something that should be added to this list. Anyway looking at my current

I do have full access to that directory. I have the bbHist package in c:/PROGRA~1/R/rw2011/library/bbHist directory. Then under the library directory I did check and build. Here's what I got: $ R CMD check bbHist * checking for working latex ... OK * using log directory 'c:/progra~1/r/rw2011/library/bbHist.Rcheck' * using R version 2.1.1, 2005-06-20 * checking for file

Since December 2014, clients using the Python poplib library (getmail in my case) started to limit the line length of RETR and other command responses sent from the server to 2048 bytes: See https://bugs.python.org/issue16041 (Included at least in Python-2.7.9) Dovecot doesn't have line split in the POP3 module, so Python fails to retrieve messages with long lines. RFC 1939 says: "

Well, "release candidate" wasn't really right name for last two versions. Maybe not for this one either, it has a few changes that could potentially break things badly (new hash table code especially). Anyway, seems to work with me. If I don't see any problems with it for a few days it'll be the final. The really great news is that we support threading. A lot of people have

lvqcl wrote: > lvqcl wrote: > > > The patch does the following: > > Does the patch work for linux git? Windows git cannot apply a patch > that was created itself. It looks like that patch was created with the 'git diff' command and hence cannot be applied using the 'git am' command. It does however apply using the patch command. > (It writes LF in

Hi, I've changed a program that fetches mail via IMAP from an Exchange Server to use our Dovecot machine. But now I'm experiencing strange problems with seem to be caused by a wrong BODYSTRUCTURE answer that causes wrong charset handling. When fetchting the BODYSTRUCTURE I see this: Dovecot: 88 UID fetch 32 (BODYSTRUCTURE) * 1 FETCH (UID 32 BODYSTRUCTURE ("text"

Hello everyone, I'm using the very good imaptest [0] tool to test my little imap server implementation. I've tried to use the dovecot-crlf [1] file, but it looks like there are some major issues : $ grep -n "In-Reply-To.*;" tests/data/dovecot-crlf 479:In-Reply-To: <20020806175441.GA7148 at linux.taugt.net>; from rueckert at informatik.uni-rostock.de on Tue, Aug 06, 2002

Hi, we are migrating from Cyrus 2.3.7 to Dovecot 2.2.13. We have ~7000 maildirs with ~500GB. Our goal is to do the migration without users have notice and with the shortest service downtime. The users use IMAP (with shared folders and ACL), POP3 and sieve filters. As a first choice, we tried the Dovecot's dsync tool. First tests were great, but we are not able to change the Cyrus auth