- dovecot - dovecot.org

[Dovecot] beta9 (auth) killed with signal 11 - backtrace
by Paul Harrington 23 Jun '06

23 Jun '06

Further to my previous email I managed to find the core file. Version: 1.0.beta9 OS: Gentoo x86 Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. (gdb) bt full #0 0xb7d575ba in strcasecmp () from /lib/tls/libc.so.6 No symbol table info available. #1 0x0805b091 in passdb_get_credentials () No symbol table info available. #2 0x00000000 in ?? () No symbol table info available.

1 0

[Dovecot] 2nd Question on v1.0 setup and maildir
by Patrick Carney 23 Jun '06

23 Jun '06

_____ From: Patrick Carney [mailto:patrick@castandcrew.com] Sent: Thursday, June 22, 2006 8:55 AM To: 'dovecot(a)dovecot.org' Subject: Question on v1.0 setup and maildir Hello all. I appreciate the responses to my problem on v0.99.14. Thank you all. We have built a new server running version 1.0-0_15.beta9.el4. The mail delivery agent is sendmail. We seem to have gotten it up fairly easily. But we have one problem. We are using the maildir feature instead of mbox and when ever mail gets delivered, it is not sending it to the \maildir\new folder. It seems to be dumping it in the root of the maildir directory, thus when a client checks for email, it appears nothing is there. Here is a sample from our config. Any suggestions will be much appreciated. Forgive me if this is elementary question, but I am new to dovecot. ## Mailbox locations and namespaces ## # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There are a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = maildir:/home/%u/Maildir # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no ##

4 4

[Dovecot] This store does not support subscriptions, or they are not enabled...
by Dan Stromberg 23 Jun '06

23 Jun '06

Hi folks. I'm using evolution 2.2.3 on Fedora Core 4 with simap to dovecot 1.0beta9. I had the same problem with dovecot 1.0alpha1. The problem is that I can't seem to subscribe to any folders. Nor can I seem to get this combination to list all of my folders. I'd be fine with either. It used to be, that if I just toggled "show only subscribed folders" a few times, I'd start getting folders, but not anymore. Of course, sometimes the behavior would be the opposite of what I'd selected, but I wasn't too worried about that. Any suggestions? Thanks!

2 8

[Dovecot] maildir++ Quotas - bizarre behavior.
by Apps Lists 22 Jun '06

22 Jun '06

Hi Timo et al. I've been trying to track down why Dovecot recalculations of maildirsize are so wildly different (lower) than what Maildrop comes up with. I think I've found some bizarre behavior in Dovecot -- this is in beta9 as well as CVS from yesterday. It appears Dovecot isn't looking at /Maildir/cur ... /Maildir/new and /Maildir/tmp. It is, however, looking at /Maildir/.Drafts, /Maildir/.Sent, and /Maildir/.Trash. None of these folders contain any messages, but Dovecot seems to count the existence of . and .. as message files. Worse, it's coming up with actual usage data for these empty (of messages) folders. Presumably it's counting the log and cache files. I've attached a diff to quota-maildir.c which will enable some verbose logging. Also attached is a ls -lR of the Maildir in question as well as the output of the aforementioned debugging. Please help. Steve

1 0

[Dovecot] Authentication problems with mysql 5
by Gianfranco Bartolini 22 Jun '06

22 Jun '06

Hello, this is my first post here, so hi to all! I've just configured a new Suse Linux 10.1 distribution that comes with: - postfix 2.2.9 + mysql tables - dovecot 1.0.beta3 - mysql 5.0.18 - kernel 2.6.16.13-4-bigsmp i386 on a Intel Xeon 2.0Ghz with 3Gb RAM I've also added postfixadmin 2.1.0 to build an IMAP server with virtual users/virtual hosts management, and ran the script DATABASE_MYSQL.TXT to build correctly database/tables and user/permissions. The problem is that dovecot fail to access to mysql tables with the following error: =================== dovecot: Jun 12 18:40:28 Info: Dovecot v1.0.beta3 starting up dovecot: Jun 12 18:40:29 Error: auth-worker(default): mysql: Connect failed to 127.0.0.1 (postfix): Access denied for user 'postfix'@'localhost' (using password: YES) - waiting for 1 seconds before retry =================== I've tried to connect to mysql using the socket instead of the local ip address, but i've got the same error: =================== dovecot: Jun 12 18:55:19 Info: Dovecot v1.0.beta3 starting up dovecot: Jun 12 18:55:20 Error: auth-worker(default): mysql: Connect failed to (null) (postfix): Access denied for user 'postfix'@'localhost' (using password: YES) - waiting for 1 seconds before retry =================== In mysql the user "postfix" is correctly created with access granted from either localhost and 127.0.0.1 If i do the same from the command line it works perfectly: =================== server01:/ # mysql -h localhost -u postfix -p Enter password: secret Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 136 to server version: 5.0.18 Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> =================== Here is my dovecot.conf: =================== default_mail_env = maildir:/home/mbox/%d/%n protocols = imap pop3 auth default { mechanisms = plain userdb sql { args = /etc/dovecot/dovecot-sql.conf } passdb sql { args = /etc/dovecot/dovecot-sql.conf } } first_valid_uid = 51 ssl_disable = yes listen = * log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log =================== And my dovecot-sql.conf: =================== driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=postfix user=postfix password=secret default_pass_scheme = PLAIN password_query = SELECT password FROM mailbox WHERE username = '%u' AND active = '1' user_query = SELECT maildir AS mail, 51 AS uid, 51 AS gid FROM mailbox WHERE username = '%u' AND active = '1' =================== I'v tried also all the password mechanisms (PLAIN, PLAIN-MD5, MD5, CRYPT) with no success. My google searches ended with no results. Btw, the same configuration on a Suse 9.3 professional works perfectly :( Please anyone can help me? Thanks in advance for all the kindly support Saluti G.Bartolini Linux User #333064

4 8

[Dovecot] Re: entered bc_action_emit with filelen:
by Alex Pimperton 21 Jun '06

21 Jun '06

Hi, I'm still getting the errors below on Debian Etch with Dovecot 1.0.8-4 and Dovecot LDA. Is this something that's fixed in 1.0.9? It doesn't seem to have an effect but I'm wary of messages I don't recognise! Regards, Alex Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: 16 Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: 112 Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: 240 Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: 368 Jun 20 14:13:04 server01 deliver: entered bc_action_emit with filelen: -- This message has been scanned for viruses and dangerous content by the MailScanner at Placet.co.uk, and is believed to be clean.

5 7

[Dovecot] problem with kqueue
by Alessandro de Manzano 21 Jun '06

21 Jun '06

Hello, I'm a new user of Dovecot (since 1.0b8) and I'ld report about a possible bug. Situation: Dovecot 1.0beta9 with kqueue support FreeBSD 6.1-Release x86 machine (IBM x206, P4 3.2 Ghz) local filesystem UFS2 This is an internal, experimental, mail server running Postfix and Dovecot configured with Maildirs e IMAP-only access. Clients are quite few, now, just because it's an experiment. However are near all Outlook Express 6. Running with dovecot 1.0 beta8 _without_ kqueue support for few weeks was fine, no problems at all. A couple of days ago I updated to beta9 (using FreeBSD's portupgrade tools) and in the _same_time_ I enabled the kqueue support. Since then I've seen about 3-4 of these in the log: (note that process traps apparently after reporting the unrecognized event) Jun 20 10:38:53 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:38:54 bigblue dovecot: IMAP(laura2): Disconnected in IDLE Jun 20 10:38:54 bigblue dovecot: IMAP(laura2): Unrecognized event: kevent {.ident = 1, .filter = 0xfffffffe, .flags = 0x0000, .fflags = 0x00000000, .data = 0x00008322} Jun 20 10:38:54 bigblue dovecot: IMAP(laura2): mode: 0x004x Jun 20 10:38:54 bigblue kernel: pid 18426 (imap), uid 1004: exited on signal 6 Jun 20 10:38:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:38:54 bigblue dovecot: child 18426 (imap) killed with signal 6 Jun 20 10:38:54 bigblue dovecot: IMAP(laura2): Disconnected Jun 20 10:38:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:38:54 bigblue dovecot: IMAP(laura2): Disconnected in IDLE Jun 20 10:38:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:39:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:39:54 bigblue dovecot: IMAP(laura2): Disconnected in IDLE Jun 20 10:39:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:39:54 bigblue dovecot: IMAP(laura2): Disconnected in IDLE Jun 20 10:39:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:39:54 bigblue dovecot: IMAP(laura2): Disconnected in IDLE Jun 20 10:39:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:39:54 bigblue dovecot: IMAP(laura2): Disconnected Jun 20 10:39:54 bigblue dovecot: imap-login: Login: user=<laura2>, method=PLAIN, rip=192.168.9.31, lip=192.168.9.68 Jun 20 10:39:54 bigblue dovecot: IMAP(laura2): Disconnected in IDLE Any ideas ? Any one else got these messages ? I'ld try recompiling beta9 without kqueue support, probably the issue would disappear, but IMHO is not the best way to "correct" things :) Many thanks in advance! -- Alessandro de Manzano System & Network Administrator Playstos - TIMA S.p.A. Corso Sempione 63 20149 Milano, Italy tel.: +39-023314153 fax : +39-02315678 email: demanzano(a)playstos.com http://www.playstos.com

1 0

[Dovecot] Dovecot servers / SAN
by Dean Manners 21 Jun '06

21 Jun '06

Hey guys, Wondering if anyone out there has any input on running Dovecot with SAN storage. Its coming to the time where we need to run load balanced servers, and past experiences steer us away from a NAS. Tips / pitfalls ? Regards __________________________________________ Dean Manners

3 4

RE: [Dovecot] imap - mailbox in an inconsistant state
by Patrick Carney 21 Jun '06

21 Jun '06

So how do I delete his indexes? Is there somewhere a step by step procedure? Timo, please help? Forgive me, I am new to all this. Thanks much, Patrick -----Original Message----- From: Jeff Graves [mailto:jeff@image-src.com] Sent: Tuesday, June 20, 2006 11:34 AM To: 'Patrick Carney' Subject: RE: [Dovecot] imap - mailbox in an inconsistant state I haven't used 0.99 in a while but it shouldn't destroy the subscriptions. I think the next login may be delayed some while the index is rebuilt. Might want to check with Timo. -- Jeff Graves, MCSA Image Source, Inc. 508.966.5200 x31 www.image-src.com -----Original Message----- From: Patrick Carney [mailto:patrick@castandcrew.com] Sent: Tuesday, June 20, 2006 2:23 PM To: 'Jeff Graves'; dovecot(a)dovecot.org Subject: RE: [Dovecot] imap - mailbox in an inconsistant state Will that destroy his folder subscriptions? Will I loose anything? Thanks PAtrick -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Jeff Graves Sent: Tuesday, June 20, 2006 11:18 AM To: dovecot(a)dovecot.org Subject: RE: [Dovecot] imap - mailbox in an inconsistant state The only quick and easy band-aid I can think of is to delete the indexes and let dovecot recreate them. -- Jeff Graves, MCSA Image Source, Inc. 508.966.5200 x31 www.image-src.com -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Patrick Carney Sent: Tuesday, June 20, 2006 12:44 PM To: 'Timo Sirainen' Cc: dovecot(a)dovecot.org Subject: RE: [Dovecot] imap - mailbox in an inconsistant state Yes. I was afraid of that. But the weird thing is it only happens with One particular user. And at that, it wasn't doing it for the longest time. It just started recently. Is there a band-aid for this. I ask because we are not in a place to upgrade at the moment. Thanks Patrick -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Timo Sirainen Sent: Tuesday, June 20, 2006 9:37 AM To: Patrick Carney Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] imap - mailbox in an inconsistant state On Tue, 2006-06-20 at 09:07 -0700, Patrick Carney wrote: > "Jun 19 08:08:34 burmail imap(ed): Corrupted binary tree > file /home/ed/mail/.imap/INBOX/.imap.index.tree: UID to be inserted > isn't higher than existing (2 <= 504)" > Can someone tell me what that means?? I have been assigned to take > over for a departed sys admin and have never used or administered > Dovecot before. You're using 0.99.x Dovecot and there's not much point anymore in trying to figure out why it's broken. I'd suggest upgrading to 1.0beta versions as the first step. If it still breaks after that I can help debug it further. Also see http://wiki.dovecot.org/UpgradingDovecot

3 4

[Dovecot] Reading the index / log files
by Raymond Lillard 21 Jun '06

21 Jun '06

Dear Dovecot, I have a user who claims his mail is being lost. I can find the message marked as having been accepted for delivery in the maillog. I am hoping there is a tool which will let me read his IMAP transactions. We are delivering the messages with procmail and storing them as Maildir files. I read mail on this very same server and process about 500 mails per day. (Its the machine where all of my mail lists are collected.) I use T-bird, he uses LookOut. My working theory is that he (or his MUA) is somehow deleting some of his mail. Being able to read a log of his IMAP transactions would be most helpful. I see nothing about this in the Wiki. Regards, Ray

2 1