- dovecot - dovecot.org

[Dovecot] Disallow folder delete
by Kenneth Porter 24 May '08

24 May '08

Is there a straightforward way to disallow the deletion of all IMAP mailboxes? I have a user who's deleted an important IMAP mailbox and I'm now recovering a recent copy from the backup. But I'd rather just blanket disallow all folder deletions. The user is using Thunderbird and this has happened more than once so I suspect Tbird is willing to let a folder get deleted too easily. Perhaps there was a delay in the confirmation dialog and the user clicked ahead and confirmed something he shouldn't have. I'm looking at <http://wiki.dovecot.org/ACL> and it looks like I should be able to use a group override to disallow "x" (mailbox delete) but the page says that groups aren't implemented, so I don't know how one says that nobody can do this for any mailbox. I'm using 1.2.rc15 from CentOS 5 (RHEL5 equivalent).

7 16

[Dovecot] Don't Understand Error Entry
by Carlos Williams 24 May '08

24 May '08

I am using dovecot-0.99.11-8.EL4 on my system and decided to check the logs since I just took over as the administrator on this system and I noticed the same error entry over and over in the logs. I went to /var/log/dovecot.err and see: imap(rangry): May 22 13:33:31 Error: Error parsing IMAP envelope: "Thu, 20 Apr 2006 10:10:01 -0400" "Re: Hi there I have a question" (("Rodney Angry" NIL "rodney.s.angry" "example.com")) (("Rodney Angry" NIL "rodney.s.angry" " example.com")) ((NIL NIL "rodney.s.angry" "example.com")) (("Gryder, Connie" NIL "CONSTANCE.L.GRYDER" "example.com")) NIL NIL "< DD3761B99DC88F4284EDE00D608383C65DF16C(a)0088-its-exmp01.us.example.com>" NIL I don't understand what this error message means and why its flooding my logs. I do know the that the name in parenthesis on line one is a user on my email server. <rangry> is a user on my domain with a valid email account but I can't tell if the problem is coming from example.com or originating from <rangry>. Anyone happen to know what is causing this? I don't know if you guys need my config here so I don't want to flood this message. If this makes sense to anyone, please let me know what I can do to resolve this or keep this from flooding my email server. Thanks!

4 5

[Dovecot] log contents questions?
by Knute Johnson 24 May '08

24 May '08

I switched from using Pegasus and POP3 to Thunderbird and IMAP for my email. Now I get a lot of "Corrupted index cache file" errors in my log. Dovecot is running under Fedora 8 and is version 1.0.13-6.fc8. The Thunderbird is version 2.0.0.14 running under Windows XP. My wife's Blackberry is also using IMAP and not reporting any errors. Any ideas what the problem is or how to fix it? Thanks, knute... --------------------- Dovecot Begin ------------------------ Dovecot disconnects: Inactivity: 2 Time(s) Logged out: 2606 Time(s) in IDLE: 27 Time(s) **Unmatched Entries** dovecot: IMAP(knute): Connection closed: 5 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/CR-FFL/dovecot.index.cache: invalid record size: 3 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/INBOX/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(knute): Corrupted index cache file /home/knute/mail/.imap/frazmtn.com/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Connection closed: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Dovecot/dovecot.index.cache: invalid record size: 2 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora List/dovecot.index.cache: invalid record size: 4 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Selinux List/dovecot.index.cache: invalid record size: 1 Time(s) dovecot: IMAP(linux): Corrupted index cache file /home/linux/mail/.imap/Fedora Test List/dovecot.index.cache: invalid record size: 2 Time(s) ---------------------- Dovecot End ------------------------- -- Knute Johnson linux(a)www.knutejohnson.com

2 4

[Dovecot] procmail --> deliver question
by Ben Budts 23 May '08

23 May '08

Hi there, I use dovecot-1.1-rc4, got imap, imaps, pop3 & pop3s working fine with the mbox format. I use sendmail-8.14.2 as an MTA, sendmail uses procmail as an LDA. I migrated to maildir format now, and pipe all my mail to deliver right now to be able to make use of the indexing etc... Problem is I run into some errors : #My .procmailrc PATH=/usr/bin:/usr/local/bin:/usr/sbin SHELL="/bin/bash" SENDMAIL="sendmail -oi -t" DELIVER="/opt/dovecot/libexec/dovecot/deliver" LOGFILE="$HOME/procmail.log" #/dev/null VERBOSE=on LOGABSTRACT = "all" #DEFAULT="$HOME/Maildir/" #MAILDIR="$HOME/Maildir/" :0 w | $DELIVER ##### My procmail.log : procmail: [12743] Wed May 21 13:43:38 2008 procmail: Assigning "LOGABSTRACT=all" procmail: Executing "/opt/dovecot/libexec/dovecot/deliver" Fatal: destination user parameter (-d user) not given procmail: Error while writing to "/opt/dovecot/libexec/dovecot/deliver" procmail: Program failure (64) of "/opt/dovecot/libexec/dovecot/deliver" procmail: Assigning "LASTFOLDER=/opt/dovecot/libexec/dovecot/deliver" procmail: Locking "/var/spool/mail/kris.lock" procmail: Assigning "LASTFOLDER=/var/spool/mail/kris" procmail: Opening "/var/spool/mail/kris" ####" It's not working out and he falls back to delivering his mail to /var/spool/mail/%u Could you guys point me out in the right direction please ? Another question about the logging with deliver... I've put the following in my deliver.conf : deliver.conf in the lda section : log_path = /var/log/dovecot/deliver.log info_log_path = /var/log/dovecot-deliver.log root@blaat:/home/kris# ls -la /var/log/dovecot/ total 232 drwxrwxrwx 2 root root 4096 2008-05-20 10:44 . drwxr-xr-x 11 root root 4096 2008-05-19 10:08 .. -rw-rw-rw- 1 root root 0 2008-05-20 10:44 deliver.log But it's not logging at all... Also tried the syslog alternative, no logging either. Also put set user or group ID on execution (s) on the deliver binary : -rwsr-sr-x 1 root root 693300 2008-05-19 09:38 /opt/dovecot/libexec/dovecot/deliver thx a lot Benjamin

2 1

[Dovecot] dovecot-sieve on freebsd
by Lazar Szilard 22 May '08

22 May '08

Hi,I need some help. I use dovecot and dovecot-sieve on a freebsd 7.0-release. everything worked fine without dovecot sieve. I want to deliver amavisd spam marked messages to the 'spam' folder of the user. the system uses virtual environment with multiple domains (and users).all want is a global sieve, to all users, all domains.I googled, but I cannot find the problem,my protocol lda section:protocol lda {    log_path = /usr/local/vmail/dovecot-deliver.log    sieve_global_dir = /usr/local/vmail/globalsieverc    mail_plugins = cmusieve    mail_debug = yes    log_path = /var/log/dovecot-deliver    info_log_path = /var/log/dovecot-deliver     postmaster_address = postmaster(a)tamann.hu    mail_plugin_dir = /usr/local/lib/dovecot/lda    sendmail_path = /usr/sbin/sendmail}globalsieverc:require "fileinto";if header :contains "X-Spam-Flag" "YES" {        fileinto "Spam";        stop;}thank you for your help,and sorry for my bad english.t

1 0

[Dovecot] auth_socket_path permissiones
by Adrián Ribao Martínez 22 May '08

22 May '08

Hello, I'm using dovecot 1.0 under debian etch. The lda socket path is set to: auth_socket_path = /var/spool/postfix/private/auth But this gives me the error: net_connect(/var/spool/postfix/private/auth) failed: Permission denied I suppose deliver is run as dovecot user. I read about running deliver as root with the suid bit set. I'm not quite sure if this is a good solution. Is there any other way. In the wiki says: "Most MTAs won't let you run deliver as root, so for now you'll need to make it setuid root. However deliver isn't designed to be run as setuid-root" My MTA is postfix, does someone know if postfix let me run deliver as root? If not, should I go to the setuid option? Thank you. -- Adrián Ribao Martínez

3 3

[Dovecot] Clients hang because imap-login discards post-login commands
by Mike Abbott 22 May '08

22 May '08

Some of my IMAP clients hang when connecting to Dovecot 1.1.rc5. I believe the problem is that imap-login reads eagerly rather than sparingly. If a client sends a login user password b select Inbox all at once, without waiting for the login reply before sending the select, imap-login eats the second command (reads it from the socket and does nothing with it; system call tracing confirms this) and the client hangs waiting for a reply to the select command. I can reproduce this simply using telnet to the dovecot on localhost, as long as I send both lines at once (I paste them in together). $ telnet localhost 143 * OK Dovecot ready. a login user password b select Inbox a OK Logged in. <dovecot never replies to select> This may also be true with pop3-login, I have not checked. It does happen (with IMAP) when authentication is delayed and Dovecot responds with "* OK Waiting for authentication process to respond.." but I believe that shares the same underlying cause as the simpler case above. I believe the login processes should read only as much as they need to satisfy the login request and leave subsequent commands in the socket for post-login processing. Or, the login processes should pass the remainder of their input buffers to the mail processes so no commands are dropped. This section of RFC 2060 explains why I think this: 5.5. Multiple Commands in Progress The client MAY send another command without waiting for the completion result response of a command, subject to ambiguity rules (see below) and flow control constraints on the underlying data stream. Similarly, a server MAY begin processing another command before processing the current command to completion, subject to ambiguity rules. [...] The exception is if an ambiguity would result because of a command that would affect the results of other commands. Clients MUST NOT send multiple commands without waiting if an ambiguity would result. If the server detects a possible ambiguity, it MUST execute commands to completion in the order given by the client. So it appears that both the client and Dovecot may be in violation, depending on how you define "ambiguity." The RFC does not explicitly define whether login causes an ambiguity, but I personally believe that login does "affect the results of other commands" (the login may fail, for instance). So the client should not issue commands before receiving the login reply, and Dovecot should not drop commands during login. I have reported the client issue to the developers of the IMAP client, as I am reporting the server issue to you. Fortunately for me, only one or the other needs to change to erase the symptom (hung clients), but fixing both would be best. Thanks for your attention.

3 2

[Dovecot] Dovecot or postfix Quota
by Adrián Ribao Martínez 22 May '08

22 May '08

Hello, I'm a bit confused with the dovecot quota support. What is it for? I thought postfix should be the one managing the quota. If I set up a quota in dovecot, does dovecot keep the messages size under certain limit? What happen when you reach the quota limit? What's the difference between postfix quotas and dovecot quota? I'm confused about this. Thank you! -- Adrián Ribao Martínez

3 4

[Dovecot] VMware and Time moved backwards
by Robert Henjes 22 May '08

22 May '08

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections within the TSC algorithms of the vmware virtual machine. More information and some hints to workaround are documented here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=di… Nevertheless we are currently working on evaluating a stable solution by doing some system measurements, which would be the best option to cope with this problem, since the XEN environment seems to have a similar issue. Running "ntpdate -u" as a cronjob is not an option due to two facts: a) Time is moving quickly and may cause "major problems" ;) b) It is not recommended by the vmware team itself as well We are currently considering two options: a) Using the "clock=pit" kernel option, which may cause the system to be to slow b) using vmware tools and use only the ntp synchronisation of the host (we have currently only little experience with this). Also vmware tools are somewhat critical in case of updates. So our intention was to use as less vmware specific things as possible within the virtual machine, so only our host itself depends on vmware specific software. The question is, which option would you prefer? Is there another solution beside the mentioned ones? According to Timo's postings, workarounds within the dovecot itself to cope with "time moved backward" problems are not planned yet to be impelented. So best regards, Robert

5 5

Re: [Dovecot] VMware and Time moved backwards
by Robert Henjes 21 May '08

21 May '08

Thank you for the prompt answers @Luuk Vosslamber >finding correct values for the following entrys in your vmware(host) >config file might solve some things: >host.cpukHz = 1596000 <== depends on processor speed ;-) >host.noTSC = TRUE >ptsc.noTSC = TRUE >hostinfo.noTSC = TRUE >tools.syntime = TRUE > >Above values go with the presumption that the host CPU is running at a >fixed frequency. The variable frequency seems to be the origin of this >problem.. We tried your parameters already, but they are not an option, unless you have the following a) machine smp disabled (enabled in our case) b) other machines on the host system have really low load c) vmware tools should not be missing on guest @Peter Hessler >never ever ever run ntp on virtual hardware. > >instead, run ntp on the host hardware, and tell the client to always obey the bios clock. I add "* * * * * /sbin/hwclock --localtime -->hctosys" >to my crontab for that. Thank you very much Peter, this hint opens up a bunch of new possibilities only mentioning "adjtimex" ... BUT: And this brings me back to, why I posted this issue to the dovecot mailinglist and not elsewhere: All these guest based solutions lead to a fixed time movement (we used previously ntpdate -u every 7 minutes, ntp itself synchronizes every 11 minutes with the hardware clock for calculating drifts), which happens about once per week, that the time movement backward is larger than 11 seconds between two dovecot imap operations, which leads to an immediate shutdown of the dovecot process. All other services on these machine can cope with this. So the question is how to get these adjustments smooth or close to realtime. Best regards, Robert Btw.: We are running Dovecot 1.0.13 from Debian etch-backports (which is an important information since debian seems to have its own rules ;) )

1 0