March 2009 - dovecot - dovecot.org

[Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Andrey Panin 14 Aug '17

14 Aug '17

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 2

[Dovecot] Missing return-path on vacation messages
by Stephen Vaughan 30 Jul '09

30 Jul '09

Hi, I can see this has been discussed previously, was just wondering if it's been fixed in v1.1.x? -- Best Regards, Stephen

3 11

[Dovecot] GSSAPI cross-realm fixed
by Bryan Jacobs 08 Jul '09

08 Jul '09

Attached is a patch which in my environment (Linux/Heimdal 1.2.1) fixes cross-realm GSSAPI authentication. Changes it makes: 1. When using krb5_kuserok, do not call gss_compare_name to check that authn_name and authz_name are the same. Instead, make TWO calls to krb5_kuserok, one for each ID. If both IDs are acceptable, allow the login. 2. Disable checking that the name is a GSS_KRB5_PRINCIPAL_NAME, as this doesn't appear to be always the case for the authz_name. If I create a .k5login listing both username@REALM1 and username@REALM2, and make that file follow the appropriate security restrictions (world read, user only write permissions), this lets me use GSSAPI logins with principals from either REALM1 or REALM2. This leaves untouched the behavior in the case where krb5_kuserok is not available. Bryan Jacobs

2 3

[Dovecot] Connecting to dovecot
by Grant Lowe 06 Jul '09

06 Jul '09

Hi All, I've got a brand new dovecot installation. I'm new to dovecot, so please be gentle :-) Anyway, I'm getting some errors when I try to connect to dovecot. I've tried searching the web and haven't been able to find a lot of information. Here's the config info: # dovecot --version 1.1.2 # dovecot -n sudo dovecot -n # 1.1.2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: /var/mail/%u auth default: verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/mail/%u # Here are the errors I'm getting. dovecot: Sep 16 18:44:15 Info: imap-login: Login: user=<wfoatst>, method=PLAIN, rip=172.20.58.4, lip=172.20.8.215 dovecot: Sep 16 18:44:15 Error: IMAP(wfoatst): mail_location not set and autodetection failed: Mail storage autodetection failed with ho me=/var/mail/wfoatst Thanks!

3 3

[Dovecot] Spliting Folders for Efficiency
by Daniel Watts 28 Jun '09

28 Jun '09

Dear Timo, Would there be any sense in giving Dovecot the option to split folders into multiple subfolders when they reached a specified size (probably message count) limit? Dovecot would monitor folders and when they reached, say, 10,000 messages, silently split the folder on the filesystem to ensure that access remains fast. I know that Dovecot scales very well but this would give practically unlimited storage capability and also keep things fast. You could even have it so that the latest 100 messages are kept in their own folder for fast access. .Folder.new .Folder.cur .Folder.tmp could become: .Folder__1.new .Folder__1.cur .Folder__1.tmp and .Folder__2.new .Folder__2.cur .Folder__2.tmp with Dovecot merging them before display as just "Folder" within the mail client. This could be further extended so that Dovecot could be configured to store 'old' message folders in a separate location. We could then have slower+cheaper+larger storage mounted so that 'old mail' does not take up the expensive local SCSI disks on the machine. Mail from 2 years ago is much less likely to be accessed than mail from the last week. This would provide very neat behind-the-scenes archiving functionality. Looking forward to hearing your thoughts. Best, Daniel -- Squirrelmail Stable 1.4.8 (and developing on 1.5.2) PHP 5.x Hardened with Eaccelerator Apache 2.x Mysql 5.0.x Imapproxy over Dovecot 1.0.rc27 with Maildir all running on Gentoo Linux for ~5,000 users.

7 11

[Dovecot] compressed mbox patch
by Axel Thimm 16 Jun '09

16 Jun '09

Some ages ago there existed a compressed mbox patch, but now all I can find are posting about it. Does such a beast exist and would it remotely apply to today's dovecot? If not, is there any hope that something like that emerges? Thanks! -- Axel.Thimm at ATrpms.net

3 5

[Dovecot] Authentication cache, failure to login after changed password
by Tom Sommer 16 Jun '09

16 Jun '09

Hi, I have an issue with the authentication cache. When a user changes his password, the cache doesn't seem to get flushed. Meaning the user is unable to log in to his IMAP account after changing his password. Flow: - Log into IMAP account using pass1 - Approved - Stored in auth cache - Change password to pass2 in MySQL - Log into IMAP account using pass2 - Access is denied - Restart dovecot - Log into IMAP account using pass2 - Approved I'd really like to continue to use the auth cache, is there any solution to the above? perhaps a way to debug the cache and auth process? I wasn't able to activate auth_debug without restarting Dovecot and solving the problem. Using version 1.1.1, MySQL userdb, with "nopassword=Y". Maybe it's due to nopassword? Thanks -- Tom

2 16

[Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
by e-frog 03 Jun '09

03 Jun '09

Hi Timo, Trying 1.2.beta1 with expire plugin currently: When I set mail_location = maildir:~/.maildir the expire plugin doesn't delete messages. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: no messages left I also noticed that above command creates a new but empty directory 'mail' in user's home dir. However using mail_location = maildir:~/Maildir and of course moving the messages to it works. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: seq=1 uid=4078: Expunge . . Info: foo/Trash: seq=100 uid=4178: Expunge Info: foo/Trash: seq=101 uid=4179: Expunge Info: foo/Trash: timestamp 1235292536 -> 1235325429 My guess is that mail_location is not respected by expire-tool for some reason and in second case mailbox auto-detection makes it working? Thanks, e-frog ---------------------------------------------------------------------------------------------- #: dovecot -n # 1.2.beta1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-11-server i686 Ubuntu 8.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota expire fts fts_squat mail_plugins(imap): quota imap_quota expire fts fts_squat mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: dovecot group: Debian-exim master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% expire: Trash 1 expire_dict: proxy::expiredict sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve fts: squat fts_squat: partial=4 full=10 dict: expiredict: mysql:/etc/dovecot/dovecot-dict-sql.conf

2 9

[Dovecot] Feature Missing OUTBOX Folder
by Frank Doege 01 Jun '09

01 Jun '09

Hi Dovecot People, i have switched my system from courier-imap to dovecot and iam quite happy with it, the performance is well and i had nearly no problems. One little feature iam missing is in Courier i had a folder called "Outbox" there i could paste mails which i want to sent out. In some networks its not always available to sent mails via port 21, i know i could just set up my email server to another port but it was a nice feature. Is this a big afford or is it just alittle hack ? could it done via a little plugin ? Thanks Timo & all others for the great work ! Frank

5 7

[Dovecot] libsieve problems / wishes
by Steffen Kaiser 26 May '09

26 May '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm trying libsieve (853:42e154b8792e) to cope with our current installation, the following issues arise: 1) vacation addresses are compared case-sensitivly, e.g.: vacation :addresses [ "Steffen.Kaiser(a)example.com" ] ""; it won't match "steffen.kaiser@...". attached patch makes a first shot about that problem, leaving: 1a) maybe one should lower-case :addresses argument at compile time and my_address at run-time and then use strcmp() again. 1b) duplicate checks are case-sensitive, too. This is probably no big issue, because if the same person uses different variants of his/her mail address for sending, s/he does not deserve better. 1c) Suppression of replies to own mails are case-sensitive, too. Well, many people I know test that "it just works" by sending themselves a mail. I would disable this check. 2) we have about 157 ways to write the domain part. Not all accounts are available in all of them, but it's close to it. The old vacation program we used prior to "cmusieve" didn't care about the domain unless explicitly given. It was quite painful. Attached patch adds a "domainless" variant of :addresses arguments in such way, that vacation :addresses [ "Steffen.Kaiser" ] ""; matches any domain. Ideally, it would be better to specify all valid domains, but perhaps one can leave that for another approach with a different syntax, e.g. with "@*" as domain? Maybe, there is a better approach. Now there is possibility that common local parts are matched from alien domains easily. If to specify a set of "default" domains would be an option for libsieve, what is the suggested way: - - as user-option via dovecot.conf? - - as admin-enforced Sieve-script that sets some internal variables? aka using the multi-script capability - - ??? 3) Because I try to migrate from cmusieve v1.0, I have a name issue with "imapflags". README sec "* Supports all extensions provided by the original CMUSieve plugin:" and sec "Implementation Status" explains that "imapflags" is available. This is not true entirly: "imapflags" is not, lib-sieve uses the name "imap4flags" as defined by RFC. So, it leaves me with two options: 3a) convert all user scripts and hack Horde-Ingo, or 3b) have libsieve accept the alias "imapflags" for the extension "imap4flags". Would it be worhtwhile for libsieve to implement aliases for extensions, so that they are available in require by more than one name? About Horde-Ingo, maybe they have an update to use "imap4flags", too, but it looks like that I upgrade Dovecot before Horde. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSYccg3WSIuGy1ktrAQLlaQf+NHtyBxMb3aqnaw58zapo3/5kgqMM4GA+ 68el9d1CK4URjuk9io3MBsSzEJ4lRy6VFHNLw0jyNEnZp7l0vv5UoiK/+af7LCW5 H2T/qYL+lG/ul870t0/3q5wHmtrriAGQqE215C1u5/trJRX/sQLzDq1tbOtV4/vQ xUa8P0TXvCsgGSzCCmNiU0AenTIRGnxo+sCiyxnDKhgmWph/t06GYHX77CKwumK8 O57rh3RD9hA5yjicTbEZVLzeDDPEmCFliiSR6qMukfxOwX6LIxqhfw8n3cmSm8+X QyK6d/pBxy6EC14XhRQ7Jjtse+gWraiVJ/kcXKuW8sNPphtrGM1fdQ== =uuB6 -----END PGP SIGNATURE-----

5 11