SMTP Relay Setup - Spam Filtering

Similar Threads:

1.anti spam filter for simply 2003 smtp relay ?

Hi,

Im looking for a free anti spam filter I can install on my 2003 smtp mail 
relay. Does not have to be anything sophisticated, just need the ability to 
reject domain names for example (at its most basic):

*@fakedomain.com

Would prefer to have anti spam working on relay machine (in DMZ) as opposed 
to back end exchange server on LAN.

Too much many examples on the net, just looking for a recommendation.

Thanks for any advice
Scott 

2.secure smtp after setup of 3rd party spam filtering

we've been mail bombed, relayed, heavly spammed, etc, 
etc.  our ISP has a spam solution that we just started 
using.  they changed our mail records to first point to a 
third party spam filter company (like clearmx.com). that 
gave me the ability to only allow connections from a 
range of their servers, thus ending all the useless 
connections from all over the world.  well, even though i 
made those changes, i still have hundreds of connections 
from mail.ru and all those spam sites.  the anti-spam 
solution seems to be doing its job, but i still see many 
connections that are not on the list of IPs i assigned 
rights to connect.  how do i get rid of these connections?

thanks

3.Third party spam filtering setup: SSL and other setup question

Thanks, I'll check this out and let you know how it works out.

Greg

"John Oliver, Jr. [MVP]" wrote:

> Inline:
> 
> -- 
> John Oliver, Jr
> MCSE, MCT, CCNA
> Exchange MVP 2009
> Microsoft Certified Partner
> 
> 
> "gnhopson" < XXXX@XXXXX.COM > wrote in message 
> news: XXXX@XXXXX.COM ...
> > Our administrator left a couple of months ago and I have inherited
> > responsibility for all adiminstration duties. We're a small company, so
> > I'm it for everything. I have had some training on Windows Server 2003, 
> > but
> > everything was set up before I got here and now I have my first change.
> >
> > We just moved to a third party provider (MXLogic) for our email and spam
> > filtering.
> > I'm trying to set up the synchronization so that our users will be
> > automatically downloaded to MXLogic.
> >
> > Here are the questions MXLogic's synchronization setup is asking me and 
> > what
> > I  know about each:
> >
> > Question: Server Hostname
> > All I know is we use mail.highwayequipment.com to access our mail 
> > remotely.
> > I see we have 66.43.207.188 as our inbound and outbound servers in our
> > MXLogic setup. None of these seem to work. I don know where else to look
> > for this or who can tell me what I needr even what to ask for.
> 
> I see no A Record for mail.highwayequipment.com so I cannot verify that 
> 66.43.207.188 is actually the Public IP it resolves too.  For MXlogix's 
> case, you only need the WAN IP of your Router/Firewall, this is what inbound 
> server must be sent to in MXlogic setup.  Your MX Records are pointing 
> correctly to MXlogic's filtering servers.
> >
> > Question 2: Enable SSL  (checkbox)
> > I don really know what this means beyond ecure Socket Layeror how to
>>>> find out if I should check this box or not.
>> 
>> If you are hosting your own SMTP mail with Exchange Server then SSL needs to 
>> be setup through Exchange. Do you currently have Commercial Certificate? 
>> You can verify through IIS Manager under Default Website- Security Tab.
>>>>
>>>> Question 3: Search Bind DN
>>>> I log into the server that Exchange runs on as dministratorMy>
> > understanding is this is the logon I should use. It wants the >
> > distinguished>
> > name so I entered:>
> > cs=Administrator,cs=Users,dc=highwayequipment,dc=com>
> >
> This is most likely related to the fact that MXlogic wants to bind to your >
> AD to automatically populate user accounts.  I would verify with their Tech >
> Support on settting this up.>
> >
> >>
> > Question 4: Search Bind Password>
> > I enterd the password for Administrator>
> >>
> > Question 5: Search Base DN>
> > I put    cs=Users,dc=highwayequipment,dc=com>
> >>
> >>
> > Question 2 is the one I need the most help with...how can I tell if we are>
> > using SSL here?>
> >>
> > Thanks,>
> >>
> > Greg>
> > >
> 

4.Third party spam filtering setup: SSL and other setup questions

Our administrator left a couple of months ago and I have inherited
 responsibility for all adiminstration duties. We're a small company, so 
 I'm it for everything. I have had some training on Windows Server 2003, but
 everything was set up before I got here and now I have my first change.

 We just moved to a third party provider (MXLogic) for our email and spam 
filtering.
 I'm trying to set up the synchronization so that our users will be
 automatically downloaded to MXLogic.

Here are the questions MXLogic's synchronization setup is asking me and what 
I  know about each:

Question: Server Hostname
All I know is we use mail.highwayequipment.com to access our mail remotely. 
I see we have 66.43.207.188 as our inbound and outbound servers in our 
MXLogic setup. None of these seem to work. I don know where else to look 
for this or who can tell me what I needr even what to ask for.

Question 2: Enable SSL  (checkbox)
I don really know what this means beyond ecure Socket Layeror how to 
find out if I should check this box or not.  

Question 3: Search Bind DN
I log into the server that Exchange runs on as dministratorMy 
understanding is this is the logon I should use. It wants the distinguished 
name so I entered:
	cs=Administrator,cs=Users,dc=highwayequipment,dc=com

Question 4: Search Bind Password
I enterd the password for Administrator

Question 5: Search Base DN
I put    cs=Users,dc=highwayequipment,dc=com


Question 2 is the one I need the most help with...how can I tell if we are 
using SSL here?

Thanks,

Greg 

5.Need to setup SPAM filtering on Exchange2K Win2K Server

I have a site that I need to get set up with spam 
filtering.  What is the best way to set this up. Can any 
of you refer me to some good instructions.  Selecting 
filtering in Exchange Manager is really lame.  

Thanks in advance

Dave

6. Exch2003 Relay/Spam Setup

7. Spam filters and SMTP service

8. Filter outgoing/relay SMTP traffic