- dovecot - dovecot.org

[Dovecot] Post Login Script in 2.0
by Mark Moseley 30 Mar '10

30 Mar '10

Been digging through the list archives but I didn't see anything about this specifically. I've been playing with trying to get the post-login script stuff working with 2.0 (tried with a mercurial checkout from today and one I had kicking around from a few days ago), mainly to run the courier conversion script after logins. I'm using the 'executable' arg in 'service pop' and 'service imap' and I've tried with and without "drop_priv_before_exec=yes". I've just been using the test script mentioned in the wiki that dumps the environment to a file in /tmp and then execs libexec/imap or libexec/pop. The script specified in 'executable' is definitely getting executed just fine and logins work just fine. When it executes though, they're getting just the basic environment, as opposed to the environment that shows up in 1.2.11 full of various MAIL*/NAMESPACE*/etc variables. And I see in strace output that there's no batch of env vars getting passed around anymore, even when dovecot invokes libexec/imap or libexec/pop directly. Is there a setting that tells the dovecot process to fork the post-login script with the fully populated set of environment variables? Or alternatively, in the 2.0 world, is the idea to get that info out of the /var/run/dovecot/config socket? If so, is there an example somewhere? I can post my configs, but I figured that since this is a conceptual problem, I might as well ask first without pasting a few pages of "dovecot -a" output :)

2 5

[Dovecot] Problem with IMAP on port 993
by Jerry 30 Mar '10

30 Mar '10

This is probably a misconfiguration of my MUA; however, I thought I would ask here first. I am using IMAP with Dovecot. Claws-mail is my MUA. Now, when fetching mail via port 143, everything works fine: Mar 29 10:33:00 imap-login: Info: Login: user=<user(a)domain.net>, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, TLS However, when I attempt to fetch mail via port 993, I get this message in the log: Mar 29 10:28:35 imap-login: Info: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: Disconnected I think I have everything set up correctly. # dovecot -n (portions obfuscated) # 1.2.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.3-STABLE i386 ufs log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): localhost:2000 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_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: Greetings From my-domain.net verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location(default): maildir:/var/mail/vhost/my-domain.net/user:INDEX=/var/mail/vhost/my-domain.… mail_location(imap): maildir:/var/mail/vhost/my-domain.net/user:INDEX=/var/mail/vhost/my-domain.… mail_location(pop3): maildir:/var/mail/vhost/my-domain.net/user:INDEX=/var/mail/vhost/my-domain.… mail_location(managesieve): maildir:/var/mail/vhost/my-domain.net/user 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_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): expire mail_plugins(imap): expire mail_plugins(pop3): expire mail_plugins(managesieve): 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 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): dict_db_config: /usr/local/etc/dovecot-db.conf managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) lda: postmaster_address: postmaster(a)my-domain.net mail_plugins: expire mail_plugins: sieve sieve: /usr/local/etc/dovecot/sieve/user.sieve sieve_global_path: /usr/local/etc/dovecot/sieve/user.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: cram-md5 digest-md5 plain login username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@+ username_format: %Lu 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: 438 master: path: /var/run/dovecot/auth-master mode: 438 plugin: expire: Trash 1 Spam 30 Sent 10 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf -- Jerry Dovecot.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Have the courage to take your own thoughts seriously, for they will shape you. Albert Einstein

4 6

[Dovecot] Dovecot 2.0 zlib and dbox
by Renaud Allard 30 Mar '10

30 Mar '10

Hello, As per wiki instructions, I tried to enable zlib compression of mails by adding/modifying the following snippets of configuration: plugin { zlib_save_level = 6 zlib_save = gz } and protocol imap { mail_plugins = fts fts_squat autocreate zlib imap_zlib imap_id_log = * } I am using dbox format and delivering the mails via dovecot deliver, however mails don't seem compressed at all. It is not very clear if compression is available for something else than maildir and mbox, so is compression available with dbox format? I am using dovecot-2-0-aefa279e2c70 from hg. Best Regards

2 3

[Dovecot] Dovecot 2.0beta4 HG 11014: Crashes on parsing settings via LMTP service
by Thomas Leuxner 29 Mar '10

29 Mar '10

Hi, unfortunately no core was dumped. Let me know if you need more info to debug. ==> /var/log/dovecot.log <== Mar 27 08:13:38 spectre dovecot: lmtp(8362): Connect from local Mar 27 08:13:38 spectre dovecot: lmtp(8362): Panic: file settings-parser.c: line 1501 (settings_link_get_new): assertion failed: (diff + sizeof(*old_link->array) <= old_link->parent->info->struct_size) Mar 27 08:13:38 spectre dovecot: lmtp(8362): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f055dec6712] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f055dec677a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f055dec6b23] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f055dea6993] -> /usr/lib/dovecot/libdovecot.so.0(settings_parser_dup+0x1d2) [0x7f055dea6be2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup+0x191) [0x7f055e1370c1] -> dovecot/lmtp(cmd_rcpt+0x4d4) [0x407924] -> dovecot/lmtp(client_input_handle+0x19b) [0x4066db] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xcb) [0x7f055ded144b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f055ded05c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f055dec0323] -> dovecot/lmtp(main+0x123) [0x405bf3] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f055d74d1a6] -> dovecot/lmtp [0x4059f9] Mar 27 08:13:38 spectre dovecot: master: service(lmtp): child 8362 killed with signal 6 (core not dumped) Regards Thomas

3 6

[Dovecot] dovecot: auth(default): Fatal: Unknown database driver 'mysql'
by Glen Lee Edwards 29 Mar '10

29 Mar '10

I just tried upgrading from 1.1.rc6 to v1.2.11, and am getting the following error: dovecot: auth(default): Fatal: Unknown database driver 'mysql'. If I change the respective line in dovecot-sql.conf from driver = mysql to driver = pgsql the error message changes accordingly: dovecot: auth(default): Fatal: Unknown database driver 'pgsql'. I quit using 1.1.rc6 because it started choking on my Debian system, so I'm back to using the stable Debian version - 1:1.0.15-2.3+lenny1. Where are the drivers kept when I do a default build, and where in the configuration file does it tell dovecot to look for the drivers? Other suggestions on a fix? Glen

3 7

[Dovecot] Which Authentication Method Best Between FreeBSD and Macintosh?
by Martin McCormick 29 Mar '10

29 Mar '10

I recently discovered that I need to occasionally forward Email from a FreeBSD system to a Macintosh. Imap does look like the best solution to this problem. The mail program on the Mac lists several protocols such as pop (okay with me) and SSL certificates which I want to avoid if at all possible. Which of the several listed methods of authentication should I compile in as I build dovecot on the FreeBSD system? Options for dovecot 1.2.10 [X] KQUEUE kqueue(2) support [ ] SSL SSL support [ ] IPV6 IPv6 support [ ] MANAGESIEVE ManageSieve support [ ] GSSAPI GSSAPI support [ ] VPOPMAIL VPopMail support [ ] BDB BerkleyDB support [ ] LDAP OpenLDAP support [ ] PGSQL PostgreSQL support [ ] MYSQL MySQL support [ ] SQLITE SQLite support � � IPV6 is not used here and my laziness says to avoid creating any new data bases or data base servers to support something I will probably use once every 2 or 3 months for one or 2 messages. I just want to get on the Mac and read messages posted in a certain account on the FreeBSD system. Sorry if this all sounds a bit odd, but I usually read mail on the FreeBSD box. Occasionally, I get a message containing a 20-mile-long URL that works better when using the Mac's safari browser tools. Presently, I have succeeded in compiling dovecot on the freeBSD system which runs and looks like it is ready to work. The Mac contacts the freeBSD box and then both appear to get a death grip on each other and nothing much happens until I force a quit of mail on the Mac. Thanks for any suggestions. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group

1 0

Re: [Dovecot] I stream read - stale NFS file handle (reboot of server)
by Damon Atkins 29 Mar '10

29 Mar '10

NFS Security 101 for NFSv2 and v3 (NOT NFSv4 a long time ago I was part of the discussion group for NFSv4 spec the short comings of v2 and v3 have been fixed) SRV: Server Exports File System /abc/123 access only to host=xyz.domain.com XYZ: Client Mount mount's SRV:/abc/123 SRV: "mountd" gets a request from SRV check access list, and if the client is allowed access, returns File Handle for the top of the mount point (I will call this the FileSystemHandle, this changes after every reboot) XYZ: Client talks to the SRV NFS Server "nfsd" using FileSystemHandle (which represents /abc/123), To find a FileHandle for a file the client sends the NFS server the FileSystemHandle, then finds the next File Handle (/mydir) and the next FileHandle (myfile) and the client has found the FileHandle for /abc/123/mydir/myfile NFSD (v2/v3) is stateless other than the information provided by mountd (mount requests) and lockd (file locking). When you share/export a file system, as part of this a FileSystemHandle is generated and stored somewhere for /abc/123 most likely store in the kernel. SRV: Reboots, a new FileSystemHandle is allocated XYZ: Reports Stale File Handle for everything (if not most things) which was mounted from SRV or the mount point on the client does not respond. A long time ago FileSystemHandle would stay the same between reboots and you wouldn't get this problem other than on an individual file. To handle deleted files which are in use by NFS clients some servers rename them to .nfs* because if one client deleted and other clients where accessing the file then they would get Stale NFS handle. Once in a while a NFS server will do find $dir -type f -name .nfs\* -mtime +7 -mount -exec rm -f {} \; to clean up. NFSv4 does not use mountd or lockd. My advice to anyone on old versions of NFS upgrade to NFSv4 as soon as possible and implement KerbV5 for improved authentication and disallow NFSv2/3 access. If you do not get the Stale File Handle error when the server reboots, it most likely means the FileSystemHandle is not changing between reboots, but then you may have more security issues. Software which Clusters NFS Servers ensures that the node which takes over, uses the same FileSystemHandle (which may only change if the whole Cluster is shutdown) Cheers Damon.

2 4

[Dovecot] failed: Too many open files
by Masaharu Kawada 29 Mar '10

29 Mar '10

Dear list, I have questions about content of the following error messages. ---</var/log/secure>--- dovecot-auth:　PAM　unable　todlopen(/lib/security/pam_nologin.so) dovecot-auth:　PAM　[error:/lib/security/pam_nologin.so:　cannot　open　shared　object　file:　Too　many　open　files] dovecot-auth:　PAM　adding　faulty　module:/lib/security/pam_nologin.so dovecot-auth:　PAM　_pam_load_conf_file:　unable　to　open　/etc/pam.d/system-auth dovecot-auth:　PAM　unable　to　dlopen(<*unknown　module　path*>) dovecot-auth:　PAM　[error:　*unknown　module　path*>:　cannot　open　shared　object　file:　Too　many　open　files] dovecot-auth:　PAM　adding　faulty　module:　<*unknown　module　path*> dovecot-auth:　PAM　_pam_load_conf_file:　unable　to　open　/etc/pam.d/system-auth dovecot-auth:　PAM　_pam_load_conf_file:　unable　to　open　/etc/pam.d/system-auth dovecot-auth:　PAM　unable　to　dlopen(/lib/security/pam_deny.so) dovecot-auth:　PAM　[error:/lib/security/pam_deny.so:　cannot　open　shared　object　file:　Too　many　open　files] dovecot-auth:　PAM　adding　faulty　module:/lib/security/pam_deny.so ---</var/log/maillog>--- dovecot: auth(default): pam(xxx(a)xxx.com,127.0.0.1): pipe() failed: Too many open files dovecot: auth(default): pam(xxx(a)xxx.com,127.0.0.1): pipe() failed: Too many open files It seems that this is due to that there are files existed to open beyond its limitation. Other information that could be relevant are as follows. # ulimit -n 1024 # cat /proc/`cat /var/run/dovecot/master.pid`/limits cat: /proc/7273/limits: No such file or directory # lsof -p `cat /var/run/dovecot/master.pid` | wc -l 29 # ls /proc/`pidof dovecot-auth`/fd | wc -l 1024 >From the above result, dovecot-auth proccess opened 10243 files, and that seems to be the limit. So I expect that adding following lines into /etc/init.d/dovecot could be fix this issue. # vi /etc/init.d/dovecot --- . /etc/init.d/functions ulimit -n 4098 <-add test -x /usr/sbin/dovecot || exit 0 <-add if [ -f /etc/sysconfig/dovecot ]; then . /etc/sysconfig/dovecot fi --- Is my understanding right? Even if so, how could I verify what files are opened by dovecot-auth? I would very much appreciate it if someone in this list could provide comments/suggestions. Sincerely,

3 6

[Dovecot] Improper use of IN-USE in case of a failed authentication
by Rainer Weikusat 29 Mar '10

29 Mar '10

RFC2449 defines the IN-USE extended POP3 response code as 8.1.2. The IN-USE response code This occurs on an -ERR response to an AUTH, APOP, or PASS command. It indicates the authentication was successful, but the user's maildrop is currently in use (probably by another POP3 client). http://www.faqs.org/rfcs/rfc2449.html In contrast to this, the POP3 login code in client_authenticate.c will send IN-USE whenever authentication was not successful because of some kind of internal failure[*]. [*] Noticed during experiments with a shell SQL database driver which only ever returns errors as reaction to any query. I happen to know of at least one (partial) client implementation (I happen to have written which is used by an iPhone application for POP3 user credential verification) which actually interprets IN-USE as it is defined by the RFC.

2 2

[Dovecot] dsync multiserver
by Renaud Allard 28 Mar '10

28 Mar '10

Hello, Maybe I am missing something obvious here (I would hope so), but is there any way to use dovecot deliver to spawn dsync to replicate changes. And dovecot to trigger dsync to sync mailboxes when a change has been done. Thanks

2 1