search for: kirchwitz

...es on "under_score" (no space but underscore). Looks like something goes wrong with the encoding/decoding of quoted-printable (sorry, haven't tried with base64). Example: Dovecot does not find "under_score" | Date: Fri, 24 Jul 2009 02:08:45 +0200 | From: "Andreas M. Kirchwitz" <amk at krell.zikzak.de> | To: "Andreas M. Kirchwitz" <amk at krell.zikzak.de> | MIME-Version: 1.0 | Content-Type: text/plain; charset=iso-8859-1 | Content-Disposition: inline | Content-Transfer-Encoding: quoted-printable | | test for under_score and dovecot sear...

Dear Dovecot developers! This problem already existed some years ago, has been fixed, and now it's there again in Dovecot 2.2.25 (2.2.24 was fine). I'm running CentOS 6 with a custom OpenSSL installation in /usr/local/ssl Therefore, Dovecot is configured like this: env SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -lcrypto

Dear Dovecot lovers! When starting Dovecot 1.x the first time, it runs "ssl-build-params" to generate a file named "ssl-parameters.dat". This takes a couple of minutes. During this time users have no access to their mail, but this can be planned in advance and users can be notified. This is explained in http://wiki.dovecot.org/SSL/DovecotConfiguration With Dovecot 2.0.rc4,

Hi folks, I've compiled the new OpenSSH 4.0p1 on my Linux box running Fedora Core 2 (kernel 2.6.10) the same way as I did with 3.9p1 and all previous versions. Key-based login works fine, but if I login from a host that require me to enter my login password (keyboard-interactive), then the sshd child process segfaults. Don't know if this is specific to my system or to Linux in general.

Hi folks, when building Dovecot 2.0.rc3 (never used any other 2.0.X before, so this issue might not be new to that specific release), then compilation fails on anything that is linked against the new "libdovecot-login.so" library. For example, "imap-login" fails: /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes

Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> ldd /usr/local/Dovecot-2.2.25/lib/dovecot/libssl_iostream_openssl.so >> linux-gate.so.1 => (0x00e8c000) >> libcrypto.so.1.0.0 => not found >> libssl.so.1.0.0 => not found >> librt.so.1 => /lib/librt.so.1 (0x00be4000) >> libc.so.6 => /lib/libc.so.6

...8d81] -> /lib/tls/libc.so.6(__libc_start_main+0xda) [0x12679a] -> imap(__fxstat64+0x6d) [0x8059ed1] Did I miss something in the upgrade process, or is this a bug that has yet to be fixed? This seems to be happening to many various users for various reasons. But I can verify for Andreas M. Kirchwitz who noted the other day that one of the easiest way to produce it seems to be "saving" or "moving" between folders in (Al)Pine... If Timo wants, I can send the dovecot.(index|index.cache|index.log) files for when this happens, but I would need to know what to send (both the fol...

Hi Timo and all others! The current Dovecot 2.0.rc4 did really well with Mutt 1.5.20 and Thunderbird 3.1.2, but a user with Alpine 2.00 crashed it immediately. I'm running Fedora 13 (Linux) and compiled Dovecot 2.0.rc4 manually like I did before with Dovecot 1.2.13. When switching from 1.2 to 2.0 I removed all those ".imap" folders with internal cache data (didn't know for sure

Hello Dovecot users! There seems to be a new dependency in some modules (eg, lib-storage, libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those modules didn't require OpenSSL, but 2.1 does. For the linking process the path to the OpenSSL library isn't specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL is in a non-standard path. (Haven't checked if SSL_CFLAGS

Hi folks, with Dovecot 1.1.1, I've had two "crashes" (SIGABRT) recently. Dovecot 1.1.1 has been compiled from source and is running on Fedora 8 Linux 32 Bit (all patches) with custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.1: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key

Merry Christmas! The brandnew Dovecot 2.3.0 seems to generate index (cache) files for all IMAP folders at once when a user logs in the first time. (Those "dovecot.index" files that live in ".imap" directories.) Previous versions generated these index files on demand when a folder was actually accessed (so if a folder was never used, no resources were wasted to ever generate

Hi folks, because I accidently missed a syslog entry from previous reports, here's a new one with both syslog lines. Same problem as always when saving mail from one folder to another with Pine 4.64. Does nobody else get this when copying/moving mail between folders? The assertion refers to src/lib-storage/index/index-sync.c, line 39 (function index_mailbox_set_recent_uid). Aug 19 23:01:15

Dear OpenSSH gurus! ;-) I recently upgraded from "OpenSSH 2.1.1p4" to "OpenSSH 2.3.0p1" on my Linux 2.2.17 box with OpenSSL 0.9.5a (RedHat 7.0). According to the "ChangeLog", there was a change in SIGPIPE handling: | 20000930 | [...] | - (djm) Ignore SIGPIPEs from serverloop to child. Fixes crashes with | very short lived X connections. Bug report from

Hello Darren! Hello OpenSSH (portable) users! After updating from OpenSSH 3.8.1p1 to OpenSSH 3.9p1 on my Fedora Core 2 Linux box, the "sshd" no longer respects "~/.hushlogin" to get a quiet and silent login. Now I get the noisy "Last login: somedate from somehost" line. I really loved that feature. ;-) The problem is related to a change in "session.c",

Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as "deleted". This is the panic: Jul 25

Hi folks, after about 3 weeks without any problems, I've found this crash in yesterday's logfile (again related to index_mailbox_set_recent_seq): Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd]