- dovecot - dovecot.org

[Dovecot] dovecot 1.1.2, another assertion failure in index-mail.c: (!mail->data.destroying_stream)
by Diego Liziero 25 Jul '08

25 Jul '08

Here is the log. --- dovecot: Jul 25 07:18:35 Panic: IMAP(user): file index-mail.c: line 1091 (index_mail_close): assertion failed: (!mail->data.destroying_stream) dovecot: Jul 25 07:18:35 Error: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x80f5fd4] -> /usr/libexec/dovecot/imap [0x80f6877] -> /usr/libexec/dovecot/imap(i_fatal+0) [0x80f6130] -> /usr/libexec/dovecot/imap(index_mail_close+0xf9) [0x80a8129] -> /usr/libexec/dovecot/imap [0x80a8148] -> /usr/libexec/dovecot/imap(index_mail_set_seq+0x50) [0x80a8302] -> /usr/libexec/dovecot/imap [0x8087e3b] -> /usr/libexec/dovecot/imap(mail_set_seq+0x21) [0x80b391c] -> /usr/libexec/dovecot/imap(index_storage_search_next_nonblock+0xcb) [0x80ad3e8] -> /usr/libexec/dovecot/imap(mailbox_search_next_nonblock+0x26) [0x80b6a97] -> /usr/libexec/dovecot/imap(mailbox_search_next+0x2c) [0x80b6a63] -> /usr/libexec/dovecot/imap [0x805b757] -> /usr/libexec/dovecot/imap(cmd_copy+0x1c4) [0x805b98e] -> /usr/libexec/dovecot/imap(cmd_uid+0xbb) [0x80610d3] -> /usr/libexec/dovecot/imap [0x8062494] -> /usr/libexec/dovecot/imap [0x80626c9] -> /usr/libexec/dovecot/imap [0x80627c7] -> /usr/libexec/dovecot/imap [0x8062803] -> /usr/libexec/dovecot/imap(client_input+0xb7) [0x8062991] -> dovecot: Jul 25 07:18:35 Error: IMAP(user): /usr/libexec/dovecot/imap(io_loop_handler_run+0x17d) [0x8100630] -> /usr/libexec/dovecot/imap(io_loop_run+0x35) [0x80ff8de] -> /usr/libexec/dovecot/imap(main+0xe4) [0x806de1d] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x42bdec] -> /usr/libexec/dovecot/imap [0x805a1a1] dovecot: Jul 25 07:18:35 Error: child 27074 (imap) killed with signal 6 dovecot: Jul 25 07:18:35 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:18:36 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:33 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:42 Error: IMAP(user): Corrupted transaction log file /mailhome/user/.imap/Trash/dovecot.index.log: record size too small (type=0x40, offset=56, size=0) dovecot: Jul 25 07:19:48 Warning: IMAP(user): fscking index file (in-memory index) dovecot: Jul 25 07:19:48 Error: IMAP(user): Transaction log got desynced for index (in-memory index)

1 0

[Dovecot] Dovecot 1.1.2, SIGABRT on copy mail
by Andreas M. Kirchwitz 25 Jul '08

25 Jul '08

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 02:13:25 linux dovecot: Panic: IMAP(user2): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 02:13:25 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd] -> imap [0x807a454] -> imap(index_transaction_commit+0x4e) [0x809ddfe] -> imap(cmd_copy+0x35f) [0x805b26f] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] Jul 25 02:13:25 linux dovecot: child 7954 (imap) killed with signal 6 Thus, the daemon died somewhere between successfully saving a copy of the mail from INBOX to the destination folder and flagging it to be deleted in the INBOX. Just a couple of minutes later, Dovecot died again. Wanted to save a message from INBOX to another folder. But this time, the message wasn't written to the destination folder. As before, the original mail in the INBOX didn't change any flags. Jul 25 02:22:07 linux dovecot: Panic: IMAP(user2): file message-parser.c: line 770 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0 || ctx->broken) Jul 25 02:22:07 linux dovecot: IMAP(user2): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap(message_parser_parse_body+0) [0x80c8ba0] -> imap(message_parser_parse_body+0x1e) [0x80c8bbe] -> imap [0x8095120] -> imap [0x809528c] -> imap(index_mail_get_special+0x3a7) [0x8095757] -> imap [0x8061b94] -> imap(imap_fetch+0x148) [0x80620f8] -> imap(cmd_fetch+0x28e) [0x805bcae] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] Jul 25 02:22:07 linux dovecot: child 17931 (imap) killed with signal 6 The error cannot be reproduced with these messages. They can be saved/copied now without problems back and forth. I've tried to send more mail and reproduce the problem, but no success. Works perfectly fine. Dovecot 1.1.2 is running on Fedora 8 Linux 32 Bit with all patches and custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.2: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd The problem was reported by a user who continued to work with his mail folders. I was only a few seconds too late to grab a copy of the INBOX and index files. Greetings, Andreas

1 0

[Dovecot] dovecot 1.1.2 dbox file_dotlock_open() failed with file
by Robert Schetterer 25 Jul '08

25 Jul '08

Hi Timo, i have failures like with deleting a folder in the log dovecot: Jul 25 02:12:14 Error: IMAP(.....com): file_dotlock_open() failed with file /usr/local/virtual/.../...@....com/zzzz/dbox-Mails/dovecot.index.log: No such file or directory with short tests i cant see any real problem folder can be created and deleted with thunderbird ( but only with tb-extra-mailbox-sep enabled ) its not a new log entry to dovecot 1.1.2 but this is first time i noticed , by near expection of the log after update, and of course i missed it by playing so much with configs -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] dovecot.conf permissions
by Dan Horák 24 Jul '08

24 Jul '08

Hi, I have a little problem with defining the right permissions for dovecot.conf. The main problem is that the password for SSL certificates is stored there and the conf file is world readable by default, which makes a security problem [1]. It is not a problem to restrict the permissions to 0600, dovecot will still work, but then deliver cannot work as it reads the conf too, but it runs under arbitrary user. So my last iteration is 0640 as permission and root:mail as ownership, but that expects that deliver is run with group = mail. For the long term solution I would prefer to move the password into a separate config file so the permissions can be properly restricted there. What are your opinions? With regards, Dan [1] https://bugzilla.redhat.com/show_bug.cgi?id=436287 -- Fedora and Red Hat package maintainer

3 2

[Dovecot] Delivery notifications
by Brandon Keepers 24 Jul '08

24 Jul '08

I'm working on an application that is backed by Postfix 2.3.8 and Dovecot 1.0.13, configured with virtual domains, for handling messaging. I need to be able to send the notification (such as "You've received a new message on SomeAwesomeService. Click here to check it out", It's evil, I know) to a different email address, such as a mobile device. Eventually, we want to do other things like clear web page caches when a message is received, or sending IM notifications, but that's for another day. So basically, we want to notify our application whenever a new mail is received, and it can do all the magical things that it needs to do. I was hoping to get some feedback on the different approaches I'm looking at. From what I can tell, there's not a way to deliver to multiple virtual transports in postfix, so here's the options I see: * Content filter I could set up a "content filter" that just delivers the mail to the application, and then re-injects it back into postfix. This seems like more work than the other options just because I have to worry about re- injecting the message * Intercept delivery Replace the dovecot deliver command with a custom one that calls the dovecot deliver and then passes the message on to the application. I've written a little proof of concept for this and it seems to work, but just seem shady. * Sieve Dovecot supports Sieve, so I could just have a global sieve script that sends the notifications. This is definitely the solution I'm leaning towards. Are there any better options? Do you think this will have a significant impact on performance? Am I crazy? Thanks, Brandon

4 4

[Dovecot] making IMAP quicker on LAN
by Andrew Von Cid 24 Jul '08

24 Jul '08

Hi all, I keep on hitting this problem when migrating new clients from POP or local IMAP servers (hosted on their LAN's) to my Dovecot setup, which is hosted properly in a data center. People usually complain that it's slower and although they're getting a kick ass mail setup it doesn't look good from their point of view. I'm wondering if there is anything I could do to speed it up on their LAN's. What I mean is probably a caching IMAP proxy or some sort of replication to a local Dovecot server. Is this something Dovecot can do? I'd be really grateful for any opinions on how to tackle this problem. Many thanks, Andrew.

3 2

[Dovecot] Case sensitve problem
by Sven Schmidt 24 Jul '08

24 Jul '08

Hi! I am using Postfix, Mysql and Dovecot 1.0.rc15. It seems that Dovecot creates new mailboxes for eg. User(a)Domain.COM althoug in the name in databse is user(a)domain.com ny logging in pop3. How to solve this problem?

3 4

[Dovecot] how to store flags \Seen into read-only mailbox?
by seriv＠parkheights.dyndns.org 24 Jul '08

24 Jul '08

Hi, I'm trying to use dovecot for storing mailing lists and read-only access for users. The OS is Solaris, authentication for all readers of these lists are from Ldap through PAM, and one local user "listuser" will receive all mail and store them into it's folders (Maildirs). These maildirs are readable (read-only) for all others and they are shared by setting --- mail_location: maildir:/home/vmail/listuser/Maildir:CONTROL=/home/vmail/%u/Maildir/control:INDEX=/home/vmail/%u/Maildir/index --- Mail became readable because in each mail folder to be shared there is dovecot-shared with mode 064, and all users included into his group. But this is the problem: how to have flag \Seen stored in read-only mailbox? As recorded by rawlog, it is ignored now: --- bash-3.00# cat 20080724-103219-10616.in 3 namespace 4 lsub "" "*" 5 list "" "INBOX" 6 list "" "Trash" 7 create "Trash" 8 select "OmniTI.FreeLotto.Ops" 9 UID fetch 1:* (FLAGS) 10 uid store 1:3 +Flags (\Seen) 11 IDLE DONE 12 close 13 logout bash-3.00# cat 20080724-103219-10616.out * OK [RAWLOG TIMESTAMP] 2008-07-24 10:32:19 * NAMESPACE (("" ".")) NIL NIL 3 OK Namespace completed. * LSUB () "." "OmniTI.FreeLotto.ODS" * LSUB () "." "OmniTI.FreeLotto.Ops" 4 OK Lsub completed. * LIST (\HasNoChildren) "." "INBOX" 5 OK List completed. 6 OK List completed. 7 NO Internal error occurred. Refer to server log for more information. [2008-07-24 10:32:19] * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 3 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1216906857] UIDs valid * OK [UIDNEXT 4] Predicted next UID 8 OK [READ-ONLY] Select completed. * 1 FETCH (UID 1 FLAGS ()) * 2 FETCH (UID 2 FLAGS ()) * 3 FETCH (UID 3 FLAGS ()) 9 OK Fetch completed. 10 OK Store ignored with read-only mailbox. + idling 11 OK Idle completed. 12 OK Close completed. * BYE Logging out 13 OK Logout completed. --- -- Sergey ivanov.

1 0

[Dovecot] Quota
by M. Rodrigo Monteiro 24 Jul '08

24 Jul '08

Hello! This might be an easy question, but here it goes: how can I know the quota of an determined user? I'm trying to use maildir quota... Regards, Rodrigo. -- M. Rodrigo Monteiro falecom(a)rodrigomonteiro.net "Free as in Freedom, not free as in free beer" Linux User # 403730

2 2

Re: [Dovecot] Dovecot antispam (X-DSPAM-Signature)
by Johannes Berg 24 Jul '08

24 Jul '08

On Wed, 2008-07-23 at 23:44 +0100, Nuno Lopes wrote: > I think that the question wasn't to the point. The problem we have is in > the transition phase. At one point we have emails with the header and > emails that haven't got it but we don't want users to notice the > introduction of this plugin and DSPAM. So we would like to allow users > to move any mail to the spam folder even if those mails haven't got the > DSPAM signature. In which case the email could be moved and not passed > to dspam. > > If you see this as a functionality that could go into your plugin we > would be willing to develop the patch based on any idea you have on how > this should be done. Hmm. I don't necessarily see that as a desirable feature because in the case that something is actually wrong with the spam tagging you want to notice it isn't working right. If you really need that, just don't set an error when it happens and do nothing, allowing the move. johannes

1 0