similar to: index

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

I'm encountering lots of Oct 31 11:14:25 postamt dovecot: pipe() failed: Too many open files errors around midday ever since the latest upgrade to 1.0.7. The errors appear in pairs like this one: Oct 31 11:20:01 postamt dovecot: pipe() failed: Too many open files Oct 31 11:20:01 postamt dovecot: imap-login: Internal login failure: user=<username>, method=PLAIN, rip=193.175.174.239,

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft

http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.6.tar.gz.sig * IDLE: Interval between mailbox change notifies is now 1 second, because some clients keep a long-running IDLE connection and use other connections to actually read the mails. * SORT: If Date: header is missing or broken, fallback to using INTERNALDATE (as the SORT draft

Found this today multiple times for the same user: Aug 16 16:59:38 postamt dovecot: IMAP(username): file strfuncs.c: line 165 (p_strndup): assertion failed: (max_chars != (size_t)-1) Aug 16 16:59:38 postamt dovecot: IMAP(username): Raw backtrace: imap [0x80c6d53] -> imap(i_fatal+0) [0x80c6795] -> imap(p_strndup+0x38) [0x80d8316] -> imap(t_strndup+0x22) [0x80d86d7] ->

I get: Making all in auth make[3]: Entering directory /usr/src/dovecot/src/auth' rm -f libpassword.a ar cru libpassword.a mycrypt.o password-scheme.o password-scheme-md5crypt.o password-scheme-otp.o password-scheme-rpa.o ranlib libpassword.a gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql -I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp

All over a sudden the getquota plugin in SquirrelMail doesn't work anymore. I activated debugging an got: IMAP command sent: a001 GETQUOTAROOT "INBOX" IMAP response received: Array ( [0] => * QUOTAROOT "INBOX" "" [1] => * QUOTA "" () ) A manual test results in: . GETQUOTAROOT "INBOX" * QUOTAROOT "INBOX"

One of our users seems to have strange problems with his mailbox: Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096, but next_uid = 1097 Oct 2 00:36:42 postamt dovecot: IMAP(rbxxxx): Corrupted transaction log file /home/r/b/rbxxxx/Maildir/.listen.CCL/dovecot.index.log: Append with UID 1096,

I'm getting these in my log: Jul 17 11:40:42 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:40:42 postamt dovecot: child 26581 (login) killed with signal 6 Jul 17 11:51:12 postamt dovecot: imap-login: file ssl-proxy-openssl.c: line 460 (ssl_proxy_new): assertion failed: (fd != -1) Jul 17 11:51:12 postamt dovecot: child

Core was generated by /usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. #0 0xb7fb6410 in __kernel_vsyscall () (gdb) bt #0 0xb7fb6410 in __kernel_vsyscall () #1 0xb7e85f15 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e87891 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080ce499 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e8f54

One of our squid proxies crashed today. I was able to make a screenshot of it's last utterings - and since ext3 is being mentioned there, I thought I'd mention it here: http://www.arschkrebs.de/images/proxy-cbf-2-crash.png # uname -a Linux proxy-cbf-2 2.6.21 #1 SMP Thu Apr 26 11:17:54 CEST 2007 i686 GNU/Linux # mount /dev/cciss/c0d0p5 on / type auto (rw,errors=remount-ro) tmpfs on

from dovecot -n: plugin: fts: squat quota: maildir quota_rule: Trash:storage=100M quota_warning: storage=10%% /usr/local/scripts/quota-warning 90 quota_warning2: storage=5%% /usr/local/scripts/quota-warning 95 quota_warning3: storage=1%% /usr/local/scripts/quota-warning 99 trash: /usr/local/etc/dovecot-trash.conf The quota warning that used to work in 1.0.10 (with the

I'm getting "Maximum number of mail processes exceeded" messages when 512 imap Processes are active. Dovecot reports: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1712). Either grow the limit or change login_max_processes_count and max_mail_processes settings But in my /var/service/dovecot/run script I use: #!/bin/sh mkdir /var/core chmod

On 1 Oct 2019, at 16.45, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > * Ralf Hildebrandt via dovecot <dovecot at dovecot.org>: > >> But why is that? Why would the index file be updated so often? > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July. Fixed by

Some of our users use to login as firstname.lastname or firstname.lastname at charite.de instead of using the "correct" "flastname" login name. In order to get this behaviour a long-gone co-worker wrote an authdaemon.pl, which speaks the courier-authdaemon protocol. How can I emulate this behaviour with dovecot? Basically, all I need is a usernamen mapping ala:

The day I switch our user to dovecot and it goes into production, there will be a few thousand people all generating their indices for the first time (we have a legacy requirement for procmail, at least for now), so I wondered: 1) Is there is anyway to pre-emptively force indexing? 2) Is there any value in doing so? That is, will I gain much in terms of making the first time everyone connects

I tried to disable courier-pop3 today in favour of dovecot pop3. Prior to that I ran: find /home -maxdepth 1 -type d | xargs --replace /usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive --convert {} ( /home is hashed two levels deep: /home/a/a/aanton/Maildir/ ) After that, I got lots of errors like: Aug 9 13:02:40 postamt dovecot: IMAP(azenclu): Maildir

Hi! I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error: Mar 20 13:25:58 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) I checked, and alas, I had ssl_client_ca_dir = ssl_client_ca_file = So I set:

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem