Question for the Experts

[Brendan Pirie]

Are you saying ServerA is no longer the MX for this particular domain, 
but it is still the MX for several other domains?

Brendan Pirie
Manager of Information Technology
Randolph-Macon Academy
bpirie at rma.edu

Kevin MURPHY wrote:
> Hi Brendan
> I cannot firewall port 25, as it receives mail for many other Domains.
> Thanks
> 
> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Brendan
> Pirie
> Sent: 14 February 2008 16:10
> To: MailScanner discussion
> Subject: Re: Question for the Experts
> 
> I just went through a similar process here.  I firewalled port 25 on 
> ServerA so ServerA could only receive email from ServerB.
> 
> Brendan Pirie
> Manager of Information Technology
> Randolph-Macon Academy
> bpirie at rma.edu
> 
> Kevin MURPHY wrote:
>> Dear all
>>
>>  
>>
>> I recently made some changes to a domains mx record. It use to be, mx = 
>> serverA, which relays clean mail to Exchange Server
>>
>> Because this domain was really getting hammered, I moved it to a more 
>> powerful spam filtering server.
>>
>> MX Record is now ServerB, which fwds clean mail to ServerA, which relays 
>> it to the Exchange Server.
>>
>>  
>>
>> My Problem now is that some spammers are still sending mail direct to my 
>> ServerA for this Domain.
>>
>>  
>>
>> So I am looking at a way to configure the ServerA, so it only excepts 
>> mail for this domain if it comes from server (The more powerful one) So 
>> it drops the spammers on ServerA
>>
>>  
>>
>> Thanks
>>
>>  
>>
>> Kevin **
>>
>>  
>>
>> This e-mail is intended solely for the addressee(s) and is strictly 
>> confidential. The unauthorised use, disclosure or copying of this 
>> e-mail, or any information it contains is prohibited. If you have 
>> received this e-mail in error, please notify us immediately and then 
>> permanently delete it. Although we make every effort to keep our systems 
>> free from viruses, you should check this e-mail and any attachments to 
>> it for viruses as we cannot accept any liability for viruses 
>> inadvertently transmitted by use.
>>
>