Re: doveconf error upon boot up

2018-10-31 Thread Stroller
I've just started getting this error on Gentoo Linux.

I've been running dovecot-2.3.2.1 for some time and didn't notice it. I 
recently updated glibc from 2.26-r7 to 2.27-r6 and dovecot was hanging on 
startup.

Recompiling dovecot fixed the hang, but now I'm seeing the same error message 
as below.

Stroller

(please CC me on replies)


On 4/10/18, Jerry  wrote:
> 
> Error message upon boot up:
> 
> doveconf: error: t_readlink(/var/run/dovecot/dovecot.conf) failed:
> readlink() failed: No such file or directory
> 
> Starting dovecot.
> 
> Dovecot appears to start correctly



Re: Disabling index files?

2017-12-06 Thread Stroller

> On 5 Dec 2017, at 15:32, Gregory Finch <gfi...@ldmltd.ca> wrote:
>> 
>> How do I disable the index files, please? 
>> … 
>> 
> 
> from https://wiki2.dovecot.org/MailLocation#Index_files
> 
> add :INDEX=MEMORY to your mail_location line, ie:
> 
> mail_location = maildir:~/Maildir:INDEX=MEMORY

Many thanks!

That works perfectly.

Stroller.



Disabling index files?

2017-12-05 Thread Stroller
The wiki says:

> Each mailbox has its own separate index files. **If the index files are 
> disabled**, the same structures are still kept in the memory, except cache 
> file is disabled completely (because the client probably won't fetch the same 
> data twice within a connection). [1]

I tend to grep my maildirs quite often, and use the output to cp emails to 
other folders, so it's annoying when the dovecot.index.cache files show up in 
the results.

How do I disable the index files, please? 

My mail server is hardly loaded, so I don't think it'll be a problem to keep 
the caching in memory.

I can find `mailbox_list_index = no` in /etc/dovecot/conf.d/10-mail.conf but 
this seems to be enabled by default, and it makes no difference when I enable 
it explicitly - deleted dovecot.index.cache are recreated when Dovecot is 
restarted. The setting `mbox_min_index_size` tends to suggests it's only for 
mbox files, not maildirs?

Thanks in advance for any help you can offer,

Stroller.





[1] https://wiki.dovecot.org/IndexFiles




Re: Migrating maildirs - Courier to Dovecot

2017-09-21 Thread Stroller

> On 22 Sep 2017, at 00:15, Adi Pircalabu <a...@ddns.com.au> wrote:
> 
> Using rsync should be fine, I've done it myself recently several times. What 
> you need to consider:
> 1. The downtime required during the final incremental transfer.
> 2. If you're using the same uid/gid on the destination server make sure you 
> preserve them when transferring the data across.
> 3. To avoid duplicate messages in the destination you *must* use --delete 
> rsync switch for the incremental transfers.
> 
> Important: I'm assuming you're using virtual mailboxes under the same uid/gid.
> 
> Suggested mandatory steps, ymmv:
> 1. Configure Dovecot in the destination to use Maildir and test everything: 
> logging, SSL, authentication, mail delivery and so on. If you have 
> Courier-IMAP specific configuration, e.g. folders that are being 
> automatically created/subscribed upon the first login, replicate it and test 
> it on the Dovecot server as well.
> 2. Do the initial data transfer using "-avz --numeric-ids" and see if you're 
> happy with the result in the destination.
> 3. Run several incrementals adding "--delete" switch, followed by 
> courier-dovecot-migrate.pl *executed as the mail user* to get a ballpark 
> figure for the estimated outage window.
> 4. Test few mailboxes post-migration and compare the results with the source 
> server.
> 5. On Day D, stop Courier-IMAP and Dovecot services on both servers to 
> prevent any mailbox changes and run the last incremental, sanity checks, IP 
> reconfiguration if Dovecot is the drop-in replacement, start Dovecot, another 
> round of sanity checks, check the logs and so on. Here you're already at the 
> point of no return :)

This is all more or less as I hoped or planned it, although you have mentioned 
some details that I will now be sure not to overlook.

Many thanks.

Stroller.


Migrating maildirs - Courier to Dovecot

2017-09-21 Thread Stroller
I apologise, because I'm sure this subject has been done to death, but I want 
to migrate from Courier to Dovecot.

I think my main question is whether there's any reason I shouldn't just rsync 
the maildirs across from the old mail server to the new one? 

There aren't many clients using this server, so I don't care if clients have to 
redownload all their messages (in fact, I expect they'll probably end up doing 
so anyway).

I'd like to preserve read/unread status of each message, but can't think of 
anything else important.

It doesn't matter if there's a few hours of downtime, but I thought to use 
rsync because I figured I copy the maildirs a day or two ahead of time, and 
then a sync immediately before going live will be quicker.

Using imapsync [1] looks pretty good, and I'm happy to use that if it'll be 
"cleaner" or help Dovecot to create its hierarchy more neatly.

It looks like Courier creates a courierimapuiddb, courierimapkeywords and 
courierimapacl in each folder - can I not just delete these, and hand Dovecot a 
bunch of maildir directories and files to reindex for itself?

There are probably only a few hundred thousand messages on the server, a few GB 
worth, although some of them are many years old.

Some of the messages on the old server have the wrong "received" date on them, 
having the wrong file creation / modification date on the server's filesystem, 
having been copied there previously (years ago) without using cp's --archive 
flag. I've always thought I should one day write a script to fix this, perhaps 
using mboxgrep.

Thanks in advance for any of your thoughts,

Stroller.





[1] https://wiki2.dovecot.org/Migration#IMAP_.3C-.3E_IMAP_copying