From: ska on
pirovano wrote:
> ah, i see!
>
> how to do it with sendmail, i don't know.
> after all, splitting a @example.net into 2 servers is a bad idea in my
> opinion.
>
> but, to make this work, the administrators must accept
> user1(a)server1.example.net and user2(a)server2.example.net,
> then you can work with local-host-names and virtusertable as you
> described before.

Well, first follow the advice of Henning, then if the Exchange
persistently does not accept your messages, try domaintable.

server1.example.net example.net
server2.example.net example.net

keep your virtuser table

user(a)example.net user(a)server1.example.net

IMHO sendmail should map the domains _after_ selecting the destination
host.
http://www.sendmail.org/m4/features.html#domaintable

-ska
From: John Nemeth on
Frank Luo (frank.luoy(a)gmail.com) wrote:
: On Jul 12, 12:31=A0pm, pirovano <pirov...(a)pirovano.ch> wrote:
: > On 12 Jul., 18:18, pirovano <pirov...(a)pirovano.ch> wrote:
: >
: > > Hello,
: >
: > > in order for @domain.com beeing passed through virtusertable, it must
: > > be added to local-host-names.
: >
: > > another option may be putting the domain into relay-domains, and make
: > > use of mailertable and access.
: >
: > > but i believe in your case local-host-names and virtusertable is the
: > > easyer way.
: >
: > > Regards,
: >
: > > lorenzo
: >
: > if us...(a)domain.com must not be changed, then put
: >
: > domain.com =A0 =A0 =A0 =A0smtp:[server1.domain.com]
: >
: > into mailertable, and
: >
: > domain.com
: >
: > into relay-domains.
: >
: > like this, anyth...(a)domain.com will be passed unchanged to
: > server1.domain.com.
: >
: > to allow certain e-mail aliases only, put
: >
: > To:us...(a)domain.com =A0 RELAY
: > To:us...(a)domain.com =A0 RELAY
: > To:domain.com =A0 =A0 =A0 =A0 =A0 =A0 =A0REJECT
: >
: > into access.

: that worked before we have to have to server2 to take care portion of
: users. So some users go to server1 and some go to server2. Also both
: the mailertable and relay are set up like what you said here already.
: It seems that virtuserable overrules them.

Then use the LDAP_ROUTING method that anfi@ suggested.