- dovecot - dovecot.org

[Dovecot] mail_log plugin logs UTF-8 mailbox name
by Ewald Dieterich 11 Jul '12

11 Jul '12

A small bug in the mail_log plugin: When I copy a mail from the inbox to a mailbox with special characters, the mailbox name is logged in UTF-8: [...] copy from INBOX: box=INBOX.Euro €, [...] I guess the name should be in mUTF-7, like it is done when I copy the other way round: [...] copy from Euro &IKw-: box=INBOX, [...]

2 2

[Dovecot] more info (more dsync problems)
by Jeff Gustafson 11 Jul '12

11 Jul '12

Rerunning the dsync command right after the timeout (see previous message) gave me these errors: dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user%domain.com/mdbox/s torage/m.60 (around offset=807789): msg header has bad magic value dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user%domain.com/mdbox/s torage/m.60 (around offset=807789): msg header has bad magic value dsync-local(vmail): Error: remote: dsync-remote(vmail): Warning: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: Inconsistency in map index (2,75904 != 2,82524) dsync-remote(vmail): Warning: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: rebuilding indexes dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage/m.60 (around offset=807789): msg header has bad magic value dsync-local(vmail): Error: remote: dsync-remote(vmail): Warning: dbox: Copy of the broken file saved to /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage/m.60.broken dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: Corrupted dbox file /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage/m.60 (around offset=807789): EOF reading msg header (got 0/30 bytes) dsync-local(vmail): Error: remote: dsync-remote(vmail): Warning: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: rebuilding indexes dsync-local(vmail): Error: remote: dsync-remote(vmail): Error: mdbox /home/.incoming_mail_migrations/users/user% domain.com/mdbox/storage: Duplicate GUID 1341304555.M433317P26661.n13,S=142447,W=144391 in m.62:790375 and m.60:790375

1 0

[Dovecot] more dsync problems: Error: proxy client timed out
by Jeff Gustafson 11 Jul '12

11 Jul '12

Hi all, I'm using dsync for backups. I recently upgraded to 2.1.7 due to issues with dsync mirror/backups. 2.1.7 fixed the issue with the guid conflict, but now I'm seeing this error on a couple of mailboxes: Error: proxy client timed out (waiting for output stream to flush, 0 bytes left) If there are 0 bytes left, why is it trying to flush? I'm using this command to backup the mailbox: dsync -vo mail_home=/home/users/user%domain.com backup ssh vmail(a)10.1.2.2 dsync -o mail_home=/home/.incoming_mail_migrations/users/user%adomain.com Any ideas? ...Jeff

1 0

Re: [Dovecot] Howto add another disk storage
by Stan Hoeppner 10 Jul '12

10 Jul '12

On 7/8/2012 5:16 PM, Matthias-Christian Ott wrote: > On 2012-07-08 23:29, Stan Hoeppner wrote: >> On 7/8/2012 8:27 AM, Patrick Domack wrote: >>> >>> Quoting Wojciech Puchar <wojtek(a)wojtek.tensor.gdynia.pl>: >>> >>>>> I think there are optimal situations where any configuration looks >>>>> good . . How often can a real-world disk actually deliver the 6Gbs >>>>> when only a minority of disk reads are long sequential runs on the >>>>> platters? >>>> none of hard drives can saturate 1.5Gb/s >>> >>> There are many disks out that do 150-200MB/sec, easily exceeding 1.5gb/s >>> speeds. >> >> There are a few SAS drives that can saturate a 150MB/s link, such as the >> Seagate Cheetah 15k.7, which can sustain 204MB/s streaming read on the >> outer tracks. >> >> But, again, streaming rate is irrelevant to mail storage. What matters >> is random seek latency. And the faster the spindle, the lower the >> latency. Thus 15k Seagate SAS drives are excellent candidates for mail >> store duty, as are any 10k or 15k drives. > > This is simply not true. SATA SSDs (~0,66 €/GB) are as expensive as the > 15k Seagate SAS HDDs (0,63 €/GB), but definitely faster. First, this sub discussion in this thread has been dealing strictly with mechanical storage, and that was intentional. Now you've injected solid state storage, and in the process you first disagreed with my statement, then agreed with it. Apparently you didn't realize you did so. Would you please clarify what I stated that is "simply not true"? You comment WRT SSD doesn't prove anything I said to be untrue. Quite the contrary, you reinforced my statements. -- Stan

11 25

[Dovecot] recover .sieve plaintext from .sievec binary file
by Florin Andrei 10 Jul '12

10 Jul '12

Hi, I upgraded a server from an old Linux distribution to a much newer one. In the process, Dovecot got upgraded from v1 to v2. By mistake, I deleted the .sieve plaintext file with all the Sieve filters, but I still do have the .sievec compiled binary. Is there any way to dump the binary file back into plaintext format? Keep in mind, I'm running v2 now, and the binary was made on a v1 Dovecot server. Thanks. -- Florin Andrei http://florin.myip.org/

3 4

[Dovecot] configuring imap_stats
by Reinhard Vicinus 09 Jul '12

09 Jul '12

Hi, i'm trying to configure imap_stats like it's documented in the wiki: http://wiki2.dovecot.org/Statistics. But as soon as i activate the imap_stats plugin i get the following error message trying to login via imap: dovecot: imap: Error: Can't load plugin imap_stats_plugin: Plugin stats must be loaded also (you must set: mail_plugins=$mail_plugins stats) But the stats plugin is configured as you can see in the attached configurations. Also i can get statistics without the imap_stats enabled, but as far as i know only of the pop3 users. Kind regards Reinhard

2 1

[Dovecot] mailboxes missing after upgrade from 2.1.4 to 2.1.7
by Micah Anderson 09 Jul '12

09 Jul '12

Hi all, I mentioned this on the #dovecot irc channel, but I thought I would post here so I can provide more details. The basic problem is that when I upgraded from 2.1.4 to 2.1.7, some users no longer are able to see their folders in pine/alpine. The folders are actually there, and are subscribed (according to doveadm) and its possible to do operations on those folders, if you know the name (for example, opening the folder works fine if you know the name). When I downgrade to 2.1.4 again, the folders appear again, so its clearly something that changed between the two versions. I looked through the changelog, and found a few possibile culprits, I think pine/alpine use imapc, so that could be related: . imapc: Use imapc_list_prefix also for listing subscriptions . Fixed looking up parent mailbox name with different namespace vs. layout separators. . imapc: Don't list mailboxes that don't match list patterns. . layout=fs: Fixed listing mailboxes with prefix=INBOX/ . LIST with mailbox {} settings incorrectly set subscribed-flags. Here is my dovecot -n output: # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 auth_default_realm = example.net auth_verbose = yes default_process_limit = 256 default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf quota = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 listen = * login_greeting = howdy, ready. mail_location = mdbox:~/mdbox:INDEX=/srv/dovecot_indexes/%d/%1n/%n mail_plugins = expire quota zlib stats maildir_very_dirty_syncs = yes namespace { inbox = yes location = prefix = separator = . } namespace { alias_for = hidden = yes inbox = no list = no location = prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { antispam_allow_append_to_spam = yes antispam_backend = pipe antispam_debug_target = syslog antispam_pipe_program = /usr/local/bin/train_spam antispam_pipe_program_args = -d;10.0.1.109 antispam_pipe_program_notspam_arg = ham antispam_pipe_program_spam_arg = spam antispam_pipe_tmpdir = /var/tmp antispam_signature = X-Spam-Flag antispam_signature_missing = error antispam_spam_pattern_ignorecase = SPAM antispam_trash_pattern = trash;Trash;Deleted * expire = Trash expire2 = Trash/* expire3 = Spam expire_dict = proxy::expire quota = dict:Your mail quota::proxy::quota quota_rule = *:bytes=100663296 quota_rule2 = Trash:bytes=+20%% quota_rule3 = Spam:bytes=+10%% quota_rule4 = INBOX.Trash:bytes=+20%% quota_rule5 = INBOX.Spam:bytes=+10%% quota_rule6 = INBOX.restored_from_backups:bytes=+500%% sieve = ~/.dovecot.sieve sieve_after = /var/lib/dovecot/sieve/after.sieve sieve_before = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve stats_refresh = 30 secs stats_track_cmds = yes zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)example.net protocols = " imap pop3" service anvil { unix_listener anvil { group = dovecot mode = 0660 user = root } } service auth { unix_listener auth-userdb { group = mail mode = 0600 user = mail } } service dict { unix_listener dict { group = mail mode = 0600 user = mail } } service imap-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service imap-postlogin { executable = script-login /usr/local/sbin/postlogin_imap } service imap { executable = imap imap-postlogin process_limit = 2048 } service pop3-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service pop3-postlogin { executable = script-login /usr/local/sbin/postlogin_pop } service pop3 { executable = pop3 pop3-postlogin } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl_cert = </etc/certs/wildcard/cert.pem ssl_cipher_list = HIGH:-ADH:-aNULL ssl_key = </etc/certs/wildcard/key.pem userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lda { mail_plugins = expire quota zlib stats sieve plugin { quota_exceeded_message = Sorry, your message cannot be delivered to that person because their mailbox is full. If you can contact them another way, you may wish to tell them of this problem. quota_rule7 = INBOX:bytes=+10%% } } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = expire quota zlib stats imap_quota imap_zlib antispam imap_stats plugin { quota_exceeded_message = You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and delete emails with large attachments. Visit https://help.example.net/quota for more help. } } protocol pop3 { mail_plugins = expire quota zlib stats pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %g } As requested by tss in #dovecot, I attempted to add 'rawlog' to: service imap-postlogin { executable = script-login /usr/local/sbin/postlogin_imap } to get: service imap-postlogin { executable = script-login rawlogin /usr/local/sbin/postlogin_imap } but with that, it doesn't even open the INBOX folder, and there is nothing in the user's rawlog folder, I get this error: dovecot: imap-postlogin: Error: Fatal: This process must not be run as root it didn't open even the INBOX imap folder I went over the http://wiki2.dovecot.org/Debugging/Rawlog and made sure everything was correct there, but it still didn't work right. Any ideas or suggestions of things to try would be greatly appreciated! thanks, micah --

1 1

[Dovecot] Howto add another disk storage
by Adrian Minta 09 Jul '12

09 Jul '12

Hi all What is the best strategy to add another storage to an existing virtual mail system ? Move some domains to the new storage and create symlinks ? Switch to dovecot hashing ? But in this case what is the easy-east way to migrate ? Thanks for any suggestions or tips !

15 50

Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX
by Joseph Tam 08 Jul '12

08 Jul '12

Timo Sirainen <tss(a)iki.fi> writes: >> #0 i_panic (format=0xff2302f8 "Trying to allocate %u bytes") at failures.c:259 >> #1 0xff2068a4 in pool_alloconly_malloc (pool=0x60330, size=0) at mempool-alloconly.c:259 >> #2 0x00018248 in client_uidls_save (client=0x54d28) at pop3-commands.c:761 >> #3 0x00018444 in cmd_uidl_init (client=0x54d28, seq=0) at pop3-commands.c:793 >> #4 0x000185a8 in cmd_uidl (client=0x54d28, args=0x19eb8 "") at pop3-commands.c:824 >> #5 0x00018a24 in client_command_execute (client=0x54d28, name=0x2b550 "UIDL", args=0x19eb8 "") >> at pop3-commands.c:889 > > Fixed: http://hg.dovecot.org/dovecot-2.1/rev/ea18b2ddb67b > > Date: Sat, 7 Jul 2012 05:52:03 +0300 2 hours after I reported it; do you ever sleep?! Thanks. Joseph Tam <jtam.home(a)gmail.com>

4 3

[Dovecot] + sub addressing setup
by Voytek Eymont 07 Jul '12

07 Jul '12

I have Dovecot/Postfix/MySQL/PostfixAdmin, I'd like to setup + sub addressing (for +spam and possibly user-defined +folders) I have setup a user+spam folder path in PostfixAdmin as so; vvv+spam@tld path:tld/vvv@tld/.spam/ that requires me to put a 'duplicate' user with the + and +path for each user, the folks on PostfixAdmin suggested that Dovecot might have a better way of handling this, how do I accomplish this in Dovecot ? thanks for any suggestions or tips -- Voytek

2 6

[Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX
by Joseph Tam 07 Jul '12

07 Jul '12

I noticed a bunch of crashes when Gmail users tried to slurp up their (empty) mailboxes. The problem is not noticed by clients though, but it crashes the pop3 process. POP3 session S: +OK Ready. C: USER user S: +OK C: PASS password S: +OK Logged in. C: UIDL ... server crash and disconnects ... Resulting log Jul 06 16:58:05 pop3(user): Panic: Trying to allocate 0 bytes Jul 06 16:58:05 pop3(user): Error: Raw backtrace: 0xff1e6454 -> 0xff1e4f78 -> 0xff20689c -> 0x18240 -> 0x1843c - > 0x185a0 -> 0x18a1c -> 0x1576c -> 0x159cc -> 0xff1fee6c -> 0xff200e24 -> 0xff1fef60 -> 0xff1d8010 -> 0x13584 - > 0x1285c Jul 06 16:58:14 pop3(user): Fatal: master: service(pop3): child 24972 killed with signal 6 (core dumps disabled) GDB traceback: #0 i_panic (format=0xff2302f8 "Trying to allocate %u bytes") at failures.c:259 #1 0xff2068a4 in pool_alloconly_malloc (pool=0x60330, size=0) at mempool-alloconly.c:259 #2 0x00018248 in client_uidls_save (client=0x54d28) at pop3-commands.c:761 #3 0x00018444 in cmd_uidl_init (client=0x54d28, seq=0) at pop3-commands.c:793 #4 0x000185a8 in cmd_uidl (client=0x54d28, args=0x19eb8 "") at pop3-commands.c:824 #5 0x00018a24 in client_command_execute (client=0x54d28, name=0x2b550 "UIDL", args=0x19eb8 "") at pop3-commands.c:889 #6 0x00015774 in client_handle_input (client=0x54d28) at pop3-client.c:629 #7 0x000159d4 in client_input (client=0x54d28) at pop3-client.c:682 #8 0xff1fee74 in io_loop_call_io (io=0x37298) at ioloop.c:379 #9 0xff200e2c in io_loop_handler_run (ioloop=0x34138) at ioloop-poll.c:211 #10 0xff1fef68 in io_loop_run (ioloop=0x34138) at ioloop.c:398 #11 0xff1d8018 in master_service_run (service=0x33c88, callback=0x13120 <client_connected>) at master-service.c:543 #12 0x0001358c in main (argc=1, argv=0xffbffe0c) at main.c:268 Some non-trivial changes in pop3-commands.c were done between 2.1.3 and 2.1.8 (expecially pop3_uidl_duplicates changes in 2.1.7). I guess this bug has crept in there. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Pigeonhole Sieve SetFlag question
by Vyacheslav Biruk 06 Jul '12

06 Jul '12

Hello, I use FreeBSD 8.2-RELEASE-p7 i386 dovecot-2.1.6 dovecot-pigeonhole-0.3.0_1 I have the following problem: When I use the following script - the flag is set in \Seen : require ["imap4flags"]; # rule:[test] if anyof (header :contains "Subject" "test") { setflag "\\Seen"; stop; } . SELECT INBOX * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UIDVALIDITY 1338600150] UIDs valid * OK [UIDNEXT 9] Predicted next UID * OK [NOMODSEQ] No permanent modsequences . OK [READ-WRITE] Select completed. . FETCH 1 (UID FLAGS BODY.PEEK[HEADER.FIELDS (DATE SUBJECT)]) * 1 FETCH (UID 8 FLAGS (\Seen \Recent) BODY[HEADER.FIELDS (DATE SUBJECT)] {57} Date: Fri, 6 Jul 2012 14:02:49 +0000 Subject: test 1 ) . OK Fetch completed. But when I use following script - the flag is not set in \Seen require ["fileinto","imap4flags"]; # rule:[test] if anyof (header :contains "Subject" "test") { fileinto "INBOX.SPAM"; setflag "\\Seen"; stop; } . SELECT INBOX.SPAM * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1338600159] UIDs valid * OK [UIDNEXT 7] Predicted next UID * OK [NOMODSEQ] No permanent modsequences . OK [READ-WRITE] Select completed. . FETCH 1 (UID FLAGS BODY.PEEK[HEADER.FIELDS (DATE SUBJECT)]) * 1 FETCH (UID 6 FLAGS (\Recent) BODY[HEADER.FIELDS (DATE SUBJECT)] {57} Date: Fri, 6 Jul 2012 13:53:29 +0000 Subject: test 1 ) . OK Fetch completed. so it should be or is it a bug? -- Best regards, magic

3 2

[Dovecot] I changed the separator from . to / and it still seems to work.
by Hans de Groot 06 Jul '12

06 Jul '12

Hello, Just as an experiment I changed the separator from . to / restarted dovecot (v2.1.1). When adding an existing account with lots of mail folders to thunderbird everything still seems to work. My directory layout is like this: .Info.mailinglists .Info.mailinglists.Horde .Info.mailinglists.modperl .Info.mailinglists.PDNS .Info.mailinglists.Sogo .Info.mailinglists.tinc .Info.mailinglists.Zabbix I added a new folder to the horde mailing using thunderbird list and got an extra folder .Info.mailinglists.Horde.testinhorde Does this mean the separator has nothing to do with the . in the directory names and I am safe to switch saparators without having to do anything else? Regards Hans de Groot

1 0

[Dovecot] Dovecot v2 shared mailboxes , a . separator and complete emailaddress as username.
by Hans de Groot 06 Jul '12

06 Jul '12

Hello, I've been trying to get shared mailboxes to work and got stuck. I tried lots of examples made the shared dict but the shared mail boxes never showed up. I am using the . separator and I think this the problem. I changed it to a / separator and now I could see my shared mailboxes. Checking the maillog in debug mode I saw a few failed login attempts between the succesful logins. The weird thing is that the username was changed, instead of hansg(a)debushalte.nl the login was hansg@debushalte without the .nl part and that user is not in my database. So I suspect that dovecot splits the shared path based hansg(a)debushalte.nl shares mailboxes with dean(a)debushalte.nl below a few lines from the log: Debug: Namespace : type=shared, prefix=INBOX.shared.%u., sep=., inbox=no, hidden=no, list=yes, subscriptions=no location=maildir:%h/mail:INDEX=/mail/debushalte.nl/dean/mail/shared.%u Debug: shared: Tried to access mails of nonexistent user hansg@debushalte Debug: Namespace INBOX.shared.hansg@debushalte.: Creating storage despite: Root mail directory doesn't exist Is there a work arround for this? I really like to keep using '.' as a seperator so I do not have to change all the existing mailboxes. If I do rename and move all existing mailboxes the '/' separator way and of course change the separator in the namespaces would my users notice this? (ie would they have to change something in their mail clients?) Regards Hans

1 0

[Dovecot] dovecot and nfs readdir vs readdirplus operations
by Angel L. Mateo 06 Jul '12

06 Jul '12

Hello, We are having performance problems trying to migrate our pop/imap servers to a new version. Our old servers are 4 debian lenny with 5GB of RAM running of XenServer VMs with kernel 2.6.32-4-amd64 and dovecot 1.1.16. New servers are 4 ubuntu 12.04 with dovecot 2.1.5 running on vmware vm with 6 cores and 16GB of RAM and kernel 3.2.0-24-generic. On both server we are using nfs 3 with same configuration (regardless of internal kernel differences, but we have no customized any of them, we are using vanilla kernels with default configurations). The problem we have is that new servers have performance problems. Even when have a small part of our total users (about 25%) directed to the new farm, performance is very poor, even useless. Looking for NFS problems, we have found a lot of differences in nfs operations. For example, this is the nfsstat of one of a new servers at this moment: myotis21:~# nfsstat Client rpc stats: calls retrans authrefrsh 414528349 885 37 Client nfs v3: null getattr setattr lookup access readlink 0 0% 95673837 23% 3961938 0% 89586364 21% 110097351 26% 2930961 0% read write create mkdir symlink mknod 20009850 4% 6065319 1% 3757720 0% 1557 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 6378134 1% 281 0% 2602358 0% 555097 0% 53126619 12% 15615402 3% fsstat fsinfo pathconf commit 113256 0% 26152 0% 0 0% 4026151 0% and this is the same on one of the new ones: amateo_adm@myotis31:~$ nfsstat Server rpc stats: calls badcalls badclnt badauth xdrcall 0 0 0 0 0 Client rpc stats: calls retrans authrefrsh 178040318 675 178040800 Client nfs v3: null getattr setattr lookup access readlink 0 0% 24350345 13% 5045924 2% 10939469 6% 30185146 16% 142865 0% read write create mkdir symlink mknod 8818016 4% 6058614 3% 2877653 1% 420 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 2842562 1% 69 0% 2961239 1% 634038 0% 0 0% 82921863 46% fsstat fsinfo pathconf commit 70861 0% 18754 0% 9377 0% 152702 0% Although nfs configuration is the same, there are a lot of differences on readdir vs readdirplus nfs operations. In fact, in the old one we have 12% readdir operations and 3% of readdirplus. And in the new one we have 46% of readdirplus and no readdir operations. Although readdirplus is supposed to be an optimization in nfs3, in situations when you have big directories and uses just a few entries of these directories it could be worse. So we think if this could be the problem (or one of them). Any idea of this difference? And if this difference could be significative? PS: I have attached doveconf -n of the new server. -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

5 12

[Dovecot] Dovecot mailstorage migration uppon logging / delivery with dsync
by Xavier Beaudouin 05 Jul '12

05 Jul '12

Hi there, I have a pretty standard setup with "simple" dovecot 2,0 configuration (eg /var/mailboxes on NFS with old netapp) and local ldap directory and Maildir. I wanted to find a good way to migrate from NFS old netapp to NFS new server (this one is not a netapp !). There 3 kind way (according to my own experience) - rsync old spool to new spool being patient stop services and then doing last rsync and mount /var/mailboxes mount point from old netapp to new nfs server). - doing imap_login (and other stuff like this) doing an rsync per box AFTER doing the first rsync with all boxes... - using dsync to fetch the maildir stuff from old server to new one, doing a simple flag, and doing "au fil de l'eau" migration. The last one seems to me a good idea, but I cannot figure host to make this correctly. Any hints or do someone here has already done this kind of stuff? Kind regards, -- Xavier Beaudouin

2 1

[Dovecot] Migration Question
by Peter Fraser 05 Jul '12

05 Jul '12

Hi all I got a shiny new server and I want to install the latest and greatest of everything on it. The old server has dovecot-1.2.17 working with postfix-2.8.4,1, dovecot quotas, sieve etc. My question is: Would it work of I installed dovecot 2 on this server along with everything I want and just copy the /home/virtualmail directory where all the user mail directories are? I use the Maildir format by the way.

3 2

[Dovecot] error: director left/right disconnected
by Patrick Westenberg 05 Jul '12

05 Jul '12

Hello, yesterday I set up a second director and even it works fine, some errors occur in the logfile on the new director: director: Error: Director 172.17.1.3:9090/left disconnected director: Error: Director 172.17.1.3:9090/right disconnected 172.17.1.3 belongs to the first director which has no errors. Where is the problem? Regards Patrick # 2.1.7: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 auth_debug = yes auth_verbose = yes director_mail_servers = 172.17.1.1 director_servers = 172.17.1.3 172.17.1.4 lmtp_proxy = yes log_path = /var/log/dovecot.log managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = proxy=y nopassword=y starttls=any-cert driver = static } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.4 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { inet_listener lmtp { address = 172.17.1.4 port = 24 } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/certs/imap.wk-serv.de.crt ssl_key = </etc/ssl/private/imap.wk-serv.de.key protocol lmtp { auth_socket_path = director-userdb } # 2.1.6: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 director_mail_servers = 172.17.1.1 director_servers = 172.17.1.3 172.17.1.4 lmtp_proxy = yes log_path = /var/log/dovecot.log managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave passdb { args = proxy=y nopassword=y starttls=any-cert driver = static } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.3 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service lmtp { inet_listener lmtp { address = 172.17.1.3 port = 24 } } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } protocol lmtp { auth_socket_path = director-userdb }

2 1

[Dovecot] dict Panic after upgrade to 2.1.7
by ckubu 03 Jul '12

03 Jul '12

Hello, after upgrade my mailsystem to dovecot version 2.1.7, dovecot doesn't work properly. something went wrong in dict service connecting the postgres backend. that happens not on every connection. the db connection data are correct, no difference connecting via tcp or linux socket. dovecot log entries: Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84 (driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY || db- >cur_result == NULL) Jun 23 23:19:10 mx dovecot: dict: Error: Raw backtrace: /usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0(+0x4478a) [0x7ffc7d8e578a] -> /usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0(+0x447d6) [0x7ffc7d8e57d6] -> /usr/local/dovecot-2.1.7/lib/dovecot/libdovecot.so.0(i_error+0) [0x7ffc7d8bc5ef] -> dovecot/dict() [0x40a9a6] -> dovecot/dict() [0x40aa01] -> dovecot/dict() [0x40be43] -> dovecot/dict() [0x409474] -> dovecot/dict(sql_db_cache_deinit+0x20) [0x4089d0] -> dovecot/dict(main+0x169) [0x4059f9] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7ffc7d335c8d] -> dovecot/dict() [0x404b59] Jun 23 23:19:10 mx dovecot: dict: Fatal: master: service(dict): child 13812 killed with signal 6 (core dumps disabled) Jun 23 23:23:09 mx dovecot: dict: Error: dict sql iterate failed: Not connected to database Jun 23 23:23:09 mx dovecot: pop3(xxx(a)yyy.zz): Error: acl: dict iteration failed, can't update dict Jun 23 23:23:09 mx dovecot: dict: Error: dict sql iterate failed: Not connected to database Jun 23 23:23:09 mx dovecot: pop3(xxx(a)yyy.zz): Error: acl: dict iteration failed, can't update dict Jun 23 23:23:17 mx dovecot: dict: Error: dict sql lookup failed: Not connected to database Jun 23 23:23:17 mx dovecot: imap(xxx(a)yyy.zz): Error: Internal quota calculation error Jun 23 23:23:19 mx dovecot: dict: Error: dict sql lookup failed: Not connected to database Jun 23 23:23:40 mx dovecot: dict: Error: dict sql lookup failed: Not connected to database maybe i have missconfigured the dovecot system, but i don't find the mistake. can anybody give me a hint ? best wiches christoph ----- doveconf -n # 2.1.7: /usr/local/dovecot-2.1.7/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-vserver-amd64 x86_64 Debian 6.0.5 ext3 auth_mechanisms = plain login digest-md5 cram-md5 apop auth_socket_path = /var/run/dovecot/auth-userdb auth_username_translation = %@ auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ dict { acl = pgsql:/usr/local/dovecot/etc/dovecot/sql-dict.conf.ext expire = pgsql:/usr/local/dovecot/etc/dovecot/sql-dict.conf.ext quota = pgsql:/usr/local/dovecot/etc/dovecot/sql-dict.conf.ext } disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 5000 hostname = mx.warenform.de last_valid_gid = 5000 last_valid_uid = 5000 listen = 178.63.63.151 2a01:4f8:121:c5::2 mail_gid = vmail mail_location = maildir:/var/vmail/%d/%n/Maildir mail_plugins = autocreate quota expire acl mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace { list = children location = maildir:/var/vmail/%%d/%%n/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /usr/local/dovecot/etc/dovecot/sql-connect.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl autocreate = Spam autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autosubscribe = Spam autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts expire = Trash expire2 = Trash.* expire3 = Spam expire_dict = proxy::expire quota = dict:User quota::proxy::quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+200M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u recipient_delimiter = sieve = ~/.dovecot.sieve sieve_before = /usr/local/dovecot/etc/dovecot/sieve/move-spam.sieve sieve_dir = ~/sieve sieve_global_dir = /usr/local/dovecot/etc/dovecot/sieve/global/ } postmaster_address = admin(a)warenform.de protocols = imap pop3 sieve lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { inet_listener imap { address = 127.0.0.1 178.63.63.151 2a01:4f8:121:c5::2 } inet_listener imaps { address = 178.63.63.151 2a01:4f8:121:c5::2 } process_min_avail = 16 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service pop3-login { inet_listener pop3 { address = 178.63.63.151 2a01:4f8:121:c5::2 } inet_listener pop3s { address = 178.63.63.151 2a01:4f8:121:c5::2 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } shutdown_clients = no ssl_cert = </etc/postfix/ssl/servercert.pem ssl_key = </etc/postfix/ssl/servercert.pem syslog_facility = local1 userdb { args = /usr/local/dovecot/etc/dovecot/sql-connect.conf.ext driver = sql } protocol lmtp { mail_plugins = autocreate quota expire acl sieve } protocol lda { mail_plugins = autocreate quota expire acl sieve } protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 24 mail_plugins = autocreate quota expire acl imap_quota imap_acl ssl_cert = </etc/postfix/ssl/imap_warenform_de.crt ssl_key = </etc/postfix/ssl/imap_warenform_de.key } protocol pop3 { mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh ssl_cert = </etc/postfix/ssl/pop_warenform_de.crt ssl_key = </etc/postfix/ssl/pop_warenform_de.key } ----- sql-dict.conf.ext: connect = host=/var/run/postgresql user=db_user password=db_passwd dbname=db_name # quota map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } # expires map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } # acl map { pattern = shared/shared-boxes/user/$to/$from table = user_shares value_field = dummy fields { from_user = $from to_user = $to } } map { pattern = shared/shared-boxes/anyone/$from table = anyone_shares value_field = dummy fields { from_user = $from } } -- e: ckubu(a)so36.net

2 3

[Dovecot] Outlook 2010 very slow when using IMAP - are there any tweaks?
by Kaya Saman 03 Jul '12

03 Jul '12

Hi, though this is a bit of a side question, has anybody had an issue while running Outlook 2010 with Dovecot? The reason why I am asking is that I have setup a Dovecot 2.1.7 server on FreeBSD which works fantastically with Thunderbird but Outlook seems to be twice as slow in transferring information across?? # dovecot -n # 2.1.7: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-RELEASE amd64 auth_debug = yes auth_mechanisms = plain ntlm login auth_use_winbind = yes auth_username_format = %n auth_verbose = yes auth_winbind_helper_path = /usr/local/bin/ntlm_auth disable_plaintext_auth = no info_log_path = /var/log/dovecot-info.log log_path = /var/log/dovecot.log mail_gid = mail_user mail_home = /mail/AD_Mail/%Ld/%Ln mail_location = maildir:~/Maildir mail_uid = mail_user passdb { args = failure_show_msg=yes driver = pam } pop3_fast_size_lookups = yes pop3_lock_session = yes pop3_no_flag_updates = yes protocols = imap pop3 ssl = no userdb { driver = static } Since (like most corporate organizations out there) we solely run Outlook coupled to Exchange, this excersize was meant to be a way of getting rid of PST files. We don't run out own Exchange however, and don't have any control over it either. My workaround was to simply use the Outlook GUI space to transfer emails between Exchange and Dovecot running the IMAPv4 protocol. For whatever reason Outlook is being really garbage about dealing with stuff and since I don't know Outlook or MS products very well (being your typical average OpenSource guy) I was wondering if there were any tweaks that could be made within Outlook to speed it up or in Dovecot to work better with Outlook? I guess one could get sidetracked into the argument of mdbox vs. Maildir from my config however, Thunderbird is really fast and transfers large amounts of data really easily. Reaches round 130Mbps using nload performance grapher, while Outlook only manages ~50kbps but spikes at 2-3Mbps on occassion. Can anyone offer any guidence or assistance in this matter?? Actually wherever I run Dovecot, including my servers at home, it is fast and reliable. Yes I know MS is the polar opposite of anything worth using however, my company won't change and I'm stuck banging my head against the wall while trying to get MS to interface with ANYTHING..... Regards, Kaya

16 64

[Dovecot] Problem with 'doveadm mailbox status -t' reporting cumulative vsizes after upgrading from v2.0.16 to v2.1.7
by Jase Thew 03 Jul '12

03 Jul '12

Hi, I upgraded from Dovecot v2.0.16 to v2.1.7 over night and I noticed this morning that one of my daily reports which lists summarised mailbox sizes per user has started listing nonsense for vsizes. The reporting script at its core calls : doveadm -f flow mailbox status -A -t 'messages vsize' '*' It appears that Dovecot 2.1.7 is not resetting the vsize after collating the sum total of mailboxes sizes for each user, so that vsize just constantly increases as it iterates over each user. Eg: # doveadm -f flow mailbox status -A -t 'messages vsize' '*' accounts(a)example.com messages=1 vsize=759 adam(a)example.com messages=0 vsize=759 amy(a)example.com messages=24 vsize=51699697 andy(a)example.com messages=5446 vsize=3220940815 anna(a)example.com messages=50 vsize=3224035563 careers(a)example.com messages=1 vsize=3224036311 craig(a)example.com messages=2471 vsize=4421343199 creative(a)example.com messages=189 vsize=4426884182 david(a)example.com messages=8 vsize=4440729729 davidw(a)example.com messages=0 vsize=4440729729 enquiries(a)example.com messages=1 vsize=4440730491 gemma(a)example.com messages=4109 vsize=6349098844 gin(a)example.com messages=86 vsize=6392599904 holly(a)example.com messages=2000 vsize=7200342663 ian(a)example.com messages=0 vsize=7200342663 info(a)example.com messages=4 vsize=7200558689 jackie(a)example.com messages=2 vsize=7200721146 jade(a)example.com messages=137 vsize=7210548548 jake(a)example.com messages=16667 vsize=15260532446 katie(a)example.com messages=1 vsize=15260533375 mark(a)example.com messages=0 vsize=15260533375 mike.a(a)example.com messages=9 vsize=15261474205 mike.s(a)example.com messages=296 vsize=15314352543 mike(a)example.com messages=6357 vsize=20631446344 nick(a)example.com messages=1184 vsize=21038046728 social(a)example.com messages=65 vsize=21038935461 will(a)example.com messages=85 vsize=21057572390 [SNIP] The same occurs with -u '*(a)example.com' in place of -A, and also for 'all' in place of 'messages vsize'. Is this expected behaviour in 2.1.x compared to 2.0.x, or have I stumbled upon a bug? Regards, Jase Thew.

2 2

[Dovecot] Dovecot shared library to replace libc-client
by Asheesh Laroia 03 Jul '12

03 Jul '12

Hi all Dovecotters, Lots of programs (e.g, PHP) link to a library called c-client, which is a derivative of the original IMAP implementation, UW IMAP. (For those new to UW IMAP, read here: http://www.washington.edu/imap/ ) UW IMAP is not in as much of active development as it used to be, so I am curious: I see there is a dovecot shared library. I haven't looked into the details, but here are things I'm interested in: 1. Replacing libc-client's use as a client library In Debian, for example, you can search for packages that depend on this library as a client. It looks like this: $ ~ apt-cache rdepends libc-client2007e libc-client2007e Reverse Depends: uw-mailutils uw-imapd libc-client2007e-dev ipopd prayer php5-imap mailsync libmail-cclient-perl asterisk aolserver4-nsimap uw-mailutils libc-client2007e-dev prayer php5-imap mailsync libmail-cclient-perl asterisk-voicemail-imapstorage Let's say, hypothetically, we wanted to switch php5-imap to using Dovecot where it currently uses libc-client. I envision creating libdovecot-c-client-alike that is a set of headers and a library that is API-compatible with (at least a subset of) c-client. You can call that a "compatibility shim." Then e.g. php5-imap could be given the path to those headers and the corresponding libdovecot-c-client-alike library, and when it thinks it is linking to c-client, it could instead link to the libdovecot-c-client-alike. This might be convenient if you want to limit how much of a public API is presented by the current "dovecot.so" that gets installed in e.g. /usr/lib/dovecot/. The compatiblity shim could have a small API, and if you don't want provide ABI guarantees within dovecot.so, the shim could dlopen() dovecot.so rather than link to it. 2. Use of Dovecot shared library within alpine, embedding the imapd Right now, the mail client "alpine" embeds a copy of the UW IMAP source. It uses this when accessing local mail spools, for example. If Dovecot's IMAPd were available as a shared library, perhaps with a c-client-like API, (although not necessarily -- it would be feasible to upgrade alpine to a different API), then alpine could use Dovecot's mail drivers directly. So, those two are the dream. Timo and others, what are your thoughts? Thanks for reading this far! -- Asheesh. P.S. The radical request #2 would be an excellent, decisive way to end a sad thread in the Debian bug tracker about Alpine + Maildir: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405762 .

2 3

[Dovecot] Authentication failed (migrate from 2.0.13 to 2.0.17)
by Dovecot user 03 Jul '12

03 Jul '12

Hi, I use OpenBSD 5.1, roundcube 0.7.2 and dovecot 2.0.17 (684381041dc4+), mysql. I get the following error when i try to connect to imap : roundcube: IMAP Error: Login failed for testing(a)mydomain.net from 192.168.0.92. AUTHENTICATE PLAIN: Authentication failed. in /var/www/webmail/roundcubemail-0.7.2/program/include/rcube_imap.php on line 205 (POST /webmail/?_task=login&_action=login) dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, TLS Jul 2 15:19:13 mx dovecot: auth-worker: mysql(localhost): Connected to database mail Jul 2 15:19:15 mx dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Can you help me please ? Here my config files : *dovecot-sql.conf driver = mysql connect = host=localhost dbname=mail user=postfix password=postfix default_pass_scheme = PLAIN password_query = SELECT email as user, password FROM users WHERE email = '%u' user_query = SELECT id as uid, id as gid, home, concat('*:storage=', quota, 'M') AS quota_rule FROM users WHERE email = '%u' *dovecot.conf #i use this on OpenBSD 5.0 and dovecot 2.0.13, works, but it doesn't seem to work with this version :-( # 2.0.13: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.0 i386 ffs auth_mechanisms = plain login digest-md5 cram-md5 apop auth_debug=yes base_dir = /var/dovecot/ first_valid_uid = 1000 mail_location = maildir:/var/mailserv/mail/%d/%n mmap_disable = yes passdb { args = /etc/dovecot-sql.conf driver = sql } plugin { antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/local/bin/sa-learn antispam_mail_sendmail_args = --username=%u antispam_mail_spam = --spam antispam_mail_tmpdir = /tmp antispam_signature = X-Spam-Flag antispam_signature_missing = move antispam_spam = SPAM;Spam;spam;Junk;junk antispam_trash = trash;Trash;Deleted Items; Deleted Messages autocreate = Trash autocreate2 = Spam autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Sent autosubscribe4 = Drafts quota = maildir quota_rule = *:storage=5G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap sieve pop3 service auth { unix_listener /var/run/dovecot-auth-master { group = _dovecot mode = 0666 user = _dovecot } unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0660 user = _postfix } } service imap-login { service_count = 0 #user = _dovecot vsz_limit = 64 M } service pop3-login { service_count = 0 #user = _dovecot vsz_limit = 64 M } ssl_cert =ssl_cipher_list = HIGH:MEDIUM:+TLSv1:!SSLv2:+SSLv3 ssl_key = userdb { args = /etc/dovecot-sql.conf driver = sql } #userdb { # driver = passwd #} protocol imap { imap_client_workarounds = delay-newmail mail_plugins = quota imap_quota autocreate } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xv%08Xu } protocol lda { auth_socket_path = /var/run/dovecot-auth-master mail_plugins = $mail_plugins sieve postmaster_address = postmaster(a)mx.itdebug.net sendmail_path = /usr/sbin/sendmail } default_login_user = _dovenull default_internal_user = _dovecot ## ## ManageSieve specific settings ## # Service definitions service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { #Max. number of ManageSieve processes (connections) #process_count = 1024 } # Service configuration protocol sieve { } Thank you very much. -- Wesley

2 7

[Dovecot] v2.1.8 released
by Timo Sirainen 03 Jul '12

03 Jul '12

http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.8.tar.gz.sig Most importantly fixes a pretty bad behavior of sending mailbox names as UTF-8 instead of mUTF-7 as required by IMAP RFC. I'm surprised nobody hadn't noticed this in v2.1.x tree before yesterday. I guess some clients might have translated the name to UTF-8 anyway and not noticed it, while others would have silently ignored the problem of not seeing STATUS updates. + pop3c: Added pop3c_master_user setting. - imap: Mailbox names were accidentally sent as UTF-8 instead of mUTF-7 in previous v2.1.x releases for STATUS, MYRIGHTS and GETQUOTAROOT commands. - lmtp proxy: Don't timeout connections too early when mail has a lot of RCPT TOs. - director: Don't crash if the director is working alone. - shared mailboxes: Avoid doing "@domain" userdb lookups. - doveadm: Fixed crash with proxying some commands. - fts-squat: Fixed handling multiple SEARCH parameters. - imapc: Fixed a crash when message had more than 8 keywords. - imapc: Don't crash on APPEND/COPY if server doesn't support UIDPLUS.

1 0

[Dovecot] Additional passdb result status
by Jürgen Pabel 03 Jul '12

03 Jul '12

Dear Dovecot-Team, I am implementing a plugin (for the pop3/imap process) that requires some data to provided from the authentication phase (a derivative of the password). For that, I have now implemented a passdb plugin that generates this data and I would like to "pass" this data down to the mail process (pop3/imap) via extra_fields in the reply of the authentication. The general idea is that my custom passdb plugin calculates the data, sets the extra_field and returns some error (authentication was not successful) so that the "real" passdb backend can be invoked to "really" validate the authentication data. However, in auth_request_handle_passdb_callback() the extra_fields are reseted unless the return code is PASSDB_RESULT_USER_DISABLED. But if that return code is used then any following passdb's aren't invoked any more - which makes sense with respect to user authenticiation. I would therefore like to propose that some IGNORE/CONTINUE-status to be introduced in auth/passdb.h, that would be handled in that extra_fields and possible other values are not reseted in order to allow such propagation of data from authentication process down to the mail process (which could be extracted from the reply string by parsing it). As a further implementation alternative (to the parsing of the reply string), I also propose that some new "environment" item be introduced (in auth_request) in order to allow such data passing in a generic manner. I hope you consider my proposal to be reasonable. If desired, I could implement this myself and provide a patch for merging (based on 2.0.x). If my proposal is generally unfavored, it would be great if any alternative approaches for my situation were suggested. Thanks. Regards, Jürgen PS: please reply to my e-mail (or CC me), as I have not subscribed to the dovecot list

3 3