- dovecot - dovecot.org

[Dovecot] Plugin Docs (Trash)
by Timothy White 17 Jun '06

17 Jun '06

I searched, and couldn't find much in the wiki, or the mailing list... What is the trash plugin? How do we use it? I notice that none of the plugins have much documentation, other that bits on the wiki, which is getting out of date. When I get the chance, I'll make sure the wiki quota stuff, is right, and post working examples. Thanks Tim -- Linux Counter user #273956

2 1

[Dovecot] Dovecot+NFS: Copying messages causes failures (possible SIGABRT)
by Tony Kay 16 Jun '06

16 Jun '06

Environment: Dovecot 1.0beta8 Host: 64 bit Red Hat AS4 Linux (2.6.9-34.0.1) Disks: NFS netapp In the case below, the two connections were going through two separate servers sharing disks via an NFS NetApp. Here is the sequence of operations: 1. Open a connection to a folder (say mail/Trash) 2. Open a connection to another folder (say Inbox) 3. Move messages from Inbox to Trash using this sequence on Inbox: uid copy #,# "mail/Trash" uid store #,# +flags (\Deleted) check expunge 4. Next, access open connection to Trash: noop (completes OK, but does not see new messages) ...wait a few seconds... noop (connection drops...no response) Attempt to reconnect: mailbox locked. Will override in 270 seconds. The dovecot logs contain the following for the exact time when the connection drops: dovecot: IMAP(tkay): file mail-index-sync-update.c: line 686 (mail_index_sync_update_index): assertion failed: (view->hdr.messages_count == map->hdr.messages_count) I cannot correlate this to the user/folder, but this message is usually nearby: child 22915 (imap) killed with signal 6 -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Perfection uncanned Like a beautiful redhead Fresh from her trailer from Spam-Ku : Tranquil Reflections on Luncheon Loaf by John Cho

2 1

[Dovecot] check pass; user unknown in logs
by james edwards 16 Jun '06

16 Jun '06

I am seeing lots of these in my logs and there are often a hundered or so imap/dovecat process running. I am running RC Core3. Can anyone shead some light on how to correct this ? Jun 16 08:38:24 jidmail dovecot(pam_unix)[27653]: check pass; user unknown Jun 16 08:38:24 jidmail dovecot(pam_unix)[27653]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:24 jidmail dovecot(pam_unix)[27657]: check pass; user unknown Jun 16 08:38:24 jidmail dovecot(pam_unix)[27657]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:24 jidmail dovecot(pam_unix)[27658]: check pass; user unknown Jun 16 08:38:24 jidmail dovecot(pam_unix)[27658]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:26 jidmail dovecot(pam_unix)[27684]: check pass; user unknown Jun 16 08:38:26 jidmail dovecot(pam_unix)[27684]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:27 jidmail dovecot(pam_unix)[27690]: check pass; user unknown Jun 16 08:38:27 jidmail dovecot(pam_unix)[27690]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:27 jidmail dovecot(pam_unix)[27693]: check pass; user unknown Jun 16 08:38:27 jidmail dovecot(pam_unix)[27693]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:29 jidmail dovecot(pam_unix)[27712]: check pass; user unknown Jun 16 08:38:29 jidmail dovecot(pam_unix)[27712]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:30 jidmail dovecot(pam_unix)[27713]: check pass; user unknown Jun 16 08:38:30 jidmail dovecot(pam_unix)[27713]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Jun 16 08:38:30 jidmail dovecot(pam_unix)[27716]: check pass; user unknown Jun 16 08:38:30 jidmail dovecot(pam_unix)[27716]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= -- James H. Edwards Network Systems Administrator Judicial Information Division jedwards(a)nmcourts.com

1 0

[Dovecot] Problem with Dovecot LDA / Postfix
by Dominique Feyer 16 Jun '06

16 Jun '06

Our setup is ok with Postfix / Dovecot. I just need to add dovecot LDA. I use the 1.0beta9 LDA Configuration: protocol lda { postmaster_address = postmaster(a)clm.net4all.ch #hostname = #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap #sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master } auth default-socket { mechanisms = plain login passdb sql { args = /usr/local/dovecot-1.0-beta9/etc/dovecot-pgsql.conf } userdb sql { args = /usr/local/dovecot-1.0-beta8/etc/dovecot-pgsql.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } } user = dovecot count = 1 } Postfix configuration, like the dovecot LDA wiki page Master.cf: dovecot unix - n n - - pipe flags=DRhu user=mail:mail argv=/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver -d ${recipient} Main.cf default_destination_recipient_limit = 1 Log: Jun 15 19:15:43 mail2 postfix/qmgr[4226]: 31FA27FF2: from=<root(a)localhost.localdomain>, size=343, nrcpt=1 (queue active) Jun 15 19:15:43 mail2 dovecot: auth(default-socket): master in: USER^I1^Iinfo(a)lda.net4all.ch^Iservice=deliver Jun 15 19:15:43 mail2 dovecot: auth(default-socket): sql(info(a)lda.net4all.ch): SELECT '/var/spool/mail/'||home AS home, uid, gid FROM users WHERE userid = 'info(a)lda.net4all.ch' Jun 15 19:15:43 mail2 dovecot: auth(default-socket): master out: USER^I1^Iinfo@lda.net4all.ch^Ihome=/var/spool/mail/lda.net4all.ch/mails/info^Iuid=1999^Igid=1999 Jun 15 19:15:43 mail2 dovecot: auth(default-socket): Jun 15 19:15:43 mail2 postfix/pipe[4314]: 31FA27FF2: to=<info(a)lda.net4all.ch>, relay=dovecot, delay=0, status=bounced (Command died with status 89: "/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver") The status 89 is for default error ... so no more informations with this. Permision on deliver is setuid (we use a different UID per domain) mail2:/etc/dovecot# stat /usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver File: `/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver' Size: 2507575 Blocks: 4912 IO Block: 4096 fichier r�gulier Device: 805h/2053d Inode: 65010 Links: 1 Access: (6755/-rwsr-sr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2006-06-15 19:15:43.314434576 +0200 Modify: 2006-06-15 13:46:15.000000000 +0200 Change: 2006-06-15 19:18:32.821665560 +0200 Can anyone help me ? Thanks, -- Dominique Feyer Administrateur Système Ch. de la Colline 5bis CH-1007 Lausanne dfeyer(a)net4all.ch

2 2

Re: [Dovecot] Problem with Dovecot LDA / Postfix
by Dominique Feyer 16 Jun '06

16 Jun '06

I have only postfix log (in syslog mail facility), no dovecot log from the LDA deliver binary (with mail_debug = yes), this is strange ... Jun 16 14:37:58 mail2 postfix/pickup[6014]: 5407F7FF3: uid=0 from=<root> Jun 16 14:37:58 mail2 postfix/cleanup[6073]: 5407F7FF3: message-id=<20060616123758.5407F7FF3(a)mail2.clm.net4all.ch> Jun 16 14:37:58 mail2 postfix/qmgr[6015]: 5407F7FF3: from=<root(a)localhost.localdomain>, size=326, nrcpt=1 (queue active) Jun 16 14:37:58 mail2 postfix/pipe[6076]: 5407F7FF3: to=<info(a)lda.net4all.ch>, relay=dovecot, delay=0, status=bounced (Command died with status 89: "/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver") Can i activate log for the LDA in the configuration file or deliver command argument in master.cf ? Thanks Le vendredi 16 juin 2006 à 08:24 -0400, My BSD a écrit : > On Thu, 15 Jun 2006 19:18:40 +0200 > Dominique Feyer <dfeyer(a)net4all.ch> wrote: > > > Our setup is ok with Postfix / Dovecot. > > > > I just need to add dovecot LDA. > > > > I use the 1.0beta9 > > > > LDA Configuration: > > > > protocol lda { > > postmaster_address = postmaster(a)clm.net4all.ch > > #hostname = > > #mail_plugins = > > #mail_plugin_dir = /usr/lib/dovecot/imap > > #sendmail_path = /usr/lib/sendmail > > auth_socket_path = /var/run/dovecot/auth-master > > } > > auth default-socket { > > mechanisms = plain login > > passdb sql { > > args = /usr/local/dovecot-1.0-beta9/etc/dovecot-pgsql.conf > > } > > userdb sql { > > args = /usr/local/dovecot-1.0-beta8/etc/dovecot-pgsql.conf > > } > > socket listen { > > master { > > path = /var/run/dovecot/auth-master > > mode = 0660 > > user = vmail > > group = mail > > } > > } > > user = dovecot > > count = 1 > > } > > > > Postfix configuration, like the dovecot LDA wiki page > > > > Master.cf: > > dovecot unix - n n - - pipe > > flags=DRhu user=mail:mail > > argv=/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver -d > > ${recipient} > > > > Main.cf > > default_destination_recipient_limit = 1 > > > > Log: > > > > Jun 15 19:15:43 mail2 postfix/qmgr[4226]: 31FA27FF2: > > from=<root(a)localhost.localdomain>, size=343, nrcpt=1 (queue active) > > Jun 15 19:15:43 mail2 dovecot: auth(default-socket): master in: > > USER^I1^Iinfo(a)lda.net4all.ch^Iservice=deliver > > Jun 15 19:15:43 mail2 dovecot: auth(default-socket): > > sql(info(a)lda.net4all.ch): SELECT '/var/spool/mail/'||home AS home, > > uid, gid FROM users WHERE userid = 'info(a)lda.net4all.ch' > > Jun 15 19:15:43 mail2 dovecot: auth(default-socket): master out: > > USER^I1^Iinfo@lda.net4all.ch^Ihome=/var/spool/mail/lda.net4all.ch/mails/info^Iuid=1999^Igid=1999 > > Jun 15 19:15:43 mail2 dovecot: auth(default-socket): > > Jun 15 19:15:43 mail2 postfix/pipe[4314]: 31FA27FF2: > > to=<info(a)lda.net4all.ch>, relay=dovecot, delay=0, status=bounced > > (Command died with status 89: > > "/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver") > > > > The status 89 is for default error ... so no more informations with > > this. > > > > Permision on deliver is setuid (we use a different UID per domain) > > mail2:/etc/dovecot# > > stat /usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver > > File: `/usr/local/dovecot-1.0-beta9/libexec/dovecot/deliver' > > Size: 2507575 Blocks: 4912 IO Block: 4096 fichier > > r�gulier > > Device: 805h/2053d Inode: 65010 Links: 1 > > Access: (6755/-rwsr-sr-x) Uid: ( 0/ root) Gid: ( 0/ > > root) Access: 2006-06-15 19:15:43.314434576 +0200 > > Modify: 2006-06-15 13:46:15.000000000 +0200 > > Change: 2006-06-15 19:18:32.821665560 +0200 > > > > Can anyone help me ? Thanks, > > > > -- > > Dominique Feyer > > Administrateur Système > > Ch. de la Colline 5bis > > CH-1007 Lausanne > > dfeyer(a)net4all.ch > > > > > > What are the corresponding "dovecot" log entries? > > (I use exim and was finally able to get "deliver" working by studying > "dovecot" log entries.) > -- Dominique Feyer Administrateur Système Ch. de la Colline 5bis CH-1007 Lausanne dfeyer(a)net4all.ch

1 0

[Dovecot] Broken on upgrade, "Protocol not supported"
by Ryan Hinton 16 Jun '06

16 Jun '06

Hello, and thanks in advance for your help. I was having trouble with dovecot-1.0beta2 after it worked flawlessly since January. Thunderbird was complaining that dovecot was not returning proper mail server capabilities (its log seems to confirm this). I checked the dovecot site and saw a new beta (beta9) with lots of bug fixes, so I downloaded it and installed it. The configure and make ran without incident. Before running 'sudo make install' I stopped the dovecot process with a SIGTERM. I installed and tried to restart the server, but now I get the two following errors: Error: socket() failed: Protocol not supported Fatal: listen(993) failed: Protocol not supported I went back and re-configured without IPv6 support, recompiled, and reinstalled. I even rebooted, but still the same result. Any help is greatly appreciated. I am running OpenBSD 3.5 i386. <time passes...> After some printf's, I found Error: socket() failed: Protocol not supported Error: section 2 port = 993 my_ip.family = 0 so.sin.family = 0 SOCK_STREAM = 1 AF_UNIX = 1 AF_INET = 2 AF_INET6 = 24 Fatal: listen(993) failed: Protocol not supported in function net_listen(...) in src/lib/network.c. My socket programming is a little rusty, but don't we want an address family of AF_INET or AF_INET6? Moving up into src/master/main.c I found set->protocols = imap imaps set->listen_ip.family = 2 set->listen_port = 143 set->ssl_listen_ip.family = 0 set->ssl_listen_port = 993 These print statements start at line 361, right after if (set->ssl_listen_ip.family == 0 && set->ssl_listen == NULL) set->ssl_listen_ip = set->listen_ip; Is there something going wrong in resolve_ip? I'm out of time tonight trying to track this down. Hopefully someone else will have more knowledge to pinpoint the problem. Let me know if I can provide more information. OK, one more tidbit. I hard-coded set->ssl_listen_ip.family to 2 and it seems to work beautifully. My mail server is back up. Why? --- Ryan Hinton iobass(a)email.com

3 2

[Dovecot] LDAP with Active Directory
by B Hatoum 16 Jun '06

16 Jun '06

Hello, I have successfully used dovecot 1.0 Beta 9 to do SASL authentication for postfix using the unix passwd/shadow files. I need to authenticate with a windows 2003 server using active directory. My system does not support PAM (I'm using slackware) so I cannot take that route. I do not need to use dovecot for POP or IMAP at the present time and so I would like to avoid modifying my active directory schema. Dovecot seems to be communicating with the active directory server, however it is sending an authentication failure to postfix: postfix/smtpd[24540]: warning: unknown[XXX.XXX.XXX.X]: SASL LOGIN authentication failed: UxxvcmxxQ6 I don't see any messages in the log from dovecot. Here is my dovecot-ldap.conf: hosts = 192.168.1.2:389 dn = "cn=dovecot,cn=Users,dc=DOM,dc=local" dnpass = "password" auth_bind = yes ldap_version = 3 base = cn=Users,dc=DOM,dc=local deref = never scope = subtree default_pass_scheme = CRYPT user_global_uid = 900 user_global_gid = 900 Can someone point out what I am missing? I can't find documentation on this type of setup. Thanks in advance. B Hatoum

4 3

[Dovecot] fedora directory server
by Alfonso Sparano 16 Jun '06

16 Jun '06

Hi all someone is successful to use fedora directory server as an ldap server for user/password and also with the LDA? I'm testing protocol smtp: sendmail + dovecot lda + fedora directory server and also: protocol pop3 and imap: dovecot + fedora directory server Thanks a lot folks Alfonso

1 0

[Dovecot] Dovecot-auth relicensing to BSD/MIT
by Timo Sirainen 15 Jun '06

15 Jun '06

Bcc'd to everyone who have sent me patches to dovecot-auth or related code. Once in a while people ask me if Dovecot's authentication server code could be relicensed to BSD so they could use it for their project. Usually they have been other BSD-licensed open source projects which just prefer not to use LGPL code. Now there's again this company asking me to give them a bit less restrictive license (they want to link it statically to a closed source program). They'd want to move the code to a separate SASL package and create a library out of it. They want SASL client code too, so they'd apparently write it for the package as well. I've been thinking about separating the dovecot-auth to be a separate package for a while too, although only around the time when Dovecot v2.0 is released (certainly not before v1.0). So, I think changing the Dovecot-auth's license from LGPL to BSD or MIT wouldn't really hurt and it could get it more widely used. Most of Dovecot's lib/ code is already MIT-licensed, so MIT would be more consistent. But I don't think there really is any real difference between BSD and MIT, so either one is fine for me. :) Now, this mail is mostly meant for asking people who have sent me patches to dovecot-auth if they allow the license change for their patch. If not, I'll either rewrite the part of the code, or for larger code parts (eg. NTLM auth) I'll just leave it LGPL licensed but so that it can be compiled out optionally. So, bcc'd people, please reply to me which one of these you're okay with: 1) I allow license change to either BSD or MIT 2) I allow license change to BSD 3) I allow license change to MIT 4) I don't allow license change

2 2

[Dovecot] SASL AUTH LOGIN mechanism problems
by Anders Karlsson 15 Jun '06

15 Jun '06

Hi all, Have anyone had problems with Exhange 2003 servers trying to use sasl against Postfix+Dovecot SASL using the AUTH LOGIN Mechanism ? I've done some smtp debugging, and it seems that Exchange sends the usename at the same time as AUTH LOGIN i.e: AUTH LOGIN <base64_username> It then expects to be able to send the password. mech-login.c silently discards all data after AUTH LOGIN and just prompts the username prompt whetever the username has already been supplied during initial AUTH LOGIN request. I've attached a patch to make mech-login.c check if additional data has been sent along with AUTH LOGIN, and in this case skip ahead directly to the Password: prompt. Cheers Anders

2 1