- dovecot - dovecot.org

[Dovecot] Stumped on adding X-Header...
by Brian Hayden 11 Sep '08

11 Sep '08

Recently I posted about wanting to add an x-header recording a timestamp for changing the \Deleted flag, for purposes of doing expiry on mbox mailboxes. Timo replied: > Be sure to add it to mbox_hide_headers[] and mbox_save_drop_headers[] > arrays in mbox-storage.c and hope that it doesn't exist in any of your > existing mails. :) Other than that there shouldn't be problems. I looked at the two places where X-Status was being written--mbox-save.c and mbox-sync-update.c--and tried adding this header. It didn't work. To test my sanity, I changed the string 'X-Status' in each of these to something else. The mbox file still ended up with 'X-Status' written in it, and I can't for the life of me find any other code that might write that string. Timo? Anyone? -- Brian Hayden UMN OIT Internet Services

2 1

[Dovecot] 1.1.3 panics
by Dean Brooks 11 Sep '08

11 Sep '08

Hi, Installed Dovecot 1.1.3 today and started receiving panic errors on a few of our users: dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index-transaction-view.c: line 204: unreached When I upgraded, I deleted all of our users index files so it started with a clean slate. We are running mbox format over NFS with fsquota plugin on Solaris 8. Here is output of dovecot -n: base_dir: /var/run/dovecot/ protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: daemon login_log_format_elements: user=%u ip=%r mail_max_userip_connections: 5 first_valid_uid: 100 last_valid_uid: 128000 mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/mail/%u:INDEX=/var/indexes/local/%u mail_nfs_storage: yes mbox_write_locks: fcntl mbox_lock_timeout: 180 mbox_lazy_writes: no mail_plugins: quota imap_quota namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: Mail/ hidden: yes subscriptions: yes auth default: mechanisms: plain login failure_delay: 5 debug: yes debug_passwords: yes passdb: driver: shadow userdb: driver: passwd plugin: quota: fs -- Dean Brooks dean(a)iglou.com

3 8

[Dovecot] SSL fields as variables for SQL statements ...
by XhE 11 Sep '08

11 Sep '08

Hi, I was wondering if there is any possibility to access the status if a user has provided a certificate, that has been accepted or not via variables. And further if there is any way to get the value of SSL certificate fields by use variables. I'd like to use those variables in sql statements. I then could assign a single certificate to a user, and make up passdb sql statements, that allow him to access multiple (but not all) mailboxes without the need to issue any further certificates. --- Michael

2 2

[Dovecot] How to propelry restore a Maildir
by Thomas Hummel 11 Sep '08

11 Sep '08

Hello, I would like to know what is the proper way to restore a Maildir : Assuming someone has got a foobar/[cur|new|tmp] maildir, loses for some reason its content and that some new mail (seen and/or unseen) comes into that mailbox inbetween (that is before the restore procedure takes place, thus creating the need to merge restored messages and new ones). I'd like to check the following (I don't use deliver but procmail) : 1. the messages filenames are unique in time (meaning that a new message cannot be assigned a name already existing in the backup (the name of an old message), at least for the same mailbox instance : if that's not the case : how can we merge safely ? 2. what naming scheme is used (the left part of the name, before the :2,) ? I've got something like : 1215166123.52887_0.host.dom.ain:2,[...] what are the 1215166123, the 52887 and 0 ? 3. what can we deduce from the last modified date of the file as seen in ls -l ? . when in new/, is it the same as the one in the Received: header or is it when in tmp/ ? . when in cur/, is it the date the client "saw" the message ? What would "saw" mean in that case ? 4. should the dovecot-uidlist and dovecot-keywords be updated after the restore or is it better to let dovecot rearrange them itself ? 5. same question for the index and cache files ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

3 8

[Dovecot] Panic in Dovecot 1.1.3: index-mail.c: line 1091: assertion failed: (!mail->data.destroying_stream)
by Peter Eriksson 11 Sep '08

11 Sep '08

Dovecot 1.1.3 Solaris 10 SPARC (Sun Fire T1000) Compiled with Sun Studio 12 compilers. Maildir on NFS Indexes on local disk (UFS). 'dovecot -n' output attached. IMAP process crashes for certain (many, but not all) users when accessing certain folders (in the example below, in crashes when accessing my INBOX, about 1700 mails). I could access other mailboxes without problems. And a simple telnet to the imap port followed by a login works fine. Erased the coredumps (was filling up the system too quickly) so I can't really produce a backtrace right now (had to back down to 1.0.13 again even though that one has another core-dump-generating problem - but that is atleast limited to only one specific user so far). Going to set up a separate test server to test things more without disturbing our normal operations... I started with an empty INDEX directory to make sure there weren't problems with old corrupted indexes. Output from syslog: Sep 9 12:34:44 ifm.liu.se dovecot: [ID 107833 mail.info] imap-login: Login: user=<peter>, method=GSSAPI, rip=130.236.160.102, lip=130.236.160.6, secured Sep 9 12:34:44 ifm.liu.se dovecot: [ID 107833 mail.crit] Panic: IMAP(peter): file index-mail.c: line 1091: assertion failed: (!mail->data.destroying_stream) Sep 9 12:34:44 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(peter): Raw backtrace: 0x1000b5188 -> 0x1000605ac -> 0x1000605e4 -> 0x100060734 -> 0x1000657b8 -> 0x100070470 -> 0x1000204e0 -> 0x100020868 -> 0x100016e78 -> 0x10001dab8 -> 0x10001debc -> 0x10001e0a4 -> 0x1000bf4b4 -> 0x1000bea68 -> 0x10002933c -> 0x100014c9c Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): client out: OK 1 user=peter Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): passwd(peter,130.236.160.102): lookup Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): master out: USER 241 peter system_user=peter uid=103 gid=10 home=/home/peter Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] imap-login: Login: user=<peter>, method=GSSAPI, rip=130.236.160.102, lip=130.236.160.6, secured Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.crit] Panic: IMAP(peter): file index-mail.c: line 1091: assertion failed: (!mail->data.destroying_stream) Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(peter): Raw backtrace: 0x1000b5188 -> 0x1000605ac -> 0x1000605e4 -> 0x100060734 -> 0x1000657b8 -> 0x100070470 -> 0x1000204e0 -> 0x100020868 -> 0x100016e78 -> 0x10001dab8 -> 0x10001debc -> 0x10001e0a4 -> 0x1000bf4b4 -> 0x1000bea68 -> 0x10002933c -> 0x100014c9c - Peter # 1.1.3: /etc/dovecot.conf.new base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_ca_file: /ifm/etc/certs/dovecot-CA.cert.pem ssl_cert_file: /ifm/etc/certs/dovecot-ifm.cert.pem ssl_key_file: /ifm/etc/certs/dovecot-ifm.key.pem login_dir: /var/run/dovecot/login login_executable(default): /ifm/libexec/dovecot/imap-login login_executable(imap): /ifm/libexec/dovecot/imap-login login_executable(pop3): /ifm/libexec/dovecot/pop3-login login_greeting: Welcome to the IFM Dovecot Server. first_valid_uid: 100 mail_location: maildir:Maildir:INDEX=/var/indexes/%u mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mbox_write_locks: fcntl mail_executable(default): /ifm/libexec/dovecot/imap mail_executable(imap): /ifm/libexec/dovecot/imap mail_executable(pop3): /ifm/libexec/dovecot/pop3 mail_plugin_dir(default): /ifm/lib/dovecot/imap mail_plugin_dir(imap): /ifm/lib/dovecot/imap mail_plugin_dir(pop3): /ifm/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: Mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~/mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~/Mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~%u/mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~%u/Mail/ hidden: yes subscriptions: yes auth default: mechanisms: plain login gssapi executable: /ifm/libexec/dovecot/dovecot-auth verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd

3 11

[Dovecot] Panic: file sieve-cmu.c: line 262 (part_save): assertion failed: (buf->used - 1 == part->body_size.physical_size)
by Maciej Polewczyński 11 Sep '08

11 Sep '08

Hello Dovecot v1.1.3 Sieve plugin v1.1.5 Debian Lenny Virtual users in mysql db dovecot -n at the end of email I have problem with sieve body rules during delivery. When I test rule if body :raw :contains [ ".exe" ] { discard; } deliver die with panic: Sep 10 15:14:37 mail deliver(user): Panic: file sieve-cmu.c: line 262 (part_save): assertion failed: (buf->used - 1 == part->body_size.physical_size) Sep 10 15:14:37 mail deliver(user): Raw backtrace: /usr/local/libexec/dovecot/deliver [0x80ca1a1] -> /usr/local/libexec/dovecot/deliver(i_syslog_fatal_handler+0x34) [0x80ca274] -> /usr/local/libexec/dovecot/deliver [0x80c9bb9] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e44bce] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e44fc4] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e4ef4a] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x3a8) [0xb7e50558] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xe2) [0xb7e56282] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x326) [0xb7e46166] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e43bf6] -> /usr/local/libexec/dovecot/deliver(main+0x111a) [0x805dfda] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e81455] -> /usr/local/libexec/dovecot/deliver [0x805bc11] Is there a bug or I have done something wrong. /usr/local/sbin/dovecot -n # 1.1.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login first_valid_uid: 150 mail_privileged_group: mail mail_location: maildir:%h/Maildir mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@+% debug: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.user.conf passdb: driver: sql args: /usr/local/etc/dovecot-sql.alias.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.user.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.alias.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir -- Pozdrowienia Maciej Polewczynski Registered Linux user #117725

1 0

[Dovecot] Support of client specific flags?
by Steinar Bang 11 Sep '08

11 Sep '08

Gnus use a lot of custom flags to represent the messages state wrt. Gnus. How well are these flags supported in dovecot? How fast are access to them? (Ie. will dovecot have to open the message and parse the headers) Are they supported when using imapsync to transfer messages from a different IMAP server? (I guess I'll find out soon, because I'm using imapsync to transfer messages from a cyrus imap daemon to a dovecot one, as I'm writing this)

2 2

[Dovecot] 1.2.alpha1: file_dotlock_open() failed with subscription file
by Frank Elsner 11 Sep '08

11 Sep '08

Hi *, running dovecot 1.2.alpha1 I find the following messages in the log: Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted Sep 10 01:28:52 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:52 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted File permissions are: -rw------- 1 steffen elsner 124 Aug 22 12:51 /home/Mail/steffen/subscriptions And finally the output of "dovecot -n" reads: # 1.2.alpha1: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ ssl_cert_file: /usr/local/etc/seymour.crt ssl_key_file: /usr/local/etc/seymour.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/dovecot/libexec/dovecot/imap-login login_greeting: c64.shuttle.de - Dovecot ready. login_log_format_elements: %u %r %c login_processes_count: 2 verbose_proctitle: yes first_valid_uid: 100 last_valid_uid: 65534 mail_location: maildir:/home/Mail/%u:INDEX=MEMORY maildir_copy_preserve_filename: yes mail_executable: /usr/dovecot/libexec/dovecot/imap mail_plugin_dir: /usr/dovecot/lib/dovecot/imap mail_log_prefix: %Us(%u,%r): mail_log_max_lines_per_sec: 100 imap_client_workarounds: netscape-eoh tb-extra-mailbox-sep imap_logout_format: [%i/%o] auth default: executable: /usr/dovecot/libexec/dovecot/dovecot-auth master_user_separator: / passdb: driver: pam args: dovecot passdb: driver: passwd-file args: /usr/dovecot/etc/masters userdb: driver: passwd plugin: mail_log_events: delete undelete expunge copy mailbox_delete What's behind? Critical? How to solve? Regards, Frank Elsner

3 4

Re: [Dovecot] Panic: IMAP: Trying to allocate 2273345672 bytes
by Mark Zealey 11 Sep '08

11 Sep '08

> > About our setup: These are on an nfs-mounted file system. > It's shared > > between two computers and connections are randomly > redirected to either > > box; so potentially it could be an nfs type corruption > issue. Timo, I'll > > send you a tarball of the dovecot* files off-list > > Sounds like it could be because of NFS caching issues. You've set > mail_nfs_index=yes, right? What OS? Linux should be OK, but > FreeBSD has > some issues. Thanks for the patch; I've not seen any issues to do with nfs caching before and we've had this live on very heavily loaded systems for several months now. We use exim with deliver to deliver the messages (maildir only). Relevant config: mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock maildir_copy_preserve_filename: yes Linux (centos5.2 w/updates). Mount options: rw,noatime,nodiratime,hard,intr,rsize=32768,wsize=32768,tcp,nocto Mark

1 0

[Dovecot] 1.1.3 vs 1.1.2 stability?
by Tomasz K Jarzynka 11 Sep '08

11 Sep '08

Hi, since I've numerous reports of segfaults/crashes/corruptions with Dovecot 1.1.3 with Sieve, I'd like to ask - is 1.1.3 an improvement over 1.1.2 or are there some acknowledged regressions and 1.1.4 is planned to fix that? I'd love to avoid figuring this on a live setup and hope to exploit other admins' courage ;P rgds, -- Tomasz Krzysztof Jarzynka / mob. +48 601 706 601 / HANDLE: TJ950-RIPE Network Information Systems Administrator / tomee(at)genesilico(d-o-t)pl Laboratory of Bioinformatics and Protein Engineering | www.genesilico.pl International Institute of Molecular and Cell Biology | www.iimcb.gov.pl

2 1