similar to: Mailbox corruption (dovecot 2.2.13, Debian 8)

Hello. I wrote about this three weeks ago but got no answer. I'm going to officially "forward" the Debian bug this time, with all the details. The test case is just 840 bytes long. Please give it a try. ---------- Forwarded message ---------- From: Santiago Vila <sanvila at unex.es> To: submit at bugs.debian.org Date: Fri, 23 Jan 2015 22:32:28 +0100 (CET) Subject:

On Sun, 15 Feb 2015, Timo Sirainen wrote: > On 14 Feb 2015, at 16:23, Santiago Vila <sanvila at unex.es> wrote: > > > I wrote about this three weeks ago but got no answer. I'm going to > > officially "forward" the Debian bug this time, with all the details. > > > > The test case is just 840 bytes long. Please give it a try. [ Small correction:

On 14 Feb 2015, at 16:23, Santiago Vila <sanvila at unex.es> wrote: > I wrote about this three weeks ago but got no answer. I'm going to > officially "forward" the Debian bug this time, with all the details. > > The test case is just 840 bytes long. Please give it a try. .. > Package: dovecot-imapd > Version: 1:2.2.13-11 > Severity: serious I can't

On 2/19/2015 4:34 PM, Santiago Vila <sanvila at unex.es> wrote: > In such case we would love to know what is the commit that fixed this, > so that we can apply it to the 2.2.13 version in Debian. We have > frozen the distribution as we are about to release jessie as Debian 8, > so no new upstream releases are allowed anymore. I have NEVER understood the rationale for doing this

Am 04.05.2015 um 21:04 schrieb Santiago Vila: > Greetings. > > Thanks to Jelmer Vernooij, who has just uploaded version 2.2.16 for > Debian unstable, I can confirm that this bug may still be reproduced > in version 2.2.16, so it has *not* been fixed yet. > > Several months ago I was told "I can't reproduce it in dovecot hg", or > something like that. Well,

Am 04.05.2015 um 22:13 schrieb Santiago Vila: > On Mon, May 04, 2015 at 09:23:57PM +0200, Robert Schetterer wrote: >> Boh fetchmail .... did you verified with getmail ? > > No, I didn't. The client should be irrelevant. Nobody should be able > to corrupt a remote mailbox only by issuing imap commands. > > BTW: Does getmail have an option doing the same as fetchmail

Am 05.05.2015 um 16:26 schrieb Santiago Vila: > I have just verified with IMAP commands. This is the procedure: > > telnet localhost 143 > > and then type this: > > A0001 CAPABILITY > A0002 LOGIN "bluser" "bluser" > A0003 SELECT "inbox-b" > A0004 EXPUNGE > A0005 FETCH 1:12 RFC822.SIZE > A0006 FETCH 1 RFC822.HEADER > A0007

On 05/06/2015 09:57 AM, Teemu Huovila wrote: > On 05/05/2015 05:26 PM, Santiago Vila wrote: >> I have just verified with IMAP commands. This is the procedure: >> >> telnet localhost 143 >> >> and then type this: >> >> A0001 CAPABILITY >> A0002 LOGIN "bluser" "bluser" >> A0003 SELECT "inbox-b" >> A0004

On 05/05/2015 05:26 PM, Santiago Vila wrote: > I have just verified with IMAP commands. This is the procedure: > > telnet localhost 143 > > and then type this: > > A0001 CAPABILITY > A0002 LOGIN "bluser" "bluser" > A0003 SELECT "inbox-b" > A0004 EXPUNGE > A0005 FETCH 1:12 RFC822.SIZE > A0006 FETCH 1 RFC822.HEADER > A0007 FETCH

Am 07.05.2015 um 01:45 schrieb Santiago Vila: > On Thu, May 07, 2015 at 12:02:12AM +0300, Timo Sirainen wrote: >> Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/94bd895721d8 > > Unfortunately, I applied single changeset 94bd895721d8 over Debian > version 2.2.16-1 to create an updated Debian package and I can still > reproduce the problem when using the updated package.

On 13 May 2015, at 01:15, Santiago Vila <sanvila at unex.es> wrote: > > On Wed, May 13, 2015 at 12:25:44AM +0300, Timo Sirainen wrote: >> - mbox: Fixed crash/corruption in some situations when the first mail >> was expunged. > > Once again: This is *not* fixed! One bug was fixed, but looks like there was another one. I tried after the fix that your test case

On Mon, May 04, 2015 at 09:23:57PM +0200, Robert Schetterer wrote: > Boh fetchmail .... did you verified with getmail ? No, I didn't. The client should be irrelevant. Nobody should be able to corrupt a remote mailbox only by issuing imap commands. BTW: Does getmail have an option doing the same as fetchmail --folder option at all? > dig you tried fetchmail with > > bad-header

Package: logcheck Version: 1.2.20a Severity: serious Tags: patch On a system where sh points to dash and LANG=es_ES, I get this: # apt-get -y --reinstall install logcheck Leyendo lista de paquetes... 0% Leyendo lista de paquetes... 0% Leyendo lista de paquetes... 23% Leyendo lista de paquetes... Hecho Creando ?rbol de dependencias... 0% Creando ?rbol de dependencias... 0% Creando ?rbol de

Am 05.05.2015 um 19:22 schrieb Santiago Vila: > On Tue, May 05, 2015 at 05:15:16PM +0200, Robert Schetterer wrote: >> is this related to mbox only ? > > I don't know. The bug happens as I explained, and current documentation > says mbox is still supported (I really hope documentation is correct here). yeah but it may be a mbox only bug > >> i have no mbox install

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz.sig Changes since rc1: - Compiling fix for fs-compress in Solaris and maybe others. - Implemented Cassandra CQL support as lib-sql backend. This is mainly usable as dict-sql backend. - lib-fts fixes and improvements - Some other small random changes If no new issues are

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc2.tar.gz.sig Changes since rc1: - Compiling fix for fs-compress in Solaris and maybe others. - Implemented Cassandra CQL support as lib-sql backend. This is mainly usable as dict-sql backend. - lib-fts fixes and improvements - Some other small random changes If no new issues are

Thanks, fixed: http://hg.dovecot.org/dovecot-2.2/rev/94bd895721d8

I have just verified with IMAP commands. This is the procedure: telnet localhost 143 and then type this: A0001 CAPABILITY A0002 LOGIN "bluser" "bluser" A0003 SELECT "inbox-b" A0004 EXPUNGE A0005 FETCH 1:12 RFC822.SIZE A0006 FETCH 1 RFC822.HEADER A0007 FETCH 1 BODY.PEEK[TEXT] A0008 STORE 1 +FLAGS (\Seen \Deleted) A0009 EXPUNGE A0010 FETCH 1 RFC822.HEADER A0011 FETCH

Fetchmail connects to your provider's e-mail server as if it were an MUA, then feeds mail to your server's MTA as if it were a peer MTA. If your provider doesn't allow client connections (by IMAP or POP), then you're right that fetchmail won't help. It sounds as though you need to set up some kind of failover for your MTA: a second SMTP server, probably configured to feed

I read about fetchmail.I understand that it doesn't work if the mail server uses an MTA. Il mercoled? 3 giugno 2020, 15:07:51 CEST, Nicholas Taylor <net20 at cam.ac.uk> ha scritto: This is pretty much exactly what I do.? I use fetchmail [1] to download mail from my ISP and feed it to exim, which delivers everything to dovecot.? I don't know whether it's possible to