- dovecot - dovecot.org

[Dovecot] Authors wanted for Linux Magazine
by Markus Feilner 25 Jun '07

25 Jun '07

Hello list, as an editor at the german linux magazine I am looking for an author who would like to write about 5-6 pages on dovecot clustering (as a workshop or presenting a detail of special interest) If you are interested, please send me an email to: <mfeilner(a)linuxnewmedia.de> Mit freundlichen Gruessen - Best Regards, Markus Feilner -- Linux New Media AG, Sueskindstr. 4, 81929 Muenchen, Germany Phone: +49 89 9934 1122, Fax: +49 89 9934 1199 mfeilner(a)linuxnewmedia.de - http://www.linuxnewmedia.de Linux New Media - The Pulse of Linux Lawrence - Malaga - Manchester - Muenchen - Sao Paulo - Timisoara - Warszawa --------------------------------------------------- Sitz der Gesellschaft: Sueskindstrasse 4, 81929 Muenchen Amtsgericht Muenchen: HRB 129161 Vorstand: Rosemarie Schuster, Hermann Plank Aufsichtsratsvorsitzender: Rudolf Strobl

1 0

[Dovecot] Dovecot and Sendmail Working Together . . .
by Eddie Johnson Jr 24 Jun '07

24 Jun '07

I am new to this, I was just given the responsibility Thursday to get Sendmail/SquirrelMail/Dovecot to work in sync. How do I start? iloadmin

2 1

Re: [Dovecot] Dovecot won't stay running
by Gunter Ohrner 22 Jun '07

22 Jun '07

Am Freitag, 22. Juni 2007 schrieb Jon Slater: > You are AWESOME!!! Thank you!!! Mh, I think this is one of the few times I read that someone was actually greatful for a "RTFM" he got... ;) > Jun 22 01:27:56 servername dovecot: Time just moved backwards by 37 > seconds. This might cause a lot of problems, so I'll just kill myself That's bad and may cause a lot of other (and more subtle) troubles than Dovecot committing suicide. I'f your' using something like "ntpdate" to periodically step the time, do not do that but run an ntp server instead which will gradually skew the clock to keep the system's time accurate. Greetings, Gunter -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I would actually distinguish between problems with compiling the kernel, and problems with the kernel after compiling. -- Karol 'sziwan' Kozimor auf der swsusp-Mailingliste +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + PGP-verschlüsselte Mails bevorzugt! + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

1 0

Re: [Dovecot] test program #2: mmaping
by Bill Boebel 22 Jun '07

22 Jun '07

On Wed, June 20, 2007 9:28 pm, Timo Sirainen <tss(a)iki.fi> said: > Attached another test program. I don't expect it to print any errors > with any OS, but I'd like to confirm it for non-Linux SMP kernels. # ./concurrency writing, page size = 4096 4: reading, page size = 4096 3: reading, page size = 4096 2: reading, page size = 4096 1: reading, page size = 4096 0: reading, page size = 4096 Red Hat ES3 (2.4.21-32.0.1.EL) athlon i386

1 0

Re: [Dovecot] Dovecot won't stay running
by Jochen Schulz 22 Jun '07

22 Jun '07

Jon Slater schrieb: > > So I got the same suggestion several times, and I upgraded to Dovecot 1.0.1. > > At 1:27am and again at 5:23am Dovecot stopped running. My cron was able to > restart the service in both instances, but how do I debug why this is > happening? Take a look at http://wiki.dovecot.org. It contains useful instructions for debugging. J.

2 1

Re: [Dovecot] Dovecot won't stay running
by Jon Slater 22 Jun '07

22 Jun '07

So I got the same suggestion several times, and I upgraded to Dovecot 1.0.1. At 1:27am and again at 5:23am Dovecot stopped running. My cron was able to restart the service in both instances, but how do I debug why this is happening? Thanks!!! Jon > -----Original Message----- > From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] > On Behalf Of Jon Slater > Sent: Thursday, June 21, 2007 5:19 PM > To: dovecot(a)dovecot.org > Subject: [Dovecot] Dovecot won't stay running > > This weekend I upgraded my OS from FC4 to FC6. At the same time I > updated > Dovecot from 0.99 to 1.0.0. > > Now, dovecot periodically shuts off. > > It will run fine for several hours then just dies. > > Right now my solution is to run a cron every 5 minutes to see if it’s > still > running, and if not, re-start it. > > I’m also having trouble finding any sort of meaningful logs to tell me > what’s going on. > > Where should I start? > > Thanks in advance! > > Jon > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: > 6/21/2007 > 1:46 PM > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: > 6/21/2007 1:46 PM > No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.4/860 - Release Date: 6/21/2007 5:53 PM

1 0

[Dovecot] Dovecot won't stay running
by Jon Slater 22 Jun '07

22 Jun '07

This weekend I upgraded my OS from FC4 to FC6. At the same time I updated Dovecot from 0.99 to 1.0.0. Now, dovecot periodically shuts off. It will run fine for several hours then just dies. Right now my solution is to run a cron every 5 minutes to see if it’s still running, and if not, re-start it. I’m also having trouble finding any sort of meaningful logs to tell me what’s going on. Where should I start? Thanks in advance! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.2/858 - Release Date: 6/21/2007 1:46 PM

1 0

Re: [Dovecot] Fwd: LDAP subtree search on AD
by Bruno Puga 22 Jun '07

22 Jun '07

Timo, I have sent this message below before but I didn't saw that it was delivered to you personal email instead to the list, I just see this now, sorry. Because I'm in a hurry I gave up using Dovecot + AD and start using Mysql as my userdb and passdb and things worked perfect until the moment. I have some doubts but I will open a new thread for this. Anyway, if you get some news about this issue I would appreciate to know, if not, that's OK. Many thanks for your help. Bruno. On 6/18/07, Bruno Puga <brpuga(a)gmail.com> wrote: > > Timo, I had set this in the dovecot.conf: > > auth_verbose = yes > auth_debug = yes > auth_debug_passwords = yes > > ########################################################### > ### My dovecot logs shows this using auth_bind = yes and userdn template > ### > > dovecot: 2007-06-17 12:35:52 Warning: Killed with signal 15 > dovecot: 2007-06-17 12:35:53 Info: Dovecot v1.0.0 starting up > dovecot: 2007-06-17 12:37:23 Info: auth(default): client in: AUTH > 1 PLAIN service=IMAP secured lip= 192.168.0.251 rip=192.168.0.251 > resp=AHRlc3RlAHRlc3Rl > dovecot: 2007-06-17 12:37:23 Info: auth(default): ldap(teste,192.168.0.251): > bind: dn=teste > dovecot: 2007-06-17 12:37:23 Info: auth(default): client out: OK > 1 user=teste > dovecot: 2007-06-17 12:37:23 Info: auth(default): master in: REQUEST > 1 31290 1 > dovecot: 2007-06-17 12:37:23 Info: auth(default): ldap(teste,192.168.0.251): > user search: base=DC=tecnicopias01,DC=com,DC=br scope=subtree > filter=(&(objectClass=organizationalPerson)(sAMAccountName=teste)) > fields=info > dovecot: 2007-06-17 12:40:23 Info: imap-login: Disconnected: Inactivity: > user=<teste>, method=PLAIN, rip=192.168.0.251 , lip=192.168.0.251, secured > > dovecot: 2007-06-17 12:52:46 Error: auth(default): ldap(teste, > 192.168.0.251): ldap_search() failed: Operations error > dovecot: 2007-06-17 12:52:46 Info: auth(default): master out: FAIL 1 > dovecot: 2007-06-17 12:52:46 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-17 13:07:46 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-17 13:22:47 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > > As we can see, first dovecot bind correct, but after it open a new > connection as showed in the ngrep output, and without bind try to make the > ldap_search, in that point AD blocks the search saying that for the new > connection opened is necessary a successful bind. > ########################################################### > > ### Now, changing for User database Lookups authenticating with krb5 ### > > dovecot: 2007-06-18 10:14:35 Info: auth(default): client in: AUTH > 1 PLAIN service=IMAP secured lip=192.168.0.251 rip= > 192.168.0.251 resp=AHRlc3RlAHRlc3Rl > dovecot: 2007-06-18 10:14:35 Info: auth(default): pam(teste,192.168.0.251): > lookup service=dovecot > dovecot: 2007-06-18 10:14:35 Info: auth(default): client out: OK > 1 user=teste > dovecot: 2007-06-18 10:14:35 Info: auth(default): master in: REQUEST > 1 32029 1 > dovecot: 2007-06-18 10:14:35 Info: auth(default): ldap(teste,192.168.0.251): > user search: base=DC=tecnicopias01,DC=com,DC=br scope=subtree > filter=(&(objectClass=organizationalPerson)(sAMAccountName=teste)) > fields=info > dovecot: 2007-06-18 10:17:35 Info: imap-login: Disconnected: Inactivity: > user=<teste>, method=PLAIN, rip=192.168.0.251 , lip=192.168.0.251, secured > > dovecot: 2007-06-18 10:29:25 Error: auth(default): ldap(teste, > 192.168.0.251): ldap_search() failed: Operations error > dovecot: 2007-06-18 10:29:25 Info: auth(default): master out: FAIL 1 > dovecot: 2007-06-18 10:29:25 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-18 10:44:26 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > dovecot: 2007-06-18 10:59:26 Error: auth(default): LDAP: ldap_result() > failed: Can't contact LDAP server > > ########################################################### > > After some time, the dovecot logs starts logging this last 3 lines saying > it "Can't contact LDAP server", and ngrep shows this: > > ########################################################### > ############# > T 192.168.0.251:49043 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:49043 [AP] > 0........a............ > ### > T 192.168.0.251:49043 -> 192.168.0.11:389 [AP] > 0....B. > ####### > T 192.168.0.251:42083 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:42083 [AP] > 0........a............ > ### > T 192.168.0.251:42083 -> 192.168.0.11:389 [AP] > 0....B. > ####### > T 192.168.0.251:52084 -> 192.168.0.11:389 [AP] > 0E...`@....1CN=postfix,CN=Users,DC=tecnicopias01,DC=com,DC=br..post123! > # > T 192.168.0.11:389 -> 192.168.0.251:52084 [AP] > 0........a............ > # > > Dovecot after a while keep trying to connect to LDAP server without any > requests being sent to server. So it keep logging this line below forever: > > LDAP: ldap_result() failed: Can't contact LDAP server > ########################################################### > > If I change the base to the same location as the user being authenticating > is, the userdb lookup is successfully because he's find at a first > ldap_seach try, and no subtree search is necessary. So again I think dovecot > must not open other connections then that opened at the bind time to make > the subtree search, like postfix do. > > Timo, I'm waiting for your reply. > > Thanks in advance to spent your time to contribute with free software, > Bruno.

1 0

[Dovecot] test program #2: mmaping
by Timo Sirainen 21 Jun '07

21 Jun '07

Attached another test program. I don't expect it to print any errors with any OS, but I'd like to confirm it for non-Linux SMP kernels. (Except for OpenBSD, it doesn't work correctly in it anyway because it doesn't support mixing write()s and mmap())

8 8

[Dovecot] Status update
by Timo Sirainen 21 Jun '07

21 Jun '07

I'm leaving soon and I'll be away until sunday. Sorry about not replying to all mails yet, most of them are somewhat tricky and require some time to reply (other than "I don't know"). The new index code for v1.1 seems to be finally working pretty nicely. After 9 hours of running imaptest I haven't gotten a single error yet. I'll leave it running until I'm back. The new code makes the internal index file design a lot easier to understand. For v1.0 I just wanted to get it working and I didn't dare try to clean up the code, so it was kind of magic sometimes why it worked. :) All that magic is finally gone and I understand completely how everything is supposed to work (and hopefully also how it does work). Most important problem with the new code is that \Recent flags are completely broken. I think they're not completely correctly working in v1.0 either, or at least I'm not sure why they're working even as well as they are now.. Maildir syncing in v1.1 is also a bit bad. For example EXPUNGE command could have to be given twice to get it to work. Again it worked badly with v1.0 also but since the index code worked differently it wasn't visible. Cydir is a pretty nice format for stress testing index code. It's really lightweight so it's practically testing only the index code. Because of it I've found a couple of race conditions in the code that existed also in v1.0 tree (v1.0.2 will fix them). My earlier stress testing with maildir never saw those problems, probably because with maildir there was a lot of other code running as well so the race condition was really unlikely to hit.

1 0

[Dovecot] pop3 creates bad index file
by Onno Molenkamp 21 Jun '07

21 Jun '07

Hi, When I use pop3 to log on to a (Maildir) mailbox that doesn't yet exist in the filesystem, the pop3 server autocreates it for me. This works. Jun 21 10:50:45 mail-04 dovecot: pop3-login: Login: user=<hwx7s(a)gqh7x.test>, method=PLAIN, rip=::ffff:192.168.42.105, lip=::ffff:192.168.42.97 Jun 21 10:50:48 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 When I log on a second time, it will complain about UIDVALIDITY that has changed, and will disconnect me: Jun 21 10:50:52 mail-04 dovecot: pop3-login: Login: user=<hwx7s(a)gqh7x.test>, method=PLAIN, rip=::ffff:192.168.42.105, lip=::ffff:192.168.42.97 Jun 21 10:50:52 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Maildir /data/mail/898/gqh7x.test/hwx7s/Maildir sync: UIDVALIDITY changed (1182415845 -> 1182415852) Jun 21 10:50:52 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Disconnected: Mailbox is in inconsistent state. top=0/0, retr=0/0, del=0/0, size=0 Jun 21 10:50:52 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Couldn't init INBOX: Internal error occurred. Refer to server log for more information. [2007-06-21 10:50:52] When I log on a third time, everything seems to work from the client side, but the server still complains: Jun 21 10:51:01 mail-04 dovecot: pop3-login: Login: user=<hwx7s(a)gqh7x.test>, method=PLAIN, rip=::ffff:192.168.42.105, lip=::ffff:192.168.42.97 Jun 21 10:51:01 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Corrupted index cache file /data/mail/898/gqh7x.test/hwx7s/Maildir/dovecot.index.cache: indexid changed Jun 21 10:51:02 mail-04 dovecot: POP3(hwx7s(a)gqh7x.test): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Fourth (and further) logons work without errors. When the Maildir is created by imap or deliver, pop3 works fine from the start. The only real difference I see with idxview between the dovecot.index created by pop3 and one created by imap is that with pop3 sync stamp is 0, and with imap it contains a timestamp. Onno

2 1

[Dovecot] mail_log plugin updates
by Timo Sirainen 21 Jun '07

21 Jun '07

It supports configuration now in devel version: # Events to log. Default is all. #mail_log_events = delete undelete expunge copy mailbox_delete # Group events within a transaction to one line. #mail_log_group_events = # Available fields: uid, box, msgid, size, vsize # size and vsize are available only for expunge and copy events. #mail_log_fields = uid box msgid size Without grouping you get pretty similar output than before: Info: copy: uid=13, dest=Trash, msgid=<20040702035043.7296C300DFC1A@asdf>, size=789 Info: delete: uid=13, msgid=<20040702035043.7296C300DFC1A@asdf> Info: expunge: uid=13, msgid=<20040702035043.7296C300DFC1A@asdf>, size=789 With mail_log_group_events=yes you get output like this: Info: copy: uids=15-17,24,26, dest=Trash, size=1534 Info: delete: uids=15-17,24,26 Info: expunge: uids=15-17,24,26, size=1534 The size is the summed size of all the messages. msgids aren't suppported. "size" means physical message size, "vsize" means the virtual size with CR+LF linefeeds. Does someone want something more?

2 2

[Dovecot] Question about pre-indexing maildirs
by David Favor 21 Jun '07

21 Jun '07

I have a situation with many users and an existing mail delivery agent. Seems like I once saw an imaptest program which I imagine might be used to pre-index maildirs. For example... - remember which users and user maildirs have changed since last pre-index - when system quiet pre-index any maildirs which have had mail delivered and no access by a mail client (using some inotify magic) If this sounds do-able, let me know where I can find an imaptest version which works with latest dovecot trunk code and the syntax for using it. Seems like I saw this once on the dovecot site. Thanks. - David -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] how do I download concurrency.c
by Stewart Dean 20 Jun '07

20 Jun '07

When I click on the link I get not found on the server. I run on a 4 way and AIX has some pretty fancy concurrency so it would be interesting. But then I'm leaving this afternoon and won't be back until Monday..... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] testing needed: log file concurrency
by Timo Sirainen 20 Jun '07

20 Jun '07

http://dovecot.org/tmp/concurrency.c I'd want to know what results this program gives with different systems. Please test and reply (but don't bother if someone already replied with the same OS+result). I expect it to print: - SMP kernels: "page size cut" once in a while - UP (uniprocessor) kernels: Nothing - The most important thing is that it never prints "broken data" It might take a while for it to print anything. With my computer it takes anything from a few seconds to a minute or so. See the file itself for compiling/running instructions. So far I've tested only with Linux 2.6.21 x86-64/SMP and a slow Solaris/Sparc/UP. If you're interested in knowing what this is about: Dovecot writes to dovecot.index.log files by first writing the transaction with its size being 0. After that it writes the 4 size bytes again (using a bit special format with all bytes ORed with 0x80). I expected that when another process is read()ing the file and it notices the size being valid (all bytes having 0x80) that the whole transaction could always be read. But looks like if the size happens to be just before a memory page boundary, it's possible that the updated size is read, but the rest of the transaction isn't.

13 18

[Dovecot] (OT) Advice on best way to collect mail from multiple domains and deliver to users via Dovecot IMAP.
by Dave Hatton 20 Jun '07

20 Jun '07

Hi Sorry if this is an inappropriate question to ask here. If it is maybe there is a better place to ask this question? I would like to collect email sent to multiple users (with previously unknown usernames) sent to multiple domains and then deliver this email to a specific set of users on my server based upon some predefined rules, with a catchall for mails that aren't caught by these rules. So as an example, I might have domains:- example.com, example.co.uk, someotherdomain.com and I'd like to say to a sender "just send a mail to anything(a)example.com". I'd like to be able to make up recipients on the fly when subscribing to a service so that I can filter mails to this address out at a later time. The method I devised when I set this up using dovecot .99 is as follows. I currently have the hosting service for the domains forwarding all email to a singular mailbox at my ISP and I user fetchmail to pop3 the mail down from this one mailbox. The mail is then passed to postfix where I use the luser_relay option to map all unknown recipients to a local address so that it doesn't get bounced. Postfix then delivers the mail via the mailbox_command to maildrop where a series of rules inspect the envelope headers and write the mail using the "to" option to an appropriate maildir for the target user. Is this a good approach? Would I be better off using dovecot LDA and sieve? Any advice or ideas would be gratefully received. Daveh

1 0

Re: [Dovecot] testing needed: log file concurrency
by Bill Boebel 20 Jun '07

20 Jun '07

On Tue, June 19, 2007 7:41 pm, Timo Sirainen <tss(a)iki.fi> said: > http://dovecot.org/tmp/concurrency.c > > I'd want to know what results this program gives with different systems. > Please test and reply (but don't bother if someone already replied with > the same OS+result). I expect it to print: ./concurrency writing, page size = 4096 ./concurrency 1 reading, page size = 4096 Red Hat ES3 (2.4.21-32.0.1.EL) athlon i386

1 0

[Dovecot] Error: net_connect(/opt/local/var/run/dovecot/auth-master) failed: No such file or directory
by J Charles Ferrari 20 Jun '07

20 Jun '07

What is auth-master, and how do I create it? Using postfix 2.1.5 dovecot 1.0.0 # /opt/local/etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot_error.log info_log_path: /var/log/dovecot.log protocols: imap pop3 ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /opt/local/libexec/dovecot/imap-login login_executable(imap): /opt/local/libexec/dovecot/imap-login login_executable(pop3): /opt/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: maildir:/var/Maildir/%u mail_debug: yes mail_executable(default): /opt/local/libexec/dovecot/imap mail_executable(imap): /opt/local/libexec/dovecot/imap mail_executable(pop3): /opt/local/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/local/lib/dovecot/imap mail_plugin_dir(imap): /opt/local/lib/dovecot/imap mail_plugin_dir(pop3): /opt/local/lib/dovecot/pop3 auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail Thanks Charles

4 3

Re: [Dovecot] dovecot Digest, Vol 50, Issue 54
by Kenny Dail 20 Jun '07

20 Jun '07

> - SMP kernels: "page size cut" once in a while does several hundred in about 4 minutes count as once in a while? Got many "page size cut" on 2.6.17-gentoo-r8 #2 SMP i686 Dual Pentium III (Katmai) no output from a FreeBSD 4.9-RELEASE-p5 single Pentium III (Katmai) -- Kenny Dail <kend(a)amigo.net>

1 0

[Dovecot] save failed to INBOX
by Erland Nylend 19 Jun '07

19 Jun '07

Hello, I'm seeing som error messages in the mail log, like this: Jun 12 12:50:44 <mail.info> smtp2 deliver(user1(a)domain.tld): msgid=<10784847.1181644475592.foo.bar@foo99>: save failed to INBOX Jun 12 12:50:44 <mail.info> smtp2 deliver(user1(a)domain.tld): msgid=<30757588.1181644556388.foo.bar@foo99>: saved mail to INBOX It seems that when two or more messages are being delivered at the same time, only one delivery succeeds. Both the maildirs and the indexes are stored on a SAN .. I'll try to read the source, to find out whether this is a locking problem. I would think that if a deliver -process finds that a maildir is locked, then it should wait, and retry? -- Erland Nylend

3 41

[Dovecot] Odd error from deliver
by Ralf Hildebrandt 19 Jun '07

19 Jun '07

I found these errors in my log today: Jun 18 01:02:11 postamt deliver(cpxxxsch): msgid=<FSL%200706180000356580.6412(a)JISCMAIL.AC.UK>: save failed to INBOX: Unknown error Jun 18 01:02:11 postamt deliver(cpxxxsch): msgid=<FSL%200706180000356580.6412(a)JISCMAIL.AC.UK>: Rejected: Unknown error Jun 18 15:37:22 postamt deliver(roxxxmy): msgid=<E1I0HPz-0002OZ-00(a)p15110889.pureserver.info>: save failed to INBOX: Unknown error Jun 18 15:37:22 postamt deliver(roxxxmy): msgid=<E1I0HPz-0002OZ-00(a)p15110889.pureserver.info>: Rejected: Unknown error This is deliver from dovecot-1.0.1 What exactly IS "Unknown error"? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Ballmer should step down in favour of Mr T, because he pity the fool who don't got high-end video cards and 4GB RAM for Vista Aero!

3 12

[Dovecot] parameters to deliver
by Bruce Bodger 19 Jun '07

19 Jun '07

Read this in the dovecot sieve wiki: "The envelope sender is taken from a Return-Path: header in the message. The envelope recipient is taken from -d option passed to deliver." Is "-d" still a valid deliver switch? When I configure postfix's main.cf like so... mailbox_command = /usr/local/libexec/dovecot/deliver -d -e ..it sqwaks with, "Jun 18 18:44:50 G518X2 deliver(-e): net_connect(/ usr/local/var/run/dovecot/auth-master) failed: No such file or directory" when configured like so... mailbox_command = /usr/local/libexec/ dovecot/deliver -e -d ${recipient} ..it burps with, "Jun 18 18:56:40 G518X2 postfix/local[19766]: 3BBC16C96E0: to=<me(a)mydomain.com>, relay=local, delay=0, status=bounced (command line usage error. Command output: Fatal: Missing destination argument )" It doesn't like... mailbox_command = /usr/local/libexec/dovecot/ deliver -e -d "$recipient" either! Is -d required any longer... and if so, how, please. B. Bodger

3 4

[Dovecot] Problem with deliver
by David Favor 19 Jun '07

19 Jun '07

Per the wiki page: http://wiki.dovecot.org/LDA Doing the following should create a Maildir directory structure in an arbitrary directory, deposit a message and create/update any dovecot indexes: mkdir /common/foo export HOME=/common/foo export PATH=/usr/libexec/dovecot:$PATH cat 1180102308.88215.4145.davidfavor.com:2,RS | deliver -f doda(a)foobar.com This gives an error "(-d user) not given" and when '-d user' given an exit code of 75 is silently returned. Let me know the correct way to test how the deliver program works. Thanks. - David -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] Outlook 2003 - Disappearing favorite folders
by Phillip T. George 18 Jun '07

18 Jun '07

Hello all, I'm having an issue with Outlook 2003, where favorite folders seem to disappear. Specifically, they are subfolders of the Inbox. The Inbox favorite folder stays there without a problem. Any clues as to what the problem may be? With the previous IMAP server (courier I believe) this wasn't a problem...so it leads me to believe that Dovecot might be the problem. I'm working with Dovecot 1.0.rc28 Thanks, Phillip

5 10

[Dovecot] v1.0.1 released
by Timo Sirainen 17 Jun '07

17 Jun '07

http://dovecot.org/releases/dovecot-1.0.1.tar.gz http://dovecot.org/releases/dovecot-1.0.1.tar.gz.sig Lots of small fixes. * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked). The expansion could have caused problems if paths contained any '%' characters. + Print Dovecot version number with dovecot -n and -a + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a fatal - Trying to start Dovecot while it's already running doesn't anymore wipe out login_dir and break the running Dovecot. - maildir: Fixed "UID larger than next_uid" errors which happened sometimes when dovecot-uidlist file didn't exist but index files did (usually because mailbox didn't have any messages when it was selected for the first time) - maildir: We violated maildir spec a bit by not having keyword characters sorted in the filename. - maildir: If we don't have write access to cur/ directory, treat the mailbox as read-only. This fixes some internal error problems with trying to use read-only maildirs. - maildir: Deleting a symlinked maildir failed with internal error. - mbox: pop3_uidl_format=%m wasn't working right - mbox: If non-filesystem quota was enabled, we could have failed with "Unexpectedly lost From-line" errors while saving new messages - mysql auth: %c didn't work. Patch by Andrey Panin - APPEND / SEARCH: If internaldate was outside valid value for time_t, we returned BAD error for APPEND and SEARCH never matched. With 64bit systems this shouldn't have happened. With 32bit systems the valid range is usually for years 1902..2037. - COPY: We sent "Hang in there.." too early sometimes and checked it too often (didn't break anything, but was slower than needed). - deliver: Postfix's sendmail binary wasn't working with mail_debug=yes - Don't corrupt ssl-parameters.dat files when running multiple Dovecot instances. - Cache compression caused dovecot.index.cache to be completely deleted with big endian CPUs if 64bit file offsets were used (default) - Fixed "(index_mail_parse_header): assertion failed" crash

5 6

Re: [Dovecot] index
by Timo Sirainen 17 Jun '07

17 Jun '07

(Ccing again the list in case someone else has similar problems) On Sun, 2007-06-17 at 20:14 +0200, Lucas -LandM- wrote: > Hi Timo, > > I patched the source and same result. We think the problem is because > everytime user access to his mailbox, dovecot do the index again. And it > consume near the 80% in iowait because, as strace shows, read all mails. The problem isn't that Dovecot indexes it. The problem is that Dovecot ISN'T indexing it. Dovecot commits changes to cache file only after a FETCH command finished successfully. So if the client is disconnected in the middle of doing the FETCH, all of the work that Dovecot did so far gets lost on Dovecot's side. And apparently your client also starts everything from the beginning, even though it already knew some of the messages' sizes.. So the previous patch I sent was supposed to prevent this because originally Dovecot was the one that disconnected the client. It logged "Disconnected for inactivity in reading our output" as the disconnect reason. This shouldn't happen anymore after you patched it, so why did the client still get disconnected? Anyway, here's another patch that makes Dovecot not forget all of its work if the client gets disconnected in the middle of FETCH: http://hg.dovecot.org/dovecot-1.0/rev/e1cd11c5e00a If the client is still disconnecting, it probably takes a couple of tries to get everything read and cached, but after that it should all work nicely. Here's a similar patch for POP3: http://hg.dovecot.org/dovecot-1.0/rev/86766f448e50

1 0

[Dovecot] subdir disappeared
by Luigi Rosa 17 Jun '07

17 Jun '07

I have an installation that sometimes acts strangely: Jun 12 11:28:00 mail dovecot: imap-login: Login: user=<nadia>, method=PLAIN, rip=10.10.10.103, lip=10.10.10.254 Jun 12 11:53:59 mail dovecot: IMAP(nadia): inotify_add_watch(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 11:53:59 mail dovecot: IMAP(nadia): stat(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 11:56:14 mail last message repeated 5 times Jun 12 11:58:14 mail last message repeated 2 times Jun 12 12:00:14 mail last message repeated 2 times Jun 12 12:02:14 mail last message repeated 2 times Jun 12 12:02:14 mail dovecot: IMAP(nadia): stat(/var/spool/mail/nadia/new) failed: No such file or directory Jun 12 12:03:23 mail dovecot: IMAP(nadia): Disconnected: Logged out ..... Jun 13 12:08:01 mail dovecot: IMAP(nadia): unlink(/var/spool/mail/nadia/cur/:2,ST) failed: Is a directory Needless to say that no modification has been made to the server for many days and the user did not complain until that time. Could it be Dovecot? Is there a way to trace this error? The MTS is Postfix and in that period the user did not receive any mail The system is a Fedora 6 2.6.20-1.2952.fc6 #1 SMP Wed May 16 17:59:13 EDT 2007 i686 i686 i386 GNU/Linux Ciao, luigi -- / +--[Luigi Rosa]-- \ You cannot achieve the impossible without attempting the absurd.

2 4

[Dovecot] 60 seconds problem
by Waheed Rahuman 17 Jun '07

17 Jun '07

I am using Dovecot-1.0-0_27.rc10.e14. And when try to login with outlook there is an error saying "You server did not respond do u want to try again in 60 seconds" Any solutions please help regards Waheed

2 1

Re: [Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 17 Jun '07

17 Jun '07

Tere. > %c expands to "secured" or empty. So you could use eg. > passdb pam { > args = %s%c > } > > and create imap, imapsecured, pop3, pop3secured > > More better, so for example user1 can access only imaps, using Yous suggestion, I have to list all users, except user1 in imap, pop3, pop3secured. But it should works also in other way, that by default all users are allowed to use all protocols and then I exclude user1 from imap, pop3, pop3secured. So I tried: passdb pam { args = %s%c } /etc/pam.d/ includes imap, imapsecured, pop3, pop3secured files which includes: auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth and only imapsecured has this line: auth required pam_listfile.so item=user sense=deny file=/etc/imapsusers onerr=succeed and /etc/imapsusers includes user1 But now even pop user can't login:(. -- Mart

2 1

[Dovecot] using 'socat' to relay Dovecot SASL's auth socket over TCP?
by snowcrash 17 Jun '07

17 Jun '07

hi, i've been running Exim & Dovecot together on the same box. Exim's been sharing Dovecot/SASL auth info over a local unix socket. works great. i'm now splitting Exim & Dovecot onto two different boxes. iiuc, Dovecot ONLY provides a UNIX (local) socket; *not* a TCP socket for over-the-network access. SUre, I could mount the Dovecot socket's volume over NFS ... but just don't want to go there. i've just discovered, socat - Multipurpose relay http://www.dest-unreach.org/socat/ "Socat is a command line based utility that establishes two bidirectional byte streams and transfers data between them. Because the streams can be constructed from a large set of different types of data sinks and sources (see address types), and because lots of address options may be applied to the streams, socat can be used for many different purposes. It might be one of the tools that one `has already needed'." which, iiuc (?), can bidirectionally bridge the Dovecot unix-socket to a TCP socket that Exim can talk/listen to. reading further, "address types" (http://www.dest-unreach.org/socat/doc/socat.html#ADDRESS_TYPES) seem to include BOTH unix & tcp sockets ... can anyone here comment further on this? known to work? possible? no way? etc etc thanks!

2 1

[Dovecot] index
by Lucas -LandM- 17 Jun '07

17 Jun '07

Hi, First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things? Thank you in advance, Lucas

4 7

Re: [Dovecot] dovecot under attack
by Dani 16 Jun '07

16 Jun '07

A Dissabte 16 Juny 2007 16:10, Jon Slater va escriure: > Hi, > > I’ve posted this before but no one was able to help. I can’t figure > out what they are trying to do, and if I should be concerned. > I am running dovecot version 0.99.14 on Fedora Core 4. It appears > that my dovecot server is under attack. This morning in my system > e-mail I saw this: Hi Jon, just my 5 cents, eventually you can figure out if they are trying to login directly to you imap/pop3 ports or maybe through a webmail? In every case why don't you give a try to a fail2ban program to block automatically login failures through iptables and of course upgrade your dovecot's installation? http://drees76.blogspot.com/2006/08/fail2ban-dovecot-and-brute-force.html greetings, dani

1 0

[Dovecot] 1st DOVECOT installation automatically quitting on login
by Benton Haynes 16 Jun '07

16 Jun '07

Hi there. I have just installed DOVECOT 1.0.1 for the first time. After launching it, I can verify that ps -ax | grep -i dovecot 1052 ?? Ss 0:00.03 /usr/local/dovecot/sbin/dovecot -c /etc/dovecot/dovecot.conf 1053 ?? S 0:00.06 dovecot-auth 1058 p2 R+ 0:00.01 grep -i dovecot ps -ax | grep -i imap 1054 ?? S 0:00.08 imap-login 1055 ?? S 0:00.08 imap-login 1056 ?? S 0:00.08 imap-login 1060 p2 R+ 0:00.01 grep -i imap Then, if I telnet to DOVECOT/IMAP & login telnet 192.168.1.30 143 Trying 192.168.1.30... Connected to 192.168.1.30. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS QUOTA STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] haynes.name IMAP4 server ready x login ben(a)haynes.name benpass x OK Logged in. Connection closed by foreign host. ^^^^^^^^^^^^^^^^^^^ It disconnects automatically. In my dovecot.conf, I currently have defined verbose_ssl = no auth_verbose = no auth_debug = yes mail_debug = no And, in dovecot.log, I get only, dovecot: Jun 15 18:51:10 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.1.30 rip=192.168.1.3resp=<hidden> dovecot: Jun 15 18:51:10 Info: auth(default): passwd-file(user= ben(a)haynes.name,192.168.1.3) lookup: user=ben(a)haynes.namefile=/etc/dovecot/user.file dovecot: Jun 15 18:51:10 Info: auth(default): client out: OK 1 user=ben(a)haynes.name dovecot: Jun 15 18:51:10 Info: auth(default): master in: REQUEST 11054 1 dovecot: Jun 15 18:51:10 Info: auth(default): master out: USER 1 ben(a)haynes.name static uid=500 gid=500 home=/var/mail/imap/haynes.name/accounts/ben nice=10 dovecot: Jun 15 18:51:10 Info: imap-login: Login: user=<user=ben(a)haynes.name>, method=PLAIN, rip=192.168.1.3, lip=192.168.1.30 dovecot: Jun 15 18:51:14 Error: child 1064 (imap) killed with signal 4 Ihaven't been able to figure out why this is happening. Is there some more detailed debugging I should turn on? Any ideas why this is going on? -- Ben

2 4

Re: [Dovecot] dovecot under attack
by Mart Pirita 16 Jun '07

16 Jun '07

Tere. > > > Does anyone know what this is? Or someone I could ask? > > Normal dictionary attack? -- Mart

1 0

Re: [Dovecot] dovecot under attack
by Charles Marcus 16 Jun '07

16 Jun '07

Hi Jon, I cannot help with the specific question, but in my opinion, your first and primary goal should be to get that server updated to 1.0.1 asap... 0.99.x is no longer supported - and *very* dated... Jon Slater wrote: > Hi, > > > > I’ve posted this before but no one was able to help. I can’t figure out > what they are trying to do, and if I should be concerned. > > > > I am running dovecot version 0.99.14 on Fedora Core 4. It appears that my > dovecot server is under attack. This morning in my system e-mail I saw > this: > > > > dovecot: > > Authentication Failures: > > rhost= : 23431 Time(s) > > adm: 33 Time(s) > > bin: 33 Time(s) > > mail: 33 Time(s) > > mysql: 21 Time(s) > > nobody: 15 Time(s) > > news: 14 Time(s) > > operator: 8 Time(s) > > sshd: 2 Time(s) > > Unknown Entries: > > check pass; user unknown: 23431 Time(s) > > > > But, when I check my log files I can’t find an IP address for the attacker. > So, for example, if I search my logs for “operator” I see: > > ./messages:Jun 15 23:30:56 lambdacenter dovecot(pam_unix)[15512]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:00 lambdacenter dovecot(pam_unix)[15670]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:16 lambdacenter dovecot(pam_unix)[16332]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:20 lambdacenter dovecot(pam_unix)[16480]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:27 lambdacenter dovecot(pam_unix)[16695]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:38 lambdacenter dovecot(pam_unix)[16884]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:31:55 lambdacenter dovecot(pam_unix)[17080]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./messages:Jun 15 23:32:11 lambdacenter dovecot(pam_unix)[17182]: > authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= > user=operator > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971858.967:156312): user > pid=15512 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971862.772:156382): user > pid=15670 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971878.710:156707): user > pid=16332 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971882.379:156775): user > pid=16480 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181971908.712:156879): user > pid=16695 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972032.080:156904): user > pid=16884 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972047.607:156917): user > pid=17080 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > ./audit/audit.log:type=USER_AUTH msg=audit(1181972066.325:156928): user > pid=17182 uid=0 auid=4294967295 msg='PAM authentication: user=operator > exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? > result=Authentication failure)' > > > > I’ve checked my snmplog for port activity on port 110 (for POP3) and 143 > (for IMAP), but I don’t see anything unusual. I also systematically > filtered out everything I knew was okay (ssh, and httpd) . > > > > Does anyone know what this is? Or someone I could ask? > > > > Thanks!!!!!!!!!!!!!!!!!!!! > > > > Jon > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 6/15/2007 > 11:31 AM > >

1 0

[Dovecot] dovecot under attack
by Jon Slater 16 Jun '07

16 Jun '07

Hi, I’ve posted this before but no one was able to help. I can’t figure out what they are trying to do, and if I should be concerned. I am running dovecot version 0.99.14 on Fedora Core 4. It appears that my dovecot server is under attack. This morning in my system e-mail I saw this: dovecot: Authentication Failures: rhost= : 23431 Time(s) adm: 33 Time(s) bin: 33 Time(s) mail: 33 Time(s) mysql: 21 Time(s) nobody: 15 Time(s) news: 14 Time(s) operator: 8 Time(s) sshd: 2 Time(s) Unknown Entries: check pass; user unknown: 23431 Time(s) But, when I check my log files I can’t find an IP address for the attacker. So, for example, if I search my logs for “operator” I see: ./messages:Jun 15 23:30:56 lambdacenter dovecot(pam_unix)[15512]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:00 lambdacenter dovecot(pam_unix)[15670]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:16 lambdacenter dovecot(pam_unix)[16332]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:20 lambdacenter dovecot(pam_unix)[16480]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:27 lambdacenter dovecot(pam_unix)[16695]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:38 lambdacenter dovecot(pam_unix)[16884]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:31:55 lambdacenter dovecot(pam_unix)[17080]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./messages:Jun 15 23:32:11 lambdacenter dovecot(pam_unix)[17182]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=operator ./audit/audit.log:type=USER_AUTH msg=audit(1181971858.967:156312): user pid=15512 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971862.772:156382): user pid=15670 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971878.710:156707): user pid=16332 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971882.379:156775): user pid=16480 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181971908.712:156879): user pid=16695 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972032.080:156904): user pid=16884 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972047.607:156917): user pid=17080 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' ./audit/audit.log:type=USER_AUTH msg=audit(1181972066.325:156928): user pid=17182 uid=0 auid=4294967295 msg='PAM authentication: user=operator exe="/usr/libexec/dovecot/dovecot-auth" (hostname=?, addr=?, terminal=? result=Authentication failure)' I’ve checked my snmplog for port activity on port 110 (for POP3) and 143 (for IMAP), but I don’t see anything unusual. I also systematically filtered out everything I knew was okay (ssh, and httpd) . Does anyone know what this is? Or someone I could ask? Thanks!!!!!!!!!!!!!!!!!!!! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.17/850 - Release Date: 6/15/2007 11:31 AM

1 0

[Dovecot] Per user based protocol access and pause after failed login?
by Mart Pirita 16 Jun '07

16 Jun '07

Hello. Tried search, no luck, sorry, if this is already answered, but I'm still looking a solution using pam_auth how to define in dovecot which user can access which protocol, for example, default is: protocols = pop3 pop3s imap imaps I'd like to use something like this: exclude_using_pop = user1, user2, @group exclude_using_pops = user1, user2, @group exclude_using_imap = user1, user2, @group exclude_using_imaps = user1, user2, @group The idea is security and also preventing imap user by accident logging in using pop3 and downloading (clearing inbox for imap) all inbox. And also some throttling, for example the adjustable time to pause access after failed login etc would be great. -- Mart

2 2

[Dovecot] SHA256 password patch
by Jasper Slits 16 Jun '07

16 Jun '07

Hi, I made a patch against branch-1.0 for SHA256 password hashing support for Dovecot. Courier Authlib supports this hashing scheme and in order to migrate from Courier to Dovecot, I've added SHA256 support to Dovecot. The attached patch is based on BSD licensed code from Olivier Gay (http://www.ouah.org/ogay/sha2/) Changes made by me in Olivier's sha2{.h,.c} code: - Prototype for sha256_transf is added to sha2.h - sha256_get_digest() is added to sha2{.h,.c} - Code for UNROLL_LOOPS is removed - Support for SHA224,SHA384,SHA512 was removed - Functions are renamed to match those in sha1{.h,.c} - SHA256_DIGEST_SIZE is renamed to SHA256_RESULTLEN I can add safe_memset calls if requested. Patch is attached and can also be found at http://www.malochia.nl/dovecot/sha256.patch Kind regards, Jasper diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/auth/password-scheme.c auth/password-scheme.c --- src/auth/password-scheme.c 2007-02-21 13:30:38.756711250 +0100 +++ auth/password-scheme.c 2007-02-21 14:18:49.645380500 +0100 @@ -10,6 +10,7 @@ #include "mycrypt.h" #include "randgen.h" #include "sha1.h" +#include "sha2.h" #include "str.h" #include "password-scheme.h" @@ -153,6 +154,17 @@ return str_c(str); } +static const char *sha256_generate(const char *plaintext, + const char *user __attr_unused__) +{ + unsigned char digest[SHA256_RESULTLEN]; + string_t *str; + sha256_get_digest(plaintext, strlen(plaintext), digest); + str = t_str_new(MAX_BASE64_ENCODED_SIZE(sizeof(digest)+1)); + base64_encode(digest, sizeof(digest), str); + return str_c(str); +} + static const void * password_decode(const char *password, unsigned int result_len) { @@ -196,6 +208,23 @@ return memcmp(sha1_digest, data, SHA1_RESULTLEN) == 0; } +static bool sha256_verify(const char *plaintext, const char *password, + const char *user) +{ + unsigned char sha256_digest[SHA256_RESULTLEN]; + const char *data; + + sha256_get_digest(plaintext, strlen(plaintext), sha256_digest); + + data = password_decode(password, SHA256_RESULTLEN); + if (data == NULL) { + i_error("sha256_verify(%s): Invalid password encoding", user); + return 0; + } + + return memcmp(sha256_digest, data, SHA256_RESULTLEN) == 0; +} + static const char *ssha_generate(const char *plaintext, const char *user __attr_unused__) { @@ -466,6 +495,7 @@ { "MD5-CRYPT", md5_crypt_verify, md5_crypt_generate }, { "SHA", sha1_verify, sha1_generate }, { "SHA1", sha1_verify, sha1_generate }, + { "SHA256", sha256_verify, sha256_generate }, { "SMD5", smd5_verify, smd5_generate }, { "SSHA", ssha_verify, ssha_generate }, { "PLAIN", plain_verify, plain_generate }, diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/Makefile.am lib/Makefile.am --- src/lib/Makefile.am 2007-02-21 13:30:38.792713500 +0100 +++ lib/Makefile.am 2007-02-21 14:21:59.437241750 +0100 @@ -73,6 +73,7 @@ sendfile-util.c \ seq-range-array.c \ sha1.c \ + sha2.c \ str.c \ str-sanitize.c \ strescape.c \ @@ -146,6 +147,7 @@ sendfile-util.h \ seq-range-array.h \ sha1.h \ + sha2.h \ str.h \ str-sanitize.h \ strescape.h \ diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/sha2.c lib/sha2.c --- src/lib/sha2.c 1970-01-01 01:00:00.000000000 +0100 +++ lib/sha2.c 2007-02-23 14:03:46.857739818 +0100 @@ -0,0 +1,257 @@ +/* + * FIPS 180-2 SHA-224/256/384/512 implementation + * Last update: 02/02/2007 + * Issue date: 04/30/2005 + * + * Copyright (C) 2005, 2007 Olivier Gay <olivier.gay(a)a3.epfl.ch> + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + +#include <string.h> + +#include "sha2.h" + +#define SHFR(x, n) (x >> n) +#define ROTR(x, n) ((x >> n) | (x << ((sizeof(x) << 3) - n))) +#define ROTL(x, n) ((x << n) | (x >> ((sizeof(x) << 3) - n))) +#define CH(x, y, z) ((x & y) ^ (~x & z)) +#define MAJ(x, y, z) ((x & y) ^ (x & z) ^ (y & z)) + +#define SHA256_F1(x) (ROTR(x, 2) ^ ROTR(x, 13) ^ ROTR(x, 22)) +#define SHA256_F2(x) (ROTR(x, 6) ^ ROTR(x, 11) ^ ROTR(x, 25)) +#define SHA256_F3(x) (ROTR(x, 7) ^ ROTR(x, 18) ^ SHFR(x, 3)) +#define SHA256_F4(x) (ROTR(x, 17) ^ ROTR(x, 19) ^ SHFR(x, 10)) + +#define UNPACK32(x, str) \ +{ \ + *((str) + 3) = (uint8) ((x) ); \ + *((str) + 2) = (uint8) ((x) >> 8); \ + *((str) + 1) = (uint8) ((x) >> 16); \ + *((str) + 0) = (uint8) ((x) >> 24); \ +} + +#define PACK32(str, x) \ +{ \ + *(x) = ((uint32) *((str) + 3) ) \ + | ((uint32) *((str) + 2) << 8) \ + | ((uint32) *((str) + 1) << 16) \ + | ((uint32) *((str) + 0) << 24); \ +} + +#define UNPACK64(x, str) \ +{ \ + *((str) + 7) = (uint8) ((x) ); \ + *((str) + 6) = (uint8) ((x) >> 8); \ + *((str) + 5) = (uint8) ((x) >> 16); \ + *((str) + 4) = (uint8) ((x) >> 24); \ + *((str) + 3) = (uint8) ((x) >> 32); \ + *((str) + 2) = (uint8) ((x) >> 40); \ + *((str) + 1) = (uint8) ((x) >> 48); \ + *((str) + 0) = (uint8) ((x) >> 56); \ +} + +#define PACK64(str, x) \ +{ \ + *(x) = ((uint64) *((str) + 7) ) \ + | ((uint64) *((str) + 6) << 8) \ + | ((uint64) *((str) + 5) << 16) \ + | ((uint64) *((str) + 4) << 24) \ + | ((uint64) *((str) + 3) << 32) \ + | ((uint64) *((str) + 2) << 40) \ + | ((uint64) *((str) + 1) << 48) \ + | ((uint64) *((str) + 0) << 56); \ +} + +/* Macros used for loops unrolling */ + +#define SHA256_SCR(i) \ +{ \ + w[i] = SHA256_F4(w[i - 2]) + w[i - 7] \ + + SHA256_F3(w[i - 15]) + w[i - 16]; \ +} + + + +uint32 sha256_h0[8] = + {0x6a09e667, 0xbb67ae85, 0x3c6ef372, 0xa54ff53a, + 0x510e527f, 0x9b05688c, 0x1f83d9ab, 0x5be0cd19}; + + +uint32 sha256_k[64] = + {0x428a2f98, 0x71374491, 0xb5c0fbcf, 0xe9b5dba5, + 0x3956c25b, 0x59f111f1, 0x923f82a4, 0xab1c5ed5, + 0xd807aa98, 0x12835b01, 0x243185be, 0x550c7dc3, + 0x72be5d74, 0x80deb1fe, 0x9bdc06a7, 0xc19bf174, + 0xe49b69c1, 0xefbe4786, 0x0fc19dc6, 0x240ca1cc, + 0x2de92c6f, 0x4a7484aa, 0x5cb0a9dc, 0x76f988da, + 0x983e5152, 0xa831c66d, 0xb00327c8, 0xbf597fc7, + 0xc6e00bf3, 0xd5a79147, 0x06ca6351, 0x14292967, + 0x27b70a85, 0x2e1b2138, 0x4d2c6dfc, 0x53380d13, + 0x650a7354, 0x766a0abb, 0x81c2c92e, 0x92722c85, + 0xa2bfe8a1, 0xa81a664b, 0xc24b8b70, 0xc76c51a3, + 0xd192e819, 0xd6990624, 0xf40e3585, 0x106aa070, + 0x19a4c116, 0x1e376c08, 0x2748774c, 0x34b0bcb5, + 0x391c0cb3, 0x4ed8aa4a, 0x5b9cca4f, 0x682e6ff3, + 0x748f82ee, 0x78a5636f, 0x84c87814, 0x8cc70208, + 0x90befffa, 0xa4506ceb, 0xbef9a3f7, 0xc67178f2}; + + +/* SHA-256 functions */ + +void sha256_transf(sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb) +{ + uint32 w[64]; + uint32 wv[8]; + uint32 t1, t2; + const unsigned char *sub_block; + int i,j; + + + for (i = 0; i < (int) block_nb; i++) { + sub_block = message + (i << 6); + + for (j = 0; j < 16; j++) { + PACK32(&sub_block[j << 2], &w[j]); + } + + for (j = 16; j < 64; j++) { + SHA256_SCR(j); + } + + for (j = 0; j < 8; j++) { + wv[j] = ctx->h[j]; + } + + for (j = 0; j < 64; j++) { + t1 = wv[7] + SHA256_F2(wv[4]) + CH(wv[4], wv[5], wv[6]) + + sha256_k[j] + w[j]; + t2 = SHA256_F1(wv[0]) + MAJ(wv[0], wv[1], wv[2]); + wv[7] = wv[6]; + wv[6] = wv[5]; + wv[5] = wv[4]; + wv[4] = wv[3] + t1; + wv[3] = wv[2]; + wv[2] = wv[1]; + wv[1] = wv[0]; + wv[0] = t1 + t2; + } + + for (j = 0; j < 8; j++) { + ctx->h[j] += wv[j]; + } + } +} + +void sha256(const unsigned char *message, unsigned int len, unsigned char *digest) +{ + sha256_ctx ctx; + + sha256_init(&ctx); + sha256_loop(&ctx, message, len); + sha256_result(&ctx, digest); +} + +void sha256_init(sha256_ctx *ctx) +{ + int i; + for (i = 0; i < 8; i++) { + ctx->h[i] = sha256_h0[i]; + } + + ctx->len = 0; + ctx->tot_len = 0; +} + +void sha256_loop(sha256_ctx *ctx, const unsigned char *message, + unsigned int len) +{ + unsigned int block_nb; + unsigned int new_len, rem_len, tmp_len; + const unsigned char *shifted_message; + + tmp_len = SHA256_BLOCK_SIZE - ctx->len; + rem_len = len < tmp_len ? len : tmp_len; + + memcpy(&ctx->block[ctx->len], message, rem_len); + + if (ctx->len + len < SHA256_BLOCK_SIZE) { + ctx->len += len; + return; + } + + new_len = len - rem_len; + block_nb = new_len / SHA256_BLOCK_SIZE; + + shifted_message = message + rem_len; + + sha256_transf(ctx, ctx->block, 1); + sha256_transf(ctx, shifted_message, block_nb); + + rem_len = new_len % SHA256_BLOCK_SIZE; + + memcpy(ctx->block, &shifted_message[block_nb << 6], + rem_len); + + ctx->len = rem_len; + ctx->tot_len += (block_nb + 1) << 6; +} + +void sha256_result(sha256_ctx *ctx, unsigned char *digest) +{ + unsigned int block_nb; + unsigned int pm_len; + unsigned int len_b; + int i; + + block_nb = (1 + ((SHA256_BLOCK_SIZE - 9) + < (ctx->len % SHA256_BLOCK_SIZE))); + + len_b = (ctx->tot_len + ctx->len) << 3; + pm_len = block_nb << 6; + + memset(ctx->block + ctx->len, 0, pm_len - ctx->len); + ctx->block[ctx->len] = 0x80; + UNPACK32(len_b, ctx->block + pm_len - 4); + + sha256_transf(ctx, ctx->block, block_nb); + + for (i = 0 ; i < 8; i++) { + UNPACK32(ctx->h[i], &digest[i << 2]); + } +} + +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]) +{ + sha256_ctx ctx; + + sha256_init(&ctx); + sha256_loop(&ctx, data, size); + sha256_result(&ctx, result); +} + diff -r -u -N --exclude=Makefile.in --exclude=.deps --exclude=Makefile src/lib/sha2.h lib/sha2.h --- src/lib/sha2.h 1970-01-01 01:00:00.000000000 +0100 +++ lib/sha2.h 2007-02-23 14:22:32.952116316 +0100 @@ -0,0 +1,72 @@ +/* + * FIPS 180-2 SHA-224/256/384/512 implementation + * Last update: 02/02/2007 + * Issue date: 04/30/2005 + * + * Copyright (C) 2005, 2007 Olivier Gay <olivier.gay(a)a3.epfl.ch> + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the project nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + */ + +#ifndef SHA2_H +#define SHA2_H + +#define SHA256_RESULTLEN ( 256 / 8) + +#define SHA256_BLOCK_SIZE ( 512 / 8) + +#ifndef SHA2_TYPES +#define SHA2_TYPES +typedef unsigned char uint8; +typedef unsigned int uint32; +typedef unsigned long long uint64; +#endif + + +typedef struct { + unsigned int tot_len; + unsigned int len; + unsigned char block[2 * SHA256_BLOCK_SIZE]; + uint32 h[8]; +} sha256_ctx; + +void sha256_transf(sha256_ctx *ctx, const unsigned char *message, + unsigned int block_nb); + + +void sha256_init(sha256_ctx * ctx); +void sha256_loop(sha256_ctx *ctx, const unsigned char *message, + unsigned int len); +void sha256_result(sha256_ctx *ctx, unsigned char *digest); +void sha256(const unsigned char *message, unsigned int len, + unsigned char *digest); +void sha256_get_digest(const void *data, size_t size, + unsigned char result[SHA256_RESULTLEN]); + + + +#endif /* !SHA2_H */ +

3 2

[Dovecot] SEGV with Dovecot v1.0.0 Deliver and cmusieve v1.0.1 and vacation
by Steffen Kaiser 16 Jun '07

16 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a small Sieve script that tries to use vacation that segfaults. The script is the one from http://wiki.dovecot.org/LDA/Sieve. When I change the email address (I changed the local part into "skai"), hence, vacation is skipped, the mail is delivered without any problem. ==== script start require ["fileinto", "vacation"]; # Move spam to spam folder if exists "X-Spam-Flag" { fileinto "spam"; # Stop here so that we do not reply on spams stop; } vacation # Reply at most once a day to a same sender :days 1 :subject "Out of office reply" # List of allowed recipient addresses from auto reply should be sent. :addresses ["ska(a)ux-2s11-9.inf.fh-bonn-rhein-sieg.de"] "I'm out of office, please contact Joan Doe instead. Best regards John Doe"; ========== END ========== Out of sieved .dovecot.sievec Sievecode version 3 4: IF (ends at 13)exists{11}X-Spam-Flag 13:JUMP 20 19: FILEINTO {4}spam 19: STOP 20: VACATION {39}ska(a)ux-2s11-9.inf.fh-bonn-rhein-sieg.de 40 SUBJ({19}Out of office reply) 60 MESG({73}I'm out of office, please contact Joan Doe instead. Best regards John Doe) DAYS(1) MIME(0) full len is: 62 ========== END gdb output: Core was generated by `/usr/local/dovecot/libexec/dovecot/deliver'. Program terminated with signal 11, Segmentation fault. #0 0xb7eef3a3 in strlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt full #0 0xb7eef3a3 in strlen () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #1 0xb7e2bcf3 in sieve_execute_bytecode (bc=0x80e3eb0, interp=0x80e3de8, script_context=0xbfb57800, message_context=0xbfb577c4) at script.c:398 hash = "\000\000\000\000¸Z0F\000\000\000\000¸Z0F" actions = (action_list_t *) 0x80e3850 notify_list = (notify_list_t *) 0x80e3830 actions_string = "Action(s) taken:\n", '\0' <repeats 4078 times> errmsg = 0x0 imapflags = {flag = 0x0, nflags = 0} #2 0xb7e1eb2c in cmu_sieve_run (storage=0x80d0a20, mail=0x80e03c8, script_path=0x80cbc48 "/home/ska/.dovecot.sieve", username=0x80cb030 "ska", mailbox=0x80bae92 "INBOX") at sieve-cmu.c:573 fd = <value optimized out> interp = (sieve_interp_t *) 0x80e3de8 bytecode = (sieve_bytecode_t *) 0x80e3eb0 sdata = {username = 0x80cb030 "ska", storage = 0x80d0a20, errors = 0x0} mdata = {mail = 0x80e03c8, mailbox = 0x80bae92 "INBOX", id = 0x80e4860 "<200704260754.l3Q7sWdu002894(a)ux-2s11-9.inf.fh-bonn-rhein-sieg.de>", return_path = 0x0, authuser = 0x80cb030 "ska", temp = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}} compiled_path = 0x80cbc68 "/home/ska/.dovecot.sievec" path = 0xb7fb0ff4 "<Í\022" ret = <value optimized out> #3 0xb7e1da72 in cmusieve_deliver_mail (storage=0x80d0a20, mail=0x80e03c8, username=0x80cb030 "ska", mailbox=0x80bae92 "INBOX") at cmusieve-plugin.c:72 script_path = 0x80cbc48 "/home/ska/.dovecot.sieve" #4 0x08057536 in main (argc=Cannot access memory at address 0x0 ) at deliver.c:679 tab = (struct var_expand_table *) 0x80cb068 config_path = 0x80bb79c "/usr/local/dovecot/etc/dovecot.conf" envelope_sender = 0x80bae98 "MAILER-DAEMON" mailbox = 0x80bae92 "INBOX" auth_socket = <value optimized out> home = <value optimized out> destination = 0x80cb030 "ska" user = 0x80cb030 "ska" mail_env = <value optimized out> flags = 1025 lock_method = MAIL_STORAGE_LOCK_FCNTL storage = (struct mail_storage *) 0x80d0a20 mbox_storage = (struct mail_storage *) 0x80d2d48 box = (struct mailbox *) 0x80dcc88 input = (struct istream *) 0x80d4044 t = (struct mailbox_transaction_context *) 0x80de2a0 mail = (struct mail *) 0x80e03c8 process_euid = 30000 i = 63 ret = <value optimized out> (gdb) - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRjBdji9SORjhbDpvAQICoggAnzLxTlL8mDonntaDvwr/4JN6eWPIAm7o XP6hSw9JlbTsPY55keQMZpN/UNB/FXojcqI6lD4f/2dJqCEHmeB40NQZEMUN+f60 6+BHkE6vb2sMnXa09eQWg2d5zVKp6bHdSsbtzmWIsYX0stUFMncFTJVQgatHstDm DaSGMf6V2SwiPst/0tUbeTMqYhud9LU2YLhU3+T9AuTmcSGztohnJPGnqC1GLP+N m+KLbLF6B7ZMQ2RX+M+arzz8EQRHZ2622aqiLKoT+rVZ8LkLPzp4Whd9HK1MqMld KSjJuZBKgKuJr61SGqPboPOip635DgJH7g2BKgGnOHWvJf6E7U+Q9A== =1M3a -----END PGP SIGNATURE-----

3 3

[Dovecot] auth process(es)
by Thomas Hummel 16 Jun '07

16 Jun '07

Hello Timo, I've got some questions about dovecot-auth processes which I cannot answer just by reading the doc : [ Note : my problem is that I often see dovecot: pop3-login: Can't connect to auth server at default: Connection refused and I'm looking for a way to tweak dovecot.conf parameters to allow more login <-> auth connections ] - I'm not sure I get the auth worker process concept right : is there a master dovecot-auth which listens to new incoming connections from login processes and fork/exec the real job of authenticating against the pass/userdbs to a child, called an auth worker ? - is it safe to increment the number of auth processes (the 'count' parameter in the auth block (auth_default { ...} for instance) ? - my understanding is that login processes communicate with auth processes through a unix type socket (named 'default') : can I create a second auth block in dovecot.conf (for instance 'aut extra {...}') in addition to the existing 'auth default {...}' one ? would it create an second unix socket and thus allowing a heavier login processes load ? what would be the difference between that and, say, changing the 'count' parameter to '2' in the 'auth default' section ? thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 5

[Dovecot] different configurations for individual user
by Joshua C.S. Chen 16 Jun '07

16 Jun '07

Hi everyone, I am planning to upgrade my current uw-imap to dovecot. I am using Linux (Redhat EL 4). The main purpose is to use maildir instead of mbox. For some reason, I don't want to upgrade all users' mail boxes all at a time, but I want to change the imap server first (to dovecot), while keeping all mbox files, then convert them to maildir user by user (one user at a time). My question is: Is it possible that dovecot can setup individual user's own configuration? so that some users can setup mail_location = mbox but others = maildir. Thanks in advance Joshua

2 1

[Dovecot] LDAP subtree search on AD
by Bruno Puga 16 Jun '07

16 Jun '07

Hello people! I'm new to the list and to dovecot too. In advance I'd like to thank everybody who could help me, and I'll be very glad if a could help somebody here. I'm working in a project to integrate dovecot and active directory authentication for 2 weeks without total success. I've tried so many waysto solve my problem, but no one gave me the right answer. I'll appreciate if someone could help me. First off all let me show some needed data. Distro: Debian Etch dovecot --version 1.0.0 dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot-imapd.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login mail_debug: yes imap_client_workarounds: outlook-idle delay-newmail auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam args: dovecot userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail /etc/dovecot/dovecot-ldap.conf hosts = 192.168.0.11 dn = cn=dovecot,cn=Users,dc=tecnicopias01,dc=com,dc=br dnpass = password ldap_version = 3 auth_bind = yes base = DC=tecnicopias01,DC=com,DC=br deref = never scope = subtree user_attrs = info=mail user_filter = (&(objectClass=organizationalPerson)(sAMAccountName=%u)) user_global_uid = 5000 user_global_gid = 5000 I can authenticate using pam+krb5 with success, but when I try to make a userdb search to get maillocation for the authenticated user, I get in trouble. The ldap_search doesn't make subtree search, making only onelevel search. So, if I point the base directive (/etc/dovecot/dovecot-ldap.conf) to where the user that is authenticating in that moment is, I can perfect login and get the maillocation. My question is: Why dovecot doesn't make ldap subtree search? Or, am I missing anything? Thanks Bruno.

2 5

[Dovecot] Looking for plugin docs
by Rajkumar S 16 Jun '07

16 Jun '07

Hello all, I had gone through the wiki, but could not find any page about writing new plugins. Any pointers towards plugin api/docs will be very helpful. with warm regards, raj

3 14

Re: [Dovecot] auth process(es)
by Kenny Dail 15 Jun '07

15 Jun '07

> > - is it safe to increment the number of auth processes (the 'count' > > parameter in the auth block (auth_default { ...} for instance) ? > > Should be. > > > - my understanding is that login processes communicate with auth > > processes through a unix type socket (named 'default') : > > > > can I create a second auth block in dovecot.conf (for instance > > 'aut extra {...}') in addition to the existing 'auth default {...}' > > one ? would it create an second unix socket and thus allowing a heavier > > login processes load ? > > > > what would be the difference between that and, say, changing the > > 'count' parameter to '2' in the 'auth default' section ? > > Increasing count allows heavier load, because there are then more > processes listening for incoming connections in the same socket. Actually increasing the count doesn't work. At least not for me on 1.0.0: Jun 14 12:28:39 mail5 dovecot: Dovecot v1.0.0 starting up Jun 14 12:28:39 mail5 dovecot: Auth process died too early - shutting down Jun 14 12:28:39 mail5 dovecot: child 19080 (auth) returned error 89 Jun 14 12:28:39 mail5 dovecot: auth(default): Socket already exists: /var/run/dovecot/auth-client -- Kenny Dail <kend(a)amigo.net>

3 2

[Dovecot] shared folders
by T. Horsnell 14 Jun '07

14 Jun '07

A number of our users would greatly benefit from truly shareable mail folders. I know we can bodge this with symlinks, but mailbox corruptions seem to occur when simultaneous updates are made, but this may be a client issue I guess. So I wonder if true shareability is creeping up the agenda. By true shareability, I mean such that if two users have the same folder open and one of them makes a modification to it, the display of that folder on the other user's screen immediately reflects that change. I guess this may well require a co-operating client... Cheers, Terry --

2 1

[Dovecot] postfix+dovecot delivering to wrong (/var/mail/%u) place
by Tom Lobato 14 Jun '07

14 Jun '07

(Dovecot 1.0.rc15) Hello I'm tring to configure postfix+dovecot on debian etch. In dovecot I use passdb pam and userdb passwd-file. I can connect pop3 clients and reveice mails and connect smtp clients and send mails, but it is delivered to /var/mail/%u instead the configured mailboxes in /var/local/dovecot/%u. I`ve configured postfix as say http://wiki.dovecot.org/LDA/Postfix. /etc/postfix/main.cf: ----------------------------------- smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no append_dot_mydomain = no myhostname = coan alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = coan.com.br myorigin = /etc/mailname relayhost = mynetworks = 121.120.0.0/16 mailbox_size_limit = 0 inet_interfaces = all smtpd_recipient_restrictions = reject_unauth_destination virtual_transport = dovecot dovecot_destination_recipient_limit = 1 ----------------------------------- belong master.cf. Below the syslog when I send mail via smtp... /var/log/syslog: -------------------------------- postfix/smtpd[16656]: connect from 201-95-99-135.dsl.telesp.net.br[201.95.99.135] postfix/smtpd[16656]: C76F948E3D7: client=201-95-99-135.dsl.telesp.net.br[201.95.99.135] postfix/cleanup[16660]: C76F948E3D7: message-id=<1181769218.7844.6.camel@mobile> postfix/qmgr[16653]: C76F948E3D7: from=<tom(a)coan.com.br>, size=457, nrcpt=1 (queue active) postfix/local[16661]: C76F948E3D7: to=<tom(a)coan.com.br>, relay=local, delay=0.52, delays=0.45/0.01/0/0.07, dsn=2.0.0, status=sent (delivered to mailbox) postfix/qmgr[16653]: C76F948E3D7: removed postfix/smtpd[16656]: disconnect from 201-95-99-135.dsl.telesp.net.br[201.95.99.135] ------------------------------- If I change 'virtual_transport = dovecot' to 'local_transport = dovecot', syslog output changes relay-local to relay=dovecot, but bounces the mail saying 'passwd-file(tom(a)coan.com.br): unknown user'. However I'm sure that the user is in the passwd-file and dovecot has permissions to read it. Can you give some hints about what can be happening? Dovecot conf: ----------------------- # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login mail_extra_groups: mail mailboxes mail_location: maildir:/var/local/dovecot/%u mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 pop3_uidl_format: %v.%u auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd-file args: /etc/mailsystem/userdb socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 438 ----------------------- Thank you Tom Lobato

1 1

[Dovecot] How do I test new code?
by Stewart Dean 14 Jun '07

14 Jun '07

I know how to run a second instance of the *base* code (to check different functionality/config) and documented it in http://wiki.dovecot.org/RunningDovecot What I realize I don't know how to do is to run an altogether different version or build of the code as that second instance, which would be good to have to check out upgrades before they go into production. While I could do a build in the regular fashion and put DC somewhere else or name it something else, so I could invoke this different code, presumably that different code will still look for the subsidiary executables in the usual place. Do I have to change the DESTDIR parm when doing the make install or some such? I do realize that, just as I did with running a second instance of the *same* code, I'd have to change the config file, have a separate /var/run directory...... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] errors in dovecot-uidlist
by Erland Nylend 14 Jun '07

14 Jun '07

We have migrated a mailsystem to postfix/dovecot, using the courier migrate script, and we have run into a problem with dovecot-uidlist. The messages are not listed in the correct order .. This is an example dovecot-uidlist -file: 1 1177585200 49 22 1179084774.P7191Q0M321163.webmail1,S=8245:2,S 24 1179377823.P15932Q0M835219.smtp1,S=3462:2,S 25 1179668346.P23942Q0M941365.webmail1,S=4820357:2,S 31 1179864561.P22903Q0M433768.smtp2,S=3306:2,S 34 1180344355.P25491Q0M17232.smtp2,S=5111:2,S 35 1180454170.P14932Q0M841649.smtp2,S=2024:2, 36 1168867750.H82058P20971.smtp1:2,SR 37 1170339716.H537368P4032.smtp1:2,S 38 1171291025.H352867P8785.smtp2:2,SR 39 1171357049.H141820P2105.smtp1:2,SR 40 1171460195.H933928P14324.smtp1:2,SR 41 1171616121.H812220P27503.smtp2:2,SR 42 1171872919.H950768P16201.smtp1:2,S 43 1173694618.H330094P23347.smtp1:2,S 44 1175238705.H589518P693.smtp1:2,SR 45 1176800600.H716261P10514.smtp1:2,SR 46 1177615732.H355340P10418.webmail1:2,SR 47 1180471524.P30985Q0M109430.smtp2,S=16621 48 1180597849.P8169Q0M990486.smtp1,S=33326 As you can see, the unix timestamps are descending between uid 35 and uid 36 .. and this causes problems if we intend to make webmail access the messages through imap. (it expects to receive the messages sorted by when they were received) Is there any way I can sort the list accourding to the unix timestamps, and still make it transparent to the pop3/imap clients? I would prefer a solution that does not involve users downloading allready downloaded messages via pop3. -- Erland Nylend

2 3

[Dovecot] 1.0.1 release candidate 3
by Timo Sirainen 14 Jun '07

14 Jun '07

http://dovecot.org/tmp/dovecot-1.0.1rc3.tar.gz Looks like I managed to do a lot of changes today. So I'll wait a few more days before v1.0.1 release. The important changes since rc2: + deliver: Added -e parameter to write rejection error to stderr and exit with EX_NOPERM instead of sending the rejection by executing sendmail. + dovecot --log-error logs now a warning, an error and a fatal - APPEND / SEARCH: If internaldate was outside valid value for time_t, we returned BAD error for APPEND and SEARCH never matched. With 64bit systems this shouldn't have happened. With 32bit systems the valid range is usually for years 1902..2037. See ChangeLog for more.

8 9

[Dovecot] Updating Folders in Mail box
by Wade Smart 13 Jun '07

13 Jun '07

Im looking on the dovecot documentation about how to update the folder structure. I had some computer problems so I back up my mail and when I reinstalled I got rid of a bunch of unused old mail. But now when I open my mail client it still things all of those folders are still there. Im looking for how to update the file on what is and isnt there. wade

5 5

[Dovecot] Domain part / auth_username_format
by Robert Coup 13 Jun '07

13 Jun '07

Hey folks, I want to authenticate a pop3 user without a domain part and then use the domain part to specify a Maildir subfolder to grab messages from. So, this was my attempt: # use the domain part to access a subfolder mail_location = maildir:/mail/%n/Maildir/%d # strip of the domain part for authentication purposes auth_username_format = %n login: testuser@.INBOX.SubFolder Authentication of testuser works great, but mail_debug shows me that the domain-part (%d) is empty when expanding mail_location. Any bright ideas? Rob :) [ Dovecot 1.0.rc15, Debian Sarge, PAM auth. ]

2 2

[Dovecot] No auto-conversion of .customflags?
by Christian Balzer 13 Jun '07

13 Jun '07

Hello, I'm in the process of migrating 0.99 dovecot maildir boxes to a pair of new machine. These servers were running the stable (etch) 1.0rc15 package of dovecot until yesterday and existing .customflags files were correctly converted to dovecot-keywords. Yesterday I upgraded to the (finally, thanks to who did this) 1.0.0 etch backports package and since then freshly migrated boxes get this error: --- Jun 12 09:48:06 mb11 dovecot: IMAP(username): stat(/longandboringpath/username/.customflags/cur) failed: Not a directory --- Firstly, I thought Linux was one of the OS' that had a free dir stat, but I guess I could have just hallucinated that. But more importantly, obviously .customflags does NOT get converted anymore and thus shows up in IMAP LIST commands. Since I doubt that the backport people did change anything in the code I suppose that this is a genuine 1.0.0 problem which probably should be addressed for the upcoming 1.0.1 release. Regards, Christian -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

2 3

[Dovecot] 1.0.1 release candidate 2
by Timo Sirainen 13 Jun '07

13 Jun '07

I'll release v1.0.1 in a day or two, but it would be nice to get some testing before the release to see if I managed to break something after the Mercurial conversion. And did I forget something that should be fixed for v1.0.1? http://dovecot.org/tmp/dovecot-1.0.1rc2.tar.gz Changes since v1.0.0: * deliver: If Return-Path doesn't contain user and domain, don't try to bounce the mail (this is how it was supposed to work earlier too) * deliver: %variables in mail setting coming from userdb aren't expanded anymore (again how it should have worked). The expansion could have caused problems if paths contained any '%' characters. + Print Dovecot version number with dovecot -n and -a - Trying to start Dovecot while it's already running doesn't anymore wipe out login_dir and break the running Dovecot. - maildir: Fixed "UID larger than next_uid" errors which happened sometimes when dovecot-uidlist file didn't exist but index files did (usually because mailbox didn't have any messages when it was selected for the first time) - maildir: We violated maildir spec a bit by not having keyword characters sorted in the filename. - maildir: If we don't have write access to cur/ directory, treat the mailbox as read-only. This fixes some internal error problems with trying to use read-only maildirs. - maildir: Deleting a symlinked maildir failed with internal error. - mbox: pop3_uidl_format=%m wasn't working right - mbox: If non-filesystem quota was enabled, we could have failed with "Unexpectedly lost From-line" errors while saving new messages - mysql auth: %c didn't work. Patch by Andrey Panin - COPY: We sent "Hang in there.." too early sometimes and checked it too often (didn't break anything, but was slower than needed). - deliver: Postfix's sendmail binary wasn't working with mail_debug=yes - Don't corrupt ssl-parameters.dat files when running multiple Dovecot instances. - Cache compression caused dovecot.index.cache to be completely deleted with big endian CPUs if 64bit file offsets were used (default) - Fixed "(index_mail_parse_header): assertion failed" crash

5 12

[Dovecot] Help with new syslog errmsgs
by Stewart Dean 12 Jun '07

12 Jun '07

I am bringing more people onto Dovecot...and am beginning to see syslog error messages I've never seen before...what are they/are they critical? 1 =========================== > Jun 12 09:53:21 mercury mail:err|error dovecot: IMAP(gregory): Corrupted index c > ache file /var/dcndx/gregory/.imap/INBOX/dovecot.index.cache: indexid changed This has the same date stamp as the user's change date on his .subscriptions...which he created by copying his UWIMAP .mailboxlist from a login prompt. Is this what happens when the user with active sessions overwrites/creates the .subscriptions file? 2 =========================== > Jun 12 11:32:36 mercury mail:err|error dovecot: IMAP(gregory): UIDVALIDITY chang > ed (1100532544 -> 1178155834) in mbox file /home/hcrc/gregory/mail/Sent Have no idea what this is about...... -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2

[Dovecot] Phantom message using mixed namespaces
by Ian R. Justman 12 Jun '07

12 Jun '07

Hi, all. At home, I have a mailbox where mbox is the default (for inbox and some smaller mailboxes) and all my lists are in a Maildir format. I'm building a mailstore server at work where I want to use Maildir as the default mailstore, but I want to keep mbox on the side to aid in archiving messages. My configs are as follows for mail location and namespaces: Home: mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace private { separator = / inbox = yes hidden = no prefix = "mbox/" location = mbox:~/mail:INBOX=/var/mail/%u } namespace private { separator = / prefix = "Maildir/" location = maildir:~/Maildir } Work: mail_location = maildir:~/Maildir namespace private { separator = / inbox = yes prefix = "Maildir/" location = maildir:~/Maildir } namespace private { separator = / hidden = no prefix = "mbox/" location = mbox:~/mail } Here's the thing: My home mailbox server looks the way it should, offering me "mbox" and "Maildir" names to expand for more mailboxes. Work on the other hand, by and large, works as well (in fact, I based its config on the home machine's config with some slight changes). However, strange things started happening the moment I did a "mkdir ~/mail" while I was at the machine's prompt to make ready for an mbox repository. My mail program nearly immediately shows a "phantom message" in the main inbox. If I try to select this "phantom message", the mailer goes into a very tight loop (I've tried this with Seamonkey and T'bird with the same results. I get cycles of these in the log: Jun 12 11:29:14 (censored) dovecot: imap-login: Login: user=<xxxx>, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y Jun 12 11:29:14 (censored) dovecot: IMAP(xxx): FETCH for mailbox INBOX UID 3 got too little data: 0 vs 512 Jun 12 11:29:14 (censored) dovecot: IMAP(xxxx): Disconnected: Disconnected I'm running the Dovecot 1.0.0 under FreeBSD 4.11 (work) (I can't run anything later on this machine, strangely enough; I haven't tried any of the later releases since updating the BIOS recently, however) and 1.0.rc17 under Ubuntu Feisty (home). If I need to provide more info, please let me know. I'd also be interested to know if it's something dumb I'm doing or if it perhaps may be a bug. Thanks! --Ian.

2 2

[Dovecot] New experimental XEXEC plugin status
by Marc Perkel 12 Jun '07

12 Jun '07

No to long ago I proposed an experimental extension to the IMAP protocol to allow IMAP to execute extername server side code and talk to email plugins to create custom client/server applications over an existing authenticated IMAP connection. I am happy to say they we have working code. It's not quite ready to download yet but we do have some life happening. I have started to document it on the Dovecot wiki here. http://wiki.dovecot.org/Plugins/xexec I'm looking to see if I can generate some interest in this. XEXEC Plugin XEXEC is an experimental non-standard extension to the IMAP protocol that allows you to run and server side application and have it communicate with email plugins (Thunderbird) allowing custom client/server applications to communicate over an existing authenticated IMAP channel. The email client sends the XEXEC command with the name of the server side module that it wishes to run along with parameters to pass to the server. Here are some examples: XEXEC blacklist add joe(a)example.com XEXEC whitelist del joe(a)example.com XEXEC changepassword MyNewPassword XEXEC forwardmail myaccount(a)yahoo.com Uses for XEXEC The XEXEC can be used to run anything but in theory it should be used for client server applications that relate to email or groupware applications like calendars and contact lists. Its main purpose is to allow email clients to set server side settings over the existing authenticated channel without having the user have to log in separately using a different application to control user settings. Examples of possible usage includes: * Setting server side white lists and black lists * Changing the password for the email account * Allowing users to set email forwarding preferences * Allowing users to set vacation messages * Allowing users to exclude email from specific countries or language character sets * Allowing users to control server side spam filter settings * Server Side Calendar and Group Contact Applications like MS Exchange has * SMTP over IMAP for sending outgoing email without separate SMTP settings * Setting rules for server side folder delivery. * Setting text message alerts to cell phones for important email notification Wouldn't it be nice if you could change your email password i your email client and have it set the new password on the server at the same time? This would eliminate the need to change the server and client passwords separately. Or imagine sending outgoing email without having to configure SMTP. You just set up the incoming email and the outgoing email works as well. Or wouldn't you like to do some of the fancy tricks that Microsoft Exchange Servers do without having to use Exchange? It is our hope that this experimental protocol will lead to significant expansion of IMAP functionality. About this Plugin This plugin is the idea of Marc Perkel of Junk Email Filter <http://www.junkemailfilter.com> who hired Nicolas Boullis ( nicolas.boullis(a)free.fr <mailto:nicolas.boullis@free.fr>) to write the code. I (Marc Perkel marc(a)perkel.com <mailto:marc@perkel.com>) am trying to get the concept out there in some sort of working form with the idea that it will catch on. Hopefully other people who find this concept useful will build on the idea, do it right, and perhaps some variation of this concept will eventually become a standard. Status This plugin is a nonstandard experimental extension to the IMAP protocol. It is offered as a proof of concept and it is my hope that it will catch on in some form and make it into the IMAP officially. At this point there is nothing on the client side to talk to anything on the server side. So this code is presently useless until more development is done. Configuration To activate and configure this plugin you have to first add it to your dovecot.conf file. You can do so as follows: protocol imap { mail_plugins = xexec } Then to add applications you specify the module name and map it to a server side executable program. xexec = module:executable Here are some examples: plugin { xexec = blacklist:/usr/local/dovecot/blacklist.sh %u xexec2 = whitelist:/usr/local/dovecot/whitelist.sh %u xexec3 = average:/usr/local/dovecot/average xexec4 = smtp:/usr/local/dovecot/smtp } The idea is that the module name will be a reference to an executable and will hide what is happening on the server. When the command XEXEC module <parameters> is passed then the server will run the executable and pass the parameters to the executable. Interacting with XEXEC A typical session with XEXEC might look like this. * OK Dovecot ready. 001 login marc(a)perkel.com password 001 OK Logged in. 002 xexec blacklist add joe(a)example.com * OK Adding joe(a)example.com to server side blacklist for marc(a)perkel.com 002 OK command exited successfully 003 xexec changepassword MyNewPassword * OK New Password set Sucessfully for marc(a)perkel.com 003 OK command exited successfully Many of the details of how everything will work under different conditions have yet to be developed. Download and Installation Coming Soon! License This software and the concepts behind is are free. No patent or copyrights are asserted on the concept. This is a gift to the world community. Code is released under GPL2. Help Needed We could use some help with this project. We haven't even started writing any client side code. We are looking for sharp people with good ideas to help develop this concept in a way that will eventually lead to becoming part of the standard. We envision that certian commands to do ordinary universal stuff (password, smpt, whit list, black list, forwarding) will become standardized so that features to set server side settings can become part of standard email applications.

1 0

[Dovecot] Warning about NFS but using local fs for INDEX
by Herbert Gasiorowski 12 Jun '07

12 Jun '07

I am playing around with dovecot and want to use local filesystem for indexing. But whenever I open a new imap connection the following warning is shown: Apr 30 10:14:42 beira dovecot: Mailbox indexes in /app/home/gasi are in NFS mount. You must set mmap_disable=yes to avoid index corruptions. If you're sure this check was wrong, set nfs_check=no. /app/home is a NFS mounted filesystem, but I want dovecot to use /export/dovecot/gasi for indexing (See namespaces below). I shurely can follow the hints(nfs_check=no), but I am not shure if I did something wrong or maybe someday will change the configuration and forget to enable the nfs check. dovecot version: dovecot-1.0-1.2.rc15.el5 on CentOS 5.0 (with all updates). [root@beira etc]# dovecot -n # /etc/dovecot.conf syslog_facility: local6 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 namespace: type: private separator: / location: mbox:~/Mail:INBOX=/var/spool/mail/%u:INDEX=/export/dovecot/%u inbox: yes namespace: type: private separator: / prefix: #home-tmp/ location: mbox:~:INDEX=/export/dovecot/%u auth default: passdb: driver: pam args: imap userdb: driver: passwd

2 2

[Dovecot] error in logfile
by Luigi Rosa 12 Jun '07

12 Jun '07

With Dovecot 1.0.0: May 11 12:16:35 mail dovecot: IMAP(xxx): stat(/var/spool/mail2/xxx/.Trash.Squid-it/new) failed: No such file or directory With Thunderbird 2.0 IMAP client: * user deleted the mailbox * TB moved the mailbox to Trash * user asked TB to empty Trash * the above message appeared No warning/error was reported bt TB to user. I don't think it's an error and should not be logged. Ciao, luigi -- / +--[Luigi Rosa]-- \ You can tune a radio, but you can't tuna fish.

2 1

[Dovecot] Getting rid of the common newbie problems
by Timo Sirainen 12 Jun '07

12 Jun '07

I think the most common Dovecot newbie problems are: - Not looking at the (correct) logs for errors - Authentication problems - Mail location problems - Mail permission problems Below are some of my ideas how I could stop people from asking these questions with future Dovecot (v1.1+) releases. Suggestions welcome. Distribution people especially should say if they're against some change. * Logging The log file problem is the most annoying one, because a lot of the other problems can be solved once the admin figures out that Dovecot is actually giving useful error messages. Often the admin is only looking at the log file where "info" messages go (eg mail.log) because Dovecot logs its startup message and login messages there, but not where the errors go (eg mail.err). This has happened even with people who in general are experienced sysadmins. Logging to eg. /var/log/dovecot.log by default would be helpful here, but it's probably better to log via syslog by default. Cyrus logs to "local6" by default. Perhaps for Dovecot v1.1 I should make that the default too? Looks like in my Debian system the info messages then go to both /var/log/messages and /var/log/syslog. Error messages only go to /var/log/syslog. So there still isn't by default a single log file where the errors are logged, but it might help a bit. * Authentication Authentication problems can usually be solved by telling the user to set auth_debug_passwords=yes and looking at the logs. I'm not sure if there's anything that can be helped in here. Except the logging message could be updated a bit: "Aborted login: user=<asdga>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, 1 failed authentications" So the last "n failed authentications" could be added, where n could also be 0. Another possibility would be to make Dovecot remember if there have been any successful logins (/var/lib/dovecot/success file) and if not, give a bit more helpful error messages: - Client gets: "NO Authentication failed. Refer to server log for more information." instead of the normal "NO Authentication failed." - Log contains: "Aborted login: user=<asdga>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, 1 failed authentications (set auth_debug_passwords=yes to debug the problem)" I'm not sure if this is a good idea. * Mail location It seems to be difficult for some people to set mail_location. I don't know if anything can be done before Dovecot v2.0 where I'll split it to multiple settings, such as: driver = maildir root_dir = ~/Maildir index_dir = /var/indexes/%u Another problem that seems to be difficult to understand is why the mail directory contains "HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB". The whole userdb concept appears to be weird. This could anyway be fixed by giving an error message earlier and failing the login with internal error. Probably the best place to give the error message would be already in the userdb lookup in dovecot-auth, but that would require that doveoct-auth knows if the home directory is really needed, and to give a useful error message it would also need to tell where it's tried to be used (mail_location, or some namespace's location, or ..). Probably too much trouble to be worth it. So the next best thing is to give the error when it's used: "Home directory is used in mail_location, but userdb didn't return a home directory" It would be nice if it didn't say userdb, but rather the userdb's name. I guess that would be possible if dovecot-auth told master (or deliver) which userdb was used, but that would normally be just extra overhead. * Mail permissions If mail location is difficult for some, then the concept of UIDs are how they're used in Dovecot is pretty much impossible for some to understand. One of the problems is that there exists "dovecot" user. So people think that their mails should be owned by the dovecot user. Although I've mentioned in everywhere I can think of that this should not be done, it won't help because either people won't read the pages or even if they do, they somehow still fail to ignore it even though it's written in bold. So unless people (and most importantly, distributions) are against it, I think the "dovecot" user should be renamed. "dovelogin" perhaps. In future I might split dovecot-auth even more, and then I would like to create a "doveauth" user as well. Another possibility would be to drop the dovecot user completely and instead use "nobody". That would mean that other nobody processes could kill Dovecot's login processes, but that's pretty much it. Once people understand that "dovecot" isn't the right user, they hit the next problem: "How do I tell Dovecot to run as vmail user?" I can paste links to wiki pages or tell them to "make userdb return uid=vmail", but that just doesn't seem to get through. There needs to be an easier way, and I think I figured out what it is: Add new "mail_uid" and "mail_gid" settings to dovecot.conf. Deprecate user_global_uid/gid in dovecot-ldap.conf and make all the userdbs mention that the uid/gid returned by userdb can be used to override the global mail_uid/gid. Perhaps also add "mail_home" template. This change makes it unnecessary to have a userdb configured at all. - "How do I tell Dovecot to run as vmail user?" - "Set mail_uid = vmail" in dovecot.conf - "Thanks"

10 36

[Dovecot] Dovecot LDA and address extensions
by Tom Metro 12 Jun '07

12 Jun '07

I'm converting over a virtual user installation that used Postfix and maildrop with a MySQL back-end for mailbox lookups to use Dovecot LDA. The maildrop setup used a database table like: +-------------------------+--------+-------------+--------------------+ | address | owner | domain | mailbox | +-------------------------+--------+-------------+--------------------+ | postmaster(a)example.com | tmetro | example.com | .admin.postmaster/ | | root(a)example.com | tmetro | example.com | .admin.root.lex/ | | tmetro(a)example.com | tmetro | example.com | .INBOX/ | | tmetro+spam(a)example.com | tmetro | example.com | .spam.tmetro/ | [...] where maildrop was handed ${recipient} from postfix, and it queries the above table matching ${recipient} to the address column, getting back the expression CONCAT_WS('/','/var/mail',domain,owner) as the home directory, and CONCAT_WS('/','/var/mail',domain,owner,mailbox) as the mailbox. The UID/GID are fixed, as this is a virtual user setup. So looking up the mailbox for the user postmaster(a)example.com returns: /var/mail/example.com/tmetro/.admin.postmaster/ Currently I'm using a static user database with Dovecot. This SQL appears to replicate the maildrop setup: user_query = SELECT CONCAT_WS('/','/var/mail',domain,owner) as home, CONCAT_WS('/','maildir:/var/mail',domain,owner,mailbox) as mail, 5000 as uid, 5000 as gid FROM vmbx2 WHERE userid = '%u' And this works for mail deliveries. The problem with this is that not only is a database lookup overkill for the IMAP server, as the root mail location for IMAP users follows a simple pattern adequately represented by the static userdb, it also breaks IMAP, because the returned 'mail' overrides mail_location, (currently set to maildir:/var/mail/%d/%n/), so for user tmetro(a)example.com it returns: maildir:/var/mail/example.com/tmetro/.INBOX/ instead of: maildir:/var/mail/example.com/tmetro/ (which is the same as the home directory). Can the "userdb sql" directive be added to the "protocol lda" section? Or perhaps instead create a new "auth lda" section, and move the "userdb sql" and "socket listen" directives to that section? The second issue is how to best deal with address extensions, something that wasn't fully implemented in the maildrop setup. Ideally I'd like a setup where a lookup is first performed for user+ext@domain, and if it fails to return a mailbox, then lookup user@domain. Assuming Dovecot can handle a multi-row query result (grabbing the first record and ignoring the rest), this can probably be hacked using an appropriate WHERE expression. But the difficulty is getting the address components. Postfix will provide them, but Dovecot's deliver doesn't seem to have a way of receiving them and passing them on to the user query. The example LDA setup shown here: http://wiki.dovecot.org/LDA/Postfix suggests passing the extension as an argument to the mailbox (-m) switch. But this assumes that one wants a one-to-one direct mapping between extensions and mailbox names. I suppose I could switch from: -d ${user}@${nexthop} to: -d ${recipient} and add even more complexity to the SQL to parse out the extension. But I'd rather avoid embedding the extension separator character in the SQL, and would rather eliminate it from the database as well. Maybe Sieve is the answer. I presume the argument to -m could be inspected in a Sieve script, which could then map to the desired target mailbox. The non-IMAP users (like postmaster(a)example.com) could be reimplemented as aliases that redirect to a user+ext(a)example.com address for the user responsible for that domain. But using Sieve scripts for extension to mailbox mappings seems far less elegant than using a database. Maybe I need to wedge a wrapper program between Postfix and deliver that will accept the address components from postfix, perform the lookup, and convert the results into a -d argument pointing to the "owner" (see table above) and a -m argument pointing to the mailbox. On a side note... When I used this command in postfix's master.cf: /usr/lib/dovecot/deliver -d ${user}@${nexthop} -n -m ${extension} as recommended in the wiki, the following error gets logged: ... status=bounced (command line usage error. Command output: Fatal: Unknown argument: -d Usage: deliver [-c <config file>] [-d <destination user>] [-m <mailbox>] [-f <envelope sender>] ) which doesn't make a lot of sense. I suspect what it is trying to say is that it didn't like something about the argument to the -d switch. Maybe that should be ${domain} instead of ${nexthop}. (What's up with all the whitespace between "[-m <mailbox>]" and "[-f <envelope sender>]"? Also, might be a good idea to have deliver always write errors - even startup errors - to the specified logging facility, given that not all programs that launch it will report what it writes to STDERR. I notice most postfix commands - even the ones people interact with - log errors.) I ended up switching to -d ${recipient} to emulate the old maildrop setup for now, and that worked fine. The sample dovecot.conf has: ## dovecot-lda specific settings ## # socket listen { # master { # path = /var/run/dovecot/auth-master I uncommented the first two lines, but left the 'path' directive commented, under the assumption that the comment was showing the default. But without it uncommented, the socket doesn't get created. This is an inconsistency compared to how defaults are shown elsewhere in dovecot.conf. -Tom

2 1

[Dovecot] vpopmail quota
by Onno Molenkamp 12 Jun '07

12 Jun '07

Hi, I'd like the vpopmail user database to return the quota settings for users, instead of having to rely on the validity of the maildirsize files. It doesn't look like this is currently possible. Would simply adding a auth_stream_reply_add call for "quota" with a suitable value in vpopmail_lookup be sufficient to make this work? (the quota can be read from the pw_shell field of the vqpasswd struct) Onno

2 3

[Dovecot] Date error bug
by Bgs 12 Jun '07

12 Jun '07

Hi all, I encountered a bug, that prevents me from moving mail and as a side effect it messes up all thunderbird/mozilla mail clients (they won't do any message copy/move until I restart them). Here is the info and the header of the mail that produces the error (a spam mail): Dovecot version: 1.0.0 Mail header: Return-Path: <xxdwwu(a)boboakes.com> Delivered-To: bgs-hu-bgs(a)bgs.hu Received: (qmail 10895 invoked from network); 7 Jun 2007 16:51:21 -0000 Received: from unknown (HELO 86.109.208.58.broad.sz.js.dynamic.163data.com.cn) (58.208.109.86) by 0 with SMTP; 7 Jun 2007 16:51:21 -0000 Received: from [58.208.109.86] by INBOUND.BOBOAKES.COM.NETSOLMAIL.NET; Tue, 15 May 2085 16:51:38 -0800 From: Nigel <xxdwwu(a)boboakes.com> To: <bgs(a)bgs.hu> Subject: explore this offer Date: Tue, 15 May 2085 16:51:38 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_021F0ADE.78E00150" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Aca6Q09K1THIO7J1RUMI4LVVDU6VQF== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 . Message-ID: <021f0a9b$6abcc150$566dd03a@xxdwwu> Attached is the error window with the actual error message. It seems that the year 2085 date is not handled but dovecot. Regards Bgs PS: Probably unrelated but here are the other infos: Linux, local XFS, AMD Athlon XP, clients Seamonket 1.1.1 and Thunderbird 2.0.0.0

2 2

[Dovecot] SEGV when user over filesystem quota and "Move to Trash"
by Steffen Kaiser 12 Jun '07

12 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've configured Dovecot v1.0.0 with filesystem quota and to use hardlinks. Latter I use intentionally to save disk space and to achieve that an user can delete mails even if over quota and using the "Delete to Trash" feature. The following happens, when the directory file of .Trash/* fills up and would need to be expanded, but fails because of an over-quota condition. The crash is not so problematic, because you can wait some time (I guess until the lock of .Trash/dovecot-uidlist.lock expires) and you can delete mails from Trash to make room. However, there are leftover files in .Trash/tmp, what may make problems. First you get a "Out of quota" error in the MUA, maybe a second or a third time, too. Then: dovecot: Jun 12 09:10:38 Info: IMAP(dvtest) [3492]: copy -> Trash: uid=500, msgid=<cs-HoeqDW06gzBNu-9HdUBR4A@> dovecot: Jun 12 09:10:38 Error: child 3492 (imap) killed with signal 11 When you try to delete another mail: process #1: nanosleep({0, 158957000}, NULL) = 0 lstat64("/var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 time(NULL) = 1181630732 nanosleep({0, 170189000}, NULL) = 0 lstat64("/var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock", {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 time(NULL) = 1181630732 process #2: gettimeofday({1181630713, 945424}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 9335) = 0 gettimeofday({1181630723, 281935}, {4294967176, 0}) = 0 gettimeofday({1181630723, 282014}, NULL) = 0 poll([{fd=4, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=2, events=POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 3, 9999) = 0 gettimeofday({1181630733, 281949}, {4294967176, 0}) = 0 gettimeofday({1181630733, 282149}, NULL) = 0 .Trash/tmp contains 28 items (growing) After the "Connection timeout" error in the client process #1 still loops repeatedly. Eventually the processes stops. Maybe it is waiting for the release of the lock by the process killed by segv? Finally it dumps core, too. dovecot: Jun 12 09:10:38 Info: IMAP(dvtest) [3821]: copy -> Trash: uid=500, msgid=<cs-HoeqDW06gzBNu-9HdUBR4A@> dovecot: Jun 12 09:12:39 Error: child 3821 (imap) killed with signal 11 Core was generated by `imap [dvtest 10.20.10.63]'. Program terminated with signal 11, Segmentation fault. #0 maildir_sync_get_keywords_sync_ctx (ctx=0xffffffff) at maildir-sync.c:242 242 { (gdb) bt #0 maildir_sync_get_keywords_sync_ctx (ctx=0xffffffff) at maildir-sync.c:242 #1 0x0806ddd4 in maildir_mf_get_path (ctx=0x0, mf=0x20) at maildir-save.c:263 #2 0x0806de80 in maildir_transaction_unlink_copied_files (ctx=0x80fcbb0, pos=0x0) at maildir-save.c:477 #3 0x0806e5cb in maildir_transaction_save_commit_pre (ctx=0x80fcab0) at maildir-save.c:561 #4 0x080693c4 in maildir_transaction_commit (_t=0x8101eb8, flags=0) at maildir-transaction.c:28 #5 0xb7ddbbd0 in quota_mailbox_transaction_commit (ctx=0x8101eb8, flags=0) at quota-storage.c:74 #6 0x08057965 in cmd_copy (cmd=0x80df0f0) at cmd-copy.c:124 #7 0x0805b1be in cmd_uid (cmd=0x80df0f0) at cmd-uid.c:19 #8 0x0805b728 in client_handle_input (cmd=0x80df0f0) at client.c:335 #9 0x0805b7b7 in client_handle_input (cmd=0x80df0f0) at client.c:389 #10 0x0805be3c in _client_input (context=0x80df0a8) at client.c:432 #11 0x080bc902 in io_loop_handler_run (ioloop=0x80dc9b0) at ioloop-poll.c:199 #12 0x080bbb58 in io_loop_run (ioloop=0x80dc9b0) at ioloop.c:326 #13 0x08063e80 in main (argc=Cannot access memory at address 0x0 ) at main.c:290 I also managed it to have to two processes waiting for /var/cache/dovecot/31045/control/.Trash/dovecot-uidlist.lock. dovecot -n: # /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/ca.crt ssl_cert_file(default): /etc/ssl/certs/imap.pem ssl_cert_file(imap): /etc/ssl/certs/imap.pem ssl_cert_file(pop3): /etc/ssl/certs/pop3.pem ssl_key_file(default): /etc/ssl/private/imap.key ssl_key_file(imap): /etc/ssl/private/imap.key ssl_key_file(pop3): /etc/ssl/private/pop3.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_log_format_elements: %p: user=<%u> method=%m rip=%r lip=%l %c verbose_proctitle: yes first_valid_uid: 1000 mail_location: maildir:%h/MailDir:CONTROL=/var/cache/dovecot/%i/control:INDEX=/var/cache/dovecot/%i/index mail_debug: yes dotlock_use_excl: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_log zlib mail_plugins(imap): quota imap_quota mail_log zlib mail_plugins(pop3): quota mail_log mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_prefix: %Us(%u) [%p]: mail_log_max_lines_per_sec: 0 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): oe-ns-eoh namespace: type: private separator: . inbox: yes hidden: yes auth default: mechanisms: plain login cache_size: 10 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890 verbose: yes debug: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /etc/passwd socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 432 group: mail plugin: quota: fs Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRm5VCi9SORjhbDpvAQLDQwgAp0Zcg4SbTXXyFTUFVsxRHjhRr1V2ZuoE Ajpar7u5hoG8IfJ8u6noxk2XvNlD0rL0g/oXHJDeRTuZs6PVwcQpSEyQ0DNUx8BY bUyX5i3sR02MOrwbKvlq6ynvV3VE5PY4fpgCfqUv7ZE4W72u577IQ4l/C3+hgC+Y qzKw2URlVzoJj6apyXEIZcv4gvxkxl4mMtOmoXrTj5nMfz7EFbbuXuK9aYfFhLFp YB/Q0FxsU3YylpYYbFGronbmrAUGb2TCJckRAwDdTzT1s++6uvbJt5BLRnwiOK6H UAEuJJllwoDcwx0WIwMzf3SXP52OSqHdEVBuJprxpHrTI7Fe2fm5FA== =WkkL -----END PGP SIGNATURE-----

2 2

[Dovecot] Cannot get cmusieve to work
by Dani 12 Jun '07

12 Jun '07

Hi, # I messed with the identities in my MUA and sent the email with a non registered address, sorry for the incinvenience ## I'm not able to make cmusieve to work to filter emails. Below is my configuration. I'm using a .dovecot-sieve example from the wiki: require "fileinto"; if exists "X-Spam-Flag" { fileinto ".Junk/"; } I've been following (as acurately as I could) the documentation, tuts and examples. I found this in the dovecot list: http://www.dovecot.org/list/dovecot/2007-March/020674.html and I used the CONCAT method but anyway mails don't filter because of two "//". *********LOGS******** Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): Loading modules from directory: /usr/lib/dovecot/modules/lda Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): Module loaded: /usr/lib/dovecot/modules/lda/lib90_cmusieve_plugin.so Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: dani(a)exampledomain.org Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: maildir=dani(a)exampledomain.org/ Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: uid=110 Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: gid=8 Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): auth input: home=/home/vmail/exampledomain.org/dani@exampledomain.org/ Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): maildir: data=/home/vmail/exampledomain.org/dani@exampledomain.org Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): maildir: root=/home/vmail/exampledomain.org/dani@exampledomain.org, index=/home/vmail/exampledomain.org/dani@exampledomain.org, control=, inbox= Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): cmusieve: Using sieve ****path: /home/vmail/exampledomain.org/dani(a)exampledomain.org//.dovecot.sieve*** Jun 12 14:12:52 yad deliver(dani(a)exampledomain.org): msgid=<20070612110825.F38F61054E8(a)sc8-sf-spam1.sourceforge.net>: saved mail to INBOX I've been looking into the problem and I must have forget something obvious, but I cannot make it work. does anyone can point me to the problem? thanks in advance. Dani CONFIGS ************** dovecot --version 1.0.0 (debian) ************** ******************** # /etc/dovecot/dovecot.conf protocol lda { postmaster_address = postmaster(a)exampledomain.org mail_plugin_dir = /usr/lib/dovecot/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master mail_plugins = cmusieve } *************** dovecot-sql.conf *************driver = mysql connect = dbname=postfix user=postfix password=qwe123dsazxc port=3306 host=localhost default_pass_scheme = CRYPT password_query = SELECT password FROM mailbox WHERE username ='%u' user_query = SELECT maildir, 110 AS uid, 8 AS gid, CONCAT('/home/vmail/%d/', @home := maildir) AS home FROM mailbox WHERE username = '%u

2 2

[Dovecot] per mailbox maildir format
by Bgs 12 Jun '07

12 Jun '07

Hi all, Is it possible to set the maildir format at mailbox level? I'd like to us Maildir++ for most of my clients, but want to emulate the other one for one of my users. Can this be done with dovecot? Thanks Bgs

2 2

[Dovecot] how to create new user account
by santhosh 12 Jun '07

12 Jun '07

Hi, I am using dovecot1.0.0. How to create new user in dovecot ? Thanks in advance Regards, Santhosh

3 2

[Dovecot] difference b/w user and login_user
by santhosh 12 Jun '07

12 Jun '07

Hi, Can any one tell what is the difference between user and login_user in dovecot.conf file ? Thanks in advance Regards, Santhosh

2 1

[Dovecot] Can't send/receive mail from other domain
by Jeremy Gillick 12 Jun '07

12 Jun '07

I've followed the instructions ( http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL) to setup Dovecot with MySql and Postfix but cannot receive from (or send mail to) other domains. FYI: email messages are supposed to be stored under /var/mail/mozmonkey.com/<user>/ Directory Permissions: drwxr-xr-x 5 vmail mail 4096 May 10 12:57 mozmonkey.com OS: Linux, Fedora 4 Dovecot version: 1.0.0 --------- CONFIG START --------- $ sudo dovecot -n # /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_listen: [::] login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 101 last_valid_uid: 101 mail_extra_groups: mail mail_location: maildir:/var/mail/%d/%u mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain digest-md5 cram-md5 user: nobody debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: vmail group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail --------- CONFIG END --------- --------- LOG START (modified email address to prevent spam) --------- Jun 10 22:48:23 mozmonkey postfix/smtpd[27592]: connect from n9.bullet.re3.yahoo.com[68.142.237.94] Jun 10 22:48:23 mozmonkey postfix/trivial-rewrite[27595]: warning: do not list domain mozmonkey.com in BOTH mydestination and virtual_mailbox_domains Jun 10 22:48:23 mozmonkey postfix/smtpd[27592]: C0093210021: client= n9.bullet.re3.yahoo.com[68.142.237.94] Jun 10 22:48:23 mozmonkey postfix/cleanup[27599]: C0093210021: message-id=< 568874.40698.qm(a)web57505.mail.re1.yahoo.com> Jun 10 22:48:23 mozmonkey postfix/qmgr[27282]: C0093210021: from=< jeremymailing123(a)yahoo.com>, size=2242, nrcpt=1 (queue active) Jun 10 22:48:23 mozmonkey postfix/trivial-rewrite[27595]: warning: do not list domain mozmonkey.com in BOTH mydestination and virtual_mailbox_domains Jun 10 22:48:23 mozmonkey postfix/local[27600]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jun 10 22:48:23 mozmonkey postfix/smtpd[27592]: disconnect from n9.bullet.re3.yahoo.com[68.142.237.94] Jun 10 22:48:23 mozmonkey postfix/local[27600]: C0093210021: to=< jerxyz(a)mozmonkey.com>, relay=local, delay=0.27, delays=0.2/0.03/0/0.04, dsn= 5.2.0, status=bounced (cannot update mailbox /var/mail/jerxyz for user jerxyz. cannot open file: Permission denied) Jun 10 22:48:24 mozmonkey postfix/cleanup[27599]: 041A7210033: message-id=< 20070611054824.041A7210033(a)mozmonkey.com> Jun 10 22:48:24 mozmonkey postfix/qmgr[27282]: 041A7210033: from=<>, size=4181, nrcpt=1 (queue active) Jun 10 22:48:24 mozmonkey postfix/bounce[27602]: C0093210021: sender non-delivery notification: 041A7210033 Jun 10 22:48:24 mozmonkey postfix/qmgr[27282]: C0093210021: removed Jun 10 22:48:24 mozmonkey dovecot: auth(default): master in: USER 1 jeremymailing(a)yahoo.com service=deliver Jun 10 22:48:24 mozmonkey dovecot: auth-worker(default): sql( jeremymailing(a)yahoo.com) SELECT concat('/var/mail/', maildir) as home, concat('maildir:/var/mail/', maildir) as mail, 101 AS uid, 12 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE (username = ' jeremymailing(a)yahoo.com' OR simpleuser = 'jeremymailing(a)yahoo.com') AND active = '1' Jun 10 22:48:24 mozmonkey dovecot: auth-worker(default): sql( jeremymailing(a)yahoo.com) User not found Jun 10 22:48:24 mozmonkey dovecot: auth(default): master out: NOTFOUND 1 Jun 10 22:48:24 mozmonkey postfix/pipe[27603]: 041A7210033: to=< jeremymailing(a)yahoo.com>, relay=dovecot, delay=0.08, delays=0.02/0.03/0/0.03, dsn=5.1.1, status=bounced (user unknown) Jun 10 22:48:24 mozmonkey postfix/qmgr[27282]: 041A7210033: removed --------- LOG END --------- Thanks, Jeremy

2 1

[Dovecot] 20070605 still hanging with SSL
by David Favor 12 Jun '07

12 Jun '07

Thought this was fixed and now it's back. No help from rawlog as the hang appears prior to authentication. Notice there is around a 90 second delay before authentication fires. Let me know how to proceed debugging. Thanks. _____ Here's my config: listen: *:143 ssl_listen: *:993 ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/pkgs/dovecot-20070605/libexec/dovecot/imap-login login_greeting: IMAP ready. login_process_per_connection: no login_processes_count: 5 verbose_proctitle: yes first_valid_uid: 12 default_mail_env: maildir:~/Maildir mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable: /usr/local/pkgs/dovecot-20070605/libexec/dovecot/rawlog \ /usr/local/pkgs/dovecot-20070605/libexec/dovecot/imap auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: shadow userdb: driver: passwd Here's a maillog snippet: Jun 11 07:50:40 net1 dovecot: Dovecot v20070522 starting up ... Immediately click on INBOX or other box and hang occurs... Jun 11 07:52:00 net1 dovecot: auth(default): client in: AUTH \ 1 PLAIN service=imap secured lip=69.94.137.124\ rip=71.155.185.14 Jun 11 07:52:00 net1 dovecot: auth(default): client out: CONT 1 Jun 11 07:52:00 net1 dovecot: auth(default): client in: CONT 1 \ AGRhdmlkAGZpcmUyM2JyaWNr Jun 11 07:52:00 net1 dovecot: auth(default): shadow(david,71.155.185.14): lookup Jun 11 07:52:00 net1 dovecot: auth(default): client out: OK 1 user=david Jun 11 07:52:00 net1 dovecot: auth(default): master in: REQUEST 1 30912 1 Jun 11 07:52:00 net1 dovecot: auth(default): passwd(david,71.155.185.14): lookup Jun 11 07:52:00 net1 dovecot: auth(default): master out: USER 1 \ david system_user=david uid=510 gid=506 home=/vhost/davidfavor.com/users/david Jun 11 07:52:00 net1 dovecot: imap-login: Login: user=<david>, method=PLAIN, \ rip=71.155.185.14, lip=69.94.137.124, TLS Jun 11 07:52:00 net1 dovecot: IMAP(david): Effective uid=510, gid=506,\ home=/vhost/davidfavor.com/users/david Jun 11 07:52:00 net1 dovecot: IMAP(david): maildir: \ data=/vhost/davidfavor.com/users/david/Maildir Jun 11 07:52:00 net1 dovecot: IMAP(david): maildir++: \ root=/vhost/davidfavor.com/users/david/Maildir, index=, control=, \ inbox=/vhost/davidfavor.com/users/david/Maildir -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 1

[Dovecot] SSL_CTX_set_info_callback problem in latest source
by David Favor 11 Jun '07

11 Jun '07

In the file ./src/login-common/ssl-proxy-openssl.c appears the code: if (verbose_ssl) SSL_CTX_set_info_callback(ssl_ctx, ssl_info_callback); It appears the SSL_CTX_set_info_callback symbol only occurs in the openssl development branch starting with 0x00909000L as this symbol is missing from openssl 0.9.8b and 0.9.8e (no check of the latest nightly snapshot of the stable 0.9.8 branch). It appears there should be a compilation guard around this code. Perhaps... #if OPENSSL_VERSION_NUMBER >= 0x00909000L if (verbose_ssl) SSL_CTX_set_info_callback(ssl_ctx, ssl_info_callback); #endif -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 4

[Dovecot] lazy_expunge and emails from Inbox, doesn't list INBOX in deleted
by Roger Binns 11 Jun '07

11 Jun '07

I'm using the dovecot available on Ubuntu Feisty (1.0rc17) and am trying to migrate from courier-imap. A really important feature for me from courier is that expunged messages end up in Trash where they are removed after 7 days. I can get an approximation of this feature as described in the documentation: namespace private { prefix = INBOX. seperator = . inbox = yes } namespace private { prefix = DELETED. seperator = . location = maildur:~/Maildir/deleted } lazy_expunge = DELETED. DELETED. DELETED. This all works fine except for messages that were deleted from the Inbox. They do end up in the right place (~/Maildir/deleted/cur) but that location is not listed as a subscribable folder. Here you can see that deleted messages from my ciontope folder show up, but not the inbox. a LIST "DELETED." * * LIST (\HasNoChildren) "." "DELETED.ciontope" a OK List completed. You can't examine the namespace itself: a EXAMINE DELETED a NO Unknown namespace. a EXAMINE DELETED. a NO Invalid mailbox name But the folder does exist: a EXAMINE DELETED.INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 4 EXISTS * 0 RECENT * OK [UIDVALIDITY 1181423860] UIDs valid * OK [UIDNEXT 5] Predicted next UID a OK [READ-ONLY] Select completed. Is there any way to convince dovecot to list DELETED.INBOX so that clients can see it an subscribe to it? Roger

3 5

[Dovecot] Multiple IP(or Host) listen in dovecot.conf.
by Yoshihiro Kawabe 11 Jun '07

11 Jun '07

Hi. Does someone make update for `Multiple IP(or Host) listen in dovecot.conf'? I made trivial patch so. But this patch doesn't solve `Support listening in multiple sockets' in TODO. It appends only the capability as multiple listen in dovecot.conf. So, `login_processes_count' becomes ambiguous. In CASE1, login_processes_count = 2, forked imap-login processes are 8. -- samples dovecot.conf applied this patch are following. CASE 1: listen = 127.0.0.1, 192.168.0.10, imap-server1, imap-server2.example.com or CASE 2: protocol imap { listen = 127.0.0.1:143, imap-server1:10143 ssl_listen = imap-server2:10943, 127.0.0.1 .. } protocol pop3 { listen = 127.0.0.1, pop-server1:10100 .. } -- Update brief. src/master/ master-setting.h: listen_fd and related members changed to array_t. also name add (s). master-setting.c: few member initialization delete. main.c: handle multiple IP and port, fds as array_t. resolve_ip argment change. login-process.h: add listen_fd and ssl_listen_fd member to login_group structre. login-process.c: add login_groups_create function for mapping login process to each listen fd. change dup2 source fd in create_login_process. src/lib network.c: change getnameinfo error value. -- Kawabe,Yoshihiro <sowhat(a)amnis.co.jp> As the stars blink in the night sky, our married hearts are never splitted. Even if we will unclasp each other hands, until we retain that. by H.S.

2 3

[Dovecot] dovecot-20070605 runtime problems
by David Favor 11 Jun '07

11 Jun '07

I've build this nightly snapshot with my installed openssl, which is 0.9.8b (Fedora 6) and the latest openssl development tree. The 20070605 version of dovecot starts up doing ssl protocol perfect, then after clicking a few directories, then when clicking back to INBOX, dovecot hangs. There is no logging info, even with --enable-debug on and all .conf file directives I can find. Doing a 'ngrep port 993' shows no SSL dialog. If I go through my same compile sequence using the dovecot-1.0.0 source all is well with both the system openssl and the latest openssl snapshot, so it appears something is wrong in the current nightly snapshot. My primary question is howto debug this hang, short of attaching gdb to the process. Any suggestions are appreciated. Thanks. I'm using the latest Thunderbird version 2.0.0.4 (20070604). I've build it using: [root@net1 dovecot-20070605]# build_dovecot mkdir -p /build/work/dovecot-20070605 cd /build/work/dovecot-20070605 unset CDPATH export CPPFLAGS='-pipe -O2 -I/usr/local/include' export LDFLAGS='-L/usr/local/lib' make distclean ./configure --prefix=/usr/local/pkgs/dovecot-20070605 --disable-nls --with-deliver --with-sqlite --without-vpopmail --with-notify=inotify --with-ioloop=epoll --with-ssl=openssl --enable-debug --enable-asserts make make check rm -rf /usr/local/pkgs/dovecot-20070605 make install install -c -m 555 doc/mkcert.sh /usr/local/pkgs/dovecot-20070605/sbin/dovecot-mkcert shmk /usr/local/pkgs/dovecot-20070605/sbin /usr/local/sbin mkdir -p /etc/ssl/certs /etc/ssl/private rm -f /etc/ssl/certs/dovecot.pem /etc/ssl/private/dovecot.pem export OPENSSLCONFIG=/tools/conf/dovecot-openssl.conf dovecot-mkcert cp -f /etc/ssl/certs/dovecot.pem /var/www/html/. chmod ugo+r /var/www/html/dovecot.pem groupadd dovecot || /bin/true groupadd: group dovecot exists useradd -M -g dovecot -d /usr/local -s /sbin/nologin dovecot || /bin/true useradd: user dovecot exists (cd /etc/init.d && ln -sf /tools/init.d/dovecot .) -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com

2 3

[Dovecot] DC V1.0.1 release date
by Stewart Dean 11 Jun '07

11 Jun '07

Is there a sense of when this might be? Will it include a fix for SSL with a second invocation? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] Connection dropped by IMAP server _ Internal login failure: root
by Saeed Abbassi 11 Jun '07

11 Jun '07

Dear reader, Please help me find a way through this problem, I have CentOS 4.2, dovecot-0.99.11-4.EL4, squirrelmail-1.4.8, While I try to log in as Root (username: root; password: password) I get the error that says, > ERROR: Connection dropped by IMAP server. > Query: CAPABILITY > Content of the file /var/log/maillog is as follows > Jun 7 12:56:59 PBX sendmail[5170]: l57Guxxr005170: from=root, > size=126838, class=0, nrcpts=1, msgid=< > 200706071656.l57Guxxr005170(a)PBX.COMPANY.COM>, relay=root@localhost > Jun 7 12:57:05 PBX sendmail[5171]: l57GuxDv005171: from=< > root(a)PBX.COMPANY.COM>, size=127100, class=0, nrcpts=1, msgid=< > 200706071656.l57Guxxr005170(a)PBX.COMPANY.COM>, proto=ESMTP, daemon=MTA, > relay=localhost.localdomain [127.0.0.1] > Jun 7 12:57:05 PBX sendmail[5170]: l57Guxxr005170: to=root, ctladdr=root > (0/0), delay=00:00:06, xdelay=00:00:06, mailer=relay, pri=156838, relay=[ > 127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (l57GuxDv005171 Message > accepted for delivery) > Jun 7 12:57:05 PBX sendmail[5172]: l57GuxDv005171: to=admin, ctladdr=< > root(a)PBX.COMPANY.COM> (0/0), delay=00:00:00, xdelay=00:00:00, > mailer=local, pri=157317, dsn=2.0.0, stat=Sent > Jun 7 22:26:11 PBX dovecot: Killed with signal 15 > Jun 11 11:39:00 PBX dovecot: Dovecot starting up > Jun 11 11:39:01 PBX sendmail[2704]: alias database /etc/aliases rebuilt by > root > Jun 11 11:39:01 PBX sendmail[2704]: /etc/aliases: 79 aliases, longest 10 > bytes, 811 bytes total > Jun 11 11:39:01 PBX sendmail[2709]: starting daemon (8.13.1): > SMTP+queueing@01:00:00 > Jun 11 11:39:01 PBX sm-msp-queue[2717]: starting daemon (8.13.1): > queueing@01:00:00 > Jun 11 11:51:27 PBX dovecot: Logins with UID 0 not permitted (user root) > Jun 11 11:51:27 PBX imap-login: Internal login failure: root [::ffff: > 127.0.0.1] And I says, [root@PBX etc]# dovecot -c dovecot.conf Fatal: listen(143) failed: Address already in use Any help is appreciated in advance, Cheers, Saeed144

2 1

[Dovecot] [Debian] Packages available for 1.0.0
by Brian T Glenn 11 Jun '07

11 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 They aren't thoroughly tested, but I've been running on them for a little while and they seem stable. This is based on the latest RC from backports.org and is built for sarge. deb http://debian.delink.net/ sarge-delink main Enjoy, - -- http://www.delink.net/ Ok, so he's got a cellphone in one hand and latte in the other, I know what he's using to steer, but what is that soccer mom using, a strap-on? - Brian Kantor in the monastery -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGZdGMFy/L+4MovqIRApa7AJ4s3jU0La4dCijm08iOpa7m9dSaowCeN1eW 6he6hZFEzREtzZ/iA4mvEms= =Ln6h -----END PGP SIGNATURE-----

2 2

[Dovecot] Can't connect to SMTP outside localhost
by Jeremy Gillick 11 Jun '07

11 Jun '07

I have Dovecot setup with Postfix and can't seem to connect to to the SMTP server (port 25) unless I'm on the server itself (telnet localhost 25). For example, I cannot use my mail client, Thunderbird, to send mail from my laptop -- it cannot even connect to the server. I checked the logs and nothing shows up for the attempted connection. Dovecot version: 1.0.0 Postfix version: 2.3.6 ---------- START DOVECOT CONFIG ---------- $ sudo dovecot -n # /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_listen: [::] login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no first_valid_uid: 101 last_valid_uid: 101 mail_extra_groups: mail mail_location: maildir:/var/mail/%d/%u mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain digest-md5 cram-md5 user: nobody debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: sql args: /etc/dovecot/sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: vmail group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail ---------- END DOVECOT CONFIG ---------- ---------- POSTFIX CONFIG (main.cf) ---------- queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix mail_owner = postfix myhostname = mozmonkey.com mydomain = mozmonkey.com inet_interfaces = $myhostname, localhost mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain local_recipient_maps = $virtual_mailbox_maps unknown_local_recipient_reject_code = 550 mail_spool_directory = /var/mail debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/sbin/sendmail.postfix newaliases_path = /usr/bin/newaliases.postfix mailq_path = /usr/bin/mailq.postfix setgid_group = postdrop html_directory = no manpage_directory = /usr/share/man sample_directory = /usr/share/doc/postfix-2.3.6/samples readme_directory = /usr/share/doc/postfix-2.3.6/README_FILES address_verify_map = btree:/var/spool/postfix/address_verify virtual_mailbox_domains = proxy:mysql:$config_directory/mysql_virtual_domains_maps.cf virtual_mailbox_base = /var/mail virtual_mailbox_maps = proxy:mysql:$config_directory/mysql_virtual_mailbox_maps.cf virtual_alias_maps = proxy:mysql:$config_directory/mysql_virtual_alias_maps.cf virtual_minimum_uid = 101 virtual_uid_maps = static:101 virtual_gid_maps = static:12 virtual_transport = dovecot dovecot_destination_recipient_limit = 1 smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtp_tls_CAfile = /etc/pki/tls/cert.pem smtp_tls_cert_file = /etc/pki/tls/certs/localhost.crt smtp_tls_key_file = /etc/pki/tls/private/localhost.key smtp_tls_session_cache_database = btree:/var/spool/postfix/smtp_tls_session_cache smtp_tls_security_level = may smtpd_tls_dh1024_param_file = $config_directory/dh_1024.pem smtpd_tls_dh512_param_file = $config_directory/dh_512.pem smtpd_tls_received_header = yes smtpd_tls_ask_ccert = yes smtpd_tls_loglevel = 1 tls_random_source = dev:/dev/urandom relay_domains = proxy:mysql:$config_directory/mysql_relay_domains_maps.cf ---------- POSTFIX CONFIG END (main.cf) ---------- ---------- POSTFIX CONFIG (master.cf) ---------- smtp inet n - n - - smtpd smtps inet n - n - - smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject pickup fifo n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr fifo n - n 300 1 qmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verify unix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o fallback_relay= showq unix n - n - - showq error unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scache unix - - n - 1 scache maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} old-cyrus unix - n n - - pipe flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} cyrus unix - n n - - pipe user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d ${recipient} ---------- POSTFIX CONFIG END(master.cf) ---------- <dovecot(a)dovecot.org>

2 1

[Dovecot] auth_username_format
by Sergio Souza 11 Jun '07

11 Jun '07

I configured in the archive dovecot.conf the parameter auth_username_format = "%Ld_%Ln" because the users of my server have access yours e-mail accounts based in /etc/passswd where they are registered in format domain.com_user. This configuration work without problems via pop3 and imap (squirrelmail). My server is CentOS 5.0 and dovecot is 1.0.rc15. The problem that occurs currently is: when the users go to have access the interface of change preferences (ISPCONFIG) where the supplied data of authentication are not the data of the email account (eg. user(a)domain.com) and yes of /etc/passwd the dovecot inserts underscore before the domain (eg. _domain.com_user) when it would have to make this only between the domain and the user. Exists a way to solve this problem? Thank in advance. -- Sergio Souza Wireless Support

1 0

[Dovecot] dovecot vs. Outlook Mobile
by J.Wendland＠scan-plus.de 10 Jun '07

10 Jun '07

Hi, I am testing dovecot with Outlook Mobile 5 (OM5), which is currently not working. OM5 connects, says "NOOP" and "CAPABILITY", does login correctly and simply loggs out after that telling the user that it could not download any messages. When I put an imapproxy[0] in front of dovecot, OM5 works perfectly well. That leads me to the thought, that something in the way dovecot sends its responses makes OM5 upset. Does anybody on this have seen this before? Thanks, Jörg [0] http://www.imapproxy.org -- Sicherheit - Verfügbarkeit - Kontinuität ------------------------------------------------------------------------- IT-Service-Management von ScanPlus GmbH Tel. +49 731 92013 150 Lise-Meitner-Straße 5, D-89081 Ulm, Germany Fax. +49 731 92013 29 150 Web: http://www.scan-plus.de/ Mail: wendland(a)scan-plus.de -------------------------------------------------------------------------

2 1

[Dovecot] Lost login process PID XXXXX
by Patrick Linstruth 10 Jun '07

10 Jun '07

Dear List: We installed Dovecot v1.0.0 a couple days ago. After running the software for a couple days, the following happened: Jun 6 15:58:10 cello dovecot: POP3(sgtdohara): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Jun 6 15:58:10 cello dovecot: POP3(dorene): Disconnected: Logged out top=0/0, retr=1/4652, del=1/1, size=4635 Jun 6 15:58:10 cello dovecot: Lost login process PID 17214 Jun 6 15:58:12 cello dovecot: Dovecot v1.0.0 starting up Jun 6 15:58:12 cello dovecot: Socket already exists: /qnet/var/run/dovecot/dict-server Jun 6 15:58:12 cello dovecot: net_listen_unix(/qnet/var/run/dovecot/login/default) failed: Address already in use Jun 6 15:58:12 cello dovecot: Couldn't create auth process listener Jun 6 15:58:12 cello dovecot: net_listen_unix(/qnet/var/run/dovecot/login/default) failed: Address already in use Jun 6 15:58:12 cello dovecot: Couldn't create auth process listener Jun 6 15:58:12 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:12 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:13 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:13 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:14 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:14 cello dovecot: login: Authentication process 17253 doesn't exist Jun 6 15:58:14 cello dovecot: login: Authentication process 17253 doesn't exist The "Authentication process 17253 doesn't exist" message continued until I changed inetd.conf to run our old POP3/IMAP server. Server vitals: BSD/OS 4.2 BSDI BSD/OS 4.2 Kernel #2: Tue Feb 21 11:10:22 PST 2006 4:46PM up 431 days, 16:40, 6 users, load averages: 1.19, 1.27, 1.02 Any help would be appreciated. We don't want to enable the software again until we know what caused the problem and hopefully find a solution to keep it from happening again. Patrick

2 3

[Dovecot] user lookups not working when using dovecot as lda
by Sven 10 Jun '07

10 Jun '07

Hi Currently I'm using local from postfix for delivering mails. Now I want to change this to using the dovecot lda as I want to use plus addressing. I configured postfix to use dovecot as I found in the wiki and several howtos in the net. My Problem is the following: dovecot delver accepts the mail but bounces it with error: user unknown. Logging in and authentication via imap4 and pop3 works, only deliver seems to be unable to lookup the users from userdb. Has anyone an idea where my mistake is? Here is my actual configuration: dovecot version: 1.0.beta9 postfix version: 2.2.10 system: FreeBSD 6.1-STABLE The system is using maildirs. I changed my postfix/master.cf to the following: dovecot unix - n n - - pipe flags=DRhu user=dovecot:dovecot argv=/usr/local/libexec/dovecot/deliver -d ${recipient} -m ${extension} In my postfix/main.cf I use the following: dovecot_destination_recipient_limit = 1 local_transport = dovecot lda & auth specific settings from my dovecot.conf: protocol lda { postmaster_address = postmaster(a)my-domain.org hostname = mail.my-domain.org #mail_plugins = #mail_plugin_dir = /usr/local/lib/dovecot/imap sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log # syslog_facility = mail } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_process_size = 256 auth_debug = yes auth_verbose = yes auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 user = dovecot group = dovecot } client { path = /var/run/dovecot/auth-client mode = 0660 } } } plugin { } Any help is appreciated as I dont know where to look for my mistake. regards, Sven

2 1

[Dovecot] bug in passdb-vpopmail.c
by Moritz Mertinkat 10 Jun '07

10 Jun '07

Hi there, i've tried to compile dovecot-latest.tar.gz (currently dovecot-20070522) with vpopmail support and spotted the following bug (patch is also attached): --- dovecot-20070522/src/auth/passdb-vpopmail.c.orig 2007-05-20 23:11:36.000000000 +0200 +++ dovecot-20070522/src/auth/passdb-vpopmail.c 2007-06-06 09:02:01.968750000 +0200 @@ -66,7 +66,7 @@ password = vpopmail_password_lookup(request, TRUE, &result); if (password == NULL) { - callback(result, "", request); + callback(result, "", 0, request); return; } Greets, Moritz. --- dovecot-20070522/src/auth/passdb-vpopmail.c.orig 2007-05-20 23:11:36.000000000 +0200 +++ dovecot-20070522/src/auth/passdb-vpopmail.c 2007-06-06 09:02:01.968750000 +0200 @@ -66,7 +66,7 @@ password = vpopmail_password_lookup(request, TRUE, &result); if (password == NULL) { - callback(result, "", request); + callback(result, "", 0, request); return; }

2 1

[Dovecot] [Fwd: mulitple instance run problem]
by Stewart Dean 10 Jun '07

10 Jun '07

As I explained, I want to be able to run a second instance of DC through another port to do testing while not interrupting the users using the primary instance in the the regular port. I was instructed to create a second config file with different listen ports and a separate base_dir. I did so and invoked dc with -c pointing to dovecot2.conf. Jun 7 10:04:23 mercury mail:info dovecot: Dovecot v1.0.0 starting up I pointed my client at the non-SSL port, and everything worked fine....until 3 hours later. The client wasn't getting things through, so I checked the syslog on the dc server where I saw rapidly repeating errmsgs:... Jun 7 12:51:07 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:58:55 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:58:59 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:59:01 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:59:05 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist and many more, then...... Jun 7 13:34:20 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:36:30 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:36:54 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist I kill the second instance.....but things don't clear up....rather I now get a different errmsg....which must be from the primary dc instance, since the 2nd instance and all of its children are gone (I checked the ps) Jun 7 13:39:20 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:40:00 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Jun 7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Jun 7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Finally I do a kill -1 of the primary instance and that cleans things up Jun 7 13:45:46 mercury mail:warn|warning dovecot: SIGHUP received - reloading configuration Is there something I'm doing wrong? Have other people run two instances without problem? I tried starting the second instance and killing it immediately thereafter....that wnet OK, but it hasn't been 3 hours yet. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

4 5

[Dovecot] auth_username_format
by Sergio Souza 10 Jun '07

10 Jun '07

I configured in the archive dovecot.conf the parameter auth_username_format = “%Ld_%Ln” because the users of my server have access yours e-mail accounts based in /etc/passswd where they are registered in format domain.com_user. This configuration work without problems via pop3 and imap (squirrelmail). My server is CentOS 5.0 and dovecot is 1.0.rc15. The problem that occurs currently is: when the users go to have access the interface of change preferences (ISPCONFIG) where the supplied data of authentication are not the data of the email account (eg. user(a)domain.com) and yes of /etc/passwd the dovecot inserts underscore before the domain (eg. _domain.com_user) when it would have to make this only between the domain and the user. Exists a way to solve this problem? Thanks in advance. -- Sergio Souza

1 0

[Dovecot] Listen on several (but not all) Interfaces
by Dominik Schulz 09 Jun '07

09 Jun '07

Hi, I'm using Dovecot 1.0rc15 from Debian stable/etch. I'd like to have Dovecot listen on more than one interface. It shall listen on one IPv4 Interface and on one IPv6 Interface. The comments in the sample configuration file say, that it's not possible to listen on more than one interface at a time. Sadly it's no option to me to listen on all interfaces. So I'd like to ask if there is a chance that Dovecot will support listening on several selected interfaces anytime soon? Thanks in advance for every helpful reply. Best Regards Dominik

5 4

[Dovecot] Dot Lock probelm resolution
by Stewart Dean 08 Jun '07

08 Jun '07

For the record/archive, so some other unfortunate dovecot implementer won't spend weeks figuring out this particular way dotlocks can have problems... here is what was trashing our dotlocks Basically, I was seeing this: May 14 15:59:58 mercury mail:warn|warning dovecot: IMAP(sdean): Our dotlock file /var/spool/mail/sdean.lock was deleted (kept it 1 secs) > May 14 15:59:58 mercury mail:err|error dovecot: IMAP(sdean): file_dotlock_delete() failed with mbox file /var/spool/mail/sdean: No such file or directory Timo justifiably blamed the usual suspect, NFS, but when I dug into the maillog to see what was going on when the locks were getting trashed, in almost all cases, NFS wasn't involved. And I had recompiled procmail so that it used the same locking strategy (and checked it), deactivated NFS client attribute caching, etc., etc. It turned out that my predecessor had done something 10 years ago that was arcane, inscrutable and kludgy in the .procmailrc file. This *purposefully* trashed the dotlock. Not knowing what it did when I took over (predecessor long gone, things in disarray), I left it in, because I worried that something would break if we removed it. We have perpetuated it in creation of all new accounts. This procmailrc stanza looks like this: ####### BEGIN SYS ADMIN ADDED LINES ####### ## !!!!!! Do not remove these lines !!!!!! ## They have been placed here by System Admin ## If removed, your mail will run slower and ## generate error messages!!!!!!!! LOCKFILE #removes preexisting lockfile LOG='lockfile $DEFAULT$LOCKEXT ' TRAP="rm -f $DEFAULT$LOCKEXT" :0 $DEFAULT ####### END OF SYS ADMIN ADDED LINES ####### # IF YOU ADD STUFF, DO IT ABOVE THIS BLOCK # I sent a note to the procmail mailing list hoping to get a clue of what is doing. Here are my Qs and their As: >> 2) Is it syntactically correct? > I think so, though highly obfuscated and semantically worthless. >> 3) Is what it's doing real/worthwhile? > No. My guess is it was a kludge to work around some error with an > older version of procmail, if it ever served any function at all. Since we removed it, there have been no dotlocking errmsgs in the syslog. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] User unknown in local recipient table? Dovecot LDA/Postfix
by Yu Chen 08 Jun '07

08 Jun '07

This probably is a postfix problem, but I think there are lots of postfix experts/users on this list, and have heard a lot good things about this list, so I am just giving it a try. Thanks in advance! I am using dovecot-1.0.0-8_56.src.rpm downloaded from atrpms.net, and rebuilt from it(rpmrebuild ...). Postfix is 2.4.3. I followed documents at http://wiki.dovecot.org/LDA and LDA/Postfix, and used passwd-file (created /etc/passwd.dovecot file) both as password Database and User database. I can send emails, but not receiving, keep getting the "User unknow error". Do I need to change the "local_recipient_map" in main.cf, and if so, how? Here are some related configuration: ########### dovecot -n ########### # /etc/dovecot.conf log_path: /var/log/dovecot.log ssl_ca_file: /etc/pki/dovecot/certs/ca-bundle.crt verbose_ssl: yes 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/libexec/dovecot/pop3-login login_greeting: Dovecot ready. verbose_proctitle: yes first_valid_uid: 102 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/mail_indexes/%d/%n mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle auth default: mechanisms: plain login executable: /usr/local/libexec/dovecot/dovecot-auth verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd-file args: /etc/passwd.dovecot socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 384 ############### postconf -n ################ alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 html_directory = /usr/share/doc/postfix-2.4.3-documentation/html inet_interfaces = $myhostname, localhost invalid_hostname_reject_code = 450 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man maps_rbl_reject_code = 450 mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain myhostname = my.host.com mynetworks = myip/24, 127.0.0.0/8 newaliases_path = /usr/bin/newaliases.postfix non_fqdn_reject_code = 450 queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.4.3-documentation/readme sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_tls_CAfile = /usr/share/ssl/certs/ca-bundle.crt smtp_tls_cert_file = /usr/share/ssl/certs/postfix.pem smtp_tls_key_file = /usr/share/ssl/certs/postfix.pem smtp_tls_session_cache_database = btree:/var/spool/postfix/smtp_tls_session_cache smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, permit_tls_clientcerts, reject_unauth_destination, check_relay_domains smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /usr/share/ssl/certs/ca-bundle.crt smtpd_tls_cert_file = /usr/share/ssl/certs/postfix.pem smtpd_tls_key_file = /usr/share/ssl/certs/postfix.pem smtpd_tls_loglevel = 2 smtpd_tls_session_cache_database = btree:/var/spool/postfix/smtpd_tls_session_cache tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_transport = dovecot Regards, C.Y =========================================== Yu Chen Howard Hughes Medical Institute Chemistry Building, Rm 182 University of Maryland at Baltimore County 1000 Hilltop Circle Baltimore, MD 21250 phone: (410)455-6347 (primary) (410)455-2718 (secondary) fax: (410)455-1174 email: chen(a)hhmi.umbc.edu ===========================================

2 1

[Dovecot] PAM info please
by Frank Bonnet 07 Jun '07

07 Jun '07

Hello I'm searching infos on using Dovecot with pam_ldap and FreeBSD 6.2 any pointers welcome :-) Thanks -- Frank

2 2

[Dovecot] Latest MANAGESIEVE patch -- how to start daemon?
by Andreas Ntaflos 07 Jun '07

07 Jun '07

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to invoke it? I haven't been able to find anything useful on that matter and there doesn't seem to be a TFM to R yet, the Wiki just links to [1]. What do I have to do? Did I forgot to patch something? I'd appreciate any insight on this subject! Thanks in advance! Andreas [1] http://dovecot.org/list/dovecot/2007-March/021130.html -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

5 8

[Dovecot] Quota Warning Message
by Gabriele Fergola 06 Jun '07

06 Jun '07

Hi to everyone, i try to implement in dovecot the quota warning message for the user but withouot success. I do the Patch found on the site but .. nothing happened. Anyone can help me please? Workino

1 0

[Dovecot] Replication plans
by Timo Sirainen 06 Jun '07

06 Jun '07

Several companies have been interested in getting replication support for Dovecot. It looks like I could begin implementing it in a few months after some other changes. So here's how I'm planning on doing it: What needs to be replicated: - Saving new mails (IMAP, deliver) - Copying existing mails - Expunges - Flag and keyword changes - Mailbox creations, deletions and renames - Subscription list - IMAP extension changes, such as ACLs I'll first talk about only master/slave configuration. Later then master/multi-slave and multi-master. Comments? Basic design ------------ Since the whole point of master-slave replication would be to get a reliable service, I'll want to make the replication as reliable as possible. It would be easier to implement much simpler master-slave replication, but in error conditions that would almost guarantee that some messages get lost. I want to avoid that. Both slave and master would be running a dovecot-replication process. They would talk to each others via TCP connection. Master would be feeding changes (transactions) to slave, and slave would keep replying how far it's committed the changes. So there would be an increasing sequence number sent with each transaction. Master keeps all the changes in memory until slave has replied that it has committed the changes. If the memory buffer gets too large (1MB?) because the slave is handling the input too slowly or because it's completely dead, the master starts writing the buffer to a file. Once the slave is again responding the changes are read from the file and finally the file gets deleted. If the file gets too large (10MB?) it's deleted and slave will require a resync. Master always keeps track of "user/mailbox -> last transaction sequence" in memory. When the slave comes back up and tells the master its last committed sequence, this allows the master to resync only those mailboxes that had changed. If this mapping doesn't exist (master was restarted), all the users' mailboxes need to be resynced. The resyncing will also have to deal with new mailboxes, ACL changes and such. I'm not completely sure yet how the resyncing will work. Probably the only important thing here is that it would be good if it would resolve any message UID conflicts (even though they shouldn't happen, see below) by comparing either the messages' MD5 contents, or with maildir it would be enough to just compare the maildir filename. It's possible that the slave doesn't die completely but only some transactions fail. This shouldn't normally happen, so the easiest way to handle it would be to try a full resync, and if that still fails stop the whole slave. Another way would be to just mark that one user or mailbox as dirty and try to resync it once in a while. imap, pop3 and deliver would connect to dovecot-replication either using UNIX sockets or POSIX message queue. Queue could be faster, but sockets would allow better security checks. Or I suppose it would be possible to send some kind of a small authentication token in each message with queues. The communication protocol would be binary and the existing dovecot.index.log format would be used as much as possible (making it simple for slave to append changes to mailboxes' dovecot.index.log). dovecot-replication process would need read/write access to all users' mailboxes. So either it would run as root or it would need to have at least group-permission rights to all mailboxes. A bit more complex solution would be to use multiple processes each running with their own UIDs, but I think I won't implement this yet. The replication would require support for shared mailboxes. That way the mailboxes could be accessed using the configured shared namespaces, for example "shared/<username>/INBOX". (LMTP server could be implemented in a similar way BTW) Configuration ------------- I'm not yet sure how this should work. The simplest possibility would be just to configure a single slave and everything would be replicated there. But it should be possible to split users into multiple slaves (still one slave/user). The most configurable way to do this would be to have userdb return the slave host. Hmm. Actually that could work pretty well if the userdb returned slave's name and each slave would have a separate socket/queue where dovecot-replication listens in. I'm not sure if they could all still be handled by a single dovecot-replication process or if there should be a separate one for each of them. The configuration would then be something like: # slave for usernames beginning with letters A..K replication users_a_k { host = slave1.example.com # other options? } # L..Z and others replication users_l_z_rest { host = slave2.example.com } Saving ------ This is the most important thing to get right, and also the most complex one. Besides replicating mails that are being saved via Dovecot, I think also externally saved mails should be replicated when they're first seen. This is somewhat related to doing an initial sync to a slave. The biggest problem with saving is how to robustly handle master crashes. If you're just pushing changes from master to slave and the master dies, it's entirely possible that some of the new messages that were already saved in master didn't get through to slave. So when you switch to using slave, those messages are gone. The biggest problem with this is that when saving new mails, they'll be assigned UIDs that were already used by the original master. If a locally caching client had already seen the UID from the original master, it'll think the message is the original one instead of the new one. So the newly added message pretty much gets lost, and if the user could expunge the message (thinking it's the original one) without ever even seeing it. This UID conflict could be avoided by making the master tell slave whenever it's saving new mails. The latency between master-slave communication could be avoided with a bit of a trick: - When beginning to save/copy a mail, tell slave to increase UID counter by one. Slave replies with the new highest-seen-UID counter. - UID allocation is done after all the mails are saved/copied within a transaction. At this stage wait until slave has replied that it has reserved UIDs at least as high as we're currently allocating (other processes could have caused it to get even higher). - If save/copy is aborted, tell the slave to decrease the UID counter by the number of aborted messages. - UID counter desync shouldn't happen, but if it does handle that also somehow. Then the UID allocation latency depends on how long it takes to write the message, and where the message comes from. With IMAP APPEND there's probably no wait required, unless the APPEND command and the whole message arrives in one IP packet. With deliver and copying it might have to wait a while. So the UID allocation should work with minimal possible latency. It could use a separate TCP connection to slave and maybe a separate high priority process in the slave that would handle only UID allocations. The above will make sure that conflicting UIDs aren't used, but it doesn't make sure that messages themselves aren't lost. If the master's hard disk failed completely and it can't be resynced anymore, the messages saved there are lost. This could be avoided by making the saving wait until the message is saved to slave: - save mail to disk, and at the same time also send it to slave - allocate UID(s) and tell to slave what they were, wait for "mail saved" reply from slave before committing the messages to mailbox permanently This would however add more latency than the simpler UID allocation counter. I don't know if it should be optional which way is used. Perhaps I'll implement the full save-sync first and if it seems too slow then I'll implement optionally the UID allocation counter. Save messages from imap/deliver would contain at least: 1. user name (unless using UNIX sockets, then it's already known) 2. mailbox name 3. UIDVALIDITY 4a) UID 4b) global UID, filename, offset and size of the message 4a) would be used with the UID allocation counter behavior. The message would be sent after the message was saved and UIDs were allocated. 4b) would be used with the wait-slave-to-save behavior. The message would be sent immediately whenever new data was received for the message, so possibly multiple times for each message. The last block would then contain size=0. After saving all the mails in a transaction, there would be a separate "allocate UIDs x..y for global UIDs a, b, c, d, etc." message which the slave then replies and master forwards the reply to imap/deliver. If the slave is down, or if a timeout (a few seconds?) occurs while waiting for the reply from slave, imap/deliver could just go on saving the message. If this is done it's possible that if the master also dies soon, there will be UID conflicts. But since this should be a rare error condition, it's unlikely that the master will die soon after a misbehaving slave. Copying ------- Copying has similar UID conflict problems than saving. The main difference is that there's no need to transfer message contents, which makes it faster to handle copies reliably. Copying could be handled with the UID allocation counter way described above. Since the message already exists in the server, there's no way that the message gets lost. So it would be possible to allow master and slave to go into desync, because the user would still find the message from the original mailbox. Move operation is done with "copy + mark \deleted + expunge" combination. This could be problematic if the master had managed to do all that before slave saw the COPY at all. Since the message isn't yet copied to the new mailbox in slave, clients wouldn't see it there, but locally caching clients might not see the message in the original mailbox either because they had already received EXPUNGE notification for it. So this should be avoided in some way. Perhaps it would be better to just treat copies the same way as saves: Require a notification from slave before replying to client with OK message. Alternatively the wait could be done at EXPUNGE command, as described below. Expunges -------- Losing expunge transactions wouldn't be too bad, because the worst that can happen is that the user needs to expunge the message again. Except that having an expunged message suddenly appear again in the middle of the mailbox violates IMAP protocol. I don't know if/how that will break clients. Solution here would again be that before EXPUNGE notifications are sent to client we'll wait for reply from slave that it had also processed the expunge. Flag and keyword changes ------------------------ Most likely doesn't matter if some of them are lost. If someone really cares about them, it would be possible to again do the slave-waiting for either all the changes or just when some specific flags/keywords change. Other changes ------------- Mailbox creations, deletions, renames and subscription changes could all be handled in a similiar way to flag/keyword changes. Handling changes implemented by IMAP extensions such as ACL is another thing. It's probably not worth the trouble to implement a special replication handler for each plugin. These changes most likely will happen somewhat rarely though, so they could be implemented by sending the whole IMAP command to slave and have it execute the command using a regular imap process. The commands could be marked with some "replication" flag so Dovecot knows that they need to be sent to slave. Although instead of executing a new imap process for each user (probably each command), it could be possible to use one imap process and just change the mailbox name in the command. So instead of eg. "setacl mailbox (whatever)" the IMAP process would execute "setacl shared/username/mailbox (whatever)". That would require telling Dovecot what parameter contains the mailbox name. Should be pretty easy to implement, unless some IMAP extensions want multiple mailbox names or the position isn't static. I can't think of any such extensions right now though. Master/multi-slave ------------------ Once the master/slave is working, support for multiple slaves could be added. The main thing to be done here is to have the slaves select which one of them is the new master, and then they'll have to sync the mailboxes with each others, because each of them might have seen some messages that others hadn't. This is assuming that save/etc. operations that are waiting for a reply from slave would wait for only one reply from the first slave that happens to respond. The number of slave replies to wait for could be also configurable, in case you're worried of a simultaneous master+slave crash. Multi-master ------------ After master/multi-slave is working, we're nearly ready for a full multi-master operation. The master farm will need global locking. Perhaps there is a usable existing implementation which could be used. In any case there needs to be a way to keeps track of what master owns what locks. The easiest way to implement multi-master is to assume that a single user isn't normally accessed from different servers at the same time. This wouldn't be a requirement, but it would make the performance better. For most users you could handle this by making sure that load balancer transfers all connections from the same IP to the same server. Or you could use a Dovecot proxy that transfers the connections. So, once the user is accessed only from one server, the operation becomes pretty much like master/multi-slave. You'll just need to be able to dynamically change the current master server for the user. This can be done by grabbing a global per-user lock before modifying the mailbox. The lock wouldn't have to be released immediately though. If no other server needs the lock, there's no point in locking/unlocking constantly. Instead the lock server could request the current lock owner to release the lock whenever another server wants it.

8 20

[Dovecot] multiple dovecot invocations
by Stewart Dean 05 Jun '07

05 Jun '07

I need to have multiple invocations of dovecot running, one for productions and then one or more for test/dev, doing things like trying different authentication methods, getting quota working, etc. I knew how to do this with inetd, but I have been convinced that direct invocation is preferable, so I need to know how to do multiple invocations of dovecot. I had thought that perhaps I could do this: dovecot -c /usr/local/etc/dovecot2.conf where dovecot2.conf has different different listen port parms. This I did, and while it does seem to work, I get this error in the syslog: > Jun 5 14:42:43 mercury mail:err|error dovecot: Socket already exists: /usr/local/var/run/dovecot/dict-server > Jun 5 14:42:43 mercury mail:crit dovecot: execv(/usr/local/libexec/dovecot/dict) failed: No such file or directo > ry > Jun 5 14:42:43 mercury mail:err|error dovecot: child 1437914 (dict) returned error 84 (exec() failed) How do I correctly run multiple dc instances? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

Re: [Dovecot] AIX mail quota plugin problems + dotlock problem resolved
by Timo Sirainen 05 Jun '07

05 Jun '07

On Tue, 2007-06-05 at 12:30 -0400, Stewart Dean wrote: > quotactl(Q_GETQUOTA, /) failed: Invalid argument So apparently this quotactl() call is wrong with AIX: if (quotactl(root->mount->mount_path, QCMD(Q_GETQUOTA, USRQUOTA), root->uid, (void *)&dqblk) < 0) { I don't know why though. You could try changing root->mount->mount_path to some actual mbox file path to see if it returns errors then. Except weren't your mailboxes NFS mounted? quotactl() doesn't work for NFS mounts at all. For NFS you could try this instead http://dovecot.org/patches/quota-rquotad.c

2 2

[Dovecot] IMAP traffic logging
by Chris Laif 05 Jun '07

05 Jun '07

Hi. I wonder if it is possible to log the number of bytes send in response to IMAP commands. Unfortunately there seems to be no config option similar to "pop3_logout_format". Courier writes a log file like this (header/body bytes): imaplogin: DISCONNECTED, ip=[::ffff:10.123.0.234], headers=0, body=0 Chris

3 4

[Dovecot] Dovecot Authentication Problem - Help pls!
by Odhiambo WASHINGTON 05 Jun '07

05 Jun '07

Hello List, This is dovecot 1.0.0 on FreeBSD 4.11-STABLE. I did not provide this information before:-) I am back again and I think I am edging closer to getting a solution. I have done some modifications and now dovecot gives me a different error message than before.... Here is what I have for the password_query and user_query password_query = SELECT popbox.cleartext AS password FROM popbox, domain \ WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' \ AND popbox.domain_name = domain.domain_name; +----------+ | password | +----------+ | boeing8 | +----------+ user_query = SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, \ 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' \ AND popbox.domain_name = 'demo.wananchi.com' AND \ popbox.domain_name = domain.domain_name; +--------------------------------------------+-----+-----+ | home | uid | gid | +--------------------------------------------+-----+-----+ | /var/spool/virtual/demo.wananchi.com/eddie | 69 | 6 | +--------------------------------------------+-----+-----+ When I test to connect to the pop3 daemon, this is what happens now: root@ns2]#telnet 0 7173 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Welcome. Dovecot is Ready to serve your emails. user eddie(a)demo.wananchi.com +OK pass boeing8 -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. ...and this is what dovecot writes to the log: [root@ns2]#less /var/log/dovecot.log dovecot: May 30 12:00:04 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVkZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 30 12:00:04 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT popbox.cleartext AS password FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:04 Info: auth(default): client out: OK 1 user=eddie(a)demo.wananchi.com dovecot: May 30 12:00:04 Info: auth(default): master in: REQUEST 2 36772 1 dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:05 Error: child 39853 (auth-worker) killed with signal 11 dovecot: May 30 12:00:05 Info: auth(default): master out: FAIL 2 dovecot: May 30 12:00:05 Info: pop3-login: Internal login failure: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured User's mail is stored in /var/spool/virtual/$domain/$user/{new,cur,tmp} The path /var/spool/virtual/ is owned by uid:gid 69:6, and is writeable by that uid. dovecot -n: # /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log protocols: imap pop3 listen(default): *:7143 listen(imap): *:7143 listen(pop3): *:7110 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: 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 login_user: exim login_greeting: Welcome. Dovecot is Ready to serve your emails. login_process_size: 64 login_max_processes_count: 200 verbose_proctitle: yes first_valid_uid: 69 first_valid_gid: 0 mail_extra_groups: dovecot:mail mail_location: maildir:/var/spool/virtual/%d/%n 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_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 outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: root group: wheel Here is a backtrace of the dovecot-auth crash: [root@ns2]#gdb /usr/local/libexec/dovecot/dovecot-auth dovecot-auth.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpam.so.1...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/compat/pkg/libmysqlclient.so.10...(no debugging symbols found)...done. Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/libsqlite3.so.8...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/lib/libz.so.2...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x805dc00 in userdb_blocking_lookup () (gdb) bt #0 0x805dc00 in userdb_blocking_lookup () #1 0x805dd50 in userdb_blocking_lookup () #2 0x806175a in sql_drivers_register_all () #3 0x8060d1c in sql_query () #4 0x805de62 in userdb_blocking_lookup () #5 0x8055724 in auth_stream_is_empty () #6 0x80557f4 in auth_stream_is_empty () #7 0x8055894 in auth_stream_is_empty () #8 0x80668ac in io_loop_handler_run () #9 0x80662a1 in io_loop_run () #10 0x805770f in main () #11 0x804fd52 in _start () (gdb) Please help! -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ Hindsight is an exact science.

4 10

[Dovecot] AIX mail quota plugin problems
by Stewart Dean 05 Jun '07

05 Jun '07

From reading the wiki for a filesystem quota, I took my shot at 1) building my binaries using the mods in AIXPluginsSupport 2) changing dovecot.conf and 3) putting the plugins in the library But I'm getting this error message when I invoke dovecot: Plugin imap_quota not found from directory /usr/local/lib/dovecot Error: imap dump-capability process returned 89 It would seem that a) I have the syntax or the parameters wrong b) I didn't get the changes to the AIX build environment right I've attached the dovecot -n output. Here are the details of what I did. 1) dovecot.conf =========== within the imap config section =========== # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap # SD 5/24/07 tryout FS quota plugin mail_plugins = quota imap_quota mail_plugin_dir = /usr/local/lib/dovecot/imap plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin. Multiple backends are supported: # dirsize: Find and sum all the files found from mail directory. # Extremely SLOW with Maildir. It'll eat your CPU and disk I/O. # dict: Keep quota stored in dictionary (eg. SQL) # maildir: Maildir++ quota # fs: Read-only support for filesystem quota #quota = maildir # SD 5/24/07 Try FS quota support quota = fs I've tried it as both mail_plugin_dir = /usr/local/lib/dovecot/imap and mail_plugin_dir = /usr/local/lib/dovecot 2) Both ways I see this error message: > 4229 root@mercury:/usr/local/etc ## dovecot > ILoading modules from directory: /usr/local/lib/dovecot > IModule loaded: /usr/local/lib/dovecot/lib10_quota_plugin.so > FPlugin imap_quota not found from directory /usr/local/lib/dovecot > Error: imap dump-capability process returned 89 > > 4272 root@mercury:/usr/local/lib/dovecot/imap ## dovecot > ILoading modules from directory: /usr/local/lib/dovecot/imap > IModule loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so > FPlugin imap_quota not found from directory /usr/local/lib/dovecot/imap > Error: imap dump-capability process returned 89 > 3) These directories have the following contents: 4292 root@mercury:/usr/local/lib/dovecot ## ls -al total 1168 drwxr-xr-x 3 root system 512 May 24 12:36 ./ drwxr-xr-x 7 root system 512 May 21 14:31 ../ -rw-r--r-- 1 root sys 292522 May 22 15:12 052207-1455-64bit-ssl.lib10_quota_plugin.a -rwxr-xr-x 1 root sys 904 May 22 15:12 052207-1455-64bit-ssl.lib10_quota_plugin.la* -rwxr-xr-x 1 root sys 270499 May 22 15:12 052207-1455-64bit-ssl.lib10_quota_plugin.so* drwxr-xr-x 2 root system 512 May 24 12:41 imap/ lrwxrwxrwx 1 root system 65 May 24 12:36 lib10_quota_plugin.a@ -> /usr/local/lib/dovecot/052207-1 455-64bit-ssl.lib10_quota_plugin.a lrwxrwxrwx 1 root system 66 May 24 12:36 lib10_quota_plugin.la@ -> /usr/local/lib/dovecot/052207- 1455-64bit-ssl.lib10_quota_plugin.la* lrwxrwxrwx 1 root system 66 May 24 12:36 lib10_quota_plugin.so@ -> /usr/local/lib/dovecot/052207- 1455-64bit-ssl.lib10_quota_plugin.so* root@mercury:/usr/local/lib/dovecot/imap ## ls -al total 152 drwxr-xr-x 2 root system 512 May 24 12:41 ./ drwxr-xr-x 3 root system 512 May 24 12:36 ../ -rw-r--r-- 1 root system 19250 May 22 15:12 052207-1455-64bit-ssl.lib11_imap_quota_plugin.a -rwxr-xr-x 1 root system 944 May 22 15:12 052207-1455-64bit-ssl.lib11_imap_quota_plugin.la* -rwxr-xr-x 1 root system 28645 May 22 15:12 052207-1455-64bit-ssl.lib11_imap_quota_plugin.so* lrwxrwxrwx 1 root system 66 May 24 12:36 lib10_quota_plugin.so@ -> /usr/local/lib/dovecot/052207- 1455-64bit-ssl.lib10_quota_plugin.so* lrwxrwxrwx 1 root system 75 May 24 12:36 lib11_imap_quota_plugin.a@ -> /usr/local/lib/dovecot/ima p/052207-1455-64bit-ssl.lib11_imap_quota_plugin.a lrwxrwxrwx 1 root system 76 May 24 12:36 lib11_imap_quota_plugin.la@ -> /usr/local/lib/dovecot/im ap/052207-1455-64bit-ssl.lib11_imap_quota_plugin.la* lrwxrwxrwx 1 root system 76 May 24 12:36 lib11_imap_quota_plugins.so@ -> /usr/local/lib/dovecot/i Any suggestions? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 2

[Dovecot] testink
by Timo Sirainen 05 Jun '07

05 Jun '07

# Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". #imap_listen = * #pop3_listen = *

3 6

[Dovecot] Is there a "connect acl" ?
by Oliver Schulze L. 05 Jun '07

05 Jun '07

Hi, I have been reading the acl documentation and it seems that a "connect acl" is not available. I need to limit the users that can login in an IP number, is that posible with dovecot 1.0? (i.e. only these users can login from the Internet) Or a new plugin should be written? It is complicated to do that? Thanks Oliver -- Oliver Schulze L. | http://tinymailto.com/oliver Asuncion - Paraguay | http://www.solojuegos.mobi

4 5

[Dovecot] Backing up mail?
by Knute Johnson 04 Jun '07

04 Jun '07

My mail server is running on a Fedora FC5 box. I need to move the mail server to another computer and so I need to back up my user's mail and move it. I have found mail in /var/spoo/mail/[users] and in their home directories there is a 'mail' directory. All users have an 'Inbox' file that is empty and I think the one IMAP user has a 'Trash' file that is huge! Are those the only files I need to copy or are there others lurking out there that I don't know about? Thanks, -- Knute Johnson Molon Labe...

1 0

[Dovecot] tweaking performance
by Paul A 04 Jun '07

04 Jun '07

Hi, I was wondering if anyone had some ideas on what I can tweak to gain more performance. We have tome timeouts reports on pop3 during heavy load periods. Using imap/pop3 with maildir with 7,000 users using mostly pop3. # /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/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 login_greeting: Cape.Com D-V.1 wpam - ready. login_processes_count: 16 login_max_processes_count: 500 max_mail_processes: 9000 mail_location: maildir:/home/%1u/%u/Maildir maildir_copy_with_hardlinks: 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_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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v.%u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: count: 6 passdb: driver: pam userdb: driver: passwd TIA, PA

2 1

[Dovecot] dovecot-shared tries to fchown index+control files but fails
by Adam McDougall 04 Jun '07

04 Jun '07

I have some public mailboxes setup in 1.0.0, location = maildir:/egr/mail/shared/org:CONTROL=%h/Maildir/dovecot/public/control/org:INDEX=%h/Maildir/dovecot/public/indexes/org I also have a dovecot-shared file in the maildir folders so messages that are added to the inbox get a decent set of default permissions. However, I think dovecot is also trying to fchown the index files (stored in a user home directory, far away from the shared mail) to match the owner of the dovecot-shared file. When I rename dovecot-shared, these errors (apparently harmless at this point) go away: May 24 18:45:35 hostname dovecot: IMAP(username): fchown(/home/username/Maildir/dovecot/public/control/org/.mailfolder/dovecot-uidlist) failed: Operation not permitted May 24 18:45:35 hostname dovecot: IMAP(username): fchown() failed with file /home/username/Maildir/dovecot/public/indexes/org/.mailfolder/dovecot.index.log: Operation not permitted At this point it is just clogging up the log, but I see two issues: 1. Isn't dovecot already running as the imap user, so as long as that user isn't root, it shouldn't be possible to change file owners at all. This is the behavior I see of dovecot-shared on new mail files, that is the group and file mode from dovecot-shared are applied, but not the owner. 2. Since these kind of metadata files aren't generally supposed to be shared anyway, why would it even want to change the permissions? Especially since I have them stored in a place where the user has ownership already. Please let me know if I am missing something, or a behavior change is needed. Thanks.

2 4

[Dovecot] Client certificate verification/authentication
by eizert 04 Jun '07

04 Jun '07

I would like to use Client certificate verification/authentication. My MTA used this function. I've a problem to make a valid certificate. For my MTA i used : openssl req -new -nodes -x509 -keyout user_key.pem -out user_req.pem -days 365 openssl ca -out user_signed.pem -infiles user_req.pem openssl pkcs12 -in user_signed.pem -inkey user_key.pem -out user.p12 -export -name "user@hotsname" user.p12 match in my MTA Not in Dovecot... In my log, i've simply : dovecot: auth(default): Client didn't present valid SSL certificate Also, in the documentation The username is taken from the subject's DN's CommonName <http://wiki.dovecot.org/CommonName> field (using OpenSSL's X509_NAME_get_text_by_NID() function). But when i used openssl req -new -nodes -keyout user_key.pem -out user_req.pem -days 365 my common name is my hostname not my username. I don't think that the option -name user@hostname (in manpage openssl :: -name is friendly name)... Sorry but it's ambiguous for me...

2 4

[Dovecot] dovecot-sieve-1.0 (hg) does not build
by Bernhard Schmidt 04 Jun '07

04 Jun '07

Hi, the dovecot-sieve plugin from the hg repository (http://hg.dovecot.org/dovecot-sieve-1.0/) does not build against current dovecot-1.0 repository. /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o libsieve.la /usr/src/dovecot-1.0/src/lib/liblib.a gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -DENABLE_REGEX -o sievec sievec.o map.o imparse.o /.libs/libsieve.a /usr/src/dovecot-1.0/src/lib/liblib.a /.libs/libsieve.a(script.o): In function `sieve_script_parse': /usr/src/dovecot-sieve-1.0/src/libsieve/script.c:140: undefined reference to `yylineno' /.libs/libsieve.a(sieve.o): In function `sieveerror': /usr/src/dovecot-sieve-1.0/src/libsieve/sieve.y:568: undefined reference to `yylineno' /.libs/libsieve.a(sieve.o): In function `sieveparse': /usr/src/dovecot-sieve-1.0/src/libsieve/sieve.c:1644: undefined reference to `sievelex' /.libs/libsieve.a(sieve.o): In function `sieve_parse': /usr/src/dovecot-sieve-1.0/src/libsieve/sieve.y:551: undefined reference to `yyrestart' /.libs/libsieve.a(addr.o): In function `addrparse': /usr/src/dovecot-sieve-1.0/src/libsieve/addr.c:1289: undefined reference to `addrlex' collect2: ld returned 1 exit status make[3]: *** [sievec] Error 1 make[3]: Leaving directory `/usr/src/dovecot-sieve-1.0/src/libsieve' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/dovecot-sieve-1.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/dovecot-sieve-1.0' make: *** [all] Error 2 dovecot-sieve-1.0.1.tar.gz builds fine. 1.0.1 is from January 2007, the last changes in the hg repository are three months ago, but none of them look like they would be causing this issue. Also there is no r_1_0_1 tag. It looks to me like 1.0.1 is something quite different to the hg-repository, right? Does the latter compile against anything at the moment? Thanks, Bernhard

2 3

[Dovecot] Sharing nested folders / maildir variations?
by SeattleServer.com 04 Jun '07

04 Jun '07

Hey all, So I've got a shared namespace in dovecot where users can, via a custom control panel, share their folders into (which creates a symlink) in order to allow anyone on their domain to access it. I store mail in maildir. The issue is that when people share folders, they expect that when they make subfolders, those are automatically shared as they are contained within it. According to the Maildir++ specification, "Can folders have subfolders, defined in a recursive fashion? The answer is no. If you want to have a client with a hierarchy of folders, emulate it. Pick a hierarchy separator character, say ":". Then, folder foo/bar is subdirectory .foo:bar." It says some other stupid things too though that nobody seems to actually follow, and I've never actually seen anything but a '.' used as the delimiter... The same is true in IMAPdir: "As with Maildir++, submailboxes can not be represented in a recursive fashion in the file system. The mailbox' representation name will contain the soft hierarchy delimiter character dot '.', and all mailboxes must reside in the same root level directory." I don't understand the reasoning behind avoiding recursion, honestly. If somebody wants to enlighten me on that one, it would be appreciated. i.e. instead of: .Folder/{cur,new,tmp} .Folder.SubFolder1/{cur,new,tmp} .Folder.SubFolder1.foo/{cur,new,tmp} .Folder.SubFolder1.bar/{cur,new,tmp} .Folder.SubFolder2/{cur,new,tmp} We'd have: .Folder/{cur,new,tmp} .Folder/.SubFolder1/{cur,new,tmp} .Folder/.SubFolder1/{cur,new,tmp} .Folder/.SubFolder1/.foo/{cur,new,tmp} .Folder/.SubFolder1/.bar/{cur,new,tmp} .Folder/.SubFolder2/{cur,new,tmp} That would both solve my issue and be a lot more convenient when browsing/scripting around maildirs (i.e. "cd ../.foo" vs "cd ../.Folder.Subfolder1.foo"). It seems to me that this would be a really easy thing to add support for via the config option used to choose between maildir/mbox/dbox. Call it rmaildir or somesuch... Thoughts? Cheers, -- Casey Allen Shobe | mailto:casey@shobe.info | http://casey.shobe.info SeattleServer.com, inc. | http://seattleserver.com

2 3

[Dovecot] Dovecot waking every 50ms when doing nothing
by Ross Burton 04 Jun '07

04 Jun '07

Hi, My laptop runs a local IMAP server so that I'm immune from breaking my mail client, and when playing around with powertop I discovered that Dovecot (in particular imap-login) wakes up every 1000ms and then every 50ms even when no clients are connected. A bit of stracing shows this: gettimeofday({1180875699, 667917}, NULL) = 0 <0.000010> poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 5, 999) = 0 <0.999595> gettimeofday({1180875700, 667627}, {4294967236, 0}) = 0 <0.000007> gettimeofday({1180875700, 667670}, NULL) = 0 <0.000007> poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 5, 0) = 0 <0.000006> gettimeofday({1180875700, 667762}, {4294967236, 0}) = 0 <0.000007> gettimeofday({1180875700, 667801}, NULL) = 0 <0.000006> poll([{fd=7, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 5, 999) = 0 <0.999699> gettimeofday({1180875701, 667638}, {4294967236, 0}) = 0 <0.000010> Is there any reason why dovecot wakes up so frequently even when there is apparently nothing to do? If it is to perform some routine task, can this timeout be extended? There are many daemons on my machine (lighttpd is another) that are waking up every second when nothing is happening, and each of these is contributing to waking the CPU from sleep. Cheers, Ross -- Ross Burton mail: ross(a)burtonini.com jabber: ross(a)burtonini.com www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF

7 16

[Dovecot] frequent index rebuilds versus disabled indexes
by Justin McAleer 04 Jun '07

04 Jun '07

Ok, here's the short and sweet version of my dilemma. I have a group of servers mounting a shared NFS device to hold mail data for many different domains. Is it worth the load balancing management nightmare of setting up dedicating smtp, pop, and imap to one server (failing over to another in the group if the server goes down) to keep indexes on local disk? It's very tempting to just disable indexes and not worry about which server a user hits, and considering the vast majority of our 170,000 accounts only have about a 20MB quota, I'm not sure indexes will help that many users. Although, I guess I would need to work out something for the few huge accounts we do have.

2 1

[Dovecot] Quota handling - v2 - updated FR
by Charles Marcus 04 Jun '07

04 Jun '07

This revised proposal for a Feature Request is the result of my desire to implement quotas, but not have the attendant headaches that inevitably accompany its implementation. Ralf Hildebrandt wrote: > I have to face it, my users are retards: Is there any other kind of user? ;) <snip> > Thus I need a feature in dovecot that will tell them via email: > > Level1: "You ALMOST exceeded your quota, you're at 90% now" > Level2: "You're very close to exceededin your quota, you're at 95% > now" > Level3: "Would you please clean up now? You're at 99% now" What I'd *really* like to see implemented is something along the lines outlined below - but of course, this will depend entirely on whether or not Timo thinks it is doable - or desirable... I'm thinking this would be best handled by the Quota plug-in - either as part of the current one, or as a separate/different one... *** 1. Have a 'special' user-specific folder (by special, I mean like the Drafts, Sent, Templates folders) that dovecot controls. For purposes of this FR, call it the 'over-quota' folder. Question: could the .tmp folder be used for this? No sense in reinventing the wheel if necessary... and then if someone migrated from dovecot to something else, and messages were left in there from an over-quota condition, that other solution would most likely just move these to .new the first time it ran, right? Or, possibly, could dovecot create a new one maybe, .oqt (for over-quota), and store the queued messages there until the over-quota condition was rectified? Anyway, the main thing is, this folder should be essentially hidden from the user so they do *not* have access to it, and should temporarily hold messages that come in that are unable to be delivered due to an over-quota condition. *** 2. Make dovecot aware of and use a special 'Quota Status' message that it uses to inform a user that they are over quota. This message should be able to be customized, with variables (like, for example, it should list the messages that are currently being prevented from being moved to the Inbox - including, optionally, the Subject, the sender, date/time, attachments, size, etc - as well as provide general quota information (ie, how close to or over quota they are, and how much they'd need to delete or move to Local Folders to allow delivery of all of the messages being held), and lastly, any custom information the System Admin wanted to provide - like, maybe, specific instructions for how to move messages to Local Folders, how to request additional storage allowance, etc. *** 3. When user is over quota, have LDA deliver to the folder referenced above (# 1) - (yes, accept the message for final delivery from the sending mta), and then update the Quota Status message and move it to the Inbox. Optionally, a bounce/notification could be generated to the sender, informing them that their message is being 'held in queue' or something to that effect, due to the recipient being over-quota. *** 4. Once the user deletes enough mail to come back under quota, dovecot would then move messages from the 'over-quota' folder to his Inbox. Ok, again, am willing to hear *valid* reasons how/why this is a terrible idea... :) -- Best regards, Charles

6 10

[Dovecot] delivery and quota question
by Arkadiusz Miskiewicz 04 Jun '07

04 Jun '07

Hi, I'm considering using delivery for delivering emails. The question is about quota. Does delivery check quota for single maildir or for entire collection of user folders? Example: /var/mail/user/{new,cur,tmp} /var/mail/user/.Some_Folder/{new,cur,tmp} /var/mail/user/.Some_Other_Folder/{new,cur,tmp} Can I somehow get deliver checking size for all these folders? I need quota per user not per folder. -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

2 1

[Dovecot] Simple questions about Quota
by Venilton Junior 04 Jun '07

04 Jun '07

Hi folks, hope that get some help for some doubts :P I've configured dovecot in a clustered environment 3 X HP Proliant DL380+RHEL ES 4.0+EVA4000+GFS. Everything is working great. But, when I putted this cluster on production, I had some problems with quota+ldap in my dovecot. Here follows my configuration: /etc/dovecot.conf last_valid_gid = 101 maildir_copy_with_hardlinks = no login_greeting = Internet ready. disable_plaintext_auth = no auth_default_realm =domain.com.br protocol imap { mail_plugins = imap_quota quota } protocol lda { postmaster_address = postmaster(a)domain.com.br <mailto:postmaster@domain.com.br> mail_plugins = quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } auth default_with_listener { mechanisms = plain login userdb ldap { args = /etc/dovecot-ldap.conf } passdb ldap { args = /etc/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } } } plugin { quota = maildir } /etc/dovecot-ldap.conf ... user_attrs = mail,homeDirectory,,,,quota=quota=maildir:storage user_filter = (&(objectClass=VirtualMailAccount)(mail=%u)(accountActive=TRUE)(delete=F ALSE)) I'm heaving heavy load of e-mails in this environment, so this problem started to happen: Almost all users have 100MB of quota, that's ok for us and we are storing 102400 at our ldap. But, when I put this configuration working on, all clients receive overquota messages. If I'm using quota information in my ldap server, do I have to use this option in my dovecot.conf file? plugin { quota = maildir } Tnx for any help and/or tips. Regards, Venilton C. Junior HP Certified Professional Sercompe Computadores Ltda. Office: +55 47 3431-9700 Fax: +55 47 3431-9747 Mobile: +55 47 9653-5872 www.sercompe.com.br <http://www.sercompe.com.br/>

2 1

[Dovecot] Dovecot and Seamonkey/Mozilla "delete attachment"
by Bryce Nesbitt 04 Jun '07

04 Jun '07

I'm having persistent trouble deleting larger attachments from messages in Mozilla/Seamonkey mail, and I'm thinking it may be related to Dovecot. A bug report is over at https://bugzilla.mozilla.org/show_bug.cgi?id=381759 I do not have the version number of Dovecot available, unless you know how to get it from the IMAP prompt: > telnet idiom.com 143 Trying 216.240.32.1... Connected to idiom.com. Escape character is '^]'. * OK Dovecot ready. How can I track this down more? Is anyone using Seamonkey and this particular new feature (delete the attachment, but keep the message body intact)?

2 1

[Dovecot] Error: no authentication failed
by gaoqiang.qian＠nokia.com 04 Jun '07

04 Jun '07

Hi, I have installed the dovecot on my redhat linux host. But when I log in with dovecot/test I got Error: no authentication failed after I got ok dovecot ready when I connect to local host. dovecot/test was set in the password.dovecot file. But I do not know how can I use this username and password in the configuration file. Could anyone give me a hand to let me know how to configurate the username and password for login. Thanks

2 1

[Dovecot] Overriding IMAP commands
by Tony Tsang 04 Jun '07

04 Jun '07

Hi all, I am writing a plugin to override some built-in imap commands. But when client logs out, imap segfaults during unregistering commands. What is the correct procedure for overriding imap commands in dovecot? Thanks. Tony Tsang.

2 1

Re: [Dovecot] Namespace Problems
by Kenny Dail 04 Jun '07

04 Jun '07

> Hi all, > > after an update from dovecot beta version to 1.0.0.-1 today morning I > had different effects: > thunderbird-, kmail-, Apple-clients, pine and squirrelmail could > receive email correct with imaps. But not MSOutlook!!! > Varying the namespace configurations in dovecot.conf I got different > results with MSOutlook working but with thunderbird, squirrelmail etc. > all folders are displayed but not the root Inbox etc. > Its important to know that I migrated from courier-imap to dovecot. > > My well working namespace config BEFORE upgrade to 1.0.0-1: > > Here my actual namespace configs: > > namespace private { > separator = > prefix = INBOX. > inbox = no > hidden = no > } > namespace private { > separator = / > prefix = INBOX/ > inbox = no > hidden = yes > } > namespace private { > separator = . > prefix = INBOX. > inbox = yes > hidden = yes > } > Try it using only one namespace which matches what you are really doing. With 1.0 this works for me with all clients I've tried, including Apple. namespace private { separator = . prefix = INBOX. inbox = yes hidden = no } > In varying inbox and hidden keywords I found this configuration. Most > things are working with this but in squirrelmal I can't access inbox, > the main folder. > > How do I have to configure that everythings works satisfying?? > > dovecot.conf and dovecot-sql.conf I send in the attachment. instead of sending dovecot.conf, next time use dovecot -n -- Kenny Dail <kend(a)amigo.net>

3 2

[Dovecot] Stop Maildir appending to path
by Henry 04 Jun '07

04 Jun '07

dovecot -n: # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps ssl_listen: 208.xxx.xxx.xxx login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_debug: yes auth default: passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail ---------------------- dovecot version: 1.0.rc15 ---------------------- Debian Etch (Stable) on AMD64

3 2

[Dovecot] What are they trying to do here?
by Jon Slater 04 Jun '07

04 Jun '07

Hi! I’m new to the list, and I’m not really having a ‘problem’, but I’m seeing something in my log files that I wonder if I should be concerned. I’ve been using Dovecot (dovecot-0.99.14-8.fc4) on my Fedora Core 4 (kernel 2.6.17-1.2142_FC4) machine from quite some time. For the last few days, I’ve been seeing this in my daily ‘Logwatch’ e-mail: dovecot: Authentication Failures: rhost= : 139 Time(s) root: 13 Time(s) Unknown Entries: check pass; user unknown: 139 Time(s) So it looks pretty obvious that someone (using root and an assortment of other login names) is trying to access by dovecot server. My first ‘issue’ is I can’t find a log file anywhere that tells me the IP address of the attacker. I see a series of ‘authentication failure’ messages in my /log/messages file: May 29 21:23:35 mydomainname dovecot(pam_unix)[15317]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root May 29 21:23:35 mydomainname dovecot(pam_unix)[15318]: check pass; user unknown May 29 21:23:35 mydomainname dovecot(pam_unix)[15318]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= May 29 21:23:36 mydomainname dovecot(pam_unix)[15320]: check pass; user unknown May 29 21:23:36 mydomainname dovecot(pam_unix)[15320]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= But I don’t find anything in any other log files to indicate where this is coming from. Secondly, I’m wondering if I have anything to be concerned about. Thanks in advance for you help! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.3/824 - Release Date: 5/29/2007 1:01 PM

2 1

[Dovecot] dovecot scaling issue?
by it-dovecot＠ml.epigenomics.com 04 Jun '07

04 Jun '07

Hi! We are running dovecot-imapd on Debian sarge out of the backports.org packages (version 1.0.rc15-1~bpo1). We have ~ 80 clients using secure IMAP. I understand that imap-login has to run for every SSL connection. Thus I already increased the max value for the number of imap-login processes. But unfortunately dovecot is unresponsive from time to time. Where can I tune the installation? Do I need to upgrade to 1.0.0, for which no backported packages exist for Debian sarge? This is the output of dovecot -n: log_timestamp: %Y-%m-%d %H:%M:%S listen: *:143 ssl_listen: *:993 ssl_cert_file: /etc/courier/imapd.pem ssl_key_file: /etc/courier/imapd.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 512 verbose_proctitle: yes mail_location: maildir:~/.Maildir:INDEX=/var/cache/dovecot/INBOX.%u:CONTROL=/var/cache/dovecot/INBOX.%u mail_full_filesystem_access: yes maildir_stat_dirs: yes maildir_copy_with_hardlinks: yes namespace: type: private separator: . prefix: INBOX. inbox: yes namespace: type: public separator: . prefix: shared. location: maildir:~/.Maildir/shared:INDEX=/var/cache/dovecot/shared.%u:CONTROL=/var/cache/dovecot/shared.%u auth default: verbose: yes passdb: driver: passwd userdb: driver: passwd Homedirectories are on NFS, /var/cache/dovecot is a local filesystem. Clients are mostly Thunderbird, where max connection to IMAP server is set to 5. Greetings -- Robert Sander Senior Manager Information Systems Epigenomics AG Kleine Praesidentenstr. 1 10178 Berlin, Germany phone:+49-30-24345-0 fax:+49-30-24345-555 http://www.epigenomics.com robert.sander(a)epigenomics.com

2 1

[Dovecot] Dovecot support for smd5 and ldap-md5
by Eric and Barbara Sammons 04 Jun '07

04 Jun '07

Working with a dovecot migration, I am curious what version (if any) of Dovecot (dovecot-auth) supports SMD5 and ldap-MD5 when using Dovecot -> OpenLDAP direct binding? Thank you! Eric

2 1

[Dovecot] TLS errors when vodafone connecting to dovecot server.
by Andrew Pounce 04 Jun '07

04 Jun '07

Hi, I've been trying to setup the vodafone email sync ( provided by visto apparently ) and have not been able to do so - I'm getting an error message in my mail logs which looks as if there is a problem with certificates somewhere. May 31 16:49:39 imap dovecot: imap-login: SSL_accept() failed: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate unknown [206.124.112.22] Thunderbird has no problems with using TLS against this server and I'm not entirely sure if dovecot (or openssl ) is generating the message or if it is something being passed from the remote end. I've had a look around but not found anything on the web pages. Thanks, -Andrew -- Andrew Pounce - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Don't look now, but the man in the moon is laughing at you.

2 1

[Dovecot] CMU Sieve pluigin missing proper charset support
by Jan Srzednicki 04 Jun '07

04 Jun '07

Hello, After testing the Sieve plugin for the LDA, I have noticed that it does not handle charset issues properly. IETF draft says: 4.3. Subject and From Parameters The ":subject" parameter specifies a subject line to attach to any vacation response that is generated. UTF-8 characters can be used in the string argument; implementations MUST convert the string to [RFC2047] encoded words if and only if non-ASCII characters are present. Implementations MUST generate an appropriate default subject line as specified below if no :subject parameter is specified. (see http://tools.ietf.org/html/draft-ietf-sieve-vacation-07) The problem is that the dovecot plugin does not convert the string to RFC2047 encoded words, it treats it literally and thus sends malformed (from RFC's point of view) message - with improper Subject field encoding. Any chances of getting that fixed? greetings, -- Jan Srzednicki w(a)expro.pl

2 1

[Dovecot] Error starting dovecot 1.0.0 /var/run/dovecot/auth-master failed: No such file or directory
by Yashesh Bhatia 01 Jun '07

01 Jun '07

Hello: i'm trying a tutorial (http://workaround.org/articles/ispmail-etch/en.html) for setting up postfix / dovecot but am getting some errors when i try to start dovecot here's some details of the enviromnent. (Fedora Core 6) $ uname -a Linux foo.com 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux $ ./dovecot --version 1.0.0 $ ./dovecot -n # /opt/dovecot-1.0.0/etc/dovecot.conf protocols: imap imaps pop3 pop3s ssl_disable: yes login_dir: /opt/dovecot-1.0.0/var/run/dovecot/login login_executable(default): /opt/dovecot-1.0.0/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.0.0/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.0.0/libexec/dovecot/pop3-login mail_location: maildir:/var/spool/foomail/%d/%n mail_executable(default): /opt/dovecot-1.0.0/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.0.0/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.0.0/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot-1.0.0/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.0.0/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.0.0/lib/dovecot/pop3 auth default: passdb: driver: pam passdb: driver: sql args: /opt/dovecot-1.0.0/etc/dovecot_sql.conf userdb: driver: passwd userdb: driver: static args: uid=721 gid=721 home=/var/spool/foomail/%d/%n allow_all_users=yes 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: foomail $ now when i try to start dovecot it dies giving the following error message in /var/log/maillog Jun 1 20:30:16 foo dovecot: Dovecot v1.0.0 starting up Jun 1 20:30:16 foo dovecot: auth(default): bind(/var/run/dovecot/auth-master) failed: No such file or directory Jun 1 20:30:16 foo dovecot: auth(default): net_listen_unix(/var/run/dovecot/auth-master) failed: No such file or directory Jun 1 20:30:16 foo dovecot: Auth process died too early - shutting down Jun 1 20:30:16 foo dovecot: child 9760 (auth) returned error 89 I've read the http://wiki.dovecot.org/CompilingSource but am stuck now with this issue. i also googled around a bit but could get any more information about this problem. any help is appreciated. thanks in advance. yashesh bhatia. ---------------------------------------------------------------- Go Pre http://www2.localaccess.com/rlalonde/pre.htm ----------------------------------------------------------------

1 1

[Dovecot] SSHA salt?
by Andreas Baitis 01 Jun '07

01 Jun '07

Hi there, I was wondering if someone could explain how dovecot/dovecotpw produces salt for use in ssha passwords, I'd like to replicate this in PHP so I can write my passwords from php in ssha instead of just sha1. Thanks in advance, Andrea Baitis

1 1

[Dovecot] Dovecot authentication for PostFix, anyone?
by Marco Fioretti 31 May '07

31 May '07

Greetings, the postfix sasl readme, http://www.postfix.org/SASL_README.htm says: >Dovecot provides an [authentication alternative to Cyrus] that may be worth considering. In principle, I like the idea of doing without Cyrus, since I have to run an IMAP server anyway and had already chosen Dovecot. The question is if that page is up to date and if you could share comments or, if they exist, safer/more efficient ways to use Dovecot as authentication server for PostFix, as well as any other relevant tips and tricks TIA, Marco

4 3

[Dovecot] Dovecot Authentication Problem (REVISED)
by Odhiambo WASHINGTON 31 May '07

31 May '07

Hello List, I am back again and I think I am edging closer to getting a solution. I have done some modifications and now dovecot gives me a different error message than before.... Here is what I have for the password_query and user_query password_query = SELECT popbox.cleartext AS password FROM popbox, domain \ WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' \ AND popbox.domain_name = domain.domain_name; +----------+ | password | +----------+ | boeing8 | +----------+ user_query = SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, \ 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' \ AND popbox.domain_name = 'demo.wananchi.com' AND \ popbox.domain_name = domain.domain_name; +--------------------------------------------+-----+-----+ | home | uid | gid | +--------------------------------------------+-----+-----+ | /var/spool/virtual/demo.wananchi.com/eddie | 69 | 6 | +--------------------------------------------+-----+-----+ When I test to connect to the pop3 daemon, this is what happens now: root@ns2]#telnet 0 7173 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Welcome. Dovecot is Ready to serve your emails. user eddie(a)demo.wananchi.com +OK pass boeing8 -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. ...and this is what dovecot writes to the log: [root@ns2]#less /var/log/dovecot.log dovecot: May 30 12:00:04 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVkZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 30 12:00:04 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT popbox.cleartext AS password FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:04 Info: auth(default): client out: OK 1 user=eddie(a)demo.wananchi.com dovecot: May 30 12:00:04 Info: auth(default): master in: REQUEST 2 36772 1 dovecot: May 30 12:00:04 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 69 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name dovecot: May 30 12:00:05 Error: child 39853 (auth-worker) killed with signal 11 dovecot: May 30 12:00:05 Info: auth(default): master out: FAIL 2 dovecot: May 30 12:00:05 Info: pop3-login: Internal login failure: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured The output of dovecot -n: # /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log protocols: pop3 listen: *:7173 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login login_greeting: Welcome. Dovecot is Ready to serve your emails. login_process_size: 64 login_max_processes_count: 200 verbose_proctitle: yes first_valid_uid: 69 first_valid_gid: 6 mail_extra_groups: exim mail_location: maildir:/var/spool/virtual/%d/%n mail_debug: yes mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_uidl_format: %Mf pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 user: root group: wheel User's mail is stored in /var/spool/virtual/$domain/$user/{new,cur,tmp} The path /var/spool/virtual/ is owned by uid:gid 69:6, and is writeable by that uid. I'd be happy to use a second brain and a third eye to help me figure out the problem. -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ Democracy is a device that insures we shall be governed no better than we deserve. -- George Bernard Shaw

1 1

[Dovecot] dovecot performance question
by Paul A 30 May '07

30 May '07

Hi, using the latest dovecot with pop3/imap. Using mostly outlook 2003 for pop3 and squirrel mail imap. I have a lot of users reporting back that imap is very slow. We average about 300 imap and another 700 pop session at any given time. Here's my config: disable_plaintext_auth: no login_dir: /usr/local/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 login_greeting: Cape.Com D-V.1 ready. login_processes_count: 14 max_mail_processes: 9000 mail_location: maildir:/home/%1u/%u/Maildir 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_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 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v.%u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: count: 4 passdb: driver: pam userdb: driver: passwd I'm trying to figure out what im doing wrong, I was seeing the same performance issues with .99. Here's what im seeing for connections, [root@pop etc]# ps aux | grep pop3 | wc -l 562 [root@pop etc]# ps aux | grep imap | wc -l 254 [root@pop etc]# I am having a time issue on this server and im not sure if its affecting dovecot. May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. May 29 11:42:31 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. May 29 11:42:42 pop dovecot: POP3(xxx): Time just moved backwards by 1 seconds. I'll sleep now until w e're back in present. Thanks, P

3 3

[Dovecot] Index file rewrite status
by Timo Sirainen 30 May '07

30 May '07

The biggest problem with getting v1.0 out was getting its index file code stable. v1.1 plans included doing large changes to the index file code, so it's important to get the new code stable as soon as possible. Since I've managed to stay pretty productive for the last few weeks, I've been mostly just coding the index changes. Once I'm sure that the code is again fully working I'll commit it to hg, relax a bit and then I'll again start answering mails in this list. It looks like the code is almost working, but it's still giving failures once in a while. Below are anyway a few benchmarks for you to see how it's progressing. I haven't yet done all the optimizations I've planned, but looks like it already gives 25-30% better performance in cydir tests. The cydir benchmarks are the most important ones because cydir relies completely on index files, so the benchmarks are practically index benchmarks. And the 25-30% is mostly about CPU usage I think, reduced dovecot.index file rewrites will help with disk I/O as well. The new index code should be pretty NFS friendly. I think there is going to be only one place where I'll need to force attribute cache flush and then probably a couple of places where data cache needs to be flushed (I'm not exactly sure about that yet, I'll have to know more about NFS data caching). One other thing I'm hoping to implement is that the index functions would almost never fail. If anything breaks, the indexes should be moved to memory. Any corrupted data should be ignored and anything that looks good would still be used (important with cydir/dbox). I've even managed to remove about 500 lines of code: 26 files changed, 3258 insertions(+), 3753 deletions(-) (about 2000 insert+deletions are just cut&pasting code to different files) Append-only tests: mmap_disable=no, fsync_disable=yes Current hg (before index rewrite), cydir: ./imaptest - append=100,0 logout=0 select=0 clients=1 secs=5 Logi Appe 100% 100% 1 2602 1/ 1 0 2671 1/ 1 0 2750 1/ 1 0 2363 1/ 1 Totals: 1 13206 Index rewrite, cydir: Totals: Logi Appe 100% 100% 1 4251 1/ 1 0 3914 1/ 1 0 3514 1/ 1 0 2985 1/ 1 0 2538 1/ 1 Totals: 1 17202 Maildir (not much difference between rewrite/no rewrite): Logi Appe 100% 100% 1 917 1/ 1 0 498 1/ 1 0 284 1/ 1 0 273 1/ 1 0 296 1/ 1 Totals: 1 2268 mbox (+300 with index rewrite): Logi Appe 100% 100% 1 1827 1/ 1 0 1688 1/ 1 0 1811 1/ 1 0 2040 1/ 1 Totals: 1 9114 Then a bit more generic test: Old index code, cydir: ./imaptest secs=10 clients=10 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 100% 30% 5% 3417 1713 1713 3416 3403 4840 1719 1260 3403 1999 6816 New index code, cydir: Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 100% 30% 5% 4686 2349 2317 4678 4675 6636 2323 1628 4675 2585 9353

1 0

[Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
by Eric and Barbara Sammons 30 May '07

30 May '07

I am running dovecot 0.99. Everything works great; however, now I am looking at several different tools to convert mbox to Maildir. It seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what they claim; however, when the messages are converted and they are stored in Maildir/cur, the email clients download these messages as new. This typically wouldn't be a problem; however, I am dealing with 100s of users with 1000s of emails and this really isn't acceptable behavior to them. Any thoughts on how to correct this issue and prevent the client from downloading these messages again? As a note, my test client is thunderbird and my preferred mbox to Maildir tool is mb2md-3.20.pl. Thanks!

5 6

[Dovecot] deliver rejection message
by Timo Sirainen 30 May '07

30 May '07

Currently the typical rejection message is: --------- Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Quota exceeded. --------- Then there is MDN + message headers in other MIME parts. But of course there sucky clients that can't display MDNs and users get confused. Any suggestions how to improve this message? I'm not sure if the "Dovecot Mail Delivery Agent" even needs to be in there. How about something like: --------- Your message to <foo(a)bar.org> was automatically rejected: Quota exceeded. See the attachment for the original message's headers. --------- And should I change this for v1.0.1 already?

5 6

Re: [Dovecot] [dovecot] IMAP basics
by Paul Scott 30 May '07

30 May '07

Picking up a broken thread after gettin exim4 to send my mail out. version 1.0.0 on Debian sid: I now have fetchmail delivering three POP mailboxes to my Maildir. How do I tell Dovecot about this mail? TIA, Paul Scott

1 0

Re: [Dovecot] Dovecot] dovecot performance question
by Kenny Dail 30 May '07

30 May '07

> Hi, using the latest dovecot with pop3/imap. Using mostly outlook 2003 for > pop3 and squirrel mail imap. > > I have a lot of users reporting back that imap is very slow. We average > about 300 imap and another 700 pop session at any given time. reporting that imap is slow or that squirrelmail is slow? ;) How is the load average on the server? We found at our site to keep Apache/squirrelmail happy, we dedicated a server for our webmail users. Mostly being a RAM issue in that case. Just how beefy is the server you are using? > I am having a time issue on this server and im not sure if its affecting > dovecot. > > May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. > May 29 11:42:19 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. > May 29 11:42:31 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. > May 29 11:42:42 pop dovecot: POP3(xxx): Time just moved backwards by 1 > seconds. I'll sleep now until w > e're back in present. It'll affect it in that you will be having 1 sec delays frequently it seems. You should definitely look into fixing that. That is bad behavior for a busy mail server. -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] namespace problem
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? Many thanks Rainer Sigl [0]root@mpemail:/etc/dovecot# dovecot -n # /etc/dovecot/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_cert_file: /etc/ssl/certs/mpemail.pem ssl_key_file: /etc/ssl/private/mpemail-key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_chroot: no verbose_proctitle: yes mail_extra_groups: mail default_mail_env: maildir:/home/virtual_mail/%u mail_location: maildir:/home/virtual_mail/%u mail_debug: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): UID%u-%v namespace: type: private prefix: INBOX. namespace: type: private separator: / prefix: INBOX/ hidden: yes namespace: type: private separator: . prefix: INBOX. inbox: yes hidden: yes auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=1002 gid=1002 home=/home/virtual_mail/%u userdb: driver: passwd userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

1 0

[Dovecot] Namespace Problems repost without attachment
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? Many thanks Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

1 0

[Dovecot] Namespace Problems
by Rainer Sigl 29 May '07

29 May '07

Hi all, after an update from dovecot beta version to 1.0.0.-1 today morning I had different effects: thunderbird-, kmail-, Apple-clients, pine and squirrelmail could receive email correct with imaps. But not MSOutlook!!! Varying the namespace configurations in dovecot.conf I got different results with MSOutlook working but with thunderbird, squirrelmail etc. all folders are displayed but not the root Inbox etc. Its important to know that I migrated from courier-imap to dovecot. My well working namespace config BEFORE upgrade to 1.0.0-1: namespace private { #separator = / prefix = INBOX. # prefix = inbox = yes #hidden = yes } #the second namespace I need to work with Apple because they use / namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } Here my actual namespace configs: namespace private { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } In varying inbox and hidden keywords I found this configuration. Most things are working with this but in squirrelmal I can't access inbox, the main folder. How do I have to configure that everythings works satisfying?? dovecot.conf and dovecot-sql.conf I send in the attachment. Many thanks Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/ -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/ ## Dovecot configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps protocols = imaps pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem #ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key ssl_cert_file = /etc/ssl/certs/mpemail.pem ssl_key_file = /etc/ssl/private/mpemail-key.pem # If key file is password protected, give the password here. Alternatively # give it when starting dovecot with -p parameter. #ssl_key_password = # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /var/log/dovecot.log # For informational messages, use this logfile instead of the default info_log_path = /var/log/dovecot-info.log # Prefix for each line written to log file. % codes are in strftime(3) # format. log_timestamp = "%Y-%m-%d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless login_chroot = no # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_connection is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_connection # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # 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 = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. There's 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 /usr/share/doc/dovecot-common/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/virtual_mail/%u # 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 { separator = prefix = INBOX. inbox = no hidden = no } namespace private { separator = / prefix = INBOX/ inbox = no hidden = yes } namespace private { separator = . prefix = INBOX. inbox = yes hidden = yes } #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 = INBOX/ # 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 = no # 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 #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # The minimum number of mails in a mailbox before updates are done to cache # file. This allows optimizing Dovecot's behavior to do less disk writes at # the cost of more disk reads. #mail_cache_min_mail_count = 0 # When IDLE command is running, mailbox is checked once in a while to see if # there are any new mails or other changes. This setting defines the minimum # time to wait between those checks. Dovecot is however able to use dnotify # and inotify with Linux to reply immediately after the change occurs. #mailbox_idle_check_interval = 30 # 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 # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. # Also note that if other software reads the mboxes/maildirs, they may handle # the extra CRs wrong and cause problems. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. NOTE: If you use NFS, remember to change also mmap_disable setting! # Solaris doesn't support flock, so Solaris users need to change this to fcntl. #lock_method = flock # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # If mbox size is smaller than this (in kilobytes), don't write index files. # If an index file already exists it's still read, just not updated. #mbox_min_index_size = 0 # Maximum dbox file size in kilobytes until it's rotated. #dbox_rotate_size = 2048 # Minimum dbox file size in kilobytes before it's rotated # (overrides dbox_rotate_days) #dbox_rotate_min_size = 16 # Maximum dbox file age in days until it's rotated. Day always begins from # midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled. #dbox_rotate_days = 0 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See # /usr/share/doc/dovecot-common/variables.txt for list of possible variables #you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/lib/dovecot/imap-login # IMAP executable location. Changing this allows you to execute other # binaries before the imap process is executed. # # This would write rawlogs into ~/dovecot.rawlog/ directory: # mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap # # This would attach gdb into the imap process and write backtraces into # /tmp/gdbhelper.* files: # mail_executable = /usr/lib/dovecot/gdbhelper /usr/lib/dovecot/imap # #mail_executable = /usr/lib/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/modules/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. # The list is space-separated. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/lib/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/lib/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # Older Dovecots : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which was # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. # # NOTE: Nowadays this is required to be set explicitly, since the old # default was bad but it couldn't be changed without breaking existing # installations. %08Xu%08Xv will be the new default, so use it for new # installations. # pop3_uidl_format = UID%u-%v # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/modules/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. # The list is space-separated. #pop3_client_workarounds = } ## ## dovecot-lda specific settings ## # protocol lda { # If you wish to use plugins you need to specify plugin directory # For example quota enforcing is implemented by plugin #module_dir = /usr/local/lib/dovecot/lda # Address from LDA should send MDNs like out of quota # postmaster_address = postmaster(a)your.dom # If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path = # UNIX socket path to master authentication server to find users. #auth_socket_path = /var/run/dovecot-auth-master # } ## ## Authentication processes ## # Executable location #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. Also note that currently auth cache doesn't work very well if # you're using multiple passdbs with same usernames in them. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Requires auth_debug=yes to be set. #auth_debug_passwords = no # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 # Kerberos keytab to use for the GSSAPI mechanism. Will use the system # default (usually /etc/krb5.keytab) if not specified. #auth_krb5_keytab = auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous gssapi # mechanisms = plain userdb static { args = uid=1002 gid=1002 home=/home/virtual_mail/%u } # passdb passwd-file { # args = /etc/passwd # } ## ## dovecot-lda specific settings ## # socket listen { # master { # path = /var/run/dovecot-auth-master # mode = 0600 # user = vmail # User running Dovecot LDA # #group = mail # Or alternatively mode 0660 + LDA user in this group # } # } # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # Users can be temporarily disabled by adding a passdb with deny=yes. # If the user is found from that database, authentication will fail. # The deny passdb should always be specified before others, so it gets # checked first. Here's an example: #passdb passwd-file { # File contains a list of usernames, one per line #args = /etc/dovecot.deny #deny = yes #} # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. # passdb pam { # [session=yes] [cache_key=<key>] [<service name>] # # session=yes makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work, such as pam_mkhomedir. # # cache_key can be used to enable authentication caching for PAM # (auth_cache_size also needs to be set). It isn't enabled by default # because PAM modules can do all kinds of checks besides checking password, # such as checking IP address. Dovecot can't know about these checks # without some help. cache_key is simply a list of variables (see # /usr/share/doc/dovecot-common/variables.txt) which must match for the # cached data to be used. # Here are some examples: # %u - Username must match. Probably sufficient for most uses. # %u%r - Username and remote IP address must match. # %u%s - Username and service (ie. IMAP, POP3) must match. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. # # Some examples: # args = session=yes * # args = cache_key=%u dovecot #args = dovecot # } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. # passdb passwd { # } # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # BSD authentication. Used by at least OpenBSD. #passdb bsdauth { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb prefetch" with this. #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database passdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for # example args = /etc/dovecot/dovecot-sql.conf } # LDAP database #passdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for # example #args = #} # vpopmail authentication #passdb vpopmail { # [cache_key=<key>] - See cache_key in PAM for explanation. #args = #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:/home/%u/mail nice=10 # #args = #} # SQL database userdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for # example args = /etc/dovecot/dovecot-sql.conf } # LDAP database #userdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for # example #args = #} # vpopmail #userdb vpopmail { #} # "prefetch" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases, see their example # configuration files for more information how to do it. # http://wiki.dovecot.org/AuthSpecials #userdb prefetch { #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no # Take the username from client's SSL certificate, using X509_NAME_oneline() # which typically uses subject's Distinguished Name. #ssl_username_from_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb pam { # } # userdb passwd { # } # socket listen { # master { # path = /var/run/dovecot-auth-master # # WARNING: Giving untrusted users access to master socket may be a # # security risk, don't give too wide permissions to it! # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot-auth-master # } # } #} plugin { # Here you can give some extra environment variables to mail processes. # This is mostly meant for passing parameters to plugins. %variable # expansion is done for all values. # Quota plugin #quota = dirsize:%h/mail # Convert plugin. If set, specifies the source storage path which is # converted to destination storage (default_mail_env). #convert_mail = mbox:%h/mail }

2 1

[Dovecot] Migration from tpop3d to dovecot - troubles galore!
by Odhiambo WASHINGTON 29 May '07

29 May '07

Hi people, I am trying to migrate some users from tpop3d (Maildir mailboxes) to dovecot. The most important aspect of this migration, and which I cannot seem to get right, is to first be able to make dovecot to authenticate against the current DB being used by tpop3d so that I can use imapsync to transfer the user mails. And I do believe that is what I am unable to get right!! So here goes what I have tried so far: Take a case of one username, eddie, who belongs to the domain, demo.wananchi.com. 1. This query is what I am using for password_query. I do suspect it is wrong, but well, this is what it yields from the current DB: mysql> SELECT CONCAT(domain.path, '/', popbox.mbox_name), popbox.password_hash FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox. domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name; +--------------------------------------------+---------------------------------------+ | CONCAT(domain.path, '/', popbox.mbox_name) | password_hash | +--------------------------------------------+---------------------------------------+ | /var/spool/virtual/demo.wananchi.com/eddie | {md5}897fad9cbef974ff95254417234ff1df | +--------------------------------------------+---------------------------------------+ 2. This is what I use for user_query and the result: mysql> SELECT CONCAT(domain.path, '/', popbox.mbox_name) as home, 6 as uid, 6 as gid FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_name = domain.domain_name; +-------------------------------------------------+-----+-----+ | home | uid | gid | +-------------------------------------------------+-----+-----+ | /var/spool/virtual/nyerimunicipal.co.ke/eddie | 6 | 6 | +-------------------------------------------------+-----+-----+ 3. Getting a typical user would need this query, for example: mysql> select CONCAT(local_part,'\@',domain_name) as user from popbox limit 10; +-------------------------+ | user | +-------------------------+ | eddie(a)demo.wananchi.com | +-------------------------+ 4. My tables, and the data they contain: (a) mysql> desc popbox; +----------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +----------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | | PRI | | | | local_part | varchar(255) | | PRI | | | | password_hash | varchar(255) | YES | | NULL | | | mbox_name | varchar(255) | YES | | NULL | | | password_hash2 | varchar(255) | YES | | NULL | | +----------------+--------------+------+-----+---------+-------+ (b) mysql> select * from popbox limit 1; +-------------------+------------+---------------------------------------+-----------+----------------+ | domain_name | local_part | password_hash | mbox_name | password_hash2 | +-------------------+------------+---------------------------------------+-----------+----------------+ | demo.wananchi.com | eddie | {md5}7bb1be8a78498a9de40098a593199819 | eddie | 9IYjWHc4Cs9/w | +-------------------+------------+---------------------------------------+-----------+----------------+ PS: Not all users have password_hash2, which I think is Unix crypt!!! (c) mysql> desc domain; +---------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +---------------+--------------+------+-----+---------+-------+ | domain_name | varchar(255) | | PRI | | | | unix_user | varchar(255) | YES | | NULL | | | password_hash | varchar(255) | YES | | NULL | | | path | varchar(255) | YES | | NULL | | | max_popbox | int(11) | YES | | NULL | | +---------------+--------------+------+-----+---------+-------+ (d) mysql> select * from domain limit 1; +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ | domain_name | unix_user | password_hash | path | max_popbox | +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ | dlsnovit.org | exim | {md5}d108219901e577db69c249645ae3a49f | /var/spool/virtual/demo.wananchi.com | 5 | +--------------+-----------+---------------------------------------+--------------------------------------+-----------------+ [root@ns2]#less /var/log/dovecot.log dovecot: May 29 17:42:57 Warning: Killed with signal 15 dovecot: May 29 17:42:59 Info: Dovecot v1.0.0 starting up dovecot: May 29 17:42:59 Info: auth-worker(default): mysql: Connected to localhost (virtualemail) dovecot: May 29 17:44:02 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=62.8.64.4 rip=62.8.64.4 resp=AGVk ZGllQGRlbW8ud2FuYW5jaGkuY29tAGJvZWluZzg= dovecot: May 29 17:44:02 Info: auth-worker(default): sql(eddie(a)demo.wananchi.com,62.8.64.4): query: SELECT CONCAT(domain.path, '/', popbox.mbox_n ame), popbox.password_hash FROM popbox, domain WHERE popbox.local_part = 'eddie' AND popbox.domain_name = 'demo.wananchi.com' AND popbox.domain_n ame = domain.domain_name dovecot: May 29 17:44:02 Error: child 40402 (auth-worker) killed with signal 11 dovecot: May 29 17:44:03 Info: auth(default): client out: FAIL 1 user=eddie(a)demo.wananchi.com temp dovecot: May 29 17:44:05 Info: pop3-login: Aborted login: user=<eddie(a)demo.wananchi.com>, method=PLAIN, rip=62.8.64.4, lip=62.8.64.4, secured o That password_hash - is it usable at all with dovecot? o Could password_hash2 be used? I could popolate the table with a known value and use it, just for imapsync to complete!! o What default_pass_scheme should I use in my userdb configuration? I'll very much appreciate help on this. I am currently testing with pop3, but once I get successful authentication, I will switch to imap for imapsync. Thanks for your time, and help, and advise:-) -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +======================================================================+ |\ _,,,---,,_ | Odhiambo Washington <wash(a)wananchi.com> Zzz /,`.-'`' -. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +======================================================================+ One, with God, is always a majority, but many a martyr has been burned at the stake while the votes were being counted. -- Thomas B. Reed

1 0

[Dovecot] About create mailbox by dovecot
by gaoqiang.qian＠nokia.com 29 May '07

29 May '07

Hi, I am a beginner of Dovecot. Actually I have just used yum install dovecot in my red hat linux host server. Could anyone tell me how can I start to use the dovecot to create a mailbox in my domain name. It seems there are lots of documents in the homepage of dovecot, but I do not know which one is the one specifically start to create mailbox. Thanks Qiang

1 0

[Dovecot] Stop Maildir appending to path
by Henry 28 May '07

28 May '07

Dovecot is working perfectly except for one problem. I have local users and virtual users. Local users are ~/Maildir. And virtual users are /home/vmail/domain/user. The problem is, it keeps trying to fetch virtual mail at /home/vmail/domain/user/Maildir. It doesn't exist the user/ dir is the Maildir. To get around this, I have to make symlinks on each virtual email. What should I check? How do I make it stop appending Maildir to my virtual users path? If I set mail_location to the virtual user path, it works fine. But I won't be able to get local mail. So I... have mail_location pointing to local users ~/Maildir while UserDatabase/Extrafields feature will overwrite the path for virtual users. dovecat-sql.conf: password_query = SELECT email as user, password, CONCAT('/home/ vmail/', path) as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM view_users WHERE email='%u';

2 1

[Dovecot] IMAP Bandwidth Monitoring
by Phillip T. George 28 May '07

28 May '07

Hello all, I'm wanting to set up IMAP bandwidth monitoring, but I don't see any IMAP size transfer entries in the log file. How would I turn this on? Please refer me to the manual if I've somehow missed it :) Thanks, Phillip

2 1

[Dovecot] IMAP basics
by Paul Scott 28 May '07

28 May '07

I have several POP mail accounts. I have installed and partially configured Dovecot 1.0.0 on Debian sid. I am having trouble understanding some of the basics. For starters do I need to fetch my POP mail (fetchmail, etc.) myself? TIA, Paul Scott

2 1

[Dovecot] Variable expansion in LDA vs POP/IMAP
by Stephane Enten 27 May '07

27 May '07

Hello all, I'm trying to understand when exactly the variable substitution happens in Dovecot, as I get different results in the LDA and in the POP/IMAP server. Here's my general setup: - Postfix MTA, delivers mail via Dovecot LDA - users list sits in a database - mail directory is stored in the database, but with Dovecot variables inside Delivery works perfectly fine, Dovecot's deliver get a "mail" column from the database (that looks like this: /mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln/ ) and expands variables, delivers the mail into the maildir's location. Now if I try to access the mailbox through Dovecot's POP/IMAP server, it looks like it gets the right field from the database, but won't expand the variables: May 24 18:31:14 mail1 dovecot: imap-login: Login: user=<XXXXX>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 24 18:31:14 mail1 dovecot: IMAP(XXXXX): Effective uid=1021, gid=304, home= May 24 18:31:14 mail1 dovecot: IMAP(XXXXX): maildir: data=/mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln/ May 24 18:31:14 mail1 dovecot: IMAP(XXXXX): maildir: root=/mail/01/%2LMd/%2.2LMd/%LMd/mail/%Ln, index=/srv/mail/01/%2LMd /%2.2LMd/%LMd/mail/%Ln, control=, inbox= May 24 18:31:14 wmail1-v dovecot: IMAP(XXXXX): Disconnected Am I missing something to get the pop/imap part expand those ? -- Stephane Enten

3 4

[Dovecot] UID confusion
by Kevin 27 May '07

27 May '07

I have just finished reading the info on the wiki on setting up virtual users with Dovecot and Postfix. http://wiki.dovecot.org/DovecotLDAPostfixAdminMySQL I'm confused about the UID and GID's. In the docs it shows a user, vmail being created with a UID of 101. Then it looks like GID 12 is used for Postfix or Mail. I'm not sure which it is and would like to know. Bulldozer

2 1

Re: [Dovecot] question mailbox format
by sc2＠gmx.at 27 May '07

27 May '07

ok after playing a while now it works , but i have one problem open.. a.) now he makes for pop3 index files in /var/indexes/%u/imap/index etc... you said that is correct too if i only use pop3 ? b.) i have as INBOX file /var/spool/mail/%u set, when somebody logs in, and the mailbox exist he gets the email (from mbox file), but when the mbox does not exist he makes a directory, instead of a file like /var/spool/mail/%u. The problem is when a new mail comes and the mbox file does not exist, the mail is saved to the directory as msg and not as mbox file any ideas? Btw im using version 1.0.0 thx

4 7

[Dovecot] locking question
by Paul Amaral 27 May '07

27 May '07

Hi, I'm using Maildir with dovecot .99, I'm getting some errors with fcntl locks. Do I still need to use a locking mechanism if I'm using maildir with pop3 access. For reasons I won't go into I cant upgrade from .99 to version one at the time. I'm getting this error with some users, I have tried to manually delete the .imap.index file but the error comes back, any thoughts? May 24 12:11:21 pop imap(generalg): Timeout while waiting for release of exclusive fcntl() lock for index file /home/g/generalg/Ma ildir/.INBOX/.imap.index TIA, Paul

3 2

[Dovecot] Address extensions with dovecot LDA
by Nick Kartsioukas 27 May '07

27 May '07

Greetings! I'm using Dovecot and Postfix with virtual mailboxes, the mailbox data is contained in a MySQL database. I'd like to use the Dovecot delivery agent so I can support Sieve filters. However, I'm not sure how to get the delivery agent to work with the Dovecot auth mechanism and MySQL to do proper lookups of email addresses with address extensions (such as test-blah(a)example.com) Does anyone have a similar setup that can tell me how I might get this to work? -- Nick Kartsioukas | KF6UZB change(a)nightwind.net | NK2694

1 1

[Dovecot] Quick question on multiple access to dovecot indexes
by Adam McDougall 26 May '07

26 May '07

I have up to 4 servers that will run dovecot behind a load balancer, which means the same user might be accessing the same mailbox from multiple servers, and it seems like dovecot doesn't like multiple access to the dovecot indexes for the one user since I currently have them stored in a nfs home directory. Is this a bad thing? Must I keep a seperate index location per server? Just today I started running dovecot on more than one server like this and started seeing things in the logs like: May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Corrupted transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log: end_offset (1332) > current sync_offset (1244) May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): broken sync positions in index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): fscking index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Fixed index file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index: log file sync pos 2,1332 -> 2, 1244 May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Unexpected transaction log desync with index /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index May 25 11:19:13 boomhauer dovecot: IMAP(mcdouga9): Disconnected: Mailbox is in inconsistent state, please relogin. May 25 11:19:17 dauterive dovecot: IMAP(mcdouga9): file mail-index.c: line 983 (mail_index_sync_from_transactions): assertion failed: (hdr.messages_count == (*map)->hdr.messages_count) May 25 11:19:17 dauterive dovecot: child 16386 (imap) killed with signal 6 ... May 25 11:19:53 dauterive in.imapproxyd[17211]: LOGIN: '"mcdouga9"' (127.0.0.1:53650) on existing sd [9] May 25 11:19:53 dauterive dovecot: IMAP(mcdouga9): Transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log: marked corrupted May 25 11:19:53 dauterive dovecot: IMAP(mcdouga9): Transaction log file /home/mcdouga9/Maildir/dovecot/public/indexes/decs/.support.In/dovecot.index.log.2: marked corrupted

2 2

[Dovecot] Dovecot crashes with malformed Qpopper's mbox
by 前田剛 26 May '07

26 May '07

I am testing migration from Qpopper 4.0.5 and have come across a problem. Dovecot dies while processing UIDL command when accessing malformed Qpopper's mbox which has duplicated "From " separator. Qpopper occasionally makes such header while rewriting mbox. In the attached file, unnecessary "From " at line 3. ---------------- * Dovecot 1.0.0 on Debian 4.0(x86) * ext3 filesystem(not NFS) * description Dovecot dies while processing UIDL command with malformed Qpopper's mbox which has duplicated "From " separator. This occurs when "pop3_reuse_xuidl" is "yes". conversation with Dovecot ~~~~~~~~~~~~~~~~~~~~~~~~~ $ telnet localhost 110 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. +OK Dovecot ready. user xxxxxxxx +OK pass xxxxxxxx +OK Logged in. uidl Connection closed by foreign host. * Dovecot configuration # /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/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 mail_extra_groups: mail mail_location: mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access: yes mbox_write_locks: fcntl 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_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 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: * how to reproduce 1. set "pop3_reuse_xuidl = yes". 2. replace test user's mailbox with attached file. 3. pop3 login and exec "UIDL". POP3 process will die. -- // -------------------------------------------------------------- // MAEDA, Go <maeda-g(a)secom-sanin.co.jp> POP3(test01): file ../../../src/lib/array.h: line 157 (_array_idx): assertion failed: (idx * array->element_size < array->buffer->used) POP3(test01): Raw backtrace: pop3 [0x80a9fab] -> pop3 [0x80a99a9] -> pop3 [0x807ec2c] -> pop3(index_mail_get_headers+0x254) [0x807eeb4] -> pop3(index_mail_get_first_header+0x18) [0x807ef48] -> pop3(mail_get_first_header+0x16) [0x809b746] -> pop3 [0x8057ae9] -> pop3 [0x8057c7f] -> pop3 [0x805674e] -> pop3(io_loop_handler_run+0x128) [0x80b03e8] -> pop3(io_loop_run+0x28) [0x80af858] -> pop3(main+0x82) [0x8058792] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7dffea8] -> pop3 [0x8055c21] child 4788 (pop3) killed with signal 6 From xxx(a)xx.xxxxxxx.xx.xx Sat Feb 17 19:27:47 2007 X-UIDL: i[f"!$h*!!S67!!/RW!! From xxx(a)xx.xxxxxxx.xx.xx Sat Feb 17 19:27:47 2007 Return-Path: <xxx(a)xx.xxxxxxx.xx.xx> X-Original-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Delivered-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Received: xxxx xxxx-xxxx-xxxxxx.xxxxxxx.xx.xx (xx [xxx.x.x.x]) xx xx-xxxxxxxx.xxxxxxx.xx.xx (xxxxxxx) xxxx xxxx xx xxxxxxxxxx xxx <xxxxxxxx(a)xx.xxxxxxx.xx.xx>; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) Received: xx xx.xxxxxxx.xx.xx (xxxxxxx, xxxx xxxxxx xx) xx xxxxxxxxxx; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) X-Mailer: xxxxxxx xx.x xx xxx.xxxxxx.xx.xx X-HTTP_REFERER: xxxx://xxx.xx-xxxxxxx.xx.xx/xxxx/xxxxx.xxxx Errors-To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx From: x.xxxxxxxxx(a)xxxxxxx.xxx Subject: $x<xxx$x$?$$(xx-xxxx Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-2022-JP" Message-Id: <xxxxxxxxxxxxxx.xxxxxxxxxx(a)xx.xxxxxxx.xx.xx> Date: Sat, 17 Feb 2007 19:27:47 +0900 (JST) Status: RO xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx From xxx(a)xx.xxxxxxx.xx.xx Tue Feb 20 14:06:25 2007 X-UIDL: 7;j"!L;8"!b\%#!pH5!! Return-Path: <xxx(a)xx.xxxxxxx.xx.xx> X-Original-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Delivered-To: xxxxxxxx(a)xx.xxxxxxx.xx.xx Received: xxxx xxxx-xxxx-xxxxxx.xxxxxxx.xx.xx (xx [xxx.x.x.x]) xx xx-xxxxxxxx.xxxxxxx.xx.xx (xxxxxxx) xxxx xxxx xx xxxxxxxxxx xxx <xxxxxxxx(a)xx.xxxxxxx.xx.xx>; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) Received: xx xx.xxxxxxx.xx.xx (xxxxxxx, xxxx xxxxxx xx) xx xxxxxxxxxx; xxx, xx xxx xxxx xx:xx:xx +xxxx (xxx) X-Mailer: xxxxxxx xx.x xx xxx.xxxxxx.xx.xx X-HTTP_REFERER: xxxx://xxx.xx-xxxxxxx.xx.xx/xxxx/xxxxx.xxxx Errors-To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx To: xxxxxxxxx(a)xx-xxxxxxx.xx.xx From: xxxxx(a)xxxxx-xxx.xx.xx Subject: $x<xxx$x$?$$(xx-xxxx Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-2022-JP" Message-Id: <xxxxxxxxxxxxxx.xxxxxxxxxx(a)xx.xxxxxxx.xx.xx> Date: Tue, 20 Feb 2007 14:06:25 +0900 (JST) Status: RO xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

3 7

[Dovecot] Return error instead of dying on time back skip?
by Amon Ott 26 May '07

26 May '07

Hello everybody! Currently, dovecot just kills itself if it detects that time has moved backwards more than a hardcoded number of seconds. I accept the reasons, but I do not like to restart dovecot manually after waiting for time to move forward again. A cron job would not help, because time might still be wrong when it restarts dovecot. All our systems run ntpd, but they might be offline for a while before they get contact to a time server, e.g. because of DSL problems. When they do get contact and time is too far off, ntpd sets the new time directly (yes, it could gradually do that, but it might take ages). Now I wonder if Dovecot could return errors to the users instead of dying until time is fine again, e.g. "System time has moved backwards, please come back in n seconds". If the time skip is just a few seconds, it can of course delay and then go on as it does now. With this change, no admin would be needed to carefully restart Dovecot at the right time. I have not looked into Dovecot code myself yet, but could try a patch if necessary. Amon Ott -- Amon Ott - m-privacy GmbH Am Köllnischen Park 1, 10179 Berlin Tel: +49 30 24342334 Fax: +49 30 24342336 Web: http://www.m-privacy.de Handelsregister: Amtsgericht Charlottenburg HRB 84946 Geschäftsführer: Dipl.-Kfm. Holger Maczkowsky, Roman Maczkowsky GnuPG-Key-ID: EA898571

6 7

[Dovecot] dovecot.org DNS finally ok
by Timo Sirainen 26 May '07

26 May '07

All DNS caches that had the old dovecot.org IP should finally be expired by now. About 20 people were unsubscribed because of bounces. I've subscribed them back. I think I'm also going to set up a dovecot.org mirror which can be quickly brought up if the current dovecot.org happens to break for some reason. www.dovecot.org and wiki.dovecot.org at least needs to be up quickly. BTW. Anyone is free to set up their own dovecot.org mirror: rsync -qavz --delete dovecot.org::hg hg rsync -qavz --delete dovecot.org::dovecotweb www rsync -qavz --delete dovecot.org::dovecotwiki wiki rsync -qavz --delete dovecot.org::dovecotmail mail rsync -qavz --delete dovecot.org::dovecotnewsmail mail-news rsync -qavz --delete dovecot.org::dovecotcvsmail mail-cvs I don't want any official mirrors though. They're more trouble than worth. :)

1 0

[Dovecot] question mailbox format
by sc2＠gmx.at 26 May '07

26 May '07

i set mail_location = mbox:/var/spool/mail/%u and protocols = pop3s pop3 why he trys to create and use imap format?` in log are May 25 18:52:25 mail dovecot: pop3-login: Login: user=<richard>, method=PLAIN, rip=80.xx.xx.xx, lip=xx.xx.24.29, TLS May 25 18:52:26 mail dovecot: POP3(richard): open(/var/spool/mail/richard/inbo x, O_CREAT) failed: Not a directory May 25 18:52:26 mail dovecot: POP3(richard): mkdir_parents(/var/spool/mail/richard/.imap/INBOX) failed: Not a directory May 25 18:52:26 mail dovecot: POP3(richard): stat() failed with mbox file /var/ spool/mail/richard/inbox: Not a directory May 25 18:52:26 mail dovecot: POP3(richard): Couldn't init INBOX: Internal erro r occurred. Refer to server log for more information. [2007-05-25 18:52:25] May 25 18:52:26 mail dovecot: POP3(richard): Mailbox init failed top=0/0, retr= 0/0, del=0/0, size=0 friendly regards and thx

3 5

[Dovecot] Quota warning not generated
by Doug Council 26 May '07

26 May '07

I am testing out the unofficial quota warning patch with Dovecot 1.0.0, and no matter what values I use for the storage or messages values, the warning script is never executed. My plugin settings are: plugin { quota = maildir:storage=20480 quota_warning = storage=80%:messages=10 /usr/local/bin/quota-warning.sh } I've tried the following quota_warning lines without any luck: quota_warning = storage=80% /usr/local/bin/quota-warning.sh quota_warning = messages=10 /usr/local/bin/quota-warning.sh quota_warning = storage=80%:messages=10 /usr/local/bin/quota-warning.sh The quota-warning.sh script is set to 0755 and currently just syslogs a warning using logger(1). Run independently of Dovecot, it works fine. Here is a sample maildirsize file (if that is at all important) from when I tried the messages=10 setting: 10485760S 335322 12 14016 1 58058 1 46529 1 37623 1 55252 1 61901 1 53422 1 56228 1 There are more than 10 messages in the mailbox, but the quota-warning.sh script never gets executed. When using storage=80%, the maildirsize file has the correct values (not included in this message), but it never executes the script as well. Does anyone have any ideas? Thanks, -Doug

2 2

[Dovecot] How about a "pipe" plugin?
by Nicolas Boullis 25 May '07

25 May '07

Hi, I have written a plugin so that each time a message is added to a specific box, a program is run and the message is piped into it. Note that the message is also really added to the box. I've been using it for nearly 3 month, for spam/ham learning, and have not had any problem with it. I guess it could also be used to implement an out box (I remember seeing someone asking for such a feature on this list). Currently, I use it with a config like this: (...) namespace private { separator = . location = maildir:/var/mail/%u inbox = yes hidden = no } namespace public { separator = . prefix = learn. location = maildir:/var/learn/%u inbox = no hidden = no } (...) plugin { (...) pipe = /var/learn/%u/.spam:spamc -d some.host -L spam pipe2 = /var/learn/%u/.ham:spamc -d some.host -L ham (...) } Would people be interested by such a feature? If enough people show some interest, I can try to convince my boss to let me release this plugin GPL-licensed. Cheers, Nicolas Boullis

6 7

[Dovecot] Will pay $500 towards a Dovecot feature
by Marc Perkel 25 May '07

25 May '07

10 days ago I proposed this addition (see below) to Dovecot and got a lot of positive response. I would like to make it happen. I'm willing to contribute $500 to the development of this feature. It doesn't have to be implemented perfectly but needs to be workable to the extent that I can telnet into the Dovecot server and run it manually from the command line. I want to at least be able to run a simple script that I will write to add or remove someone from a black list text file. Timo has limited time but has indicated that he will allow it as a kind of undocumented feature (or wiki documented only). This is a sort of proof of concept feature and if it ever becomes a standard the standard will probably be different. However, we should implement it in a way that would be as close to a standard as possible. So - I'm looking for a programmer to make it happen. I'm also looking for others who might also kick in a few bucks as well if necessary. Here's the rough spec. ---------- Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP interface? For example, personalized server settings. Suppose for example I want Thunderbird to edit my server side white lists or black lists or any other setting? Wouldn't it be nice if IMAP supported these changes? The connection is made. It's a secure connection that's been authenticated. Lets use it! Here's my initial thoughts on this. Suppose we extended IMAP to include an EXECUTE command as follows: EXECUTE command parameter, parameter .... On the server side is a config file that has the commands that execute will allow and what programs they run. When the execute command is seen by Dovecot then Dovecot runs the program in the list with the parameters passed. For example, suppose there is a command to add a user to a server side blacklist. 100 execute blacklist add joe(a)smith.com 100 ok Dovecot would open a two way connection to the server application allowing the client to talk to any application that is configured and can send and receive text. The connection persists until the server end terminates or the client closes the connection. With a tool like this one can write generic applications easily that would greatly expand what email clients can do interacting with the server. Not only can setting be changes but you could interact with server side calendars, pick up voice messages from phone systems, run any sort of groupware, all over a generic IMAP connection with this simple extension. Example: 100 EXECUTE calendar 100 ok 100 list schedule today 8:00 10:00 100 8:00 make coffee 100 9:00 meeting with boss 100 9:30 Call Joe Blow at 415-555-1212 100 ok 100 quit 100 ok One thing I'd like to use it for is an outgoing SMTP connection to send outgoing email over IMAP. A session might look like this: 999 EXECUTE smtp 999 220 darwin.ctyme.com ESMTP Exim 4.67 Sun, 13 May 2007 06:52:26 -0700 999 helo ctyme.com 999 250 darwin.ctyme.com Hello localhost [127.0.0.1] 999 mail from:marc@perkel.com 999 250 OK 999 rcpt to:dovecot@dovecot.org 999 250 Accepted ...... 999 quit 999 OK Config File: There would have to be a config file that would be a table of what command run what. An example might look like this: calendar: /usr/bin/dovecot/calendar blacklist: /etc/exim/scripts/blacklist Probably might eventually want to add UID/GID and root directory restrictions for security. Login information and connection IP should be passed in the environment.

17 30

Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
by Eric and Barbara Sammons 24 May '07

24 May '07

Can you elaborate on this convert plugin? I have not heard of it and am curious if it is available in 0.99. Thank you! Bruce Bodger wrote: > > On May 24, 2007, at 3:22 PM, Eric and Barbara Sammons wrote: > >> I am running dovecot 0.99. Everything works great; however, now I am >> looking at several different tools to convert mbox to Maildir. It >> seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what >> they claim; however, when the messages are converted and they are >> stored in Maildir/cur, the email clients download these messages as new. > > Like you, I played with all the available scripts. Settled on using > ONLY Dovecot's convert plugin to convert a uw-imap mbox system to > Dovecot maildir. Believe it or not, it ran 100% perfectly and users > never even noticed the switch! > > Good luck. > B. Bodger > New York, NY >

3 2

[Dovecot] quota plugin
by maximatt 24 May '07

24 May '07

hi... i not undestand this plugin (quota) , because if i set a value 10240 (like in example) when i send a 4 messages with attaches sizes like 4MB they do not nothing, but if i want to send a message like 12MB the dont me do that, but in the first way the user inbox have like 20MB. ¿:(? i have these settings for this plugin: protocol imap { mail_plugins= quota imap_quota } plugin { quota= maildir:storage=10240 } ¿can anybody explain me that? :( thanks in advance!!! :)

1 0

[Dovecot] needing UNSELECT to notice new mail?
by Greg Troxel 24 May '07

24 May '07

I am running NetBSD/i386 3.1ish and 4.0ish dovecot 1.0.0 procmail delivering into maildirs gnus from CVS head emacs 21.4 thunderbird 2 gnome mail-notification 4 configured to required SSL. Basically everything works fine except that in gnus typing 'g' in the *Group* buffer, which is supposed to check for new mail and list the number of new messages, fails to notice new mail. Notably, gnus does not do an UNSELECT or CLOSE when it is done with a group. So basically the following sequence of commands SELECT "INBOX" blah blah EXPUNGE STATUS "INBOX" shows no unseen but really there is one With (setq nnimap-need-unselect-to-notice-new-mail t) gnus will do UNSELECT before STATUS, and then things work fine. Another gnus user reports what seems like the same problem with Courier IMAP. So, is dovecot complying with the IMAP spec here? Is there some notion of a transaction bracketed by SELECT/{UNSELECT,CLOSE}, and is that using something like READ COMMITTED isolation so that it doesn't see messages added by other transactions? Or should dovecot be not relying on cached state and revalidate the mailbox on STATUS, even if it is already SELECTED? Further, is it the group's opinion that a well-behaved client would UNSELECT or CLOSE when the user takes an action that indicates being finished with a mailbox? Or is it reasonable to leave a mailbox SELECTed as an optimization. It seems that for Thunderbird, etc., the user sits in INBOX with IDLE, but with gnus I tend to be in *Group* with no mailboxes selected.

2 4

[Dovecot] unexpected error message (maildir_sync_index)
by Kyle Wheeler 24 May '07

24 May '07

Hello, I recently saw these errors in my log, and one of my users complained that Dovecot disconnected him unexpectedly. Any idea what might have happened? dovecot: Error: IMAP(bmoore(a)forkit.org): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid > prev_uid) dovecot: Error: IMAP(bmoore(a)forkit.org): Raw backtrace: /usr/local/libexec/dovecot/imap [0x80b6501] -> /usr/local/libexec/dovecot/imap [0x80b641c] -> /usr/local/libexec/dovecot/imap(maildir_sync_index+0x902) [0x8069042] -> /usr/local/libexec/dovecot/imap [0x8069243] -> /usr/local/libexec/dovecot/imap(maildir_storage_sync_init+0x48) [0x8069428] -> /usr/local/libexec/dovecot/imap(imap_sync_init+0x40) [0x8062590] -> /usr/local/libexec/dovecot/imap(cmd_sync+0x71) [0x80626d1] -> /usr/local/libexec/dovecot/imap(cmd_noop+0x26) [0x8059cc6] -> /usr/local/libexec/dovecot/imap [0x805b878] -> /usr/local/libexec/dovecot/imap [0x805b907] -> /usr/local/libexec/dovecot/imap(_client_input+0x6c) [0x805bfbc] -> /usr/local/libexec/dovecot/imap(io_loop_handler_run+0x120) [0x80bc7e0] -> /usr/local/libexec/dovecot/imap(io_loop_run+0x28) [0x80bb808] -> /usr/local/libexec/dovecot/imap(main+0x4b0) [0x8063fd0] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7e7eea8] -> /usr/local/libexec/dovecot/imap [0x8056a11] dovecot: Error: child 8418 (imap) killed with signal 6 ~Kyle -- All we have to decide is what to do with the time that is given us. -- Gandalf the Grey

2 2

[Dovecot] Timeout while waiting for shared lock for index file /var/mail/XXX/Maildir/dovecot.index
by Giannis Zachariadis 24 May '07

24 May '07

Hello, I'm using dovecot v1.0rc23 for about 500 users since february with no particular problems. I'm using Maildir format and ldap authentication. A recently added user can't check his mails any more. In the logs I get May 23 14:35:58 mailsrv deliver(XXXX): [ID 702911 mail.error] Timeout while waiting for shared lock for index file /var/mail/XXXX/Maildir/dovecot.index The user connects with IMAP to retreive his mails. Currently I can login to his account with pop3 and retreive the mails, but when it comes to IMAP I get this error and no mail at all. thanks in advance, -- giannis.

2 1

[Dovecot] Updated v1.1 and summer plans
by Timo Sirainen 24 May '07

24 May '07

Webmail.us will be sponsoring my Dovecot development for this summer. Other companies are also welcome to participate in the costs. Participation gets you: - listed in Credits in www.dovecot.org - listed in AUTHORS file - you can tell me how you want to use the feature and I'll make sure that it supports it (within reasonable limits) For already implemented v1.1 features, see http://www.dovecot.org/list/dovecot/2007-April/021974.html Some of those features require some more testing (new SORT and THREAD code especially) and a bit of fixes to mailbox list indexes. Otherwise I think it's working pretty well already, I've been using it for a long time for my own mails. Upcoming v1.1 features, more or less implemented in this order: - Index file optimizations: http://www.dovecot.org/list/dovecot/2007-May/022591.html - Less indexing for POP3 users (both in pop3 and in deliver) - Replace Squat FTS indexes with my new design - Configurable mail_log plugin - Limit number of connections for a user - A combined LIST + STATUS command (or possibly NOTIFY extension? http://tools.ietf.org/html/draft-gulbrandsen-imap-notify-03) - Fully supported shared mailboxes and IMAP ACL extension: http://www.dovecot.org/list/dovecot/2007-April/021624.html - Remote (shared) mailboxes. Automatic proxying, but possibly also support for MAILBOX-REFERRALS extension if it's not much extra trouble (few clients support it, so probably not worth the trouble unless it can be done in a couple of hours) - Remove unused keywords from mailboxes - Some other small things Upcoming v1.1/v1.2/v2.0 features (planned to be implemented at the end of the summer): - virtual mailboxes: http://www.dovecot.org/list/dovecot/2007-May/022828.html - dbox redesign: http://www.dovecot.org/list/dovecot/2007-May/022602.html Implementing the above features will keep me busy for most of the summer, but there have also been requests for replication support (http://www.dovecot.org/list/dovecot/2007-May/022792.html) I'm interested in implementing it as well, but unfortunately it looks like I don't have time for it at least for the next 3 months or so. There's already at least one company that's willing to pay for replication, but if you're also interested please let me know. Perhaps someone else could implement it instead (if you're interested, please let me know), or if not it'll just have to wait until I have time for it.

6 10

[Dovecot] dovecot, uidplus and apple mail.app (was: Re: Will pay $500 towards a Dovecot feature = calender ?)
by DINH Viêt Hoà 24 May '07

24 May '07

On 5/24/07, Robert Schetterer <robert(a)schetterer.org> wrote: > DINH Viêt Hoà schrieb: > > On 5/24/07, Timo Sirainen <tss(a)iki.fi> wrote: > >> On Thu, 2007-05-24 at 09:37 +0200, Adi Kriegisch wrote: > >> > As a calendaring solution with group calendars and all the like, use > >> CalDAV > >> > -- a webdav extension designed for exactly that purpose. There is an > >> > excellent implementation available at: http://rscds.sourceforge.net/ > >> (also > >> > Apple has released their calendar server supporting caldav open > >> source). > >> > >> I'm using iCal in my OSX Laptop and Evolution in Linux Desktop. Once OSX > >> 10.5 is released with its CalDAV support I'm planning on installing some > >> CalDAV server and probably implement dovecot-auth support for it. > >> > >> Perhaps some day in future I'll also implement CalDAV, but first I'll > >> need to write a web server. :) > > > > CalDAV server of Apple is open-sourced. > > I heard that Cyrus Daboo was involved in :) > > That suggests it could be a good implementation. > > > hi @ll i have a customer who uses > ical apple with a apache webdav setup , this seems to works nice, > but there are a lot of problems with apple mail and imap about apple mail and imap, I think that's because apple mail uses UIDPLUS to work properly. -- DINH Viêt Hoà

1 0

Re: [Dovecot] Will pay $500 towards a Dovecot feature = calender ?
by Robert Schetterer 24 May '07

24 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Curtis Maloney schrieb: > Robert Schetterer wrote: >> Hi all, i think sombody would have like to a imap calender solution >> implemented in dovecot? Am i right here? >> >> You can have simular right now using thunderbird , lightning, kolab >> plugin, ( should be shown in horde webmail too ) > > I tried the kolab plugin... it never worked for me. So disappointed - > especially since synchronising my contacts/calendar between sites would > be very valuable. > > -- > Curtis Maloney > cmaloney(a)cardgate.net > Hi Curtis, sorry to hear this, i know kolab extension is still beta but it works for me in small setups, maybe you should inform the devolopers about your problems and they may help you - -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGVW5XfGH2AvR16oERAv4tAJ9d5ijEXK7F/cujwCp32dm9diMeQwCfQNwb N8RDveBHLqW73zZABw6z6GA= =EDpj -----END PGP SIGNATURE-----

1 0

[Dovecot] Old style qouta to new style convert?
by Mart Pirita 24 May '07

24 May '07

Tere. I'm using Debian, postfix & dovecot, with system quotas and settings in dovecot.conf: default_mail_env = maildir:%h/Maildir:INDEX=/var/spool/dovecot/index/%u:CONTROL=/var/spool/dovecot/control/%u But if system quota is full, users won't get new messages but won't get also any kind information, and also in mail.log is nothing. Is this normal? Should I use dovecot -s own quota with postfix or dovecot own LDA is needed? And how to convert these index and control files into users homedir? Just making changes in dovecot.conf seems not be good idea? Or it is and the control and indexes will be created again? -- Mart

2 1

[Dovecot] Courier migrating issues: indexes, maildirsize, update query
by Jan van den Berg 24 May '07

24 May '07

Hi, (my first post to the list) I'm in the process of testing Dovecot to see whether it meets our needs to replace our current Courier setup which serves well over 100.000 mailboxes (pop3 and imap: mysql with NFS) So far dovecot seems pretty straight forward; however I ran into a couple of things that I'm curious about. 1. What's the deal with dovecot.index/dovecot.index.log/dovecot.index.cache. I understand Dovecot uses this for POP3 primarily but this will no doubt cause a lot of overhead on our platform. Also getting this to work with our NFS setup would be a pain (locking etc.). I've been following this discussion: http://www.dovecot.org/list/dovecot/2006-January/thread.html#10758; and it ends with C. Malony suggesting that an disable index option would be in place; but no further action is taken. Basically I want to get rid of the index files (courier also doesn't use any). Any suggestions; will there be a disable-index option? 2. One of the reasons we want to get rid of Courier is because the maildirsize is often incorrect. Whether this is because of a bad Courier implementation or NFS issues or whatever, I haven't figured out yet. But I'd like to test this function in Dovecot; but there seems to be very little documentation. I read the link http://wiki.dovecot.org/Quota/Dict but this info is too scarce. Any pointers on where to go? 3. In our MySQL setup we have a field with the latest poptime and pophost (IP). This info can come in handy when troubleshooting or filtering out inactive mailboxes. With our Courier setup this field gets updated by a rather elaborate script that checks the logs and runs updates queries. I could get this to work for Dovecot; but with Dovecot being more actively in development, I wonder could this be a feature; like after a user_query, another update query? Cheers, Jan

3 6

[Dovecot] May 21 09:13:14 mail dovecot: imap-login: No authentication sockets found
by dhottinger＠harrisonburg.k12.va.us 23 May '07

23 May '07

I started getting this message this morning: May 21 09:13:14 mail dovecot: imap-login: No authentication sockets found Ive been runing dovecot on a fc6 dell poweredge 2950 for about 4 weeks now with no issues. Im authenticating against openldap 2.3.27. It appears ok. I restarted ldap, and dovecot, and everything looked fine for a few minutes, then this started again. I have around 720 users. Is there a setting in the dovecot.conf that I can use to fix this? Or is the problem elsewhere? -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools

5 11

[Dovecot] Quota Limits Newbie Question
by Craig Carriere 23 May '07

23 May '07

I have Dovecot 1.0 running on a SLES 10 mail server using postfix 2.2 and amvisd-maia. The mailboxes are stored in Maildir format with all the domains and users stored in a mySQL database. I would like to implement quotas for the system and have looked at the VDA patch for postfix and/or quotas within Dovecot. Any advantages to either? From what I can see from a couple of searches, Dovecot does not appear to respond either to the sender or recipient when they are over quota while one can set-up postfix-vda to do so which would be of value. Thank you for the time and input.

1 0

[Dovecot] index-related crash in dovecot 1.0.0
by J.Wendland＠scan-plus.de 23 May '07

23 May '07

Hi, dovecot crashes with the following trace when accessing some Maildirs: dovecot: 2007-05-16 13:30:09 Error: IMAP(6126360): file index-mail-headers.c: line 260 (index_mail_parse_header): assertion failed: (part != NULL) dovecot: 2007-05-16 13:30:09 Error: IMAP(6126360): Raw backtrace: imap [6126360] [0x80b6d6b] -> imap [6126360] [0x80b6769] -> imap [6126360] [0x808abda] -> imap [6126360](message_parse_header+0x56) [0x80b2166] -> imap [6126360](index_mail_parse_headers+0x113) [0x808ad03] -> imap [6126360] [0x80891bb] -> imap [6126360](index_mail_get_special+0x112) [0x8089632] -> imap [6126360] [0x806dc3b] -> imap [6126360](mail_get_special+0x16) [0x80a7cf6] -> imap [6126360] [0x805dc2f] -> imap [6126360](imap_fetch+0xf3) [0x805d7b3] -> imap [6126360](cmd_fetch+0xff) [0x805845f] -> imap [6126360](cmd_uid+0x52) [0x805b272] -> imap [6126360] [0x805be65] -> imap [6126360] [0x805bddb] -> imap [6126360](_client_input+0x6d) [0x805bf4d] -> imap [6126360](io_loop_handler_run+0x128) [0x80bd1a8] -> imap [6126360](io_loop_run+0x28) [0x80bc618] -> imap [6126360](main+0x69) [0x80645c9] -> /lib/libc.so.6(__libc_start_main+0x9e) [0x400383be] -> imap [6126360] [0x8056a01] dovecot: 2007-05-16 13:30:09 Error: child 6845 (imap) killed with signal 6 The command leading to the crash is (line wrapped for readability): UID FETCH 1:214748367 (UID ENVELOPE BODYSTRUCTURE INTERNALDATE RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (Importance X-Priority Priority X-PIM-INFOS Content-Type Date)]) When I connect to dovecot and simply fetch with the following command: UID FETCH 1:* (ENVELOPE) dovecot seems to updates its dovecot.index.cache files and the crash never appears again. I have a mailbox that can be used to reproduce the error. Best wishes, Jörg # dovecot --version 1.0.0 # dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot-error.out info_log_path: /var/log/dovecot.out log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: DVAG IMAP server ready login_process_per_connection: no login_chroot: no login_greeting_capability: yes login_processes_count: 5 login_max_connections: 2048 max_mail_processes: 2048 verbose_proctitle: yes mail_extra_groups: mail default_mail_env: maildir:%h/Maildir mail_location: maildir:%h/Maildir mail_read_mmaped: yes maildir_copy_with_hardlinks: yes mail_drop_priv_before_exec: yes mail_executable: /usr/local/bin/dovecot-postlogin mail_plugins: quota imap_quota acl namespace: type: private separator: . prefix: INBOX. location: maildir:%h/Maildir inbox: yes auth default: mechanisms: plain login master_user_separator: * worker_max_count: 64 passdb: driver: passwd-file args: /etc/dovecot/dovecot-master.pwd master: yes passdb: driver: checkpassword args: /usr/local/bin/checkpassword-zob userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: maildir:storage=0 acl: vfile:/etc/dovecot/acls -- Sicherheit - Verfügbarkeit - Kontinuität ------------------------------------------------------------------------- IT-Service-Management von ScanPlus GmbH Tel. +49 731 92013 150 Lise-Meitner-Straße 5, D-89081 Ulm, Germany Fax. +49 731 92013 29 150 Web: http://www.scan-plus.de/ Mail: wendland(a)scan-plus.de -------------------------------------------------------------------------

2 5

[Dovecot] dovecot + ldap tls
by aza zel 23 May '07

23 May '07

hi... i trying to have a secure conetion between dovecot and directory server, but i cant do it. The documentation are so poor ( http://wiki.dovecot.org/AuthDatabase/LDAP) these are my configurations files: (pre: i have a directory server accepting secure conections (port 389 via TLS and port 636 via SSL). File "/opt/csw/etc/dovecot-ldap.conf": hosts=100.0.4.98 dn = cn=bindmailusers,cn=mailusers,dc=prueba,dc=uy dnpass =passbindmailUsers tls = yes ldap_version = 3 base= cn=mailUsers,dc=prueba,dc=uy deref = never scope = subtree user_attrs = uidnumber=uidnumber, gidnumber=gidnumber,homedirectory=homedirectory, mailbox=mailbox user_filter = (&(objectClass=mailaccount)(uid=%u)(disableimap=FALSE)) pass_attrs = uid=uid,userpassword=password pass_filter= (&(objectClass=mailaccount)(uid=%u)(disableimap=FALSE)) default_pass_scheme = CRYPT user_global_uid =12356 user_global_gid =12356 File "/opt/csw/etc/openldap/ldap.conf" (openldap client): TLS_REQCERT allow host 100.0.4.98 TLS_CACERT /opt/csw/etc/postfix/ldap-cert/cacert.pem these are my log file: # tail dovecot-log.log : : dovecot: May 22 15:48:31 Error: auth(default): LDAP: ldap_start_tls_s() failed: Can't contact LDAP server any suggest :( -- Salu2 ;)

2 2

[Dovecot] need some help please
by Paul A 23 May '07

23 May '07

We currently had dovecote 99 running and ran into some issues with it, mainly our pop3 sessions timeout and were slow. I upgraded to the latest version and im serving imap with pop3 using pam. Heres my pam file: [root@pop etc]# cat /etc/pam.d/dovecot #%PAM-1.0 auth required pam_unix.so nullok account required pam_unix.so The problem I'm having is I can authenticate to imap, but it's very slow, however pop3 doesn't work at all. I have auth debug set and I can see the imap authentication but not pop3. Here is my config file. ssl_disable: yes login_dir: /usr/local/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 mail_location: maildir:/home/%1u/%u/Maildir 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_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 auth default: debug: yes debug_passwords: yes passdb: driver: pam args: dovecot passdb: driver: passwd userdb: driver: passwd May 21 13:51:15 pop dovecot: imap-login: Login: user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:51:38 pop dovecot: auth(default): passwd(test,127.0.0.1): lookup May 21 13:51:53 pop dovecot: IMAP(ftest): Disconnected: Logged out May 21 13:51:54 pop dovecot: imap-login: Login: user=<ftest>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:51:54 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:51:56 pop dovecot: auth(default): client out: OK 1 user=ftest May 21 13:51:56 pop dovecot: auth(default): passwd(ftest,127.0.0.1): lookup May 21 13:51:56 pop dovecot: auth(default): master out: USER 95 ftest system_user=ftest uid=11094 g id=503 home=/home/f/ftest May 21 13:52:18 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:52:21 pop dovecot: IMAP(ftest): Time just moved backwards by 1 seconds. I'll sleep now until we're back in pre sent. May 21 13:52:21 pop dovecot: imap-login: Login: user=<ftest>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:52:22 pop dovecot: IMAP(ftest): Disconnected: Logged out Using maildir's with pam authentication, I really would appreciate any help.

3 6

[Dovecot] shared folders
by David Obando 23 May '07

23 May '07

Dear all, I would like to use shared folders but I'm not quite sure whether Dovecot supports it the way I want it: -user A should be able to share a folder with users B, C, D -B, C and D should have read-access to this folder Did anyone implement shared folders like this? Regards, David -- The day microsoft makes something that doesn't suck is the day they start making vacuum cleaners. gpg --keyserver pgp.mit.edu --recv-keys 1920BD87 Key fingerprint = 3326 32CE 888B DFF1 DED3 B8D2 105F 29CB 1920 BD87

2 1

[Dovecot] Quota warning message ala courier
by Ralf Hildebrandt 23 May '07

23 May '07

I have to face it, my users are retards: * either they're using crap MUAs which will not display their quota to them * or they're using POP with "leave mail on server" and will never notice their quota, unless it's too late * and once their quota is exceeded, their mails will bounce -- they'll never notice that, though. Thus I need a feature in dovecot that will tell them via email: Level1: "You ALMOST exceeded your quota, you're at 90% now" Level2: "You're very close to exceededin your quota, you're at 95% now" Level3: "Would you please clean up now? You're at 99% now" -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de "Hardware: the parts of a computer that can be kicked." -- Jeff Pesis

4 3

[Dovecot] Quota handling - opportunity for new Feature?
by Charles Marcus 23 May '07

23 May '07

This initial proposal for a Feature Request is the result of my desire to implement quotas, but not have the attendant headaches that inevitably accompany its implementation. Ralf Hildebrandt wrote: > I have to face it, my users are retards: Is there any other kind of user? ;) <snip> > Thus I need a feature in dovecot that will tell them via email: > > Level1: "You ALMOST exceeded your quota, you're at 90% now" > Level2: "You're very close to exceededin your quota, you're at 95% > now" > Level3: "Would you please clean up now? You're at 99% now" What I'd *really* like to see implemented is something along the lines outlined below - but of course, this will depend entirely on whether or not Timo thinks it is doable - or desirable... I know this would only be applicable if also using the dovecot LDA, because what I want to do requires cooperation at both the deliver and pop/imap ends... 1. Have two 'special' user-specific folders (by special, I mean like the Drafts, Sent, Templates folders) that dovecot controls: a) one, that the user has read-only access to and shows up in his folders list, that is used only for system-related messages, like over-quota notices - and maybe even user-specific log-type errors could be delivered here? b) and one (hidden) that the user does *not* have access to, to temporarily hold messages that come in that are unable to be delivered due to an over-quota condition 2. When user is over quota, have LDA deliver to folder b (yes, accept the message for delivery from the sending mta), and then generate an over-quota message that is delivered to folder a. Optionally, a bounce could be generated to the sender, informing them that their message is being 'held in queue' or something to that effect, due to the recipient being over-quota. 3. Once the user deletes enough mail to come back under quota, dovecot would then move messages from the 'over-quota' folder to his Inbox. Ok, am willing to hear reasons how/why this is a terrible idea... :) -- Best regards, Charles Marcus I.T. Director Media Brokers International 678.514.6200 x224 678.514.6299 fax

2 5

[Dovecot] dovecot.pid
by Dehnert James Sr 23 May '07

23 May '07

Can I define where dovecot.pid should be in the config file on 1.0.0? Nothing is being written to /var/run/dovecot, even after I changed the ownership to dovecot. Thanks, Zeke -- James "Zeke" Dehnert mailto:jdehnert@norcalnetworks.com Phone: +1 707.546.6620 x602 Fax: +1 707.324.8043 "Life is racing, everything else is just waiting"

2 1

[Dovecot] dovecot.org moves to a new server
by Timo Sirainen 23 May '07

23 May '07

Parts of dovecot.org will be down for a few hours while I'm moving to a new server (and to a new ISP as well). The new server won't be virtual anymore, so I'm hoping to get a bit better performance from it as well (the old virtual server had some disk I/O hogs). The DNS records have been using 1 hour TTL for last few days, so this move should be fast for everyone. Thanks to Nebula for hosting dovecot.org for the last 7 months. So, beginning the move by shutting down Postfix and Mailman..

4 6

[Dovecot] newbie with dovecot acls needs a little help :-)
by Rachid Zarouali 22 May '07

22 May '07

hy all, i'm trying to make an acl so a local unix user 'sie' can access exalead mboxes. my exalead mboxes are stored in : /opt/exalead/mail/sie/ mailboxes are automatically created every week like sie.2007.W17 for the 17th week of the year. how can i do this ? i've tried several things but none succedded. dovecot version 1.0.rc15 # /etc/dovecot.conf ddIEffective uid=65534, gid=65534 ddILoading modules from directory: /usr/lib64/dovecot/imap ddIModule loaded: /usr/lib64/dovecot/imap/lib01_acl_plugin.so log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap imaps login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes mail_extra_groups: exalead mail_location: mbox:/opt/exalead/mail mail_debug: yes mail_plugins: acl auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd userdb: driver: prefetch socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: exalead group: exalead thanks for your help -- Rachid Zarouali Administrateur Systèmes/Applications AFNIC rachid.zarouali(a)nic.fr 01.39.30.83.47

2 2

[Dovecot] simultaneous access to folder
by David Lee 22 May '07

22 May '07

We have for many years been a UW-IMAP site, with users having their own traditional, private, mbox-format INBOX and folders: almost (but not quite) no complications of shared or simultaneous access. We have just completed a transparent transition to dovecot (official 1.0.0 release). But we have one residual issue affecting one important user account. UW-IMAP specifically only allows single access to "mbox" folders. If different IMAP connections are attempted to such a folder, the latest attempt kills off earlier connections. (That's just the way it works, which was mostly fine for us.) On this particular account we had explicitly set two folders to UW-IMAP's different "mbx" format, so that a group of staff could simultaneously access that folder and delete messages. This is by a single, common, id/pw account. But dovecot doesn't support "mbx" format. Is there a way for us to set up such a group-access folder under dovecot? I've checked wiki pages such as "http://wiki.dovecot.org/SharedMailboxes" but that doesn't seem to be clear on the particular matter of which formats are suitable for such simultaneous access. It talks about different users accessing a folder; in our case it is multiple instances of the the same user. Under dovecot, can we simply let it be "mbox" format? And can dovecot (unlike UW-IMAP) then handle the simultaneous access? [Background: this is just two folders (amongst many) on one username; the overall service successfully handles over 15,000 usernames. And the solution (work-around) will only need to last a few months until that whole account is Exchange-ified (but let's not digress...!)] If I've missed something on the wiki which addresses this matter, point me in the right direction... -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

2 1

[Dovecot] [PATCH] add some const's
by Andrey Panin 22 May '07

22 May '07

Add some const's. I think patch is self-explaining :) -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

Re: [Dovecot] No authentication sockets found
by Stewart Dean 22 May '07

22 May '07

Back on 5/9, I made a post by this subject http://dovecot.org/list/dovecot/2007-May/022482.html Timo replied: > The error message means that /var/run/dovecot/login directory or its > contents was deleted while Dovecot was running. I'd guess that you start > Dovecot too early and after startup another script goes and deletes the > entire /var/run/ directory. Or maybe that's done in background. Or > something.. and funkypunkydrunky reported: > I have lived the same problem in my system. But not evrytime sometimes it > only happens when i restart dovecot while mta is working. I think postfix > (my mta) cannot connect the new authentication socket. If i need the > restarting dovecot, i restart postfix too. It happens only for the above > situation. This happened again under these circumstances: 1) The machine had been up for 5 days. Having made some changes (largely de-verbosifying the dovecot.conf file), I killed the master dovecot process and restarted it (this before I was informed I could just do a kill -1 to effect the same result with less trouble). > May 14 15:34:09 mercury mail:info dovecot: Dovecot v1.0.0 starting up > > 2) Using TBird a an imap client, I got back on > May 14 15:24:48 mercury mail:info dovecot: auth(default): client out: CONT 1 > May 14 15:24:48 mercury mail:info dovecot: auth(default): client in: CONT 1 AHNkZWFuAEFsYW1hcjJi > May 14 15:24:48 mercury mail:info dovecot: auth(default): pam(sdean,10.20.10.75): lookup service=dovecot > May 14 15:24:49 mercury mail:info sendmail-SndRcv[2220248]: l4EJOief2949348: to=<cooper(a)bard.edu>, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=36928, dsn=2.0.0, stat=Sent > May 14 15:24:49 mercury mail:info dovecot: auth(default): client out: OK 1 user=sdean > May 14 15:24:49 mercury mail:info dovecot: auth(default): master in: REQUEST 6 909440 1 > May 14 15:24:49 mercury mail:info dovecot: auth(default): passwd(sdean,10.20.10.75): lookup > May 14 15:24:49 mercury mail:info dovecot: auth(default): master out: USER 6 sdean system_user=sdean uid=202 gid=200 home=/home/hcrc/sdean > May 14 15:24:49 mercury mail:info dovecot: imap-login: Login: user=<sdean>, method=PLAIN, rip=10.20.10.75, lip=192.246.229.21, TLS > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): Effective uid=202, gid=200, home=/home/hcrc/sdean > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): mbox: data=/home/hcrc/sdean/mail:INBOX=/var/spool/mail/sdean:INDEX=/var/dcndx/sdean > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): mbox: root=/home/hcrc/sdean/mail, index=/var/dcndx/sdean, inbox=/var/spool/mail/sdean > > > 3) 15 seconds after that, I started seeing a slew of these error messages, every 15 seconds or so: > May 14 15:25:03 mercury mail:info imapd[2052334]: Logout user=ot119 host=[10.20.10.10] > May 14 15:25:04 mercury mail:err|error dovecot: imap-login: No authentication sockets found > May 14 15:25:04 mercury mail:err|error dovecot: child 835676 (login) returned error 89 > 4) Since this is the production server, I kill the master dovecot instance and reinvoke dovecot in the foreground. I haven't seen the problem again since....but twice is problematic with just 3 people using DC. Now. My thoughts about what has been suggested so far, first by Timo: 1) This machine had been booted 5 days before so it's not a boot related problem 2) I'd find it hard to believe that something is nuking the contents of /var/run because: a) The directory doesn't exist by default in AIX; I created it for the DC install b) I have cron jobs that do cleanup with /var/log, /var/log/arc and /var/spool/mqueue, but nothing that does anything to /var/run 3) /var/run is local to the DC host and is not exported 4) funkypunkydrunky's comments about interaction with the MTA (sendmail in my case) seem unlikely, since it doesn't use SSL...or the same ports My questions: 1) What is happening? This is OpenSSL related, yes? 2a) Will this affect my production UWIMAP (which also supports/utilizes SSL)? If it doesn't, I can take my time debugging it (given that there are only 3 IT guys using DC currently), instead of frantically shutting it up by rebooting ASAP. I /think/ previously established DC connections continued to work 2b) How will this affect other imaps DC nex and pre-extant connections? I'm thinking of putting the whole IT dept on DC, but it'd be good to know how flaky things would get if/when this happens again. 3) What can I do to debug it, given that it happens infrequently and of no known causation? What should I check and look for afterwards? I guess I could put a cronjob that checks that /var/run/dovecot/login/ default= and ssl-parameters.dat exists periodically ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 5

[Dovecot] per user quota using LDAP entries
by Kenneth Oncinian 22 May '07

22 May '07

Hi List, This is my first post to this list so please be gentle :-). First of all, kudos to the developers of dovecot! Im trying to implement quota, and I followed the instructions in the wiki. My problem is the quota specified per user is not being honored, only the global quota setting. I do have an "quota = maildir:storage=204800" in the plugin area and enabled quota in the mail_plugins for both imap and pop3. This is my user attribute in /etc/dovecot-ldap.conf: user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuota=quota wherein the "mailQuota" attribute has an entry of "mailQuota: maildir:storage=30720". So i was expecting of a 300MB quota for that user, but dovecot is using the global quota of 200MB instead of 300MB. My dovecot version is 1.0.0 My dovecot.conf: ----------------------- # /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no mail_location: /var/mail/vhost/%u mail_debug: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: prefetch plugin: quota: maildir:storage=204800 trash: /etc/dovecot-trash.conf --- my dovecot-ldap.conf ------------------------------------------ hosts = localhost.localdomain dn = "cn=Directory Manager" dnpass = "xxxxxx" tls = no auth_bind = no ldap_version = 3 base = ou=people, dc=xx, dc=xx, dc=xx user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuota=quota pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = LDAP-MD5 -------------- sample LDAP query: ------------------------------ ldapsearch -x -Z '(uid=kenneth.oncinian)' # LDAPv3 # base <> with scope sub # filter: (uid=kenneth.oncinian) # requesting: ALL # # kenneth.oncinian, People, ph.panasonic.com dn: uid=kenneth.oncinian,ou=People, dc=xx,dc=xx,dc=xx givenName: Kenneth sn: Oncinian telephoneNumber: xxx-xxxx loginShell: /bin/bash gidNumber: 2516 uidNumber: 1000 mail: kenneth.oncinian(a)xx.xx.xx facsimileTelephoneNumber: xxx xxxx objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: posixAccount objectClass: account objectClass: mailgroup objectClass: mailgroupmanagement objectClass: mailgroupmanagement-globalconfig objectClass: mailgroupmember objectClass: mailrecipient objectClass: netscapemailserver objectClass: nsmailclient objectClass: ntuser objectClass: sambaSamAccount objectClass: proxyaccess objectClass: jabberaccess uid: kenneth.oncinian preferredLanguage: en cn: Kenneth Oncinian homeDirectory: /var/mail/vhost/kenneth.oncinian ou: Information Systems Department (ISD) x500UniqueIdentifier: mailAlternateAddress: koncinian(a)gmail.com ntUserDomainId: kenneth.oncinian ntUserCreateNewAccount: true ntUserDeleteAccount: true sambaSID: S-1-5-21-1685363153-499155089-1962420841-3000 sambaPrimaryGroupSID: S-1-5-21-1685363153-499155089-1962420841-3001 displayName: Kenneth Oncinian sambaPwdMustChange: 2147483647 sambaPasswordHistory: 00000000000000000000000000000000000000000000000000000000 00000000 sambaAcctFlags: [U ] myproxyaccess: yes myjabberaccess: yes sambaPwdCanChange: 1179303932 sambaLMPassword: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx sambaNTPassword: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx sambaPwdLastSet: 1179303932 mailQuota: maildir:storage=30720 # search result search: 3 result: 0 Success # numResponses: 2 # numEntries: 1 -- snip-- thanks and best regards, Kenneth

2 2

[Dovecot] Something about IMAP log
by Mu-Cheng Hsieh 22 May '07

22 May '07

Hi When the user used POP3 to handle her/his mailbox, we could know something happened as below. May 16 10:16:29 server dovecot: [ID 107833 local5.info] POP3(user): Disconnected: Logged out top=675/723063, retr=0/0, del=1/675, size=18124546 However, if the user used IMAP, we can not know what happened. May 18 15:25:42 server dovecot: [ID 107833 local5.info] IMAP(user): Disconnected: Logged out Is it possible to log something (e.g. delete or expunge) through IMAP? Thanks. -- Mu-Cheng Hsieh

2 1

Re: [Dovecot] Conflict -> Dovecot + Maildrop (maildirsize)
by Kenny Dail 21 May '07

21 May '07

> As I said in my original mail, this is simply a configuration issue: > > Looks like you're trying to tell the quota in bytes to Dovecot. Dovecot > wants it to be in kilobytes in its configuration file / userdb (it still > writes it in bytes to maildirsize, as you can see above it writes 1GB * > 1024 value in there). > > Where do you get the quota value for Dovecot? Divide it by 1024 and > it'll work right. I also use maildrop + dovecot. My quotas are stored in a mysql DB in couriers expected format: 50000000S (note the S on the end for storage). It makes for a very ugly userdb query trying to get that formatted to dovecot style of "maildir:storage=48828:ignore=Trash" How much would it take to allow dovecot's quota plugin to alternately accept "maildir:50000000S:ignore=Trash"? -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] Conflict -> Dovecot + Maildrop (maildirsize)
by Roberto Gonzalez Azevedo 21 May '07

21 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having some problems with quota from sql (maildir++) and dovecot + maildrop. I'm using maildrop for MDA and dovecot as IMAP server. When an e-mail arrives, maildrop calculates the quota and updates the 'maildirsize' file. When i use dovecot (webmail, thunderbird) it updates the 'maildirsize' too, overwriting it, but in a different way. Both programas don't use the same pattern for 'maildirsize'. Let me show: 'maildirsize' with maildrop: " 1073741824S 117395679 1760 3675 1 3675 1 1610 1 1612 1 3222 2 9641 1 9641 1 5301 1 6415 1 11716 2 15419 1 15419 1 " 'maildirsize' with dovecot: " 1099511627776S 585847701 102542 5504023 959 " In both examples the quota is 1GB (1073741824S). And now ? Does anybody known how to fix that ? thanks - -- - ---------------------------- Roberto Gonzalez Azevedo Rio de Janeiro, Brazil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGQcttF+EMwkXLsEwRAoUOAKC0VXeC4USHyxOhsE5TQixk77hpmwCgxk5P ABOk8XHurCx/gEnd5StCkB8= =B+0f -----END PGP SIGNATURE-----

3 6

[Dovecot] mail_location %d expansion
by Mark Par 21 May '07

21 May '07

hi, i'm trying to read the mails of virtual users by setting the value of mail_location to /mail/virtual/%d/%u/Maildir. however, the %d does not resolve to the domain. i am using ldap as my passdb and userdb. what am i missing here? using this telnet session, | $ telnet localhost imap | Trying 209.235.254.94... | Connected to localhost | Escape character is '^]'. | * OK Dovecot ready. | 1 login foo.bar(a)mydom.com TopSecret | 1 OK Logged in. | 2 select inbox | 2 NO Internal error occurred. Refer to server log for more information. [2007-05-21 04:32:42] here are the relative entries from the log: | May 21 04:32:42 localhost dovecot: auth(default): auth(iris.lames(a)pointwest.com.ph,xx.xx.xx.xx): username changed foo.bar(a)mydom.com -> foo.bar | May 21 04:32:42 localhost dovecot: auth(default): ldap(foo.bar,xx.xx.xx.xx): result: uid(user)=foo.bar uidNumber(userdb_uid)=2301 gidNumber(userdb_gid)=2301 userPassword(password)=TopSecret | May 21 04:32:42 localhost dovecot: auth(default): client out: OK 1 user=foo.bar | May 21 04:32:42 localhost dovecot: auth(default): master in: REQUEST 3 99112 1 | May 21 04:32:42 localhost dovecot: auth(default): prefetch(foo.bar,xx.xx.xx.xx): success | May 21 04:32:42 localhost dovecot: auth(default): master out: USER 3 foo.bar uid=2301 gid=2301 | May 21 04:32:42 localhost dovecot: imap-login: Login: user=<foo.bar>, method=PLAIN, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, secured | May 21 04:32:42 localhost dovecot: IMAP(foo.bar): mkdir(/mail/virtual//foo.bar/Maildir/cur) failed: Permission denied | May 21 04:32:59 ptwest1 dovecot: IMAP(foo.bar): mkdir(/mail/virtual//foo.bar/Maildir/cur) failed: Permission denied dovecot --version: 1.0rc29 dovecot.conf: ssl_disable: yes ssl_cert_file: ssl_key_file: disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:/share/mail/virtual/%d/%u/Maildir imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: prefetch dovecot-ldap.conf: auth_bind = no hosts = localhost base = dc=mycompany,dc=com dn = uid=dovecot,ou=auth,dc=mycompany,dc=com dnpass = TooMuchToAsk pass_attrs = uid=user,userPassword=password,uidNumber=userdb_uid,gidNumber=userd b_gid pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = PLAIN ldap_version = 3

2 1

[Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 21 May '07

21 May '07

Is anyone using LDAP along with Dovecot where mail is being accessed in the form of /var/vmail/${domain}/${user}? I have not figured out how to extract the domain from LDAP in order to make this work. I know this is sparse information but maybe there is an easy fix. If not, I can post more information. Bryan

6 13

[Dovecot] [Blasphemy] Can I build dovecot with "-fstack-protector"?
by Ralf Hildebrandt 21 May '07

21 May '07

I tried building dovecot using : CPPFLAGS="-fstack-protector" LDFLAGS="-lssp" ./configure That would result in a proper build, yet the binary would complain once being run: dlopen(/usr/local/lib/dovecot/imap/lib10_quota_plugin.so) failed: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so: undefined symbol: __stack_chk_fail_local Error: imap dump-capability process returned 89 and the like. So: Is it possible at all? And sorry for the blasphemy of daring to ask this in the first place :) -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de First Law of System Requirements: "Anything is possible if you don't know what you're talking about..."

3 14

[Dovecot] NFS lock contention for dovecot-uidlist
by Doug Council 21 May '07

21 May '07

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the dovecot-uidlist file, causing both deliver and Thunderbird to hang until the dotlock timeout runs out and the lock gets replaced. Once the lock is replaced, both will go about their business until the next lock miss and hang again. Eventually, everything is delivered and Thunderbird wakes up. Looking at each of the processes with truss, they are looping trying to stat the dotcot-uidlist.lock file, which no longer exists. We are using NFS, and based on reading through the mailing list archives, it can be a little difficult to get working reliably. But, I've read quite a few posts with our same or similar configuration having good luck with the setup. To reduce multiple box access-issues for now, I've been doing all testing with a single NFS client. Our configuration: NetApp filers for storage FreeBSD 6.2-RELEASE NFS clients Postfix 2.3.9 MTA Dovecot 1.0.0 LDA for local deliveries Dovecot 1.0.0 IMAP for pickup My dovecot.conf file is at the end of this message. NFS access cachcing on the FreeBSD has been disabled (vfs.nfs.access_cache_timeout = 0, see NFS mount options below). Postfix destination recipient and concurrency limit for the Dovecot LDA is set to 1. The NFS mount options: rw,tcp,-r=32768,-w=32768,nfsv3,dumbtimer,noatime,acregmin=0, acregmax=0,acdirmin=0,acdirmax=0 The dovecot.conf file: protocols = imap imaps pop3 pop3s disable_plaintext_auth = no syslog_facility = local0 ssl_cert_file = /nethere/conf/dovecot/ssl-nh-cert.pem ssl_key_file = /nethere/conf/dovecot/ssl-nh-key.pem login_greeting = Server ready. login_log_format_elements = user=<%u> ip=[%r] method=%m encryption=%c pid=%p login_log_format = %U$: %s mail_location = maildir:~/Maildir:INDEX=MEMORY mmap_disable = yes dotlock_use_excl = no lock_method = dotlock first_valid_uid = 200 last_valid_uid = 200 first_valid_gid = 200 last_valid_gid = 200 maildir_copy_with_hardlinks = yes namespace private { prefix = INBOX. inbox = yes } protocol imap { login_executable = /usr/local/libexec/dovecot/imap-login mail_executable = /usr/local/libexec/dovecot/imap imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { login_executable = /usr/local/libexec/dovecot/pop3-login mail_executable = /usr/local/libexec/dovecot/pop3 pop3_uidl_format = UID%u-%v pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)nethere.com sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master syslog_facility = mail } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth default { mechanisms = plain digest-md5 cram-md5 passdb ldap { args = /nethere/conf/dovecot/dovecot-ldap.conf } userdb ldap { args = /nethere/conf/dovecot/dovecot-ldap.conf } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = mailuser group = mailuser } } } It may just be "how it works", but the lock contention seems a little too fragile for busy mailboxes. Does anyone have any ideas? Thanks in advance for any assistance. -Doug

2 3

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 21 May '07

21 May '07

On May 18, 2007, at 11:33 PM, Daniel L. Miller wrote: >> Thank you for that info. Do you mind posting the relevant portions >> of your Postfix config? > main.cf: > .... > virtual_mailbox_base = /var/mail > virtual_mailbox_domains = <all your external / internal domains here> > virtual_mailbox_maps = ldap:/etc/postfix/maps/ldap-virtual.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:8 > virtual_alias_maps = hash:/etc/postfix/maps/virtual-aliases > .... > ##EOF > > ldap-virtual.cf: > server_host = localhost > search_base = ou=People,dc=amfeslan,dc=local > query_filter = (&(mail=%s)) > result_attribute = mail > result_format = /%d/%u/ > version = 3 > > The ldap-virtual settings look a little odd - but I'm rather proud > of my gimmick. You look for the mail address matching the sender > (mail = %s). Return that same address - but format it as domain/ > user. Append it to /var/mail and there it is! > > virtual-aliases is a simple file for me - I haven't settled on an > LDAP implentation for aliases yet I'm satisfied with. I'm using > ldap-account-manager for adminstration, and there's no explicit > provision for aliases within LAM or the base schemas used. I just asked Pascal as well how he gets around Postfix asking for mailacceptinggeneralid in order to allow messages to be accepted. How do you get around that? Dovecot is working fine but I can't get Postfix to accept messages because it keeps trying to find mailacceptinggeneralid. Bryan

3 3

[Dovecot] per-user delivery to commands
by martin f krafft 20 May '07

20 May '07

Hi, we are using dovecot IMAP in a complex virtual setup with almost 4000 accounts; postfix hands over to deliver for local delivery into a home directory as stored in the SQL database. That's /srv/vmail/$DOMAIN/$LOCALPART for most of them, but I'd rather not hardcode this scheme anywhere as it's in SQL. By a policy change, we need to insert a filter in this chain and the filter must be called in such a way that it knows where to find the "home" directory since the command needs to read a configuration file in ~/.mailfilt.rc. Thus I am looking for a way to make deliver pass incoming messages via this filter, but I cannot find any way to do that. Ideally I want this to happen before the LDA runs the mail through sieve. As an alternative, is there a command I can call to make dovecot look up $HOME for me so that I can use the dovecot data in the SQL database without making assumptions about the representation? A command that would proxy and convert my request into an SQL select as per dovecot.conf and feed back the result? Then I could use a Maildir delivery programme or even procmail to do the delivery according to the dovecot configruation. Thanks for any insights, hints, tips, help, jokes, flames, and useful information. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus(a)madduck.net will kill for oil!

1 1

[Dovecot] CVS to Mercurial switch
by Timo Sirainen 20 May '07

20 May '07

I've been meaning to switch away from CVS for a few years now, but I was never sure what I wanted to switch to, so I kept delaying it. I finally decided yesterday that Mercurial is pretty nice. The Mercurial repository is available from http://hg.dovecot.org/ (has a nice web interface). I wrote a small Mercurial mini-howto below. I'm not a Mercurial expert yet, so if you know better ways to do some things please let me know. The CVS repositories will still exist for a while, but they won't be updated anymore. If you notice the CVS being referenced somewhere (wiki, docs, etc.) please let me know (or fix yourself in wiki). 1. Fetch the initial repository: - ex. CVS HEAD: hg clone http://hg.dovecot.org/dovecot/ - ex. branch_1_0: hg clone http://hg.dovecot.org/dovecot-1.0/ - sieve plugin: hg clone http://hg.dovecot.org/dovecot-sieve-1.0/ The Sieve plugin currently works only with v1.0. I'll make a new "dovecot-sieve" repository for CVS HEAD later. 2. Update the repository: hg pull hg merge # only needed if you had done any changes hg update # to actually see the pulled changes All of this can be done with fetch extension. You can enable it by adding to ~/.hgrc: [extensions] hgext.fetch = After that you can use "hg fetch" which does all the above 3 commands (as far as I know, haven't really tried yet). 3. If you want to modify the sources, add your name to ~/.hgrc so it goes nicely into changelogs: [ui] username = Timo Sirainen <tss(a)iki.fi> You're able to "hg commit" your own changes into your repository. If you want to publish them, use "hg log" to see the changeset ID, and then use "hg export changesetid" to get patch ("hg export tip" might work too if you just want the last change(?)). You can then email the patch to Dovecot mailing list to get it merged. With CVS the ChangeLog file was updated every 15 minutes. Now the ChangeLog file doesn't exist in the repository at all. Instead it's generated with "hg log --style=changelog" when running "make dist".

6 12

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 20 May '07

20 May '07

On May 18, 2007, at 11:33 PM, Daniel L. Miller wrote: >> Thank you for that info. Do you mind posting the relevant portions >> of your Postfix config? > main.cf: > .... > virtual_mailbox_base = /var/mail > virtual_mailbox_domains = <all your external / internal domains here> > virtual_mailbox_maps = ldap:/etc/postfix/maps/ldap-virtual.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:8 > virtual_alias_maps = hash:/etc/postfix/maps/virtual-aliases > .... > ##EOF > > ldap-virtual.cf: > server_host = localhost > search_base = ou=People,dc=amfeslan,dc=local > query_filter = (&(mail=%s)) > result_attribute = mail > result_format = /%d/%u/ > version = 3 > > The ldap-virtual settings look a little odd - but I'm rather proud > of my gimmick. You look for the mail address matching the sender > (mail = %s). Return that same address - but format it as domain/ > user. Append it to /var/mail and there it is! > > virtual-aliases is a simple file for me - I haven't settled on an > LDAP implentation for aliases yet I'm satisfied with. I'm using > ldap-account-manager for adminstration, and there's no explicit > provision for aliases within LAM or the base schemas used. Thank you. I'll try this out. Bryan

1 0

[Dovecot] IMAP "freezing" on OSX
by Ben Carter 20 May '07

20 May '07

Hi, I've got a problem with dovecot on an Intel Mac OSX box. Basically, I was running an older verion (0.8.?, I think), and everything was fine. Then, when I upgraded to 1.0.0 via MacPorts, I found that periodically the system gets into a state where it simply stops dealing with IMAP requests. This tends to manifest itself as Thunderbird simply stalling, not fetching any new messages or folder contents. Sometimes quitting and restarting Thunderbird will help, but at other times the problem persists even afterwards. It seems to be linked to specific mailboxes (or messages?) - often one "problem folder" will reproduce the effect 100% whilst operating on the rest of the mailbox is fine. The problem /seems/ to often start as a result of trying to move messages between folders. I'm not certain if that's a root cause, though, or simply a consequence of "opening" an affected folder to perform the move. I have a spam folder with a large number (>10000) of messages in it, and trying to file stuff in there is a relatively surefire way to generate the problem. Once it's happened once, it inevitably escalates - restarting the client helps a bit, as does restarting dovecot. However, the only way to "fix" it and restore full functionality seems to be to delete all of the index and dovecot* files from the mailbox and folders... it generally takes a day or so after that before things start to go wrong again. All of this seems to point to corruption of the index files in some way, but the log is universally unhelpful - there are no error messages of any kind showing up there. The actual dovecot instance doesn't appear to crash or even "hang" properly - you can still make inbound IMAP connections OK, it's just that they don't ever give a response to commands that touch the affected mailboxes. Sometimes, I end up with temporary files lying around in the folders in the mailbox - apparently mails which were in the process of being moved when the server "gave up". I'm not sure if this is actually part of the problem, though, or just a symptom. My configuration (from dovecot -n) is: # /opt/local/etc/dovecot/dovecot.conf ssl_disable: yes disable_plaintext_auth: no login_dir: /opt/local/var/run/dovecot/login login_executable: /opt/local/libexec/dovecot/imap-login mail_location: maildir:~/Library/Mail/IMAP auth default: passdb: driver: pam args: * userdb: driver: passwd I'm running this on my personal machine, so there's only one user on the system, which I have set up using MailDir (on HFS). There's a fair bit of mail in many of my folders, but I doubt that's the problem as the previous version didn't seem to have any issues... I'm doing mail delivery using postfix directly into the maildir folders. That doesn't seem to be affected at all by this, though - mail still arrives fine even when Dovecot is failing to serve the folder contents to IMAP clients... you just can't see it ^-^ Has anyone seen an effect like this? Or does anyone have any pointers as to what I could try to debug it? Any suggestions would be very greatly appreciated! Thanks! -- Ben Carter - ben(a)gunk.demon.co.uk / ben(a)saillune.net (preferred)

4 6

[Dovecot] Thinking Outside the Box - Extending IMAP
by Marc Perkel 19 May '07

19 May '07

Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP interface? For example, personalized server settings. Suppose for example I want Thunderbird to edit my server side white lists or black lists or any other setting? Wouldn't it be nice if IMAP supported these changes? The connection is made. It's a secure connection that's been authenticated. Lets use it! Here's my initial thoughts on this. Suppose we extended IMAP to include an EXECUTE command as follows: EXECUTE command parameter, parameter .... On the server side is a config file that has the commands that execute will allow and what programs they run. When the execute command is seen by Dovecot then Dovecot runs the program in the list with the parameters passed. For example, suppose there is a command to add a user to a server side blacklist. 100 execute blacklist add joe(a)smith.com 100 ok Dovecot would open a two way connection to the server application allowing the client to talk to any application that is configured and can send and receive text. The connection persists until the server end terminates or the client closes the connection. With a tool like this one can write generic applications easily that would greatly expand what email clients can do interacting with the server. Not only can setting be changes but you could interact with server side calendars, pick up voice messages from phone systems, run any sort of groupware, all over a generic IMAP connection with this simple extension. Example: 100 EXECUTE calendar 100 ok 100 list schedule today 8:00 10:00 100 8:00 make coffee 100 9:00 meeting with boss 100 9:30 Call Joe Blow at 415-555-1212 100 ok 100 quit 100 ok One thing I'd like to use it for is an outgoing SMTP connection to send outgoing email over IMAP. A session might look like this: 999 EXECUTE smtp 999 220 darwin.ctyme.com ESMTP Exim 4.67 Sun, 13 May 2007 06:52:26 -0700 999 helo ctyme.com 999 250 darwin.ctyme.com Hello localhost [127.0.0.1] 999 mail from:marc@perkel.com 999 250 OK 999 rcpt to:dovecot@dovecot.org 999 250 Accepted ...... 999 quit 999 OK Who likes this idea?

10 23

[Dovecot] [Fwd: An invitation to the "morg" (Message Organization) mailing list]
by Luigi Rosa 19 May '07

19 May '07

This messages has been posted on SquirrelMail development mailing list. Maybe someone is interested in morg mailing list. Ciao, luigi -------- Original Message -------- Subject: [SM-DEVEL] An invitation to the "morg" (Message Organization) mailing list Date: Sat, 19 May 2007 17:08:03 +0300 To: squirrelmail-devel(a)lists.sourceforge.net Hello all, [Note: Yes, I'm not gone after all... There has been a change of plans! I'll be mostly active, time permitting] There is a new IETF effort on IMAP standards, continuing on the work of "IMAPExt" Working Group which has practically closed now. I'm sending this here because people might be interested in joining it and either contributing actively or simply keeping an eye on what will be available in IMAP servers soon. Personally I'm very interested on message and mailbox annotations / metadata, but some other stuff like dynamic, multi-mailbox, persistent searches and virtual mailboxes might be of more interest to you. Anyway, you can join this effort by subscribing to the morg mailing list: https://www1.ietf.org/mailman/listinfo/morg http://www.ietf.org/maillist.html To quote Dave Cridland about the purpose of the list: ====== Quote start ======== This list has been created to look carefully at how existing mail clients search through, sort, and generally organize email. We're also going to - hopefully - have client developers talk about what they'd like to be able to do. There's another group that might be interested in this, too - the "desktop search" people might well be interested in the ability to search effectively through remote message stores. Kjetil commented (on IMAPEXT) that this area might be very interesting to IMAP webmail people, who can't simply download everything and work locally, so if there are any IMAP webmail developers about it'd be interesting to hear from you, and if anyone knows any, please invite them to join. Meanwhile, we're also going to look at what features we have on the store - the IMAP server - that we can leverage for this. There's a number of RFCs and Drafts in the area of searching, organization, etc, and we'll need to ensure we're all aware of the current state of play. So, IMAP specialists need to start to enumerate these - any volunteers? It occurs to me that both the above might benefit from a Wiki page or two - Lisa, is there an Apps Wiki we can use for this, or should I just set one up? [For anyone new to the IETF, Lisa and Chris are the Applications Area Directors] Finally, we'll look at what new work we can do to satisfy client requirements, write up a draft charter, and move to BOF (the first stage in forming a new IETF working group), aiming to form a new working group to do the work, and produce RFCs as we decide is appropriate. I'd like to take a decision on going down this road after Chicago in the summer, hopefully ready for a BOF at the IETF in December. I personally think our ultimate output is likely to be some Standards Track and some Experimental specifications for extensions, and maybe a couple of Informational documents on how this stuff ties together. I'd also note that searching is something that, like a lot of IETF work, has patent minefields in places - please do read that Note Well stuff, and let us know of any IPR you're aware of as soon as you can. ====== Quote end ======== -- / +--[Luigi Rosa]-- \ Sheridan: We have an open door policy. Ivanova: And an open airlock policy. --"The Illusion of Truth", Babylon 5

1 0

[Dovecot] permissions on some dovecot directories
by Arkadiusz Miskiewicz 19 May '07

19 May '07

Hello, What smallest permissions are needed on directories: /var/run/dovecot /var/run/dovecot/login /var/lib/dovecot dovecot run as dovecot:dovecot. Currently I have 775 dovecot:dovecot /var/run/dovecot 750 root:dovecot /var/run/dovecot/login 755 root:root /var/lib/dovecot -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

1 0

[Dovecot] Maildir subfolder conversion from courier-imap
by Remy Blank 19 May '07

19 May '07

Hello, I am trying to convert a maildir that was managed by courier-imap up to now to dovecot. I am using the courier-dovecot-migrate.pl script as follows: courier-dovecot-migrate.pl --convert --recursive ~/Maildir However, this command only seems to convert the base maildir, but not all the subfolders. I thought that that's what the --recursive option was for. Is the command above supposed to convert the base maildir as well as the subfolders, or should I run the command on all subfolders separately (e.g. using a shell script)? Thanks. -- Remy

2 2

Re: [Dovecot] Replication plans
by Bill Boebel 19 May '07

19 May '07

On Fri, May 18, 2007 1:42 am, Troy Benjegerdes <hozer(a)hozed.org> said: > I'm going to throw out a warning that it's my feeling that replication > has ended many otherwise worthwhile projects. Once you go down that > rabbit hole, you end up finding out the hard way that you just can't > avoid the stability, performance, complexity, and whatever problems. > .. > I've found myself pretty much in the same "all roads lead to the > filesystem" situation. I don't want to replicate just imap, I want to > replicate the build directory with my source code, my email, and my MP3 > files. One of the problems with the clustered file system approach seems to be that accessing Dovecot's index, cache and control files are slow over the network. For speed, ideally you want your index, cache and control on local disk... but still replicated to another server. So what about tackling this replication problem from a different angle... Make it Dovecot's job to replicate the index and control files between servers, and make it the file system's job to replicate just the mail data. This would require further disconnecting the index and control files from the mail data, so that there is less syncing required. i.e. remove the need to check directory mtimes and to compare directory listings against the index; and instead assume that the indexes are always correct. Periodically you could still check to see if a sync is needed, but you'd do this must less frequently. I agree that there are already great solutions available for replicated storage, so this would allow us to take advantage of these solutions for the bulk of our storage without impacting the speed of IMAP. Bill

3 2

Re: [Dovecot] dbox redesign
by Bill Boebel 19 May '07

19 May '07

On Sat, May 12, 2007 9:10 am, Timo Sirainen <tss(a)iki.fi> said: > Fast copying > ============ > > Would be nice if copying a message from one mailbox to another wouldn't > require actually reading+writing the whole message contents. But I can't > really figure out how to implement this without requiring that there is > only a single dbox storage which contains the mails for all the > mailboxes, and the mailboxes themselves are just Dovecot's index files > containing pointers to the dbox storage. > > The problem with having everything in one storage is that if the index > files are broken, the messages can't be placed into correct mailboxes > anymore. > > Although one possibility would be treat mailboxes a bit similarly than > keywords. So that when a message is copied to another mailbox, the > message in dbox file is updated to contain information that it exists in > such and such mailboxes. Hmm. Perhaps that would be good enough, yes. > Yes, I think treating mailboxes similary to keywords is ideal. There really is no reason to physically separate mailboxes on disk. All that is needed is this logical separation if it can be done in a reliable way. Or maybe track this in mailbox-specific index files, and also have a corespodning text file that stores a list of messages that are contained in that mailbox... similar to maildir's dovecot-uidlist file. Then if you lose the index you can rebuild the index from the text file. Bill

4 7

[Dovecot] dovecot-shared being ignored?
by bhayden＠umn.edu 19 May '07

19 May '07

So, I'm working on a shared folder. Everything is nice except for one bit. My dovecot-shared file in the Maildir is either being ignored, or doesn't work the way I think it does. Any messages copied into the Maildir using a mail client are mode 660 and owned by the user who did the copy. Perms on the dovecot-shared file are 700 (I'm using Solaris ACLs in addition to the Dovecot ACLs in order to prevent unauthorized access via means that don't pass through Dovecot's IMAP server... ie SFTP/SCP, and so I'm using 700 with a rwx mask and access to the file set per user in the Solaris ACL). The message files being created 660 means they are accessible via SFTP/SCP to anyone in the group, and we have a single one for (nearly) all users. This is not really acceptable, so if anyone can offer guidance on the dovecot-shared that'd be great. I checked the wiki, and it has very minimal information. -Brian

2 1

[Dovecot] Virtual mailbox plans
by Timo Sirainen 18 May '07

18 May '07

Configuration ------------- There could be global and user-specific configuration files, similar to how ACLs work. I think the global virtual mailboxes should be only defaults though, so that users could delete them and create a new mailbox (virtual or non-virtual) with the same name. The global virtual mailboxes could be described in a single file, such as: Trash deleted Work/My Unseen (mailboxes "box1" "box2" "box2/*") or to "tss(a)iki.fi" to "timo.sirainen(a)iki.fi" unseen So the format would be <virtual mailbox name> LF <search condition, allowed to wrap to new line> LF LF <next virtual mailbox, etc.> Per-user virtual mailboxes could also be listed in a similar file. If the search condition is empty, a globally defined virtual mailbox has been deleted. Another way would be to have per-mailbox dovecot-virtual files, but I'm not sure how global virtual mailboxes could then be easily deleted. Also having all of them in a single file makes listing the mailboxes pretty fast. The search condition would be a standard IMAP SEARCH reply, with the exception of the mailboxes parameter to specify what mailboxes are used. Virtual mailboxes would be implemented as a new mail storage backend, so their namespace configuration would be like: namespace private { prefix = "virtual/" location = virtual:~/virtual:GLOBAL=/etc/dovecot/virtual-globals.conf } Syncing ------- ~/virtual directory would contain index files for the virtual mailboxes. If the index files don't exist, a full resync for the virtual mailbox is done. This means opening all the real mailboxes configured for the vbox, running the SEARCH command and adding the returned UIDs to the vbox's indexes. The index would contain at least mailbox ID and message UID numbers. Probably would be a good idea to also save UIDVALIDITY numbers just to be safe, although that's a bit of a waste of space and it could be handled in other ways too, such as changing the mailbox ID whenever its UIDVALIDITY changes.. Mailbox IDs would be mapped to names in mailbox list index. This index already exists, although there still seems to be some bugs in it. At least creating a new list index has a race condition. I should look into making the list index a bit more realiable. Also the list indexes work only with Maildir++ layout currently. After the vbox has initially been synced, it needs to also handle updates. I think optionally the updates could be done the same way as full sync (opening all mailboxes to see if there are changes), but a faster way would be to update the virtual mailboxes immediately when the real mailboxes are being modified. So IMAP, POP3 and deliver all need to be aware of the virtual mailboxes and what real mailboxes are mapped to what virtual ones. Whenever doing a change that causes the message to either be added to or removed from a virtual mailbox according to their rules, the virtual mailbox's index is updated immediately. Being able to determine this change quickly might be the biggest change required to Dovecot's base code. Changes ------- Virtual mailboxes would share their state with the real mailbox, so any flag changes done in the vbox would be immediately changed in the real mailbox as well. The same goes for expunges. Virtual mailboxes' transaction logs would use different records for expunges and removals. Expunges would be handled normally, but removals wouldn't be removed from the in-memory view of the mailbox until EXPUNGE command was given (although they would be removed from dovecot.index immediately, so new sessions wouldn't see them). This makes it possible to have a vbox with only unseen messages, but without the message getting expunged immediately after a client opens the mail. So the EXPUNGE command could act as a "session synchronization" command. And of course it would also expunge the messages that had been marked as \Deleted.

1 0

[Dovecot] deliver exit codes?
by Ralf Hildebrandt 18 May '07

18 May '07

Before switching to dovecot deliver for all local deliveries, I'm calling deliver from maildrop (yes, don't laugh). Snippet from my global /etc/maildroprc: # Store maillist & junk messages directly /^Precedence: ?list/ if ( $MATCH ) { exception { log "Bulk message: $MATCH" #to "$DEFAULT" to "|$DELIVER" } } I replaced to "$DEFAULT" (meaning: delivery to $HOME/Maildir) with to "|$DELIVER" (meaning: pipe the mail into dovecot deliver, and deliver to INBOX = $HOME/Maildir) This works really well, UNLESS a user exceeds his/her quota: In that particular case, deliver fails to deliver the mail and generates a bounce, all on it's own. It's exit status is 0 in that case, so my MTA (postfix) thinks that the mail has been delivered successfully. I'd prefer deliver to return EX_TEMPFAIL, which I can pass through maildrop back to postfix, which will then log a temporary error and will bounce the mail all by itself after 5 days time. But how? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de The Imperial Vendor or Contractor probably told them that droid armies don't need redundant command centers, nor any kind of high availability ... you're supposed to buy several, and cluster them. Redundant Array of Inexpensive Droids?

2 1

[Dovecot] Disable plaintext authentications
by Alexander Moisseev 18 May '07

18 May '07

Dear Sirs, I have Postfix 2.5 with Dovecot 1.0.0 as authentication server. Can I disable SMTP plaintext authentications for WAN clients, but allow it for LAN ones?

2 1

[Dovecot] UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist
by Chris Jeans 18 May '07

18 May '07

I'm having the following problem and would appreciate any help or tips on how to fix it. None of my users can send email via pop3 or imap clients the only consistent thing that i keep seeing in the logs are the following 2 messages: UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist sync: UID inserted in the middle of mailbox After searching the web all I can find is this link http://dovecot.org/list/dovecot-cvs/2007-May/008819.html which deals with Index: maildir-uidlist.c I'm running dovecot 1.0.0 on FreeBSD 6.2. -- Chris Jeans cmjeans(a)gmail.com

2 1

Re: [Dovecot] Replication plans
by Bill Boebel 18 May '07

18 May '07

On Fri, May 18, 2007 1:10 pm, Timo Sirainen <tss(a)iki.fi> said: > On Fri, 2007-05-18 at 12:20 -0400, Bill Boebel wrote: >> So what about tackling this replication problem from a different >> angle... Make it Dovecot's job to replicate the index and control >> files between servers, and make it the file system's job to replicate >> just the mail data. This would require further disconnecting the >> index and control files from the mail data, so that there is less >> syncing required. i.e. remove the need to check directory mtimes and >> to compare directory listings against the index; and instead assume >> that the indexes are always correct. Periodically you could still >> check to see if a sync is needed, but you'd do this must less >> frequently. > > This would practically mean that you want either cydir or dbox storage. > > This kind of a hybrid replication / clustered filesystem implementation > would simplify the replication a bit, but all the difficult things > related to UID conflicts etc. will still be there. So I wouldn't mind > implementing this, but I think implementing the message content sending > via TCP socket wouldn't add much more code anymore. > > The clustered filesystem could probably be used to simplify some things > though, such as UID allocation could be done by renaming a "uid-<next > uid>" file. If the rename() succeeded, you allocated the UID, otherwise > someone else did and you'll have to find the new filename and try again. > But I'm not sure if this kind of a special-case handling would be good. > Unless of course I decide to use the same thing for non-replicated > cydir/dbox. Dbox definitely sounds promising. I'd avoid putting this uid-<nextuid> file in the same location as the mail storage though, because if you can truly keep mail storage isolated and infrequently accessed, then you can do cool things like store your mail data remotely on Amazon S3 or equivalent.

1 0

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 18 May '07

18 May '07

On May 16, 2007, at 10:29 PM, razor wrote: > 17.05.07 в 05:06 Bryan Vyhmeister в своём письме > писал(а): > >> Is anyone using LDAP along with Dovecot where mail is being >> accessed in the form of /var/vmail/${domain}/${user}? I have not >> figured out how to extract the domain from LDAP in order to make >> this work. I know this is sparse information but maybe there is an >> easy fix. If not, I can post more information. >> >> Bryan > > i am using exim+dovecot+lda+openldap Thank you for the info. Bryan

1 0