Ed Richards posted this informative email to the newbies list:
--
John Hebert
System Engineer
I T Group, Inc.
225-922-4535
-------------- next part --------------
An embedded message was scrubbed...
From: "Richards Jr, Edward C." <[EMAIL PROTECTED]>
Subject: [brlug-newbies] Announcing the CodeWeavers Compatibility and
Certification Center
Date: Tue, 20 Jan 2004 11:21:15 -0600
Size: 6994
Url:
http://oxygen.nocdirect.com/pipermail/general_brlug.net/attachments/20040120/effd546b/brlug-newbiesAnnouncingtheCodeWeaversCompatibilityandCertificationCenter.eml
From [EMAIL PROTECTED] Tue Jan 20 13:06:27 2004
From: [EMAIL PROTECTED] (Dustin Puryear)
Date: Tue Jan 20 13:02:16 2004
Subject: [brlug-general] Exchange to another mail server
Message-ID: <[EMAIL PROTECTED]>
An Exchange server in an AD environment hosts a domain example.com. I want a
few users to use Exchange because of the groupware capabilities, but the
remaining users in the AD will be using a Linux mail server. (This is the
problem given to me. I realize there are Linux-based groupware solutions.)
Anyway, the trick here is to separate those users. (Authentication against
AD from a Linux mail server isn't a big deal so I am not talking about
that.)
My thoughts:
1. All mail for example.com goes through the Linux server. Any mail not to a
Linux mail user gets routed to Exchange using a catch-all address (this
catches mail not destined for a known, local user). Problem solved for
incoming mail, but not outgoing.
With outgoing mail a user of the Exchange box (her email addy is
[EMAIL PROTECTED]) emails Bob ([EMAIL PROTECTED]). Bob is on the Linux box. I
don't think I can get Exchange to route Bob's mail. Instead, Exchange will
bounce it. I could create a forward address for Bob to
[EMAIL PROTECTED], but that requires an Exchange CAL for [EMAIL PROTECTED]
I believe, and we are trying to avoid licensing of Exchange for
non-Exchanged hosted email.
2. All mail goes through the Exchange server. Exchange routes non-local mail
to Linux. Same problem as above.
I'm really just at the brainstorming stage, so any ideas are welcome.
What's tricky here isn't hosting two sets of users, but hosting two sets of
users for the same domain on two machines.
Goal: Users using Linux for POP3 do not need an Exchange CAL.
