OOPS!
Excuse my misdirected post of this... Stupid entourage doesn't automatically
respond to where it came from for some reason, so I have to manually select
a destination each time, and well, I picked the wrong courier mail list
address!
Sam Varshavchik scribbled something like:
I copied the mailboxes to the new server using rsync (after that I only
changed the UID/GID of the files). If a user is fetching mail via pop3
and leaves the messages on the server, ALL messages (even those which
are in the cur directory of the Maildir) get again delivered to the
client (vie pop3) after the transfer to the new server.
This is saved in the courierpop3dsizelist file, which should've been copied.
You should be copying everything in the Maildir directory, not just the
message files themselves in new and cur.
If maybe he is coming from an older version of courier-imap, then those
files didn¹t exist. That was the case for me when upgrading from courier 39
to 50... Those files didn¹t exist, and such all clients who left mails on
the server after POP, had to get them all again after the switch.
Its a one time shot, as I gathered from the UPGRADING documentation, and
shouldn¹t happen again unless you delete those special new files.
2 messages in net.sourceforge.lists.courier-users[courier-users] Re: Migrating courier...
