At 01:12 4/7/2005, Alexander Hagenah wrote: > >> Once it's all set up, though, the Exchange server will receive > >> incoming mail from Xmail (with all validation and spam / virus scans > >> done prior to receipt), and all outbound mail from the Exchange > >> server will go through Xmail as a smarthost. > >=20 > > I can't seem to get Exchange to do that - even tho it is 'supposed' > > to do that. > >It's working without any problems. Just have to set the `real-adress' >mail-adress of each sender into ActiveDirectory-Users. XMail will >forward all incoming messages to Exchange - and Exchange looks into AD >and spread it to the specified user. In this case - Exchange must NOT >have a Smarthost. It doesn't matter - but it is not bad, to do this. >There *might* be some DNS problems, if not using a Smarthost - by >sending/receiving mails with the LOCAL.DOMAIN as a (non-)valid address.
This sounds like a recipe for "accept then bounce" to me. The idea is to set it up so the gateway server (in this case Xmail) can validate each recipient (preferably at RCPT TO time) as being a valid user (so that a protocol session error can be returned for invalid users - rather than generating a bounce message to a (likely forged) invalid user email). Plus, we want to get away from Exchange acting as an SMTP delivery agent - we want *all* inbound *and* outbound mail to pass through the gateway (for archiving, virus scanning, and other purposes). This would require having the Exchange server use the gateway server as a smarthost (rather than attempting to delivery the mail itself). - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
