Thank you very much for pointing this out .... the only thing i'd like also to do is to teach my user to download mail from mydomain.com forgetting mydomain.net so the first month i'd like to copy every mail from mydomain.net to mydomain.com (so that when a user reply to a message the sender sees the new mail address) and from the second month i'll close the mydomain.net domain accounts manteining only the alias.
How can copy (or move) all mail from one domain to another one ?? Il giorno 30/dic/2009, alle ore 00.25, Sam Varshavchik ha scritto: > Federico Baraldi writes: > >> I'm quite courious .... so can i have all four descriptions ?? >> My problem is that for an administrative error i'm not able to renew >> mydomain.net (valid until 30-06-2010) so i registered mydomain.com and i'd >> like that all mailbox >> as name.surn...@mydomain.net were redirected to name.surn...@mydomain.com. > > That would be something else entirely. "Forward" generally means doing > something that involves forwarding the mail to another server, which is not > the case here. This is why it's always best to explain exactly what you're > trying to accomplish. > >> My user have been told to switch from mydomain.net to mydomain.com and to >> advise all possible sender .... we have 6 months ti perform the migration !! >> I've added mydomain.com to hosteddomains and i've created all >> name.surn...@mydomain.com mailboxes .... but i don't know which solution is >> the best .... perhaps both #2 and #3. > > You should not have to individually create new mailboxes immediately. The > makehosteddomains man page gives you a direct example of what you need to do: > > Each domain can optionally be followed by a single tab character, in > order to specify an alias for a domain, for example: > > domain.com > mail.domain.com<TAB>domain.com > example.com<TAB>domain.com > > First, we list the domain "domain.com" as a hosted domain. Then, we > also list the domain "mail.domain.com", which is an alias for > domain.com. The Courier mail server will take any address of the form > <addr...@mail.domain.com>, rewrite it as <addr...@domain.com>, and > attempt to deliver the mail to a local mailbox for that name. The third > entry does the same for "example.com"; mail addressed to > <addr...@example.com> is delivered to the local mailbox > <addr...@domain.com>. > > In your case, your hosteddomains file should contain: > > mydomain.net > mydomain.com<tab>mydomain.net > > No changes to the names of accounts, for now. Now, either u...@mydomain.net > or u...@mydomain.com will end up being delivered to your existing > u...@mydomain.net mailbox. This only affects actual mail delivery, the > headers, if any, in the messages remain unchanged. Mail servers generally do > not rewrite mail headers. Mail servers use message envelope sender and > recipient addresses, which are separate from the contents of any headers, > which, from the mail server's perspective, are for informative purposes only. > > At some point, though, you will have to flip this around, create a matching > u...@mydomain.com account to replace each existing u...@mydomain.net address, > then switch the domains in the hosteddomains file as well. -- Federico Baraldi GPG FP: 6907 438C 403E C896 5D67 75FD 9E17 7BA6 E975 5C08 ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
