- dovecot - dovecot.org

[Dovecot] Per-user flags/indexes for shared mailboxes
by Timo Sirainen 03 Apr '12

03 Apr '12

The attached patch adds support for doing e.g.: namespace { type = public prefix = Public/ location = mdbox:/var/lib/public/mdbox:INDEXPVT=~/mdbox/public list = yes } So the private flags are stored in indexes under ~/mdbox/public/, while the shared flags are stored under /var/lib/public/mdbox/. The patch currently hardcodes the shared flags as only MAIL_SEEN. I'm not really sure what would be the best place to configure which flags are private. Perhaps a per-namespace default, but how to configure it per-mailbox? Also per-user keywords aren't currently supported. And it's a little bit annoying that each private flag update must increase the shared modseq for the message, but that can't really be helped. (Alternative would be for each user to have their own private modseqs, which could get difficult.) I'll probably commit this to v2.1 after some more testing.

1 0

[Dovecot] dsync redesign
by Timo Sirainen 03 Apr '12

03 Apr '12

In case anyone is interested in reading (and maybe helping!) with a dsync redesign that's intended to fix all of its current problems, here are some possibly incoherent ramblings about it: http://dovecot.org/tmp/dsync-redesign.txt and even if you don't understand that, here's another document disguising as an algorithm class problem :) If anyone has thoughts on how to solve it, would be great: http://dovecot.org/tmp/dsync-redesign-problem.txt It only deals with saving new messages, not expunges/flag changes/etc, but those should be much simpler.

9 17

[Dovecot] Dovecot 1.2.9. next_uid was lowered
by Müller Lukas 03 Apr '12

03 Apr '12

Hi There A while ago I posted here about a crash of dovecot, that had to do with nfs and was quite certainly due to bad luck. But still one problem persists: We have a Mailbox, that is accessed from multiple users using IMAP. Occasionally all the Emails in the mailbox seem to be missing, when accessing the Mailbox through IMAP, although they're still there on the server. This seems to happen, if the users are accessing the Mailbox on Server1 and at the same time an email gets delivered to the mailbox on server2. Since it happens quite seldom, there must be other conditions or circumstances that have to be met for the problem to occur. Unfortunately I don't know which. Shortly after the mail gets delivered on server2, I get the following errors on server1: mail01 dovecot: IMAP(akzidenz(a)triner.ch): fdatasync(/data/vmail/example.com/user/dovecot-uidlist) failed: Input/output error mail01 dovecot: IMAP(akzidenz(a)triner.ch): /data/vmail/example.com/user/dovecot-uidlist: next_uid was lowered (2143 -> 2142, hdr=2142) The new mail is than missing in the uidlist and as long as no new mail arrives all folders of the mailbox appear to be empty. If a new mail arrives, it will get the uid that should have been given to the pervious mail (the one that caused the error). The previous mail still won't be listed in the uidlist, but everything works as expected. Best regards Lukas Müller Systems Engineer _______________________________________________ NEWMEDIA Südostschweiz Newmedia AG http://www.newmedia.ch<http://www.newmedia.ch/> _______________________________________________ TYPO3 & Drupal - Wir wissen wie. Ihre professionelle Web Agentur in Chur, Ilanz, Glarus und Zürich.

2 1

[Dovecot] setting up ldap for sasl
by jeff donovan 02 Apr '12

02 Apr '12

Greetings im new to the list dovecot --version 2.0.13 ubuntu 11.10 i want to use dovecot to authenticate my ldap users. My local users can authenticate and send email. Using postfix sasl/tls dovecot pam. I have read many docs/tutorials, which all have a plethora of options and information. my file structure is different than most of the documentation. I have ../etc/dovecot.conf which points to. !include_try /usr/share/dovecot/protocols.d/*.protocol !include conf.d/*.conf !include_try local.conf which leads me to /etc/dovecot/conf.d, which is full of config files. All were traditionally located in dovecot.conf in previous versions. im using PAM to authenticate my local system users. I have read that could adjust PAM, to use LDAP. How do I configure dovecot to keep using pam for local users and ldap for remote ? Do i just add the passdb lines dovecot.conf: passdb ldap { args = /etc/dovecot-ldap.conf } userdb prefetch { } # The userdb below is used only by deliver. userdb ldap { args = /etc/dovecot-ldap.conf } dovecot-ldap.conf: pass_attrs = uid=user,userPassword=password, homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid # For deliver: user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid any assistance would be helpful. -j

1 2

[Dovecot] Dsync automation
by Jitendra Bhaskar 02 Apr '12

02 Apr '12

Hi, I am using dovecot-2.1.3 on centos 5.7. Its running fine. I have two systems for mail server one is for backup. Currently I am running rsync daily. But I want to use dsync. I went through all the http://wiki2.dovecot.org/Tools/Dsync and http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.htmlbut I couldn't understood how to automatize dsync. Can anybody give me any idea ho to do it ? -- * Thanks & Regards * *Jitendra Kumar Bhaskar* Cell:- +91 7306311531 +91 8102997821

2 1

Re: [Dovecot] Mail migration troubles
by Spyros Tsiolis 02 Apr '12

02 Apr '12

I have a suspicion that, as usual, no one is going to answer my message. Because of the fact that this is a call for help and no-one ever bothers, I 'll just have to re-phrase my question : Here's what I found on the dovecot wiki : imapsync Here's an example of how to run imapsync for a single user: imapsync --syncinternaldates \ --host1 192.168.1.57 --authmech1 LOGIN --user1 leah(a)example.com --password1 secret \ --host2 127.0.0.1 --authmech2 LOGIN --user2 leah(a)example.com --password2 secret It is quite easy to script this for a number of users, assuming you have their passwords. Even if you do not, imapsync also supports logging in as an admin user that has the ability to copy message for sub users, and a variety of other authentication options. Is the above what I need if I migrate mailboxes FROM dovecot TO dovecot ? E.g. in my example, I only copy mailboxes from an old "user(a)domainA.gr" to "user(a)domainB.gr". Is the above all I need ? Is there a native dovecot tool for this or should I just use imapsync ? Thank you again, s. ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis ----- Original Message ----- > From: Spyros Tsiolis <stsiol(a)yahoo.co.uk> > To: Spyros Tsiolis <stsiol(a)yahoo.co.uk> > Cc: > Sent: Monday, 2 April 2012, 11:24 > Subject: Re: [Dovecot] Mail migration troubles > > Hello again, > > Well, it seems I have trouble with the migration after all. > After the migration and eventhough all folders and messages > are on their respective places, any new mail users get > inside their mailbox cannot be dragged-and-dropped to > their respective folders. > > So, if a user has a folder with my name on it and I send > him an e-mail, the user will try to drag-and-drop that > message to the folder with my name, but the message won't > move. > > Any gurus out there on this ? > Any help would be greatly appreciated. > > spyros > > > > ---- > "I merely function as a channel that filters > music through the chaos of noise" > - Vangelis >

4 9

[Dovecot] strike my last
by Spyros Tsiolis 01 Apr '12

01 Apr '12

strike my last, looks like its a thunderbird issue Apologies... s. ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

1 0

[Dovecot] Problem compiling dovecot-antispam on Ubuntu 11.10 using Doveot 2.0.13
by Guillaume Hilt 31 Mar '12

31 Mar '12

Hello, Last dovecot available version on Ubuntu 11.10 AMD64 is dovecot 2.0.13. dovecot-antispam package is compiled for dovecot 2.0.15. So, i'm trying to compile a new dovecot antispam plugin. I followed dovecot wiki but i'm running into this error : Successfully compiled dspam.c (plugin). mailbox.c: In function 'antispam_save_begin': mailbox.c:138:12: error: 'struct mail_save_context' has no member named 'copying_via_save' mailbox.c: In function 'antispam_save_finish': mailbox.c:174:12: error: 'struct mail_save_context' has no member named 'copying_via_save' Failed to compile mailbox.c (plugin)! Any hint please ? Regards, -- Guillaume Hilt

2 2

[Dovecot] Problem managing mbox
by PSTM 30 Mar '12

30 Mar '12

Hello, I have a problem with dovecot. seems that do not erase mail that mail client request to be erased. And I have this errors: > Error: Next message unexpectedly corrupted in mbox file Info: > dovecot-2.1.1-2.0.cf.fc16.i686 > root 5979 0.0 0.1 3208 1260 ? Ss 20:18 0:00 > /usr/sbin/dovecot -F > dovenull 5985 0.0 0.2 7060 2280 ? S 20:18 0:00 > dovecot/imap-login > vmail 5988 0.0 0.1 7888 1848 ? S 20:18 0:00 > dovecot/imap permissions on mail dir: > total 4 > drwxr-xr-x 9 vmail mail 4096 ene 21 21:43 vmail Any suggestion? Regards, -- -- http://www.0pc.eu/

3 2

[Dovecot] Proxying Authentication on both sides
by Andy Dills 30 Mar '12

30 Mar '12

I've recently set up a director proxy environment on my test servers, with the intention of deploying on our cluster soon. One thing I found confusing in the proxying documentation [1] was the first bit about their being two ways to do the authentication...either you have the proxy forward the auth to the real server for authentication, or you have the proxy authenticate it and then login to the real server with a master password. Well, we use /bin/checkpassword authentication which hooks into a variety of subsytems for various specific customer needs, and sometimes we need to know the username AND password of the user in order to determine their home directory information. So, using a master password (which requires the back-end server not getting the user password) is out. However, when we have the front-end server do a static director proxy, the problem is that authentication failures are logged on the back-end server with a source IP of the proxy, and no authentication failure with the client IP address is logged on the proxy. So, fail2ban (which is a MUST these days, at least for us) will not be able to properly filter out the brute force attackers. My solution was an alternative: I authenticate with our /bin/checkpassword on the proxy, which authenticates the user and only at that point returns the proxy=y nopassword=y switch to proxy the connection and forward the authentication. As a result, we get logs on the proxy for failed attempts, and the full username and password is supplied to the back-end server for proper processing. Food for thought in case anybody else is implementing this. Thanks, Andy [1] http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---

2 3