- dovecot - dovecot.org

[Dovecot] Dove LDA vs Exim LDA
by Kumar Shantanu 02 Dec '13

02 Dec '13

Hello All, I have built up my email server with exim + dovecot + clamv/spamassasin. I am using exim as LDA(local delivery agent). I was reading about using dovecot as LDA but I couldn't find why should I use it? Now, I am looking expert advice on "Why should I use dovecot LDA" ? Is there any benefit in terms of functionality or performance ? Any advice/suggestion/feedbacks welcome. Thanks Shantanu

5 5

[Dovecot] "[CANNOT] Mailbox GUIDs are not permanent without index files" when trying to delete folder
by Nissim Etrog 02 Dec '13

02 Dec '13

Hello, Dovecot 2.0.9 on Red Hat Enterprise Linux Server release 6.4 (Santiago) location is set to : mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=MEMORY Index is set to memory due to permissions problems when using disk index. Everything works, even rename folder, but when trying to delete folder, using any mail client, it fails with: "[CANNOT] Mailbox GUIDs are not permanent without index files". Why ? Regards,Nissim Etrog

1 0

[Dovecot] doveadm table formatter: hidden titles may cause misaligned headers
by Julian Reich 02 Dec '13

02 Dec '13

Hello, I recently noticed a small bug in the doveadm table formatter: hidden titles may cause the headers to be misaligned. The behavior in question was introduced by commit <http://hg.dovecot.org/dovecot-2.2/rev/210282ae46e1> and doveadm -f table quota get -A may be used to reproduce it. Most simple patch attached: it simply restores the old behavior, to some extent. Actually hiding those titles may be desired. Regards, Julian Reich

1 0

[Dovecot] dovecot-antispam plugin problem with multiple messages
by Richard Platel 29 Nov '13

29 Nov '13

Hi With dovecot 2.2.5, and dovecot-antispam built from a recent HEAD pull, when copying multiple messages to or from a Spam folder, the plugin sends multiple copies of the first message to the backend. I've tried this with the pipe and spool2dir backends. For example with the spool2dir backend, via IMAP doing A COPY 1:3 Spam yields 3 copies of message id 1 in the dir: dev:imap-8.1 rplatel@imap01:/var/run/dovecot_as_tmp$ sudo -u mail md5sum * 28ad0a215eb7ecbd3a814a8a334d85bf 00000000001385586164-rplatel(a)ff-dev.com-00001s 28ad0a215eb7ecbd3a814a8a334d85bf 00000000001385586164-rplatel(a)ff-dev.com-00002s 28ad0a215eb7ecbd3a814a8a334d85bf 00000000001385586164-rplatel(a)ff-dev.com-00003s I see the same behaviour with the pipe backend, the pipe program is invoked 3 times, but with the same message content.

1 1

[Dovecot] proxy_maybe & director incompatibility
by Trent Lloyd 29 Nov '13

29 Nov '13

Hi Folks, I spent quite some time yesterday understanding how proxy works along with the director. I came to the conclusion that proxy_maybe and director cannot be used together, but this isn’t a true incompatibility so much as caused by the way things are handled and the order they are processed in. The way proxy_maybe works is that it is processed by the auth provider once it gets the response from the passdb, it checks for proxy_maybe and then checks for the ‘host’ parameter and compares it to the local IP (this is always null at that stage, because director won’t add host until later). proxy_maybe is deleted and then if the IPs do not match (i.e. the connection should be proxied) it sets proxy. This result is returned from the auth provider and then piped into director, which adds the relevant ‘host’ parameter if ‘proxy’ is set. The problem here is that because proxy_maybe is processed before director, it is not possible to conditionally proxy when using director — only if host is also returned from passdb. The secondary problem is that director only adds host= if proxy is set (and the auth code generally assumes proxy/proxy_maybe/proxy_always are exclusive settings) — this logic would also need to change. You would also need some logic to add host only if host doesn’t already exist, to handle situations where proxies might come from both passdb and/or director. I am seeking to understand if there is any significant reason proxy_maybe is handled during the auth section, it would seem better to simply always set ‘proxy=yes’, and then optionally have proxy_maybe passed all the way through to the connection stage and then do the local host check there. This would solve my use case, and I cannot imagine what else it would break — but I am no expert on dovecot or other people’s use cases, so I am hoping for feedback from others on this and what else would need to be considered or why this would not work before I spent time trying to implement the change. Thanks, Trent Lloyd w: www.webinabox.net.au

2 1

[Dovecot] Dovecot's brittle configuration syntax
by Kai Hendry 29 Nov '13

29 Nov '13

Hi there, Whilst trying to come up with a minimal configuration for Dovecot: http://dabase.com/blog/Minimal_Dovecot/ I noticed the configuration syntax is a bit admin unfriendly. It's easy to get an infamous Error code 89. Is there any back story to the grammar or language this configuration is in? Kind regards,

2 1

Re: [Dovecot] Dovecot's brittle configuration syntax
by Joseph Tam 29 Nov '13

29 Nov '13

Kai Hendry <hendry(a)dabase.com> wrote: > Whilst trying to come up with a minimal configuration for Dovecot: > http://dabase.com/blog/Minimal_Dovecot/ I think your characterization of the complexity of dovecot configuration by simply counting configuration lines to get it working is off base. It's conceivable to have all the default values work for you and only specify those that differ from defaults (or configure your system to conform to defaults if you want to place the proverbial cart before the horse), but that doesn't make it less complex -- it just hides it. (See doveconf -a if you want to see what you're shorthanding). If you want minimal configuration fuss, you can try uw-imapd. Not a lot of knobs to twist on that thing, but you'll have to accept all its limitations as well. A well chosen set of defaults that works for most people is a good design decision, but I've seen plenty of different and oddball layouts (including the sneakernet post preceding this one) that requires a lot of flexibility, which necessarily requires a lot of configuration to express them. The sample configuration is verbose because it doubles as documentation: you can use it as a starting point and remove the parts you don't need, or start from the documentation and move forward. I agree, though, that the documentation needs an editorial overhaul -- it's a little bewildering to find what you need along with the contextual information. > I noticed the configuration syntax is a bit admin unfriendly. It's easy > to get an infamous Error code 89. > > Is there any back story to the grammar or language this configuration is > in? It appears to me to have grown organically, and maybe will need pruning some day. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: [Dovecot] Replication via sneakernet
by David Bishop 29 Nov '13

29 Nov '13

D'oh. Replied to Timo instead of to the list. Apologies! On Thu, Nov 28, 2013 at 1:07 PM, David Bishop <dovecot(a)dpe.lusars.net>wrote: > On Thu, Nov 28, 2013 at 1:02 AM, Timo Sirainen <tss(a)iki.fi> wrote: > >> On 28.11.2013, at 5.17, David Bishop <dovecot(a)dpe.lusars.net> wrote: >> >> > There are trams shuttling back and forth along this road (stopping at >> each >> > station), and adding a small box (such as a weatherproofed Raspberry Pi >> > with a wifi dongle) to transport files up and down the road is pretty >> > simple. >> >> But if you do it this way and you can keep a full copy of the shared mail >> storage on your Raspberry, that would be possible already with dsync I >> think. dsync supports quick incremental updates by keeping track of the >> previous state between the servers. This state is saved in a file, so you >> could keep a different state for each different dsynced server. >> > > Bravo for a solution that doesn't require a code change and doesn't seem > to require directly touching the spools! :) > > Reading the man page, it looks like only mirroring for people who happen > to be checking email at a given place (as well as people who have received > mail and the shared mailboxes) seems like a pretty simple thing to do. > Hurrah! > > Thank you, this is wonderful. > > And more questions... > > If I'm running a virtual mail domain, the user/pass I give is for the > virtual mail user, correct? And, in a virtual mail setup, do I specify > "username" or "username@domain"? > > Is there a window beyond which synchronization becomes more difficult? For > instance, if messages (or metadata updates, like "I deleted this message") > get parked overnight without updating, and in the morning (9 hours later), > the trams (one at a time) pull into range of wifi, there won't be > confusion, right? > >

2 1

[Dovecot] sendmail to postfix-dovecot
by Roger Berger 28 Nov '13

28 Nov '13

Hi, I am a newbie to postfix and dovecot so I hope you can help me. I have an old server running sendmail for many years now. On this server I have about 100 domains and 500 users. The users are named as myuser or myuser.dom. People use pop3 and imap for fetching reading their email. I've setup a new server with postfix and dovecot2 on freebsd and managed to get it all working with virtual users. However, now I found out that I overlooked something; People have to login with username(a)domain.tld<mailto:username@domain.tld> on the new server but only use their username on the old server. This means they all have to change their login credentials, which is not an option. Is it possible to do some scripting before authentication where the username is looked up in the database and the right domain is added to the account? If I understand right it is not possible to use system and virtual users together. Thanks, Roger

5 6

Re: [Dovecot] Permissions problems
by Joseph Tam 28 Nov '13

28 Nov '13

<md.benson(a)gmail.com> wrote: > Nov 24 17:34:27 proliant-1 dovecot: [ID 583609 mail.error] imap(mark): Error: > rename(/mpool/mail/mark/dovecot.index.log.newlock, > /mpool/mail/mark/dovecot.index.log) failed: Permission denied > ... > This is what the directory currently looks like: > > mark@proliant-1:~$ ls -la /mpool/mail > total 6 > drwxrwxrwx+ 3 root root 3 2013-11-24 17:17 . > drwxr-xr-x+ 5 root root 5 2013-11-24 13:50 .. > drwxrwxrwx+ 5 mark staff 9 2013-11-24 22:20 mark I'm think the "+" is the problem: you have, in the words of the manpage for ls, ... this character is a plus sign (+) character if a non-trivial ACL is associated with the file ... Try ls -alv /mpool/mail I don't use ACLs, so I can help you how to modify them. Joseph Tam <jtam.home(a)gmail.com>

1 0