- dovecot - dovecot.org

[Dovecot] Login with firstname.lastname instead of loginname - WORKING
by Ralf Hildebrandt 06 Jan '11

06 Jan '11

3 years ago (!) I aksed about this and finally I implemented it today: >> # NEW >> passdb { >> driver = passwd >> # firstname.lastname@charite.de:password:uid:gid:(gecos):home:(shell):user=realloginname >> args = /usr/local/etc/dovecot.login_via_email >> } >If you're only using it as a passdb, you don't need the uid/gid/home. So >an example field would be: > >firstname.lastname@charite.de:password::::::user=realloginname But now I'm encountering problems with users writing Firstname.Lastname(a)charite.de instead of firstname.lastname(a)charite.de (capitalized first letters) How can I "normalize" the usernames by lowercasing them? The coolest solution would be to strip realms AND force lowercasing of usernames in one pass -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

4 5

[Dovecot] Upgrade from 1.2.16 with sieve/managesieve to 2.0.8 with pigeonhole
by Nick Rosier 06 Jan '11

06 Jan '11

Hi, I would like to upgrade my server from 1.2.16 with sieve and managesieve to 2.0.8 with pigeonhole. Will I get all functionality I was having before? Should this migration be painless or will it require some additional work? I've read the Upgrading guide so I know I need to create an additional user. I've migrated the mails from Maildir to dbox in the past (using the convert plugin); does that mean I'm fully dbox or am I in a maildir-dbox hybrid situation? I've noticed that there are still some maildir-formatted mail (e.g. 1259960330.M322229P62710.mail,W=2195:2,S) in some of the maps. root@mail /usr/local/etc # dovecot -n # 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-PRERELEASE amd64 zfs protocols: imap imaps managesieve ssl_ca_file: /etc/ssl/cert.pem ssl_cert_file: /etc/ssl/mail.crt ssl_key_file: /etc/ssl/mail.key version_ignore: 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(managesieve): /usr/local/libexec/dovecot/managesieve-login valid_chroot_dirs: /var/spool/vmail mail_max_userip_connections(default): 50 mail_max_userip_connections(imap): 50 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_uid: 5000 first_valid_gid: 5000 mail_privileged_group: mail mail_location: dbox:/var/spool/vmail/%d/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): acl imap_acl fts fts_squat autocreate mail_plugins(imap): acl imap_acl fts fts_squat autocreate mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap 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(managesieve): dict_db_config: /usr/local/etc/dovecot-db.conf namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)xxx.xxx mail_plugins: sieve acl mail_plugin_dir: /usr/local/lib/dovecot/lda deliver_log_format: msgid=%m: %$ sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login cram-md5 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/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: acl: vfile:/usr/local/etc/dovecot/acls:cache_secs=300 acl_shared_dict: file:/var/db/dovecot/shared-mailboxes.db convert_mail: maildir:/var/spool/vmail/%d/%n expire_dict: proxy::expire expire: Trash 365 sieve: /var/spool/vmail/%d/%n/dovecot.sieve sieve_dir: /var/spool/vmail/%d/%n/sieve sieve_global_dir: /usr/local/etc/dovecot/sieve fts: squat fts_squat: partial=4 full=10 autocreate: Trash autocreate2: Drafts autocreate3: Spam autocreate4: Sent autosubscribe: Trash autosubscribe2: Drafts autosubscribe3: Spam autosubscribe4: Sent dict: expire: db:/var/db/dovecot/expire.db

1 0

[Dovecot] RFC: grouped (f)sync
by Attila Nagy 06 Jan '11

06 Jan '11

Hello, Currently Dovecot (and any other application, which cares about e-mail delivery) does at least one fsync per mail delivery. Given that hard disk drives have a very limited IOPS, this effectively limits the maximum mail delivery performance to a very low value, under utilizing the available storage IO capacity. Calculating with an average mail size of 50 kB and an average consumer HDD with 120 IOPS, the theoretical mail delivery performance will be 50 kB*120 IOPS=5.85 MBps. But if we could write 500 kB with every transaction, the delivery speed would be nearly 10 times as well. Dovecot have two process models: separate processes for each client connection and an async in-process multiplexing method. This works for each one, albeit the timing is somewhat different. So here's the idea: instead of fsyncing immediately in the LDA (lmtpd) every time when the client says "\r\n.\r\n" after the DATA phase, let's introduce a user settable timer (let's call that sync_delay from now on) and only sync in every sync_delay seconds. This would introduce an up to sync_delay seconds delay in lmtpd returning "250 Ok" to the client, but that's generally not a problem, because in high traffic setups there is a great amount of concurrency, so you could use a lot of client connections easily. Take an example setting of sync_delay = 100 ms. With this, 10 syncs would happen in every second from Dovecot LDA processes, meaning if a client connects in t=0 it will immediately got the response 250, if a client connects in t=0.05, it will get the response in 50 ms (in an ideal world, where syncing does not take time), and the committed blocks could accumulate for a maximum of 100 ms. In a busy system (where this setting would make sense), it means it would be possible to write more data with less IOPS needed. I can see two problems: 1. there is no call for committing a lot of file descriptors in one transaction, so instead of fsync() for each of the modified FDs, a sync() would be needed. sync() writes all buffers to stable storage, which is bad if you have a mixed workload, where there are a lot of non-fsynced data, or other heavy fsync users. But modern file systems, like ZFS will write those back too, so there an fsync(fd) is -AFAIK- mostly equivalent with a sync(pool on which fd is). sync() of course is system wide, so if you have other file systems, those will be synced as well. (this setting isn't for everybody) 2. in a multiprocess environment this would need coordination, so instead of doing fsyncs in distinct processes, there would be one process needed, which does the sync and returns OK for the others, so they can notify the client about the commit to the stable storage. Any opinions on this?

2 2

[Dovecot] virtual user problems
by G.Nau 06 Jan '11

06 Jan '11

dovecot 2.0.8 with postfix; transfer postfix -> dovecot by lmtp is fine Now i have to redirect a couple of virtual email names (like admin(a)mydomain.com, postmaster@, webmaster@, info@, sales@ ...) to a single user postbox named xxx@mydomain. As I use mysql for the auth-sql, it's returning userhome /home/<name>/maildir for all sql requests to <name>=admin, postmaster etc. I also verified that "doveadm user info" is returning the maildir/home: /home/xxx/maildir So I assumed, that all mails to admin, postmaster etc. are transfered to user xxx mailbox. But it isn't. Dovecot is creating the maildirs /home/admin/maildir, /home/info/maildir and so on. What do I miss here to get that virtual users mapped to the correct user xxx? Regards Birte

1 0

[Dovecot] good value of vsz_limit
by fakessh ＠ 06 Jan '11

06 Jan '11

hello dovecot network hello Timo I've just upgraded to 2.0.8 dovecot and I wonder it should be good value of vsz_limit I put value as 64 M but I do not know if it's good value return are welcome sincerely and happy new year this my dovecot -n ~]# /usr/sbin/dovecot -n # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.2-xxxx-grs-ipv6-32 i686 CentOS release 5.5 (Final) auth_mechanisms = plain login base_dir = /var/run/dovecot/ imap_capability = +IDLE listen = [::] log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_location = maildir:~/Maildir mail_max_userip_connections = 20 managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { inbox = yes location = prefix = separator = . } passdb { driver = pam } plugin { plugin = autocreate managesieve sieve sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever } protocols = sieve imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { mode = 0666 } vsz_limit = 64 M } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = * , [::] port = 993 } process_limit = 128 vsz_limit = 64 M } service imap { client_limit = 5 service_count = 0 } service managesieve-login { inet_listener managesieve-login { address = * port = 2000 } process_limit = 128 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = * , [::] port = 995 } process_limit = 128 vsz_limit = 64 M } ssl_ca = </etc/pki/tls/certs/root.crt ssl_cert = </etc/pki/tls/certs/r13151.ovh.net.crt ssl_key = </etc/pki/tls/private/r13151.ovh.net.key ssl_verify_client_cert = yes userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_max_line_length = 64 k mail_plugins = autocreate } protocol pop3 { mail_plugins = autocreate pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lda { hostname = r13151.ovh.net mail_plugins = autocreate sieve postmaster_address = postmaster(a)fakessh.eu sendmail_path = /usr/lib/sendmail } protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes ( in=%i : out=%o ) managesieve_max_line_length = 65536 } -- gpg --keyserver pgp.mit.edu --recv-key 092164A7 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7

1 0

[Dovecot] merging the best of mdbox and sdbox
by Joan Moreau 06 Jan '11

06 Jan '11

Hi, Is there a way to use the mdbox format (i.e. several message per files) for EACH IMAP folders (sdbox approach) ? Thanks Joan

2 5

[Dovecot] case (non-)sensitivity for folder names
by Phil Howard 06 Jan '11

06 Jan '11

Is IMAP supposed to be case sensitive or case in-sensitive? It seemed it would be case sensitive because I've had different cases of folders. But today I found I had two folders "Spam" and "spam", with directories ".INBOX.Spam" and ".INBOX.spam" on the server. Messages existed in each directory on the server and they were different. The messages could be read from Evolution. However, the list of messages had info mixed up between the folders. I then selected all messages in one of the folders and trashed them (click on trash icon). Messages disappeared in BOTH folders. On the server, after a couple minutes delay, messages in BOTH directories were flagged "T". That doesn't seem right. But I don't know enough about what IMAP is supposed to do, or on which end the names of folders get remapped into directory names, to even guess which is messed up here. I do know Evolution keeps a track of what it thinks the folder has, because in the past I have just "rm -fr" on a folder directory and Evolution still showed each message in its list, although it could not access them. Anyone know what's the deal with that? Unfortunately, there seems to be no operation in Evolution to tell it to discard its own cache. I'm also wondering if life would be any better if I used Thunderbird. -- sHiFt HaPpEnS!

2 6

[Dovecot] FTS crash
by Joan Moreau 05 Jan '11

05 Jan '11

Hi, Following the instructions on the page http://wiki2.dovecot.org/Plugins/FTS [1] I get the following: Jan 5 21:09:43 server dovecot: master: Error: service(imap): child 22514 killed with signal 11 (core dumps disabled) at every IMAP login Any suggestions ? Thanks Joan Links: ------ [1] http://wiki2.dovecot.org/Plugins/FTS

1 0

[Dovecot] sdbox to mdbox
by Joan Moreau 05 Jan '11

05 Jan '11

Hi all, What is the process to convert "sdbox" installation to a "mdbox" installation ? Thanks Joan

6 18

[Dovecot] courier-dovecot-migrate.pl maintaining order of pop3 uidl's
by Mark Zealey 05 Jan '11

05 Jan '11

Hi there, I've just been experimenting with the latest courier-dovecot-migrate.pl script and I notice that it favours keeping pop3 UIDL ordering rather than IMAP UID preservation. There is this comment (line 312): # POP3 clients may want to get POP3 UIDLs in the same order always. # Preserve the order even if it causes IMAP UIDs to change. Does anyone have details as to which clients this actually causes a problem with? If it's some really old software then perhaps we'd prefer to keep the imap UID's the same but change the POP3 UIDL ordering (not the UIDL numbering though of course) Thanks, Mark

2 2