similar to: critical performance problem

Dovecot dies with signal 11 (segfault) when doing some commands with a specific message you'll find relevant information stored here: http://www.luria.ch/9e93676668e453b739ee3e085434e086/ the email: msg.anon.txt input rawlog: 20081001-120137-24371.in dovecot -n: dovecot-n.txt the gdb backtrace: bt.txt test system is running debian sarge, but same thing happens with debian etch (both x86)

Dovecot dies with signal 11 (segfault) when doing some commands with a specific message here attached: the email: msg.anon.txt input rawlog: 20081001-120137-24371.in dovecot -n: dovecot-n.txt test system is running debian sarge, but same thing happens with debian etch (both x86) using xfs always reproductible Can you help me with this ? -- Rene Luria -------------- next part

I'm trying to set up dovecot's deliver program as the lda for sendmail. I seem to need a config file for it '/etc/dovecot-deliver.conf'. Is there any documentation for this configuration file and it's contents? sendmail will call it under the recipient's uid, and all it has to do is drop the message into the proper maildir as defined in /etc/dovecot.conf and update

Hi guys, How can I modify the timeout value for the pop3_lock_session ? I'd like it to be much bigger.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just pulled and built version 1.0.rc22 root at ux-2s11-9:/mnt/mailcache/dvtest/MailDir# dovecot -n # /usr/local/etc/dovecot.conf log_path: /var/tmp/dovecot.log info_log_path: /var/tmp/dovecot.info ssl_disable: yes disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/var/run/dovecot/login login_executable:

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them

I am using dovecot-lda from cvs (checked out on september the 21st) and dovecot 1.0alpha2 (not yet upgraded ok). I have a strange feeling about "redirect" feature. Let's see two sieve scripts examples: # ex1 require ["fileinto", "vacation"]; if header :is ["blabla"] "blabla" { fileinto "blabla"; } redirect

Hi all, I recently installed Dovecot rc22 from the FreeBSD ports and I have some problem with the dovecot startup: - If I start dovecot manually, it works fine, it starts and I get messages in /var/log/maillog - If I reboot the machine, that's where the problem appears, dovecot doesn't seem to start and I get nothing, no errors in /var/log/maillog Any idea if this is a known

Hi, I experience problems everytime i forward a mail (basically, when forwarding an email containing an attachement). I'm using thunderbird (it does the same with outlook clients) with the forward parameter "as attachement" instead of "inline". (Using the inline parameters works fine). When i forward a mail with attachements (eg a jpeg file), the attachements file is

Feb 27 14:17:46 wurfel dovecot: imap-login: Login: user=<USER>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 27 14:17:46 wurfel dovecot: IMAP(USER): file mbox-sync-update.c: line 387 (mbox_sync_update_header): assertion failed: (ctx->mail.uid != 0 || ctx->pseudo) This is happening for dozens of users. Anyone have a suggestion of what to adjust? It was happening somewhat

Hello, I tried to upgrade dovecot from 1.0.rc7 to rc22 but I got this error at the end of the upgrade process: Dovecot has reserved the groupname 'dovecot' and gid '143': ERROR: groupname 'dovecot' already in use by gid '1003' Please resolve these issues and try again: Either remove the conflicting group or if you wish to continue using a legacy gr

On the whole we are pleased with our trials of dovecot to replace UW-IMAP. But (ah!) we have hit one particular problem, in which we think dovecot could probably benefit from a resilience improvement. We're running dovecot on Fedora Core 5 (FC5), with passwd map details supplied by NIS. We have found that "nscd" sometimes thinks that a username is invalid, even though it is valid.

convert_mail = mbox:%h/mail Convert plugin. If set, specifies the source storage path which is converted to destination storage (mail_location) when the user logs in. The existing mail directory is renamed to <dir>-converted. I'm not entirely clear on what this does. If someone can clarify for me, I'll update the Wiki. I'm hoping it'll allow me to convert

http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz.sig Found another bad bug in rc19 changes. Wonder why my imaptest catched the bug only in CVS HEAD but not in branch_1_0 even though both had it. Anyway, now the imaptest runs nicely for both, and I'm again optimistic that the bug count is low enough for v1.0 to be released soon :) BTW. My

http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz http://dovecot.org/releases/dovecot-1.0.rc22.tar.gz.sig Found another bad bug in rc19 changes. Wonder why my imaptest catched the bug only in CVS HEAD but not in branch_1_0 even though both had it. Anyway, now the imaptest runs nicely for both, and I'm again optimistic that the bug count is low enough for v1.0 to be released soon :) BTW. My

v1.0.rc22 FC6 x86_64 So, here is my config: protocol imap { } protocol pop3 { } protocol lda { postmaster_address = postmaster at example.com } auth_master_user_separator = * auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot.masterusers master = yes } passdb pam { } userdb passwd { }

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

Running rc24 and with one user in particular they are getting "(auth) killed with signal 11" when trying to pop email. IMAP works. What causes this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://dovecot.org/pipermail/dovecot/attachments/20070224/195f61be/attachment-0002.html>

I had our production systems running on rc23, however we ran into problems when the server was under heavy load. Eventually, the server would begin to freeze all imap connection after authentication (according to the logs). A user would connect, authentication would succeed, and then the connection would sit until timing out. No error logs were produced. Upgrading to rc24 did not