- dovecot - dovecot.org

[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 04 Jul '12

04 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 04 Jul '12

04 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