similar to: [patch] make <chroot>/./<home> a config option.

I'm trying to use the rsync algorithm for incremental backups. After a quick look at rsync I saw the batch mode operations, and I thought that maybe I can modify them for incremental backups. What is needed is to add an option to save the checksums of all the files of the level 0 backup and a second option to use the level n checksum to calculate the delta batch files for the level n+1

Hi At line 1118 of src//lib-index/mail-index-map.c, inside the function mail_index_map_move_to_memory, there is: mail_index_map_copy_header(map, map); Valgrind is stating that "Source and destination overlap in memcpy". I'm wondering if this code is just coping the same memory over itself, or if it is doing something useful. Regards, Diego Liziero. --- 1104 void

Hi, I'm collecting users feedback of latest dovecot 1.1.rc3 development release. Some users are complaining that their sent mails sometimes don't get written to imap Sent-mail folder. It seems that all these users were using multiple istances of imap processes to read their mail (thunderbird+horde-imp, evolution+horde-imp or multiple thunderbird istances). No error message is written in

mbox messages gets header corruption caused by an extra linefeed after Content-Length Users sees their mails in Sent mbox folder without the from and to fields, without attachments and with the date of 1/1/1970 Diego. --- Here is an anonymized header: >From xxxxxxxx at xxxxxx.xxxxxx.xxxxx.xx.xx Tue Jun 03 09:14:33 2008 Message-ID: <xxxxxxxx.xxxxxxx at xxxxxx.xxxxx.xx.xx> X-UID: 3913

And got this regression with dovecot-1.1.rc7 with each pop3 connection, hg version of 2 days ago was working fine. Now I'm back again to hg before "Message sort index handling rewrite". Regards, Diego. --- Panic: POP3(username): file index-mail.c: line 1007: unreached (gdb) bt #0 0x00b91402 in __kernel_vsyscall () #1 0x00725ba0 in raise () from /lib/libc.so.6 #2 0x007274b1 in

I was wondering if it could be useful to use such tools to keep track of users bugs. I find somehow harder to search the mailing list if a bug is known, if it's being worked on, if it needs more feedback, in witch release it has been eventually solved, and so on. Any thoughts? Regards, Diego.

I am setting up dovecot for imap on a new Fedora 3 box. Through SquirrelMail I can access my email - no problem. However my other users are getting this error message: ERROR : Connection dropped by imap-server. Query: CAPABILITY Looking in the maillog file for further error details gives me this: dovecot: chroot directory no included in valid_chroot_dirs: /home/user Looking through the

I'm still collecting user feedback after moving from uw-imap to dovecot development release 1.1.rc3. What said in the subject seems the obvious result of an improper configuration. Office emails are configured and accessed on multiple clients with the same automatic filters, and sometimes the filtered emails get duplicated on the destination folder. The fact is that this was perfectly

Sorry, this time I've no core file, (I forgot to set ulimit -c unlimited before starting dovecot) Regards, Diego. --- dovecot: Dec 09 08:26:52 Panic: IMAP(user): file mbox-sync-rewrite.c: line 590 (mbox_sync_rewrite): assertion failed: (mails[idx].from_offset == start_offset) dovecot: Dec 09 08:26:52 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f739e] ->

I'm talking about mbox Sent folder, where some mailers append through imap server a copy of each message they send. Sometimes, just three header lines got appended instead of the whole mail message, such as: >From xxxxxxxx at xxxxxx.xxxxxx.xxxxx.xx.xx Fri May 23 12:30:14 2008 X-UID: 2852 Status: RO This happened in the past (dovecot-1.1-beta/rc with Evolution and with Thunderbird), and

I've tried to stress test dovecot 1.1.4 with imaptest for days without any assertion failure or crash. Just some "got too little data" messages. So far it's the most stable 1.1.x version. Today a user got this imap segfault with vanilla 1.1.4 (I don't know if it's something you have already fixed in current tree). The user didn't complain of anything, I've just

We are pleased to release v2.3.13. Please find it from locations below: https://dovecot.org/releases/2.3/dovecot-2.3.13.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.13.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * CVE-2020-24386: Specially crafted command can cause IMAP hibernate to

We are pleased to release v2.3.13. Please find it from locations below: https://dovecot.org/releases/2.3/dovecot-2.3.13.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.13.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * CVE-2020-24386: Specially crafted command can cause IMAP hibernate to

It was recently brought to my attention that a writable rsync daemon that has "use chroot" enabled could potentially be tricked into loading a user-supplied library file if the library can be uploaded into a spot where a normal rsync action (such as an attempt to lookup a username from an ID) would cause the loader to load it in. If you haven't already taken steps to exclude library

It was recently brought to my attention that a writable rsync daemon that has "use chroot" enabled could potentially be tricked into loading a user-supplied library file if the library can be uploaded into a spot where a normal rsync action (such as an attempt to lookup a username from an ID) would cause the loader to load it in. If you haven't already taken steps to exclude library

Plagued with an error I can't get past: ==> dovecot_info.log <== dovecot: Mar 04 22:09:06 Info: Dovecot starting up ==> dovecot.log <== dovecot-auth: Mar 04 22:09:07 Fatal: Can't open configuration file /usr/local/etc/dovecot-pgsql.conf: No such file or directory dovecot: Mar 04 22:09:07 Error: child 18211 (auth) returned error 89 dovecot: Mar 04 22:09:07 Error: Auth process

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz.sig I didn't have time/energy to fix everything I wanted, so it'll probably be a few more RCs left until v1.1.0. This is anyway an important release, because it fixes two buffer overflows in search code which have been in all v1.1 releases (but not v1.0). Really stupid

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz.sig I didn't have time/energy to fix everything I wanted, so it'll probably be a few more RCs left until v1.1.0. This is anyway an important release, because it fixes two buffer overflows in search code which have been in all v1.1 releases (but not v1.0). Really stupid

On Wed, Oct 8, 2008 at 7:36 PM, mouss <mouss at netoyen.net> wrote: > > an alternative is > > content_filter = > smtpd_sender_restrictions = > check_sender_access hash:/etc/postfix/sender_ok > check_sender_access pcre:/etc/postfix/filter > > == dsn_ok > <> OK > > == filter > /./ FILTER filter:[1.2.3.4]:10024 > > where

I got it with multiple imaptest instances even with current dovecot-1.1 hg tree. I checked the emails with that UIDs and they are actually truncated. Some things I noted on these mails: - they are all with MIME multipart attachments. - the last multipart attachment is truncated - the truncated last line is not complete - the following line is the beginning of a new mail (From line) without any