Sendmail- E2K3 co-existence SMTP problems

[Evilbart]

Hi, I'm migrating from Sendmail on FreeBSD towards Exchange 2003

both systems have to co-exist for 5 months (migration time)
this is how it is set up: Sendmail receives mail from the internet (for

domain realdomain.com). For every user that allready has got a mailbox on

E2K3 I forward the mail to a dummy SMTP domain (eg. fakedomain.local), all

other users have their own mbx on sendmail (pop3 download)

E2K3 is configured so that they share smtp namespace (realdomain.com) by

running Recipient policies so every mbx on Exchange has 2 mail-addresses:

%G.%S@Fakedomain.local and %G.%S@realdomain.com
fakedomain.local = exchange is authoritive
realdomain.com = exchange is not authoritave

i put up 2 SMTP connectors : CONNECTOR1 : that says realdomain.com to use

Sendmail as smart host with cost 1 and allow relaying enabled
CONNECTOR 2 : that says : *, use DNS to send, allow relaying disabled ;-)

this all works fine except for one thing: we cannot send mail from exchange

2003 to sendmail: it keeps stuck in the Queue 4 ever, when i track messages

they are stuck infinite in the queue

in the log files on the sendmail server i see these messages:

Nov 13 16:03:53 mail sendmail[21285]: PAA21285: collect: premature EOM:
Undefined error: 0
Nov 13 16:03:53 mail sendmail[21285]: PAA21285: collect: unexpected close
on connection from fakedomain.local,
sender=Bart.Bultinck@realdomain.com: Undefined error: 0
Nov 13 16:03:53 mail sendmail[21285]: PAA21285:
from=Bart.Bultinck@realdomain.com, size=3311, class=0, pri=0,
nrcpts=1, proto=SMTP, relay=fakedomain.local[172.16.1.2]

it all worked fine when i was doing LAB-TESTING with Exchange 2000, using

exchange 2003 gives these messages.

Can somebody please shed a light on what is wrong here and how to solve this

All help is appreciated

kind regards
// Bart

 

[colemanrob]

I am trying to do the same thing....I have followed the MS article 321721. Email flows from Sendmail to Exchange but not the other way.....cannot reply or send to the Internet.

Everything sticks in the 'Waiting for Directory Lookup' queue.

Mail between Exchange users works fine.

Any help would be greatly appreciated. I can be reached at colemanrob2001@hotmail.com

Sorry....I am up against the clock on this one.

 

[Evilbart]

Hi, this was solved by creating a mail-enabled user in AD for every MBX still on sendmail

to help you with your problem: this is what i have done
1/ create a smtp connector for the internal domain to flow back to the sendmail for users who have their mbx still there

2/ external mail on exchange goes directly to the internet through another smtp connector (have your firewalls allow this)

hope this helps

// Bart

 

[colemanrob]

Thanks Bart....this helps...

Just so I get this right tho.....you are still maintaining the configuration you mentioned in the original post..that is, a default policy of 2 addresses, one fake and one real?

Are you still using the 2 connectors configured as before or are you adding 2 more......one to Sendmail and one to the Internet ? And if so, how are you configuring these?

I apologise if I seem a little dense here........the way I read things is a little quirky now and then and I can get myself into the glue without really trying!

The real domain is using a Linux gateway server in front of the Sendmail server. All mail comes into the gateway and is then sent on to the Sendmail Server or to the Exchange server via the alias list. As per MS Q article 321721 I have set up 2 recipient policies and an SMTP connector pointing to the Gateway on the real domain....... I have configured a SMTP connector like you did on the Exchange server, forwarding to the Smarthost (gateway) using it's IP with relaying enabled and another SMTP connector using DNS and and address space of * with relaying disabled.

I do not have users on the sendmail system setup with mailboxes on the Exchange system but will do that now.

My fake domain is @local and my real domain is @snohomish.lan. The email address for the Sendmail users is in the format @srvr.domain.wa.gov. Do I need to put this address space in the default policy?



How's this look to you?

Thanks

Rob