May 2010 - dovecot - dovecot.org

[Dovecot] Wiki page(s) to document executable tools?
by William Blunn 14 May '10

14 May '10

Motivated by a desire to know what "doveadm" does: Do we want to be having a page or pages in the Dovecot Wiki which document the executable tools? It might be an idea for each one to say: * What the tool does * How it normally gets invoked (e.g. manually by the administrator, automatically by some other part of Dovecot, automatically by something else) * What parameters it could take and what they would do List of executable tools: (found in Debian dovecot 1.0.15) lib/dovecot/ checkpassword-reply deliver dict dovecot-auth dovecot-config gdbhelper idxview imap imap-login logview managesieve managesieve-login modules pop3 pop3-login rawlog sievec sieved ssl-build-param (found in dovecot 2.0beta5) bin/ doveadm doveconf dsync libexec/dovecot/ anvil auth config dns-client dovecot-lda expire-tool imap-utf7 listview lmtp log maildirlock script ssl-params Regards, Bill

2 1

[Dovecot] Debian package for 2.0beta5 (was: Re: %d is empty in mail_location)
by William Blunn 14 May '10

14 May '10

Thomas Leuxner wrote: > Am 14.05.2010 um 20:03 schrieb Phil Howard: > > >> I've been thinking that as soon as I get this working, I will plan a transition over to a newer server with Slackware instead of Ubuntu. Slackware is easier about letting you run packages you build from source. >> > > Probably OT, but did you consider using Stephan Bosch's builds for that? > > http://xi.rename-it.nl/debian/pool/testing-auto/dovecot-1.2/ That's interesting. I can also see Dovecot 2.0 builds in there. But they appear to be being made every couple hours, so presumably based on the bleeding edge of the Mercurial repository. It would be kind of handy to have a Debian package of the original 2.0 beta 5 build. Is that lying around anywhere? Regards, Bill

1 0

[Dovecot] dovecot 2.0 vs. SELinux
by Michal Hlavinka 14 May '10

14 May '10

Hi, we were modifying old SELinux rules for dovecot 2.0. Everything seems ok, only one report seems odd: "SELinux is preventing /usr/sbin/dovecot "write" access on dovecot.conf." Looking at strace output, dovecot tries to use socket on /etc/dovecot/dovecot.conf which is regular file and no socket: ... geteuid() = 0 getegid() = 0 open("/dev/null", O_WRONLY) = 3 fcntl(3, F_GETFD) = 0 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(4, {sa_family=AF_FILE, path="/var/run/dovecot/config"}, 110) = -1 ECONNREFUSED (Connection refused) close(4) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(4, {sa_family=AF_FILE, path="/etc/dovecot/dovecot.conf"}, 110) = -1 ECONNREFUSED (Connection refused) close(4) = 0 nanosleep({0, 70000000}, NULL) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(4, {sa_family=AF_FILE, path="/etc/dovecot/dovecot.conf"}, 110) = -1 ECONNREFUSED (Connection refused) close(4) = 0 nanosleep({0, 90000000}, NULL) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 4 fcntl(4, F_GETFL) = 0x2 (flags O_RDWR) fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(4, {sa_family=AF_FILE, path="/etc/dovecot/dovecot.conf"}, 110) = -1 ECONNREFUSED (Connection refused) close(4) = 0 nanosleep({0, 80000000}, NULL) = 0 ... (tries to connect 14x) traceback for connect causing this selinux denial is: connect net_connect_unix : lib/network.c #246 net_connect_unix_with_retries : lib/network.c : #255 master_service_open_config : lib-master/master-service-settings.c #157 master_service_settings_read : lib-master/master-service-settings.c #302 master_settings_read : master/main.c main : master/main.c Does anyone know what happens here? Why dovecot tries to use regular file dovecot.conf as socket? There is probably some magic in it (from my pov) which I don't understand. Regards, Michal Hlavinka

3 3

[Dovecot] mdbox: Is there a tool to recover space used by refcount=0 messages in mdbox storage files?
by William Blunn 14 May '10

14 May '10

Is there a tool to recover space used by refcount=0 messages in mdbox storage files? The wiki talks about it but it isn't clear where the tool is. Regards, Bill

2 2

[Dovecot] big mail Single-instance storage
by 范宜坚 14 May '10

14 May '10

hi, I am currently experiencing a problem: there is a group of 200 people to this group when a user send a large message (50MB), can easily lead to congestion. Is there a good way to handle such a situation, like the hard link cyrus?

2 1

[Dovecot] Compressed mail archives
by Will Palmer 14 May '10

14 May '10

Hello, I have recently begun using IMAP to access my mails, and have found that the size of my maildir is quickly getting larger than I had anticipated. Googling around, I've seen a lot of messages related to compressing individual messages in a maildir. However, what I'm really looking for is a solution which will allow multiple messages to be compressed into a single compressed file, while still allowing those messages to be accessed via IMAP. The reasoning behind this is that most of my incoming mail consists of many very-similar messages (for example, it is not unheard of for me to receive 10,000 emails detailing the same error report over a weekend, with the actual "needs to be processed" parts stuck on the end of each message) I'm expecting a simple "no, there's no way to do that", but I wouldn't mind being pleasantly surprised. My question again: Is there any way to keep a bundle of older mails compressed, so that they can enjoy the high compression of being very similar to each-other, while still allowing access via imap? A solution may involve (just throwing out ideas here, which I have no idea how to implement) putting messages older than N days into an MBox file, and either somehow linking my account to that file (so that my account consists of [compressed readonly Mbox]+[live uncompressed Maildir]), or perhaps the first half of that, but accessing archived messages through a separate account. (Not the preferred way, but if it's the only way, I'll do it) But really I don't even know if it's possible to have dovecot support MBox and Maildir simultaneously, nor do I know enough about the MBox format to even know if the IMAP-style "multiple mailboxes" thing is possible in MBox. Please excuse my no-doubt confused terminology and general air of doesn't-know-what-he's-talking-about. The internals of e-mail are generally not my thing, so I'd appreciate any pointing in the right direction which anyone may have to offer. Any ideas?

4 7

[Dovecot] Can't get Thunderbird 2 to delete a folder under mdbox (Dovecot 2.0beta5)
by William Blunn 13 May '10

13 May '10

Can't get Thunderbird 2 to delete a folder under mdbox (Dovecot 2.0beta5) I have built Dovecot 2.0 and installed it under "/opt/dovecot2". I have done the minimum configurations necesary to get it to work with SSL, systems users but with a secondary password database, and set up mail location as "mdbox:~/dbox". I had to create the directory "dbox" in the user's home directory to get things working. Using Thunderbird 2, I can happily copy messages into this system and read them out again, and that all works. In the user's "~/dbox" directory, I get a "storage" directory and a file "m.1". I can also create folders, and nested folders, and put messages into those and read them out again, and that all works. If I try to delete a folder through Thunderbird 2, what happen is that the folder gets moved to be under a folder "Trash" (which Thunderbird calls "Deleted"). So if I had a folder "foo" and deleted it, I end up with a folder "Trash/foo" (which Thunderbird calls "Deleted/foo"). Fair enough: Thunderbird is doing a trash can model on folders. I then go to remove the folder foo from "Trash". Thunderbird doesn't complain, and the folder disappears from the folder list. But upon re-starting Thunderbird, we see that the folder "foo" is still there under "Trash". So it seems the folder was never properly deleted. Perhaps this is a bug in Thunderbird 2, but since this is a beta Dovecot with a new storage subsystem, I thought I would suggest that it might be an issue with Dovecot 2.0beta5. Regards, Bill

3 7

[Dovecot] antispam plugin problem
by Danila 13 May '10

13 May '10

Hi I have installed a plug-in an antispam and when I try to move the message to a folder a spam mutt produces an error "Failed to call dspam." Here's my configuration(all built from ports): dovecot 1.2.11 dovecot-antispam 1.2_4,1 dspam 3.9.0_1 FreeBSD 8.0 Relevant sections from dovecot.conf: protocol imap { mail_plugins = antispam ... } plugin { antispam_signature = X-DSPAM-Signature antispam_dspam_result_header = X-DSPAM-Result antispam_signature_missing = error antispam_spam = SPAM;spam;JUNK antispam_dspam_binary = /usr/local/bin/dspam antispam_dspam_args = --client;--user vmail antispam_crm_args = --config=/home/vmail } .config used by dovecot-antispam: BACKEND=dspam-exec PLUGINNAME=antispam DEBUG=syslog DEBUG_VERBOSE=1 May 11 10:54:09 evil imap: antispam: mail copy: src spam: 0, dst spam: 1, src unsure: 0 May 11 10:54:09 evil imap: antispam: /usr/local/bin/dspam --source=error --class=spam --signature=4be87a9f953248352114216 --client --user vmail May 11 10:54:09 evil imap: antispam: executing /usr/local/bin/dspam failed: 13 (uid=1009, gid=1010) uid=1009, gid=1010 is vmail user %> grep vmail /usr/local/etc/dspam.conf Trust vmail Thanks

4 5

[Dovecot] Dovecot and POP3
by DJ GRP 13 May '10

13 May '10

Hi all, I run Dovecot 1.2.9, for both IMAP and POP3 access. I was wondering if there is a way to force messages be deleted from server when the user uses POP3, even if she has selected a 'Leave messages on server' option. I was able to do it in the past using Qpopper (--enable-auto-delete option). Thanks

1 0

[Dovecot] auth: Error: PLAIN(user): Request 27511.1 timeouted after 150 secs, state=3
by Mark Sapiro 13 May '10

13 May '10

Since upgrading from Dovecot 2.0.beta4 + patches http://hg.dovecot.org/dovecot-2.0/rev/96496e1d3d12 and http://hg.dovecot.org/dovecot-2.0/rev/aefa279e2c70 to Dovecot 2.0.beta 5, I have started to see the subject error from Dovecot for SASL authentications. It doesn't happen every time, but it happens more often than not. It doesn't seem to affect Postfix's acceptance of the message. One other change made about the same time as the dovecot upgrade that may be involved is the addition of smtpd_sasl_authenticated_header = yes in Postfix. Here is a sequence of relevant log messages for one incoming message. May 12 10:59:59 sbh16 postfix/smtpd[27511]: connect from msapiro.net[68.183.193.239] May 12 11:00:00 sbh16 postfix/smtpd[27511]: 076A36900A9: client=msapiro.net[68.183.193.239], sasl_method=PLAIN, sasl_username=mark May 12 11:00:00 sbh16 postfix/smtpd[27511]: disconnect from msapiro.net[68.183.193.239] May 12 11:00:00 sbh16 postfix/cleanup[27513]: 076A36900A9: hold: header Received: from [192.168.0.4] (msapiro.net [68.183.193.239])??(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))??(No client certificate requested)??(Authenticated sender: mark)??by sbh16.song from msapiro.net[68.183.193.239]; from=<mark(a)msapiro.net> to=<xxx(a)example.com> proto=ESMTP helo=<[192.168.0.4]> May 12 11:00:00 sbh16 postfix/cleanup[27513]: 076A36900A9: message-id=<4BEAECA2.7060300(a)msapiro.net> May 12 11:00:12 sbh16 MailScanner[25960]: Requeue: 076A36900A9.A66FD to B52366900BA May 12 11:02:29 sbh16 dovecot: auth: Error: PLAIN(mark): Request 27511.1 timeouted after 150 secs, state=3 Note that the timeout occurs, about 149 seconds after Postfix has accepted and queued the message. [root@sbh16 ~]# dovecot -n # 2.0.beta5: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl dotlock passdb { args = /usr/local/etc/dovecot.passwd driver = passwd-file } passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/postfix/sbh16-cert.pem ssl_key = </etc/postfix/sbh16-key.pem userdb { driver = passwd } [root@sbh16 ~]# Excerpt from postconf -n smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2