- dovecot - dovecot.org

[Dovecot] Is it possible to migrating mail to dovecot using imapc?
by Dr Josef Karthauser 04 Apr '12

04 Apr '12

I'm excited to hear that dovecot now supports imap as a mailbox type. I've got a mailbox over on another imap server, which I want to migrate to dovecot. I was wondering whether I could use 'doveadm backup' to setup a two way synchronisation process between the old imap mailbox and the new dovecot mailbox. That way I can do the migration, and can coordinate the mail clients changing where they pick up their email from later. But, I can't find much documentation on imapc, other than it exists. Is this kind of move possible now? Would someone mind giving me some hints as to how to make it work please? Thanks :), Joe

2 9

[Dovecot] dovecot 2.1 breaks FTS + pre-auth?
by dm-list-email-dovecot＠scs.stanford.edu 04 Apr '12

04 Apr '12

Hi. I use dovecot in the simplest possible way, as an IMAP server in pre-auth mode over ssh or just locally over a unix-domain socket (e.g., with offlineimap, which runs much faster using dovecot for the local message store). Ideally I would like to avoid running any extra daemons or setting up anything as root. Until recently, this has worked fine by just setting the CONFIG_FILE environment variable to something in my home directory. Here is my configuration: $ export CONFIG_FILE=$HOME/etc/dovecot.conf $ dovecot -n # 2.1.3: /home/dm/etc/dovecot.conf # OS: Linux 3.2.13-1-ARCH x86_64 mail_location = maildir:~/Mail/inbox mail_plugins = " fts fts_squat" plugin { fts = squat fts_squat = partial=4 full=10 } doveconf: Error: ssl enabled, but ssl_cert not set doveconf: Fatal: Error in configuration file /home/dm/etc/dovecot.conf: ssl enabled, but ssl_cert not set Full text search used to work just fine with this configuration, and still does on a machine I have running dovecot 2.0.13. However, on the machine with 2.1, I get errors about /var/run/dovecot/index not existing. $ printf "a select INBOX\nb search text xyzzy\nc logout\n" \ | /usr/lib/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE] Logged in as dm imap(dm): Error: net_connect_unix(/var/run/dovecot/indexer) failed: No such file or directory ... Needless to say, no dovecot.index.search or dovecot.index.search.uids file is created after this error. While I can't write /var/run/dovecot, this is not a permission issue. For example, adding base_dir=/home/dm (my home directory) to the configuration file yields the same error for /home/dm/indexer. I'm guessing something has changed where imap requires an indexer daemon and doesn't launch it in pre-auth mode any more, but I can't find anything about this in the documentation. In short, if anyone can tell me how to use FTS in conjunction with pre-auth mode or point me to a working example, I would appreciate it.

2 1

[Dovecot] 2.1.3: doveadm mailbox delete lost the -s option
by Micah Anderson 04 Apr '12

04 Apr '12

Looks like the recently added -s (for unsubscribing) option to doveadm mailbox delete went missing: root@vireo# /usr/bin/doveadm mailbox delete -u micahtest -s restored delete: invalid option -- 's' doveadm mailbox delete [-u <user>|-A] [-S <socket_path>] [-s] <mailbox> [...] although the option still is shown as valid :) micah --

2 1

[Dovecot] Dovecot stones
by Timo Sirainen 03 Apr '12

03 Apr '12

For the last few days I've been thinking about my company and what it really should do, and as much as the current plan seems reasonable, I think in good conscience I really can't help but to bring up an alternative plan: The support for Dovecot is quite good already, but wouldn't it be better if it was GUARANTEED that your email server was ALWAYS working with zero downtime or other problems? After some thinking, planning and consulting with my spiritual guides I realized I really should just go ahead and do it: From now on you can buy blessed Dovecot stones (http://www.dovecot.org/tmp/stone1.jpg) which are guaranteed to keep your email server running. I don't think there's really any further reason for me to provide commercial support. Probably the whole Dovecot mailing list will be pretty much useless after this as well, so I might as well stop posting there. If you have any problems, you'll just buy a Dovecot stone and the problem will go away. If for any reason that doesn't work, it means that your problem is more difficult than most and you need to buy a few more stones. Please remember that each shipment may take up to 3 weeks to reach you, so get your stones early and in sufficient quantities. A small email server will be happy enough with a single small Dovecot stone, but the more users you have the more stones you'll likely need. This is because most people are rather unhappy with their lives, and they project their negative energies towards their surroundings, including their email servers. To overcome this negative energy you need to have a counterbalancing positive energy, which the Dovecot stones will provide you. The Dovecot stones are hand painted from the finest materials available to the sister of the author of Dovecot that she could find in the local shops. Each stone contains such love and dedication towards the well being of Dovecot that you will shed tears when you lay your eyes upon their physical being. The images provided here unfortunately don't do justice to them. http://www.dovecot.org/tmp/stone2.jpg - This is how i keep my home desktop running all day every day. I have NEVER broken a single hard drive in my life. I don't even bother to keep backups, because I KNOW it is useless for me. A small Dovecot stone can be bought for 10 euros, a medium sized stone for 100 euros and a large stone for 500 euros. Each large stone can usually handle around 1000-2000 users before you need to buy more. If you have millions of users we'll need to find you a larger rock from my parents' backyard. There are only a limited number of such rocks available (we disposed of most of them to our neighbors' yards years ago), so their prices need to be negotiated in advance.

12 12

[Dovecot] Mail migration troubles
by Spyros Tsiolis 03 Apr '12

03 Apr '12

Hello all, OK, I would really appreciate your help on this. I managed to do a pretty straight-forward and flawless migration on dovecot from one domain to another. However, I have this nagging problem with most of the thunderbird MTAs. When I try to delete some "test" messages I sent to make sure that everything works, it comes back with the following message on the bottom of the Thunderbird window : "The current operation on InBox did not succeed. The mail server for account "Account(a)bloomingdomain.gr" responded [TRYCREATE] mailbox doesn't exist : Trash" Now, I know it has to do something with automatically creating a trash folder. But don't know anything more. Could someone shed some light on this ? Dovecot v1.2.15 AFAIK CentOS 5.5 x86 (32-bit) other stuff On Clients : Thunderbird v11.0.1 (XP Pro / 32-bit) s. ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

3 4

[Dovecot] imapdir still a configuration option?
by Kurt Mosiejczuk 03 Apr '12

03 Apr '12

I've been looking at moving an old IMAPdir-based solution to dovecot. I came across references that dovecot (to my pleasant surprise) added imapdir support in 1.1. However, in trying 2.0.13 (from an OpenBSD package) things start okay, but I see in the logs: "Initialization failed: Initializing mail storage from mail_location setting failed: Unknown mail storage driver imapdir" Poking around in the sources, I still see lots of references to imapdir, but see very little in the documentation. Is IMAPdir still supported in 2.0.x (or even 2.1.x)? I'd prefer not to have to migrate users via renaming, especially since they like the IMAPdir layout for their own searching. --Kurt

2 2

[Dovecot] Connection queue full on dovecot 2.0.13
by Giovanni Mancuso 03 Apr '12

03 Apr '12

Hi, i have a problem with dovecot 2.0.13. I have one dovecot in Front-end that has only: passdb { driver = static args = proxy=y host=10.0.0.6 nopassword=y } In Back-end i have one dovecot that does auth and exports imap/pop3 ports. In dovecot's log of Front-end i see: /Apr 02 14:33:34 imap-login: Info: proxy(//user(a)example.com/ <mailto:amministrazionevendite@pec.gmatica.it>/): started proxying to 10.0.0.6:143: user=<//user(a)example.com/ <mailto:amministrazionevendite@pec.gmatica.it>/>, method=PLAIN, rip=//xx.xx.xx.xx//, lip=xx.xx.xx.xx, TLS Apr 02 14:34:36 imap-login: Info: Disconnected: *Connection queue full *(auth failed, 1 attempts): user=<//user(a)example.com/ <mailto:amministrazionevendite@pec.gmatica.it>/>, method=PLAIN, rip=//xx.xx.xx.xx//, lip=//xx.xx.xx.xx//, TLS/ I see this wiki page: http://wiki2.dovecot.org/LoginProcess but i read: It works by using a number of long running login processes, each handling a number of connections. This loses much of the security benefits of the login process design, because in case of a security hole (in Dovecot or SSL library) the attacker is now able to see other users logging in and steal their passwords, read their mails, etc. Is there another way? Thanks

2 1

[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