Forward mail to exchange for some users

Hi, all.
My boss wants to use exchange for collaboration. But we already have
>100 users and ~15 mailing lists set up. I want only ~20 users to have mailbox in exchange.
What is the best way to do it? I'd like those users to receive mail for
their old addresses too.
Let's say I'm v_volodin on qmail machine. I want to connect to exchange
via mapi, so that I don't care about my actual address on exchange. I
want to receive and send email as v_volodin. Is there a way to tell
qmail to forward my messages to exchange?

Gary L. Burnore wrote:
> On 5 May 2006 01:22:26 -0700, "zGollum" <zgollum@gmail.com> wrote:
>> My boss wants to use exchange for collaboration. But we already
>> have 100 users and ~15 mailing lists set up. I want only ~20 users
>> to have mailbox in exchange.
>> What is the best way to do it? I'd like those users to receive mail for
>> their old addresses too.
>> Let's say I'm v_volodin on qmail machine. I want to connect to exchange
>> via mapi, so that I don't care about my actual address on exchange. I
>> want to receive and send email as v_volodin. Is there a way to tell
>> qmail to forward my messages to exchange?
>
>
> Put exchange on servername.yourcompany.com
>
> Forward mail on your qmail box to the twenty some with regular
> forwards from username@yourcompany.com to
> username@servername.yourcompany.com. Make sure that
> severname.yourcompany.com uses the qmail server as its smarthost.
> (Called something else in Exchange)

I did this at work but there was one remaining problem that I was never
able to solve (so I kicked out Exchange instead :-).

The problem was that every now and then - but not always - emails
originating from the Exchange server would have
user@exchange.example.com as its sender address. This hadn't been a
problem if people had used decent clients, like Eudora, Thunderbird, and
even OE, where the sender's address can be set to whatever the user
thinks it should be, but people insisted in using Outlook and it's not
doable there as far as I know.

A part of the problem here was that 'exchange.example.com' wasn't valid
outside of the company so replies to those emails would bounce.

I'm happy with the current Exchange-free setup but it would be
interesting how this problem should have been solved? Adding a
real-world MX record for exchange.example.com would cause problems when
forwarding from the qmail SMTP server to the Exchange server.

Btw, one reason Exchange was thrown out was that it required around 300
MB RAM on a 2.4 GHz P4 to handle a load of some 50 emails a day, whereas
the qmail server, running on a 166 MHz Pentium with 32 MB of memory,
could handle a load 100 times that. Amazing.