Linux POP mail and MS Exchange integration

Hello,

I would like to setup 200 remote users in our organization with Linux
POP accounts, the other 50 internal users would use Microsoft Exchange
mailboxes for their email. I need a solution that would allow all
Microsoft and Linux email users to use a common domain name (ie.
(E-Mail Removed)), without having to split Linux POP accounts into
a sub-domain (ie. (E-Mail Removed)). I also do not want to
create mailboxes on the Exchange server that simply forward messages
to Linux POP accounts. The whole point of this is to lower the $$ we
spend on Micro$oft licen$ing.

Thanks,
Marvin

In article <(E-Mail Removed) >
(E-Mail Removed) (Marvin) writes:

>I would like to setup 200 remote users in our organization with Linux
>POP accounts, the other 50 internal users would use Microsoft Exchange
>mailboxes for their email. I need a solution that would allow all
>Microsoft and Linux email users to use a common domain name (ie.
>(E-Mail Removed)), without having to split Linux POP accounts into
>a sub-domain (ie. (E-Mail Removed)). I also do not want to
>create mailboxes on the Exchange server that simply forward messages
>to Linux POP accounts. The whole point of this is to lower the $$ we
>spend on Micro$oft licen$ing.

This might be totally off-topic, but on the other hand it might
come in handy if you start running into problems. Just last week
a customer notified us that my homebrewed e-mail sending program
was failing when trying to send mail to a Microsoft Exchange server.
It turns out that the server was barfing on the RCPT TO: commands
that my program was sending to it, because it didn't like the way
my program enclosed the e-mail address in angle brackets, as mandated
by RFC2821. I had to add an option to drop the angle brackets when
talking to an Exchange server.

--
/~\ (E-Mail Removed)lid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!

Charlie Gibbs wrote:

> In article <(E-Mail Removed) >
> (E-Mail Removed) (Marvin) writes:
>
>>I would like to setup 200 remote users in our organization with Linux
>>POP accounts, the other 50 internal users would use Microsoft Exchange
>>mailboxes for their email. I need a solution that would allow all
>>Microsoft and Linux email users to use a common domain name (ie.
>>(E-Mail Removed)), without having to split Linux POP accounts into
>>a sub-domain (ie. (E-Mail Removed)). I also do not want to
>>create mailboxes on the Exchange server that simply forward messages
>>to Linux POP accounts. The whole point of this is to lower the $$ we
>>spend on Micro$oft licen$ing.
>
> This might be totally off-topic, but on the other hand it might
> come in handy if you start running into problems. Just last week
> a customer notified us that my homebrewed e-mail sending program
> was failing when trying to send mail to a Microsoft Exchange server.
> It turns out that the server was barfing on the RCPT TO: commands
> that my program was sending to it, because it didn't like the way
> my program enclosed the e-mail address in angle brackets, as mandated
> by RFC2821. I had to add an option to drop the angle brackets when
> talking to an Exchange server.
>
> --
> /~\ (E-Mail Removed)lid (Charlie Gibbs)
> \ / I'm really at ac.dekanfrus if you read it the right way.
> X Top-posted messages will probably be ignored. See RFC1855.
> / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!


/me shakes head.

--
Donovan Hill

Couldn't you set up all mailboxes on the linux
machine as the default mail host, then forward
the inhouse mail to exchange for MS problems.
I never could get MS to act as secondary DNS
it complains that my SAO records are currupt.
I wouldn't put it past them to do the same thing
with email.
Robert