Windows Exchange Server

[Gary Pentland]

Of course, I forgot to mention, there is an even easier way...

Just configure Exchange to block/reject invalid recipients (it doesn't in most default setups) set a mailertable entry for it and run milter-ahead.

That works as well, use whichever you are most comfortable with.

Gary

mailscanner-bounces at lists.mailscanner.info wrote:
> I've been doing this for years, it's slightly off topic and
> there is stuff about this in the MailScanner wiki but as
> people tend to forget about that:-)
>
> I have attached some old perl, based on something I found on
> the net years ago.  It dumps list of Exchange recipients from
> an AD, use as basis for sendmail virtusers map or valid users
> map, run every 10 mins or so.  Obviously change the
> passwords, domain controller names and baseDN.
>
> Simplest in sendmail is to configure is to define a virtual
> domain, default recipient is "user does not exist type
> error", every other recipient becomes user at exchange.domain...
> Then chuck in a mailertable entry or an MX for
> exchange.domain pointing at a hub transport (2007) or a
> front-end (2003) and use a script based on the attached perl to make
> the virtusers map.
>
> Alternatively, if you know you will only ever need to send to
> Exchange and nowhere else you could use something like the M4
> fragment attached.  This is old so will probably need some
> tweaking for your site but it will give you an idea.
>
> I'll leave it to Ronny here to help with postfix if you choose that
> route.
>
> Hope that helps,
>
> Gary
>
> mailscanner-bounces at lists.mailscanner.info wrote:
>>> I have numerous clients doing it this way and it just works.  If you
>>> are using sendmail as your MailScanner MTA I can provide complete
>>> help on how to make this work with MailScanner and exchange (all
>>> versions).
>>
>> And I can help with postfix (+ Active Directory / LDAP)!
>>
>>
>> As for the inter-Exchange traffic: this really should be "trusted"
>> internal traffic, between internal servers, on an strictly internal
>> network. If it is NOT then it should not be allowed to flow freely
>> between servers directly.
>>
>> In any case you should run a mail scanning virus scanner on your
>> Exchange servers so internal viruses can not propagate.
>>
>>
>> Cheers,
>> Ronny