Brian Candler wrote:
On Sat, Feb 25, 2006 at 09:04:42PM -0500, David J. Greenberger wrote:
Nope, because I migrated from courier-imap to dovecot on the old system
several months ago. Everything worked fine, so I never bothered
investigating what I could safely delete. (But now that you've
confirmed which files I can delete, I might as well go right ahead and
delete them.)
So, IIUC:
1. you migrated from courier-imap to dovecot on the old system a while ago.
2. therefore, the old system was running dovecot up until the migration.
3. Then you migrated from dovecot on the old system, to courier-imap on the
new system.
Sorry, I misspoke above. I meant to say that I migrated /to/
courier-imap /from/ dovecot on the old system several months ago.
So what you said originally - that this was a straightforward courier-imap
to courier-imap migration - was wrong.
Nope, it was a straightforward courier-imap to courier-imap migration,
with the remnants of a previous dovecot installation still present.
I personally can't help you, having very little experience of dovecot
(tested it a few years ago, found it unsuitable for my ISP application at
that time). Maybe there's someone else on this list who can help you with a
dovecot to courier-imap migration.
As I said, I solved the problem with a cp -a. All is working fine now.
David
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
