- dovecot - dovecot.org

[Dovecot] Alerts and pre-authenticated connections
by Mike Brudenell 15 Mar '07

15 Mar '07

Greetings - Work moves onward here at setting up our Dovecot IMAP service and I've got a couple more questions, I'm afraid... :-} ============================================== Q1. The UW IMAP Server supports "pre-authenticated connections" -- does Dovecot? Specifically, it is possible to create a symlink from /etc/rimapd to the UW IMAP server binary and then use rsh or ssh from within the Pine mail client to execute that on the server to establish the IMAP connection: rsh imap.york.ac.uk /etc/rimapd Pine uses this to open a "pre-authenticated" connection to the UW IMAP server to avoid the user having to enter their username and password -- the rsh/ssh mechanism provides the IMAP server with the user's login name. I've grepped the Dovecot source but it looks like it doesn't support this. Am I right in thinking this? ============================================== Q2. The UW IMAP Server can issue "IMAP Alerts" The UW IMAP server can issue a sequence of one-line notices to mail clients using IMAP's ALERT mechanism. The notices are formed formed from each line in a systemwide file (if non-empty) and a per-user file (~/.imapalert). Many, but by no means all, mail clients display these notices to the user -- currently we use this mechanism to advise people who have totally run out of mail quota. I've grepped the Dovecot source for "alert" but it looks like the IMAP Alert mechanism isn't supported. Am I right in thinking this? ============================================== Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

2 7

[Dovecot] imap connection problems
by Ivan Pesin 15 Mar '07

15 Mar '07

Hi, Have encountered some strange behavior of dovecot: after few days of work (5-7 days, ~50 users, imap over ssl or tls) dovecot stops respond with "* OK Dovecot ready.". I.e. connection gets accepted, but no response from dovecot: [ivan@dyn-226 bin]$ telnet imap 143 Trying 192.168.100.9... Connected to imap.n-ix.com.ua (192.168.100.9). Escape character is '^]'. while obvious should be [ivan@dyn-226 bin]$ telnet imap 143 Trying 192.168.100.9... Connected to imap.n-ix.com.ua (192.168.100.9). Escape character is '^]'. * OK Dovecot ready. After dovecot restart everything works OK. This behavior we started to observe since rc24, before that on rc9 we didn't see that problem. Currently running on rc26. Any ideas? Thanks, Iv

2 2

[Dovecot] convert_mail plugin doesn't work
by Giuseppe Giacomini 15 Mar '07

15 Mar '07

Hi I'm trying to use convert_mail plugin to convert wu-imap mailbox to maildir. I'm using dovecot rc 27 on Centos 4.4 linux. I have user INBOX in /var/spool/mail/ and mbox file in mail ~/mail When I do the first login with a test user (test1), the plugin convert all the mbox under ~mail, but doesn't do any conversion on the INBOX (/var/spool/mail/test1). After conversion those are file in MailDir where .testmail is converted from ~mail all other folder (cur,new) are empty rwx------ 2 test1 persone 4096 Mar 15 11:59 cur drwx------ 2 test1 persone 4096 Mar 15 11:59 new drwx------ 5 test1 persone 4096 Mar 15 11:59 .testmail drwx------ 2 test1 persone 4096 Mar 15 11:59 tmp Why doesn't mail in /var/spool/mail/test1 be converted? Thanks This is my dovecot -n protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/share/ssl/certs/dovecot.pem ssl_key_file: /usr/share/ssl/private/dovecot.pem disable_plaintext_auth: no 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 first_valid_uid: 200 mail_location: maildir:%h/MailDir:INDEX=%h/.index/%u:CONTROL=%h/.control/%u mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins: convert 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_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd plugin: convert_mail: mbox:%h/mail:INBOX=/var/spool/mail/%u convert_skip_broken_mailboxes: yes and this is maillog dovecot: POP3(test1): Loading modules from directory: /usr/lib/dovecot/pop3 dovecot: POP3(test1): Module loaded: /usr/lib/dovecot/pop3/lib20_convert_plugin.so dovecot: POP3(test1): Effective uid=10400, gid=502 dovecot: POP3(test1): mbox: data=/homeH2/t/test1/mail:INBOX=/var/spool/mail/test1 dovecot: POP3(test1): mbox: root=/homeH2/t/test1/mail, index=/homeH2/t/test1/mail, inbox=/var/spool/mail/test1 dovecot: POP3(test1): mbox: data=/homeH2/t/test1/mail:INBOX=/var/spool/mail/test1 dovecot: POP3(test1): mbox: root=/homeH2/t/test1/mail, index=/homeH2/t/test1/mail, inbox=/var/spool/mail/test1 dovecot: POP3(test1): maildir: data=/homeH2/t/test1/MailDir:INDEX=/homeH2/t/test1/.index/test1:CONTROL=/homeH2/t/test1/.control/ test1 dovecot: POP3(test1): maildir: root=/homeH2/t/test1/MailDir, index=/homeH2/t/test1/.index/test1, control=/homeH2/t/test1/.contro l/test1, inbox= dovecot: POP3(test1): maildir: data=/homeH2/t/test1/MailDir:INDEX=/homeH2/t/test1/.index/test1:CONTROL=/homeH2/t/test1/.control/ test1 dovecot: POP3(test1): maildir: root=/homeH2/t/test1/MailDir, index=/homeH2/t/test1/.index/test1, control=/homeH2/t/test1/.contro l/test1, inbox= dovecot: POP3(test1): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0

2 1

Re: [Dovecot] Benchmarking CVS HEAD vs. v1.0
by Bill Boebel 15 Mar '07

15 Mar '07

On Wed, March 14, 2007 11:51 am, Timo Sirainen <tss(a)iki.fi> said: > Some new features in CVS HEAD are: > > - Mailbox list index. LIST command can be handled by reading the > mailboxes from the index. The index also contains the mailbox's message > counters, so STATUS command can be handled by only looking into the > index file. Nice. Now that it can pull this from index files, it would be pretty sweet if there was a variant of the STATUS command that would provide STATUS information for all mailboxes at once, rather than just for one. This could be used by webmail applications to update a folder listing that shows unseen mail counters with one command. Like maybe: a1 X-LIST-STATUS (MESSAGES UNSEEN) * X-LIST-STATUS "INBOX" (MESSAGES 8 UNSEEN 0) * X-LIST-STATUS "Drafts" (MESSAGES 0 UNSEEN 0) * X-LIST-STATUS "Trash" (MESSAGES 89 UNSEEN 3) a1 OK X-LIST-STATUS complete.

3 3

[Dovecot] [PATCH] fix gcc warnings in 1.0rc26
by Max Kellermann 15 Mar '07

15 Mar '07

Hi, I have made a small patchset to fix some of the GCC warnings. With these patches, I was able to compile dovecot r_1_0_rc26 with the following options: -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast Wstrict-prototypes -Wredundant-decls -Wcast-align -Wwrite-strings Wpacked -Winline -Wdisabled-optimization -Wno-long-long -Wundef Wfloat-equal -Wsign-compare -Waggregate-return -Werror Some of the changes may be arguable, escpecially the const warning fixes, example: char *pass = ""; I changed that to "pass = NULL" and changed the function call: - auth_request_verify_plain(request, pass, + auth_request_verify_plain(request, pass == NULL ? "" : pass, In other sources, I added "const" to parameters or to the return value where it seemed to make sense and didn't cause harm. Dealing with the const problem can be tricky, and sometimes dirty deconstification hacks are the only way to go.. however I believe we should always turn on "-Wconst" and explicitly add manual deconstitication where we assume it's not dangerous. I didn't fix all "const" and "missing noreturn" warnings, but my patches may be a good start... if there is further interest in fixing all of them, I'd be glad to do it. Max

2 1

[Dovecot] Problems with seen flag on OS X mail
by Nicolas Cianca 15 Mar '07

15 Mar '07

I'm having a problem with dovecot and apple mail not always remembering the seen flag. Some cases when mail is read it stays that way but other times it reverts back to unread on the next connection. I've tried to rebuild the Apple Mail mailbox but that doesn't do it. The mail is stored in Maildir format in the users home directory. All the connections Apple Mail are done via IMAP. I'm currently running rc27 on Centos and this has been ongoing since I switched from cyrus about 3 months ago. Any suggestions? nicolas cianca LIGHTBULB ncianca(a)lightbulb.com

2 1

[Dovecot] mbox and pop3, maildir and imap
by Hans Lammerts 15 Mar '07

15 Mar '07

Hi, Been reading a lot of posts about dovecot configuration, but can't really figure out if what I want is even possible or how to achieve this. My setup is simple : One linux machine that collects mail from my provider and sorts them for me and my wife, where my email is stored in Maildir format in ~myuser/.maildir and my wife's email is stored in mbox format in /var/spool/mail. Before making my wife crazy with a new way of getting and reading email with IMAP, I tried to do the following : My PC (not the linux server) runs either linux or XP, and the client I'm using is Evolution 2.8.2.2. I can get my email using IMAP without problems. My wife's PC just runs XP and the email client is Outlook which gets its email from the linux server through pop3. I've setup Dovecot to service both IMAP and POP3. The default_mail_env is now set to maildir:~%u/.maildir (which of course only reflects Evolution's IMAP need on my own PC) Now for the big question: How can I achieve that when I get email from the server using IMAP, I will automatically just look in the Maildir location (~%u/.maildir) __AND__ when my wife logs on through POP3, dovecot will only look for her email in her mbox directory /var/spool/mail/... ? In other words, different protocols used by (two) different users need to look for email in different locations (maildir and mbox). I tried to get this working using the Namespaces thingy in dovecot, but couldn't get it to work. Any suggestions (hyperlinks) are most welcome. Thanks, Hans

2 1

[Dovecot] solaris 10 + dovecot (1)
by aza zel 15 Mar '07

15 Mar '07

hi... i try to make dovecot (v1.0.r26) in solaris 10 and i have the following problem # ./configure --with-ldap ... ... Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : none Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword ldap (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword ldap (modules) Building with SQL drivers ............: # make ... ... Making all in pop3-login Making all in pop3 /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 -I/usr/sfw/include -export-dynamic -o pop3 client.o commands.o mail-storage-callbacks.o main.o ../lib-storage/register/libstorage-register.a ../../src/lib-storage/index/maildir/libstorage_maildir.a ../../src/lib-storage/index/mbox/libstorage_mbox.a ../../src/lib-storage/index/dbox/libstorage_dbox.a ../../src/lib-storage/index/libstorage_index.a ../../src/lib-index/libindex.a ../lib-storage/libstorage.a ../lib-storage/subscription-file/libstorage_subscription_file.a ../lib-imap/libimap.a ../lib-mail/libmail.a ../lib-dict/libdict.a ../lib-charset/libcharset.a ../lib/liblib.a ../lib/mountpoint.o ../lib/str-sanitize.o -export-dynamic -lsocket -lnsl -lrt -lsendfile gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -o pop3 client.o commands.o mail-storage-callbacks.o main.o ../lib/mountpoint.o ../lib/str-sanitize.o ../lib-storage/register/libstorage-register.a../../src/lib-storage/index/maildir/libstorage_maildir.a ../../src/lib-storage/index/mbox/libstorage_mbox.a ../../src/lib-storage/index/dbox/libstorage_dbox.a ../../src/lib-storage/index/libstorage_index.a ../../src/lib-index/libindex.a ../lib-storage/libstorage.a ../lib-storage/subscription-file/libstorage_subscription_file.a ../lib-imap/libimap.a ../lib-mail/libmail.a ../lib-dict/libdict.a ../lib-charset/libcharset.a ../lib/liblib.a -lsocket -lnsl -lrt -lsendfile ld: error de elf: archivo pop3: elf_update: Error de E/S: escritura en salida: No queda espacio de memoria en el dispositivo collect2: ld returned 1 exit status *** Error code 1 make: Fatal error: Command failed for target `pop3' Current working directory /maxi/dovecot-1.0.rc26/src/pop3 *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='lib lib-dict lib-sql lib-ntlm lib-settings lib-charset lib-mail lib-imap lib-index lib-storage lib-auth auth dict master login-common imap-login imap pop3-login pop3 deliver util plugins'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /maxi/dovecot-1.0.rc26/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /maxi/dovecot-1.0.rc26 *** Error code 1 make: Fatal error: Command failed for target `all' if i do # df -h Sistema de archivos tamaño usados aprovechar capacidad Montado en /dev/dsk/c0d0s0 4,4G 4,3G 57M 99% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K 0% /system/contract proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab swap 689M 652K 688M 1% /etc/svc/volatile objfs 0K 0K 0K 0% /system/object /usr/lib/libc/libc_hwcap1.so.1 4,4G 4,3G 57M 99% /lib/libc.so.1 fd 0K 0K 0K 0% /dev/fd swap 688M 40K 688M 1% /tmp swap 688M 24K 688M 1% /var/run /dev/dsk/c0d0s7 32G 583M 31G 2% /export/home /export/home/sunone 32G 583M 31G 2% /home/sunone ¿if a dovecot problem with solaris or my configuration of the solaris installation? ¿how i can fix this problem? ¿why this happends? -- Salu2 ;)

4 3

[Dovecot] Newbie index infrastructure and location questions
by Stewart Dean 15 Mar '07

15 Mar '07

I've been lurking for a year or more and am now actually bringing Dovecot up (it seems that any time I make a serious effort at this, something else falls in the pot and I have to give it up yet again). Index questions: I understand the indices should be placed in a non-file-system-quoted place. I have in mind to create /var/dcndx 1) Roughly how much space do indices take up (so I can size space for a directory for them)? I have 4000 users, average mbox inbox size is 5.5MB (totalling 22GB), the number of messages/user mailbox I'd guess to average around 100 and go as high as 5000. They have maybe as much as 3x times space and messages in folders, though I guess the average is about half that of INBOX 2) I'm clear that DC will automagically create the index files, but a) do I have to create a subdirectory for each user, ex: /var/dcndx/user1 b) Is there one index file theat handles a user's mailbox and folders or a separate one for each? -- ==== 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] Newbie NFS question
by Stewart Dean 15 Mar '07

15 Mar '07

As is usually the case, I'm not sure enough of what the DC docs are referring to; there are some implicit info assumptions that I, the Newbie, miss... Anyway, here is my situation Dovecot is to run on one machine only, its index files are stored in on a separate, non-quotaed, not NFS filesystem. INBOX and folder filesystems (all mbox format) are native to this machine and are NFS exported to three machines with root access. NFS access can be NFS V2, or 3 or 4. 1) a user maintenance server that may add or delete users and their INBOXES/folders 2) a mailing list server that writes mailings email to the NFS mounted file system of user INBOXes 3) A user login machine where the users may access their INBOXes and folders All machines are running vanilla IBM AIX; I have never known there to be corruption from NFS locking problems, and am not aware of any locking/caching parameters for AIX's NFS implementation. All machines are running NTP synched to a common NTP master server My questions: 1) Since my index files are stored in on a separate, non-quotaed, not NFS filesystem, can I correctly assume this means I can ignore the nmap_disable and lock_method parms? 2) The docs say: > The easiest way to get better performance without caching problems is > to just make sure the user is always redirected to the same server. If > you can manage to do that, then it's safe to enable attribute caching. The INBOXes and folders live on the mail server where a) DC is going to run and b) they are exported to the three other machine. Does this mean that I don't have to mess with actimeo? 3) Pardon my ignorance....Is actimeo set on the NFS server as an attribute of exportation or on the NFS client on the imported FS...or both 4) Is there any reason related to data integrity or performance to prefer NFS V2 or 3 or 4? 5) Are there other questions I should ask of IBM about NFS client and Server daemon config Thanks in advance........... -- ==== 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