|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Ari Gordon-Schlosberg (regs
nebcorp.com)Date: Thu Feb 01 2001 - 15:03:38 CST
[Nicolaj Ottsen <no
tjantik.dk>]
> I know it is here somewhere but I can't find it.
>
> I want to be able to "reroute" one domain to another, so that domainA.com
> becomes domainB.com.
>
> Could someone please give en example I can't seem to figure it out.
Use virtual or canonical. The difference between the two is that if use
canonical, mail sent to user
domiana.com wil be delivered to
user
domainb.com and will appear to originally posted to user
domainb.com.
Using, virtual, the mail will be delivered to user
domainb.com but will
apear to be originally posted to user
domaina.com
USING CANONICAL
If you want mail to domaina.com to actually be re-written to
doimanb.com, use canonical:
(from the canonical man page)
The format of the canonical table is as follows, mappings
being tried in the order as listed in this manual page:
blanks and comments
Blank lines are ignored, as are lines beginning
with `#'.
user
domain address
user
domain is replaced by address. This form has
the highest precedence.
This form useful to clean up addresses produced by
legacy mail systems. It can also be used to pro
duce Firstname.Lastname style addresses, but see
below for a simpler solution.
user address
user
site is replaced by address when site is equal
to $myorigin, when site is listed in $mydestina
tion, or when it is listed in $inet_interfaces.
This form is useful for replacing login names by
Firstname.Lastname.
domain address
Every address in domain is replaced by address.
This form has the lowest precedence.
In all the above forms, when address has the form
other
domain, the result is the same user in otherdomain.
So you would want canonical table that looks this:
# rewrite mail to user
domaina.com to user
domainb.com
domaina.com
domainb.com
USING VIRTUAL
To just redirect the mail to domainb.com, use virtual:
(from the virtual man page)
The format of the virtual table is as follows, mappings
being tried in the order as listed in this manual page:
blanks and comments
Blank lines are ignored, as are lines beginning
with `#'.
user
domain address, address, ...
Mail for user
domain is redirected to address.
This form has the highest precedence.
user address, address, ...
Mail for user
site is redirected to address when
site is equal to $myorigin, when site is listed in
$mydestination, or when it is listed in
$inet_interfaces.
This functionality overlaps with functionality of
the local alias(5) database. The difference is that
virtual mapping can be applied to non-local
addresses.
domain address, address, ...
Mail for any user in domain is redirected to
address. This form has the lowest precedence.
In all the above forms, when address has the form
other
domain, the result is the same user in otherdomain. This
works for the first address in the expansion only.
So you would want a virtual table that looks like this:
# Set the domain as virtual (the second value on that first line
# can literally be anything
domaina.com somethingsomething
# redirect mail from domaina to domainb
domaina.com
domainb.com
-- Ari there is no spoon ------------------------------------------------------------------------- http://www.nebcorp.com/~regs/pgp for PGP public key
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]