- dovecot - dovecot.org

[Dovecot] One LDAP attribute for many variables
by Juan Asensio Sánchez 31 Jul '08

31 Jul '08

Hi Using Dovecot 1.1.2 with LDAP. If i have this: user_attrs = uid=home=/var/vmail/%$,mailuserquota=quota_rule=*:storage=%$,=mail=maildir:/var/vmail/%n/Maildir OK. But if i have this: user_attrs = uid=home=/var/vmail/%$,mailuserquota=quota_rule=*:storage=%$,uid=mail=maildir:/var/vmail/%$/Maildir I get this error: deliver(usuario1): Jul 25 12:59:08 Error: Per-user script path is unknown. See http://wiki.dovecot.org/LDA/Sieve#location The only difference is that I use the uid LDAP attribute twice. Why does this happen?

2 1

[Dovecot] Seen flag in maildir filename not being respected
by Eduardo M KALINOWSKI 31 Jul '08

31 Jul '08

Hi, I'm using dovecot 1.1.2 (but I've noticed this since 1.1.1 which I was using until yesterday). It seems dovecot is ignoring the "S" flag in Maildir filenames, and is relying only in its Index Files to determine if a message has been read or not. I say that because if I delete the dovecot.index.* files for a mail folder, all the mails in there appear as unread. Also, I've tried accessing the maildir directly (using heirloom-mailx, but mutt should have done, too) and reading a new message. The file name was changed to add a "S" to the end, but this message was still marked as "unread" when the mail folder was accessed via IMAP. The flags R, F and T are correctly read from the filename if no index is present. I haven't tested the other flags. I'm using dovecot's deliver, and it creates filenames such as "1217450416.M77457P5201.mail.kalinowski.com.br,S=1377,W=1411:2,S", that is, perfectly fine. dovecot -n: # 1.1.2: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot/main.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/certs/server.pem ssl_key_file: /etc/ssl/private/server.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_processes_count: 1 first_valid_uid: 100 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n/INBOX:INDEX=/home/vmail/%d/%n/dovecotidx mail_plugins: quota imap_quota zlib auth default: mechanisms: plain login cram-md5 passdb: driver: passwd-file args: username_format=%n /home/vmail/%d/db/passwd passdb: driver: pam userdb: driver: static args: uid=104 gid=8 home=/home/vmail/%d/%n userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 438 master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: mail plugin: quota: maildir quota_rule: ?:storage=0 quota_rule2: Trash:ignore quota_rule3: Spam:ignore quota_rule4: Spam.Errado:ignore sieve: /home/vmail/%d/db/sieves/%n.sieve

2 3

[Dovecot] wrong permission
by Cor Bosman 31 Jul '08

31 Jul '08

Im still finding a number of control directories that have the wrong permission: Jun 26 00:02:34 userimap13.xs4all.nl dovecot: IMAP(xxx): file_dotlock_create(/var/spool/mail/dovecot-control/g/gl/xxx/INBOX/.Apple Mail To Do/dovecot-uidlist) failed: Permission denied userimap1# ls -al "/var/spool/mail/dovecot-control/g/gl/xxx/INBOX/.Apple Mail To Do" total 8 drw------- 2 xxx user 4096 May 12 23:43 . drwx------ 7 xxx user 4096 May 12 23:43 .. This folder was created May 12, well after us starting to use 1.1RC versions. I currently fixed a few hundred of these (out of millions of folders), and whats interesting is that a very large percentage of those (1/3th) is the folder "Apple Mail To Do", created by Mail.App I think. Obviously that same folder is no where near 1/3th of our total folder number, so thats a bit strange. I really doubt this is some local setting issue, because then id see much more of those. Right now it's a tiny fraction of our total folder amount, which leads me to believe it's some weird edge case in the dovecot code. Anyone have any ideas? Cor

2 9

[Dovecot] dovecot-imap displays empty domainalias mailboxen
by Kacper Wysocki 31 Jul '08

31 Jul '08

Hi folks, I'm using dovecot 1.0.13 as the IMAPS frontend for a vpopmail/qmail virtual domain setup. Dovecot is set up as follows: passdb vpopmail{ } userdb vpopmail{ } I've added a domain alias for the main domain with vaddaliasdomain and email to post@aliasdomain is delivered to post@maindomain and can be checked with pop. However, when I try to check IMAP through the account post@aliasdomain I am confronted with an empty mailbox. If I log in using post@maindomain I get the expected contents. Why can't my users log in using user@aliasdomain to check their emails? Regards, Kacper Wysocki -- http://kacper.doesntexist.org http://windows.dontexist.net There is symmetry in chaos, and chaos in excessive order. Though you may see heaven or hell, remember that it is your mind which creates them. Avoid grasping the one or fleeing the other.

1 0

Re: [Dovecot] Some help required - dovecot: IMAP(matthew): unlink(/home/matthew/Maildir/cur/new) failed: Operation not permitted
by Matthias Andree 31 Jul '08

31 Jul '08

Hi I hope you're not offended by posting a quote to the list... you sent the mail just to me. On Thu, 31 Jul 2008, matbic(a)gmail.com wrote: > Here here is an excerpt: > > ls -l home/matthew/Maildir/cur > ... > drwx------ 2 matthew matthew 512 Jul 30 17:48 cur:2,ST > drwx------ 2 matthew matthew 512 Jul 31 06:55 new > drwx------ 2 matthew matthew 512 Jul 30 18:21 tmp:2,ST > > Is this to be expected or is this my problem? These (in .../Maildir/cur) are your problem - someone created a Maildir underneath Maildir/cur, and dovecot or some other software considered the three directories messages, and goofed up. Check your delivery recipes so that none deliver to .../Maildir/, if you find any, adjust them deliver to .../Maildir/ instead. I'd suggest to: cd /home/matthew/Maildir/cur # move potential messages out to the proper new/... directory # if mv complains about nonexistent .../*, all the better! mv 'cur:2,ST/'* 'new/'* 'tmp:2,ST/'* ../new/ # get rid of the bogus directories rmdir '???:2,ST/' new cd - and see if that fixes the problem. If rmdir fails because there are hidden files, see what they are and where to move them, if the {cur,tmp}:2,ST or new are empty, fine, someone accidentally ran maildirmake with bogus arguments. HTH Matthias

2 1

[Dovecot] .files in dovecot-1.1.1
by John Baker 31 Jul '08

31 Jul '08

Hi there We had been using the stock Ubuntu Dapper Dovecot which is an early 1.0 beta but just upgraded to 1.1.1 to fix some read flag issues with Horde. Previously dovecot seemed to ignore files beginning with "." in the ~/mail (mbox format) directory but now shows them. There doesn't seem to be any switch in the dovcot.conf file to change this. Any such settings are about maildir. Is there anyway to make dovecot-1.1.1 ignore hidden files? Thanks -- John Baker Network Systems Administrator Marlboro College Phone: 451-7551 off campus; 551 on campus

2 1

[Dovecot] login processes from attacks staying for hours
by Kai Schaetzl 31 Jul '08

31 Jul '08

I'm in the process of rolling out new setups with dovecot on CentOS 5.2 and I notice that dovecot doesn't handle the brute-force attacks too nice. I reduced the limit a bit to some reasonable looking value: login_max_processes_count = 32 to stop them earlier and the number of processes stops at that figure when an attack happens. However, it stays at this count for hours although the attack is already over since long. For instance, my monitoring alerts me at the moment when the process count for pop3-login goes over 20 processes. This happened on three machines at 2 am with a brute-force attack from the same source that didn't last longer than a minute or so. However, the process count dropped only at 7am under 20 on two machines and on the third machine it was still over 20 when I was in the office at 9 am and finally killed them. As these machines are all not in production yet, there weren't any other logins and the single brute-force ended within one minute according to the logs (obviously when pop3-logins hit the limit). Shouldn't these processes go down to login_processes_count (3) within a few minutes? An strace shows that they are mostly doing gettimeofday lookups (=sleeping). This is the default dovecot (1.07) coming with CentOS 5.2. I've been running only one other instance of dovecot in production (0.99.11) on CentOS 4.6 so far and I don't know which behavior that displayed in the past as I just recognize that I accidentally ommitted it from monitoring. :-( I had this mailing list searched for "brute-force" to see how others handle this and what dovecot provides to stop these attacks. I have found not many threads about this. There is one with a bit more information: "Delay on failed pw attempts" from January 1. Unfortunately, this functionality is only in a later version of dovecot and it's not clear if it was implemented or not or if it would be helpful. Was it implemented? This thread also mentions fail2ban which may be one way to go, although I don't like this log parsing approach too much. Does anyone use iptables for rate-limiting per IP on the pop/imap ports to prevent brute-force attacks? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

7 9

[Dovecot] installing plugin (autocreate_plugin.c)
by Marcin Gryszkalis 31 Jul '08

31 Jul '08

Hi I want to enable autocreate-plugin, I downloaded http://dovecot.org/patches/1.1/autocreate-plugin.c compiled as specified in comment and got autocreate_plugin.so but I'm not sure how do I install it. I have many plugins in /usr/local/lib/dovecot/ (it's FreeBSD) and subdirs, but they all have libXX_ prefixes (what do they mean?). I couldn't find any information about installing plugins on dovecot's wiki and I don't want to experiment as the server is live (not really important but still live). regards -- Marcin Gryszkalis, PGP 0x9F183FA3 jabber jid:mg@fork.pl, gg:2532994 http://the.fork.pl

2 1

[Dovecot] Some help required - dovecot: IMAP(matthew): unlink(/home/matthew/Maildir/cur/new) failed: Operation not permitted
by matbic＠gmail.com 31 Jul '08

31 Jul '08

Hi all, I have tried very hard to solve this problem but turn to the mailing list as a last resort. In the log I get, for just one account: Jul 31 09:06:17 bickertons dovecot: imap-login: Login: user=<matthew>, method=PLAIN, rip=78.130.81.201, lip=168.143.5.18, TLS Jul 31 09:06:17 bickertons dovecot: IMAP(matthew): Effective uid=1003, gid=1003, home=/home/matthew Jul 31 09:06:17 bickertons dovecot: IMAP(matthew): maildir: data=/home/ matthew/Maildir Jul 31 09:06:17 bickertons dovecot: IMAP(matthew): maildir: root=/home/ matthew/Maildir, index=/home/matthew/Maildir, control=, inbox= Jul 31 09:06:17 bickertons dovecot: IMAP(matthew): unlink(/home/ matthew/Maildir/cur/new) failed: Operation not permitted Jul 31 09:06:18 bickertons last message repeated 3 times All the other accounts work fine. I have tried removing the dovecote.index and the dovecote-keywords and uidlist files. This gets it working for a while but soon we are back to the same problem. I would really not like to lose all the mail in this account, its that of my boss, (slight note of panic) Matthew bickertons# dovecot --version 1.0.13 bickertons# dovecot -n # 1.0.13: /usr/local/etc/dovecot.conf protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_max_processes_count: 30 max_mail_processes: 50 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape- eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam args: * userdb: driver: passwd

2 1

[Dovecot] lib90_cmusieve_plugin.so: undefined symbol: message_decoder_init
by Thomas Harold 31 Jul '08

31 Jul '08

After upgrading our CentOS 5 box to the latest revisions last week (including Dovecot 1.1), we're seeing the following error message in the log files. Sieve was working fine with Dovecot 1.0. I have yet to turn up anything via Google for this particular error. SELinux is not logging any error messages at the moment, so I'm pretty sure that we've properly allowed all the SELinux permissions. # cat /var/vmail/dovecot-deliver.log deliver(ruth(a)example.com): Jul 28 11:11:44 Error: dlopen(/usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so) failed: /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so: undefined symbol: message_decoder_init deliver(ruth(a)example.com): Jul 28 11:11:44 Fatal: Couldn't load required plugins # ls -l /usr/libexec/dovecot/sievec -rwxr-xr-x 1 root root 165152 Jun 11 03:21 /usr/libexec/dovecot/sievec # ls -l /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so -rwxr-xr-x 1 root root 141328 Jun 11 03:21 /usr/lib64/dovecot/lda/lib90_cmusieve_plugin.so # yum list | grep "dovecot" dovecot.x86_64 1:1.1.1-2_76.el5 installed dovecot-sieve.x86_64 1.1.5-8.el5 installed dovecot.x86_64 1:1.1.2-2_77.el5 atrpms dovecot-devel.x86_64 1:1.1.2-2_77.el5 atrpms

3 8