I tried to disable courier-pop3 today in favour of dovecot pop3.
Prior to that I ran:
find /home -maxdepth 1 -type d | xargs --replace
/usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive --convert
{}
( /home is hashed two levels deep: /home/a/a/aanton/Maildir/ )
After that,
On Thu, 2007-08-09 at 15:19 +0200, Ralf Hildebrandt wrote:
I tried to disable courier-pop3 today in favour of dovecot pop3.
Prior to that I ran:
find /home -maxdepth 1 -type d | xargs --replace
/usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive
--convert {}
( /home
* Timo Sirainen [EMAIL PROTECTED]:
If you had run Dovecot as IMAP server, then it wasn't such a great idea
to run the migration, because it recreates dovecot-uidlist files trying
to make them compatible with Courier's POP3 uidlist file.
Oops.
Creating dovecot-uidlist then caused the
On Thu, 2007-08-09 at 15:35 +0200, Ralf Hildebrandt wrote:
Creating dovecot-uidlist then caused the UIDVALIDITY to change, which
causes IMAP clients to redownload all messages, and as you can see
Dovecot doesn't handle UIDVALIDITY changes all that nicely. v1.1 does a
better job with it
* Timo Sirainen [EMAIL PROTECTED]:
Well, what you just did probably did that. It just caused IMAP users to
download the mails again, but that's more transparent to users because
it doesn't create duplicates.
OK
I did think about adding the possibility of storing POP3 UIDLs to a
separate
