3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Migrating to new ...
FromSent OnAttachments
Rich DuzenburyDec 6, 2003 12:23 am 
Gordon MessmerDec 6, 2003 12:14 pm 
Rich DuzenburyDec 8, 2003 1:15 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Migrating to new server slowlyActions...
From:Gordon Messmer (yiny@eburg.com)
Date:Dec 6, 2003 12:14:39 pm
List:net.sourceforge.lists.courier-users

Rich Duzenbury wrote:

I think I can set up a .qmail file to forward any new mail that appears for my id at the current server over to the new server.

Good plan.

First problem: sqwebmail shows my email address as rd@newserver.theduz.com, not rd@theduz.com. newserver is not listed as an mx (yet). Seems like that will mess up replies from folks that I send e-mail to from that server.

Look at the "defaultdomain" section in 'man courier'. It won't mess up replies (a domain doesn't need an record if the A resolves to the proper place), but it's probably not what you want. Once you fix "defaultdomain", remove the sqwebmail preferences file from your Maildir.

Second problem: I have more than one user in the domain. If I migrate just myself, how should I set up courier's locals file? Other users of my domain are still on the old server...

Your .qmail file should direct mail to rd@newserver.theduz.com. That host should only have newserver.theduz.com in its locals file. Later, as the last step of your transition, you'll change your MX record for theduz.com to point to newserver, and add theduz.com to it's locals file.

Should I be doing something with esmtproutes, perhaps?

Nope. As long as theduz.com isn't in locals, normal routing rules will get mail where it's supposed to go.