by Has anyone tried this before?
I have a client with a small NT4.0/Exchange Server network which
currently dials up once an hour via an ISDN card in the server to an
SMTP server at their ISP.
They are considering using other internet services, and I think a Linux
firewall/NAT/web proxy would be the way to go. Nobody seems to have much
good to say about the MS products.
On the other hand, while I've dabbled with Linux, I'm not a Linux guru,
and don't really have the spare time to become one. I've just spent
fif* to twenty hours on a new Debian installation at home, and can
now use my network card and can play Windows wavs on my AWE32. I
haven't yet managed Linux wavs or MIDI. The thought of switching the
ISDN card to a non-Red-Hat Linux box and making it work is not a
pleasant one.
I do have a 3Com ISDN Dial-on-Demand LAN router laying around, and this
would seem to offer the most straightforward solution. If I can get
email working, I can sort out web access at a later date. I presume I
need to run a Linux mail server, send mail to the DoD router using cron
to keep the bills down, but somehow persuade Exchange Server to talk to
the Linux mail server by ethernet rather than over a ppp link.
I can't find anything in my ES literature on using another local SMTP
server for outside mail (that's what ES is, after all). Configuration of
the ES mail delivery and collection seems to assume either a dial-up ppp
link, or permanent connection using a DNS server. What I actually need
is for non-local mail to be sent to the Linux mail server to hold for
scheduled delivery.
I can see no point in asking on the MS groups about Linux, but does
anyone here have any experience of routing ES via Linux?
--
Joe