Re: From Exchange to 2 separate MTA's

On Jan 16, 12:51 pm, Grant Taylor <gtay...@xxxxxxxxxxxxxxxxx> wrote:
You do not "have to" create entries for every user, but it is advisable
to ""Educate Sendmail on valid recipients in some way, be it /etc/access
entries or LDAP routing that interfaces with AD, or some form of
call-ahead, or something else. This way, your Sendmail edge gateways
will not accept messages for invalid recipients.

Yeah - I've been googling like crazy and came across that one. I also
like the idea of using milters to spread the load across several
systems for sanitizing etc..

I'm not sure if you can configure the Mailertable entry to load balance
per say. It is my (mis)understanding that Mailertable entries do
support multiple hosts per entry, but only in a backup fashion in case
one (or more) fail, use the subsequent backup(s). If you are wanting to

Apparently - you can get some crude load balancing via comma
delimitation in
the mailertable. However, I saw a message in my google searches from
one
of the developers pointing out a) it's undocumented and may go away b)
that's
why we have MX records.

Can't really argue with the logic there.

Exchange servers. (LVS is worth the 15 minute read to see what it can
do for you on commodity hardware.)

Yes - very cool stuff. But my MTA's are in different timezones and
forwarding
to exchange servers in different branch offices.

My setup isn't that big. We have less than 2000 accounts. I don't
admin exchange
so I don't know if have more servers or not than needed. It's still
slow as hell to
replicate. But, that's another story ;-)

Good idea about using the milters to spread the load across several
systems. Something
else I'll play around with to get going.

This is also why I suggested that you use Mailertable verses something
else like Smart Hosting on the Sendmail systems. Smart hosting forwards
all email to the Smart Host, while Mailertable forwards email where you
tell it to.

I like it all. I think the only area where I have some more thinking
and planning to do is wether
or not I can use Active Directory to actually deliver the mail
straight to the mailbox on the exchange
server.

Right now I've got my 2 MTA's dumping everything straight to a MX
record that goes to the Exchange MTA's which
know where to route the messages.

I don't think the AD has the right attributes out of the box to
support this. And that's (thankfully)
out of my control. Also - I wonder if I did that and one of our
Exchanges machines went down, wouldn't I
end up generating message undelivables?

Whereas if I mx'd it I could at least queue up the message until the
crappy exchange server came back online?

-Mike
.

Relevant Pages
Loading