- dovecot - dovecot.org

[Dovecot] sieve/dovecot folder separator inconsistency
by Daniel Mayer 06 Jun '09

06 Jun '09

Hi, I'm running dovecot 1.0.15 and ran recently into a problem with the folder separators when using sieve scripts. The server is set to use a slash as a folder separator for all namespaces and announces this correctly when issuing the NAMESPACE command. We are using Ingo (http://www.horde.org/ingo/) of the horde framework to manage our sieve scripts. It creates the folder name / folder path to be used in the sieve scripts based on the result of the NAMESPACE given by the IMAP Server. It therefore created the path separated by slashes ("/"). According to my tests, the delivery agent along with sieve expects the folders to be separated by dots (".") instead of slashes. Is this a correct observation or can this be set using a parameter or something similar? The result of this otherwise inconsistent behavior is that a client who sticks to the provided namespace creates a folder path which cannot be understood by the deliver process. Please let me know if you need any additional information. Thanks, Daniel

3 5

[Dovecot] Dovecot under brute force attack - nice attacker
by henry ritzlmayr 05 Jun '09

05 Jun '09

Hi List, optimizing the configuration on one of our servers (which was hit by a brute force attack on dovecot) showed an odd behavior. Dovecot Version 1.0.7 (CentOS 5.2) The short story: On one of our servers an attacker did a brute force attack on dovecot (pop3). Since the attacker closed and reopened the connection after every user/password combination the logs showed many lines like this: dovecot: pop3-login: Aborted login: user=<test>,...... The problem: If the attacker wouldn't have closed and reopened the connection no log would have been generated and he/she would have endless tries. Not even an iptables/hashlimit or fail2ban would have kicked in. How to reproduce: telnet dovecot-server pop3 user test pass test1 user test pass test2 ... QUIT ->Only the last try gets logged. If I enable auth_verbose every attempt gets logged, but if I read the docs correctly this option should only be used for figuring out why authentication isn't working. Question: Is there any way to close the connection after the first wrong user/pass combination. So an attacker would be forced to reopen it? This would be perfect since an easy iptables/hashlimit would avoid such a brute force attack. Any other Ideas? Henry

8 21

[Dovecot] v1.2.rc5 released
by Timo Sirainen 05 Jun '09

05 Jun '09

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc5.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc5.tar.gz.sig Some small fixes mainly. I guess I'll still have to release rc6 and rc7 after all. I've been a bit busy with v2.0 changes recently. BTW. I'm leaving tomorrow to San Francisco and I'm going to check out what's happening in Apple WWDC next week. * auth_cache_negative_ttl is now used also for password mismatches (currently only with plaintext authentication mechanisms). + Added support for EXTERNAL SASL mechanism. + FETCH X-SAVEDATE can now be used to get messages' save timestamps + deliver_log_format: %s is now in UTF8 - If message body started with a space, some operations could have assert-crashed. - Fixed using LDAP support as a plugin - Fixes to virtual mailboxes.

2 2

[Dovecot] ldap_search() failed "Server Busy"
by Paul Carter-Brown 05 Jun '09

05 Jun '09

Hi, We are using dovecot 1.1.11 on Solaris 10u6. Under load, we are experiencing the following errors: Jun 4 18:30:59 ug1s02-zone1 dovecot: [ID 107833 mail.error] auth(default): ldap(0202934816(a)ug.smilecoms.com,10.31.3.13): ldap_search() failed (filter (uid=0202934816(a)ug.smilecoms.com)) Server is busy We are authenticating against sun directory server yet see no errors in the directory server and it seems to be under low load. Any ideas if there is something on dovecot we should tune to erradicate this? We are running a web front end on top of dovecot and hence have a lot of login/logout happening as the user navigates around. I have included our config below: dovecot.conf: base_dir = /opt/csw/var/run/dovecot/ protocols = imap pop3 listen = * disable_plaintext_auth = no shutdown_clients = yes log_timestamp = "%b %d %H:%M:%S " syslog_facility = mail ssl_listen = ssl_disable = yes login_dir = /opt/csw/var/run/dovecot/login login_chroot = yes login_user = dovecot login_process_size = 128 login_process_per_connection = no login_processes_count = 3 login_max_processes_count = 128 login_max_connections = 256 login_greeting = Dovecot ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s mail_location = maildir:/sapool1/mail/%3n/%3.3n/%6.3n/%u mail_full_filesystem_access = yes mail_debug = no fsync_disable = yes first_valid_uid = 101 mail_save_crlf = yes mbox_dirty_syncs = yes protocol imap { login_executable = /opt/csw/libexec/dovecot/imap-login mail_executable = /opt/csw/libexec/dovecot/imap login_greeting_capability = no imap_client_workarounds = outlook-idle } protocol pop3 { login_executable = /opt/csw/libexec/dovecot/pop3-login mail_executable = /opt/csw/libexec/dovecot/pop3 pop3_no_flag_updates = no pop3_enable_last = no pop3_reuse_xuidl = no pop3_lock_session = no pop3_uidl_format = %v-%u pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol lda { postmaster_address = postmaster(a)example.com hostname = sol10-dev.dutoit.net } auth_anonymous_username = anonymous auth_verbose = no auth_debug = no auth_debug_passwords = no auth_worker_max_count = 30 auth default { mechanisms = plain passdb ldap { args = /opt/csw/etc/dovecot-ldap.conf } userdb static { args = uid=exim gid=mail home=/sapool1/mail/%u } user = root count = 1 ssl_require_client_cert = no ssl_username_from_cert = no socket listen { master { path = /opt/csw/var/run/dovecot/auth-master mode = 0600 user = root group = root } } } dict { } plugin { } dovecot-ldap.conf: hosts = ldap1.it.ug.smilecoms.com:389 dn = cn=Directory Manager dnpass = blahblah sasl_bind = no tls = no ldap_version = 3 base = dc=smilecoms,dc=com deref = never scope = subtree user_filter = (uid=%u) pass_attrs = uid=user,PIN=password pass_filter = (uid=%u) default_pass_scheme = PLAIN Thanks so much! Paul

2 3

[Dovecot] Under POP attack - now to prevent?
by James Brown 05 Jun '09

05 Jun '09

Looks like we are under a dictionary login attack on our POP server: Jun 5 11:48:20 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<audrey>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:24 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<august>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:24 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:25 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<austin>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:27 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<audrey>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:28 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:30 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<august>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:31 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<autumn>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:31 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<austin>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Jun 5 11:48:32 mail dovecot[2620]: pop3-login: Aborted login (auth failed, 1 attempts): user=<atlanta>, method=PLAIN, rip=85.189.169.94, lip=192.168.1.9 Any suggestions on how to prevent this? Using Dovecot 1.2RC4 Thanks, James.

5 5

[Dovecot] feature request - zlib compression via LDA
by J.P. Trosclair 05 Jun '09

05 Jun '09

Any chance of getting compression support via the zlib plugin for dovecot deliver in future versions?

2 4

[Dovecot] imapmagicplus equivalent?
by Juergen Kreileder 04 Jun '09

04 Jun '09

Hi, is anything like Cyrus IMAP's imapmagicplus option available for Dovecot? If not, would it be possible to implement as a plugin? > imapmagicplus: 0 > Only list a restricted set of mailboxes via IMAP by using userid+namespace syntax as the authentication/authorization id. Using userid+ (with an empty namespace) will list only subscribed mailboxes. It's a quite useful option for clients that don't understand subscriptions. E.g., I don't want to see all of my folders on my iPhone, by using userid+ I can limit them to a useful set. Juergen

2 1

[Dovecot] deleteing label (cheating crackers)
by Mohsen Pahlevanzadeh 04 Jun '09

04 Jun '09

Dear all, When i telnet to my server, I see following things: [root@daka ~]# telnet 0 110 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. +OK Dovecot ready. Now i want to delete Dovecot word & put my word. How i do? Yours, Mohsen

3 2

[Dovecot] Password environment variable - logging the password
by Donovan Craig 04 Jun '09

04 Jun '09

Hi, We¹re migrating to a Cpanel hosting system. Our passwords are currently stored in MD5. I looked at the post login scripting to be able to start storing the plain text passwords as people login temporarily so we can automate our migration. It seems that the password is not available in the post login environment variables. Is there any way we can get access to the plain text password upon login so we can insert this into our user table? Best regards, Donovan

3 2

[Dovecot] Some questions about deliver
by Axel Luttgens 04 Jun '09

04 Jun '09

While investigating Dovecot's deliver with Postfix, I encountered some behaviors making me wonder whether I really understand the purpose of that binary. So, if you allow... This is from Postfix' main.cf: mailbox_command = /usr/local/dovecot/libexec/dovecot/deliver -e -n This is my quick setup for Dovecot: # 1.2.rc4: /usr/local/etc/dovecot.conf # OS: Darwin 9.7.0 i386 protocols: pop3 ssl: no disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/dovecot-1.2.rc4/libexec/dovecot/pop3- login first_valid_uid: 2001 mail_location: mbox:~/_mailboxes:INBOX=~/_inbox/mailspool mbox_read_locks: flock mbox_write_locks: flock dotlock mail_executable: /usr/local/dovecot-1.2.rc4/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/dovecot-1.2.rc4/lib/dovecot/pop3 pop3_lock_session: yes pop3_uidl_format: %08Xv%08Xu auth default: passdb: driver: pam args: * userdb: driver: passwd Here is an excerpt from mail.log: postfix/smtpd[4117]: connect from localhost[127.0.0.1] postfix/smtpd[4117]: 163E1CA2675: client=localhost[127.0.0.1] postfix/cleanup[4120]: 163E1CA2675: message-id=<27002A3F-AF44-410D-A500-368D04F5FA9A(a)almbp.local > postfix/qmgr[3232]: 163E1CA2675: from=<testuser(a)almbp.local>, size=2650, nrcpt=1 (queue active) dovecot[4129]: deliver(www): mail_location: mbox: mkdir(/Library/ WebServer/_mailboxes) failed: Permission denied (euid=70(_www) egid=70(_www) missing +w perm: /Library/WebServer) dovecot[4129]: deliver(www): Fatal: Namespace initialization failed postfix/local[4122]: 163E1CA2675: to=<www(a)almbp.local>, relay=local, delay=0.09, delays=0.02/0/0/0.07, dsn=4.3.0, status=deferred (temporary failure) postfix/smtpd[4117]: disconnect from localhost[127.0.0.1] 1. Shouldn't deliver honor the first_valid_uid setting? After all, if some user isn't allowed to login, is that user supposed to receive mail? 2. What exactly is the -e option supposed to do? User _www clearly isn't configured for receiving mail, but Postfix will nevertheless try to deliver the message until maximal_queue_lifetime has expired. From the log excerpt, it appears that Postfix has been led to consider a temporary failure; unless I'm wrong, that's because Postfix didn't receive neither a "D.S.N text" string nor an EX_* fatal return code. From deliver.c, it seems that many calls to i_fatal() are liable to be executed before the -e option is taken into account (through the local variable stderr_rejection). As a result, I'm wondering under which circumstances exactly deliver is liable to return EX_NOPERM, so that Postfix may consider a permanent failure and bounce the message. Note that the question may somehow be re-phrased as: when invoked without the -e option, under which circumstances will deliver send a rejection message? 3. Doesn't failure_exit_callback() in deliver.c tend to merge many (possibly dissimilar) errors into the single EX_TEMPFAIL one? And BTW, is that function guaranteed to be always called with an EX_* value? Seems to be the case, but... ;-) TIA for your patience, Axel

2 5

[Dovecot] Maildir compression utility
by John Fawcett 04 Jun '09

04 Jun '09

Does anyone know of a script to compress old mails stored in a maildir format by carrying out the steps described at http://wiki.dovecot.org/Plugins/Zlib thanks, John

2 2

[Dovecot] Lost sub-mailboxes - not showing after upgrading to Dovecot from Courier-IMAP
by James Brown 04 Jun '09

04 Jun '09

Last night we migrated from Courier-IMAP to Dovecot 1.2RC5 and all seems to work fairly well, but I seem to have lost all my mailboxes apart from INBOX. The maildirs are all on the HD in the correct place (/usr/local/virtual/bordo.com.au/jlbrown): mail:jlbrown root# ls -l total 21400 drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .4D drwxrwxr-x 14 _vmail _postfix 476 Jun 4 00:06 .ASSP drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:06 .ATO drwxrwxr-x 12 _vmail _postfix 408 Jun 4 00:06 .Actionable drwxrwxr-x 11 _vmail _postfix 374 Jun 3 23:56 .Apple Mail To Do drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:12 .ClamAV drwxrwxr-x 10 _vmail _postfix 340 Jun 3 08:28 .Deleted Messages drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .Drafts drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .Expenses drwxrwxr-x 12 _vmail _postfix 408 Jun 4 00:06 .Follow Up drwxrwxr-x 10 _vmail _postfix 340 Jun 4 09:11 .INBOX.INBOX.Drafts drwxrwxr-x 9 _vmail _postfix 306 Jun 4 09:11 .INBOX.INBOX.Sent drwxrwxr-x 10 _vmail _postfix 340 Jun 4 09:11 .INBOX.INBOX.Trash drwxrwxr-x 10 _vmail _postfix 340 Jun 4 09:04 .INBOX.Trash drwxrwxr-x 14 _vmail _postfix 476 Jun 4 00:12 .Iain drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:06 .Jokes drwxrwxr-x 15 _vmail _postfix 510 Jun 4 00:06 .Junk drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:06 .Nessus drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .Postfix drwxrwxr-x 14 _vmail _postfix 476 Jun 4 00:11 .Sapphire drwxrwxr-x 15 _vmail _postfix 510 Jun 4 00:08 .Sent drwxrwxr-x 10 _vmail _postfix 340 Jun 3 16:15 .Sent Messages drwxrwxr-x 8 _vmail _postfix 272 May 26 10:28 .ToDos.mbox (Dovecot) drwxrwxr-x 11 _vmail _postfix 374 Jun 3 23:58 .ToDos.mbox (IMAP Account) drwxrwxr-x 11 _vmail _postfix 374 Jun 3 23:58 .ToDos.mbox (jlbrown IMAP) drwxrwxr-x 13 _vmail _postfix 442 Jun 4 00:11 .Trash drwxrwxr-x 3 _vmail _postfix 102 Jun 3 23:58 courierimaphieracl drwxrwxr-x 3 _vmail _postfix 102 Jun 3 23:58 courierimapkeywords -rw-r--r-- 1 _vmail _postfix 290 Dec 16 14:51 courierimapsubscribed -rw-r--r-- 1 _vmail _postfix 394010 Jun 3 17:46 courierimapuiddb -rw-r--r-- 1 _vmail _postfix 513065 May 25 17:04 courierpop3dsizelist drwxrwxr-x 6933 _vmail _postfix 235722 Jun 4 09:09 cur -rwxrwxr-x 1 _vmail _postfix 34 May 26 10:17 dovecot-keywords -rw-rw-r-- 1 _vmail _postfix 537661 Jun 4 09:07 dovecot-uidlist -rwxrwxr-x 1 _vmail _postfix 8 Jun 4 09:09 dovecot- uidvalidity -rwxrwxr-x 1 _vmail _postfix 0 May 26 09:55 dovecot- uidvalidity.4a1b2fff -rw-rw-r-- 1 _vmail _postfix 111504 Jun 4 09:04 dovecot.index -rwxrwxr-x 1 _vmail _postfix 9335808 Jun 4 09:09 dovecot.index.cache -rw-rw-rw- 1 _vmail _postfix 30724 Jun 4 09:11 dovecot.index.log drwxrwxr-x 2 _vmail _postfix 68 Jun 4 09:07 new -rw-rw-r-- 1 _vmail _postfix 118 Jun 4 09:09 subscriptions drwxrwxr-x 3 _vmail _postfix 102 Jun 4 09:07 tmp Any idea how to get them back? Same with my Sent emails - only the emails sent since switching to Dovecot are there. Thanks, James.

4 3

[Dovecot] Help please- Post - Login Script--- Migration
by Ashraf 04 Jun '09

04 Jun '09

Hi all I am in the process of migrating Courier to Dovecot, am using courier-dovecot-migrate.pl<http://www.dovecot.org/tools/courier-dovecot-migrate.pl>it works fine. I want to migrate each user as they login using post-login script (As i have huge no of users). We are using NFS storage, users are authenticated using mysql, User home directories as passed using variable mail ( usign mysql query). I am trying to execute postlogin script which does the conversion but unable to pass the user home directories . --*/etc/dovecot.conf mail_executable = /usr/libexec/dovecot/postloginscript.sh %h ---* %h ---- for home directory. ---*postloginscript.sh #!/bin/sh /usr/libexec/dovecot/courier-dovecot-migrate.pl --quiet --to-dovecot --recursive --convert $1 # This is for pop3 exec /usr/libexec/dovecot/pop3 ----* When i pass %h as argument its creating "%h" directory and writing dovecot-uidlist and rest the files in %h directory. Its not interpreting the %h and not passing the home directory. Its just passing as it is. Hope i am clear in articulating my problem. Please help. -- Regards Ash

2 7

[Dovecot] system accepts my domains without point
by Esteban Torres Rodriguez 03 Jun '09

03 Jun '09

I have postfix+ dovecot + ldap (AD). my system accepts user@domain as user@domain. as user(a)domain.com. To send as much to create the mailbox when I login to squirrelmail, for example. Problem is postfix, dovecot or from AD? Someone can help me? -- ################################################## # Esteban Torres Rodríguez # # Área de Soporte Técnico # # Subdirección de Sistemas Informáticos # # Empresa Pública Desarrollo Agrario y Pesquero # # email: etorres(a)dap.es # ##################################################

2 1

Re: [Dovecot] expire tool - individual user/folder?
by Andre Hübner 03 Jun '09

03 Jun '09

Hello, > The patch shouldn't really have changed anything. > >> in 1.1.16 it works without the patch. > > And I didn't fix anything in 1.1.16 either. Maybe it was some weird > compiling issue or something.. i do not have an explanation, but effect is the same. i repackaged 1.1.15 with and without patch and only the one with the patch works. for 1.1.16 i do not need a patch. gcc is 4.1.2 but its not important for me, just some tests... Andre

1 0

[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] expire tool - individual user/folder?
by Andre Hübner 02 Jun '09

02 Jun '09

Hello, is the expire plugin usable to delete mails with different settings for each individual user? If i view sample config at http://wiki.dovecot.org/Plugins/Expire it looks like expire-data are related to foldernames. Is it possible to let each user "activate" the expire-plugin for different folders with different settings? Thanks, Andre

2 11

[Dovecot] Running imaptest revision 209:939fa886391a built against dovecot revision 9116:9ae55b68cf61 on AIX 5.3 core dumps
by Jonathan Siegle 02 Jun '09

02 Jun '09

# ./imaptest host=127.0.0.1 port=143 user=tstem38 pass=pass4you mbox=/ gpfs/users/t/s/tstem38/IMAP/foo4 Panic: file client.c: line 620: assertion failed: (idx >= array_count(&clients) == NULL) IOT/Abort trap(coredump)

3 3

Re: [Dovecot] Missing IMAP folders after Server reboot
by punit_j 02 Jun '09

02 Jun '09

Did you try looking for the folders by connecting to IMAP using command line. telnet servername 143 a1 login username pass a2 list "" * Check if you could see anything.

3 2

[Dovecot] v1.1.16 released
by Timo Sirainen 02 Jun '09

02 Jun '09

http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz.sig Fixes a couple of bugs in v1.1.15's changes. Hopefully the last v1.1 release before v1.2.0. - v1.1.15 could have crashed if mailbox-closing command was pipelined after a mailbox-accessing command. - v1.1.15's zlib plugin may have caused crashes when fetching INTERNALDATE. - Maildir: If messages had been deleted externally from new/ directory and mailbox was opened with EXAMINE, Dovecot didn't immediately notice that the messages were deleted. - If message body started with a space, some operations could have assert-crashed.

3 3

[Dovecot] Log filenames of saved files to inbox by dovecot-deliver
by Sven Eulberg 02 Jun '09

02 Jun '09

Hello, Is it possible to log the filenames into deliver.log where dovecot- deliver saved incoming emails? If not so, please add this as a feature request. Thanks in advance! Regards, Sven

2 1

[Dovecot] recipient delimiter and lmtp
by John Fawcett 02 Jun '09

02 Jun '09

I read in the list archives about work in progress on an lmtp delivery agent.As a previous cyrus user where that was the preferred delivery method from postfix, this sounds interesting. I was wondering whether it will handle recipient delimiters. ie will it be able to map user+foo(a)example.com to user(a)example.com? I'm not interested in the delivery into folder stuff, just the plain delivery to inbox. thanks, John

6 10

[Dovecot] IMAP labeling sometimes not taken into account
by Olivier Cailloux 02 Jun '09

02 Jun '09

Dear Dovecot list, I recently switched from uw-imapd to dovecot to manage my huge mbox files (about 1 GB). I now observe a very strange behavior, difficult to reproduce reliably, which might be related to some misunderstanding on my part on how either dovecot works or imap labeling works. What I call "labeling" is the fact of marking some e-mail, in my e-mail client (currently Thunderbird), with a label, which can be chosen among five labels (plus the "no-label" case). Evolution also supports labeling. As far as I understood until a few days ago, when I put a label, say, number five, on an e-mail, a keyword "$Label5" is added on the "X-Keywords:" line of the corresponding e-mail in my mbox file. Removing the label simply removes the keyword on the same line. That is, at least, what happened with uw-imapd (not that I have seen that documented somewhere but this is what I observed). The label is thus stored on the e-mail server, not on the client hard disk, which is important for me as I extensively use that feature to sort e-mails, and need to access them from several different places (and find the same labels at the same places, naturally, whatever client I use). Since the change for dovecot, however, things are going strange. Sometimes the labels disappear for some reasons. Sometimes they stay there. And I can't reproduce the behavior, it just seems random. This is very annoying as it totally breaks my e-mail management. Currently there is something strange I can reproduce however, and if someone could explain me what is happening I guess it would be a good step towards a solution. I see a specific e-mail as being labeled in thunderbird, having label number five. I also tried with evolution, accessing the same imap folder, evolution also sees that e-mail as having a label number five. I tried running these clients from my imap server, and I tried thunderbird on a Windows box at home, and every clients agree: this e-mail has a "5" label. BUT when I open the mbox file directly on the imap server (using "less"), and scroll to that given e-mail, I see NO "X-Keywords: " line. How then can the e-mail clients know that this e-mail is labeled? Please note that this behavior does not happen with only one specific e-mail, but I take it as an example of what is strange. In fact I can see, especially at the end of the mbox file (thus the latest e-mails), that plenty of e-mails have either no "X-Keywords: " line or a line with "X-Keywords: " and nothing else, whereas they are seen as being labeled (and indeed I remember having labeled most of those through thunderbird). The former e-mails I checked in the m-box (for example, one month ago) all correctly have an X-Keywords line indicating "$Label5" or other appropriate labels. It seems like dovecot is keeping some track of labeled e-mails somewhere which is NOT in the mbox file, probably related to its indexing capabilities. But I don't know how that works and where these index files are stored, how to purge them and rebuild the index, and so on. Apparently these index files have remembered some e-mails as being labeled (which is good, because I indeed labeled them). But I'd like to know how that works to be able to better troubleshoot why sometimes the label disappear. Note that restarting dovecot does not change the label status of the e-mail, so the status must be stored somewhere on disk and not only in memory. Or is all these labeling stuff some unsupported, non-standard extension to IMAP that only uw-imapd supports? (I hope not because I find it very practical and I'd like to use it with dovecot as well!) Thank you for any help. (Technical informations follow.) Olivier ------ 2-12h38-~#dovecot --version 1.0.15 ------ 2-12h38-~#dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail auth default: passdb: driver: pam userdb: driver: passwd ------

2 2

[Dovecot] Capability problems dovecot 2.0
by ja nein 01 Jun '09

01 Jun '09

Hi, I had some problems connecting TB 2.x with dovecot 2.0. TB2 complained about not being an IMAP4 server. TB 3 worked. It seems that dovecot 2.0 doesn't return capabilities when queried. Maybe some wrong config, thoug? Here are the debug logs from TB2 comparing dovecot 2.0 (not working) and dovecot 1.2 (working): Dovecot 2.0: NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. NA:SendData: 1 capability ReadNextLine [stream=26c2d60 nb=15 needmore=0] NA:CreateNewLineFromSocket: * CAPABILITY ReadNextLine [stream=26c2d60 nb=28 needmore=0] NA:CreateNewLineFromSocket: 1 OK Capability completed. ProcessCurrentURL: aborting queued urls NA:SendData: 2 logout Dovecot 1.2: NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. NA:SendData: 1 capability ReadNextLine [stream=27dcf50 nb=303 needmore=0] NA:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 ReadNextLine [stream=27dcf50 nb=28 needmore=0] NA:CreateNewLineFromSocket: 1 OK Capability completed. NA:SendData: 2 authenticate plain ReadNextLine [stream=27dcf50 nb=4 needmore=0] NA:CreateNewLineFromSocket: + NA:SendData: Logging suppressed for this command (it probably contained authentication information) ReadNextLine [stream=27dcf50 nb=266 needmore=0] NA:CreateNewLineFromSocket: 2 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA] Logged in A:SendData: 3 namespace And all goes well... TB3 seems to be fine without extra capability stuff. Regards, Sebastian

5 20

[Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
by James Butler 01 Jun '09

01 Jun '09

Postfix 2.5.5 SpamAssassin 3.2.5 (under Perl 5.10.0) ClamAV 0.95.1 Dovecot 1.2.rc2 works fine on Fedora 10. Installed Dovecot and ClamAV from source and everything else using yum. I'm using the ClamAV plugin for Spamassassin: http://wiki.apache.org/spamassassin/ClamAVPlugin I'm calling Spamassassin with: /etc/postfix/main.cf: mailbox_command = /usr/bin/spamc -f -e /usr/local/libexec/dovecot/deliver Postfix hands off to Spamassassin, which processes ALL mail (not just attachments) through the ClamAV plugin before parsing for spam, and then hands the whole mess off to Dovecot for 'deliver' to handle. How simple is that? Since ClamAV scanns all mail, it might be too processor-intensive for really large mail systems, but it is working great for our 120+ user system with lots of spam coming in. If you're using Procmail or some other preprocessor that can hand off to a pipe, then you could skip the plugin and pipe messages over a certain size (i.e. >1024) to clamd, instead. Enjoy! James

4 3