Re: Question about filtering..

From: Kevin Longley (kwlongley_at_cirtronics.com)
Date: 07/30/04


Date: Fri, 30 Jul 2004 16:12:10 -0400

You should purchase a 3rd party spam filtering solution or upgrade to
Exchange 2003 which comes with many more tools for filtering spam. Sender
filtering is an endless task and in Exchange can only support up to about
850 entries (this is also true of Exchange 2003 - AD issue). I use Exchange
2003 with all of the filtering options (sender, recipient, blacklists,
whitelists) including the IMF and also use Block & Tackle by Turbogeeks.com.
It has worked very well.

"jim" <jim@NOSPAM.com> wrote in message
news:uQwhHYmdEHA.3016@tk2msftngp13.phx.gbl...
> I would imagine that *@*.domain.com would not catch that much as it would
> imply domains with two names (a.domain.com, b.domain.com, c.domain.com)
> and
> this is pretty unusual.
>
> That's exactly what i'm dealing with. I'm getting a lot of spam that show
> up from 123.specificdomain.com, 456.specificdomain.com,
> abc.specificdomain.com, and so on. The only constant in all of this is
the
> "specificdomain.com" part. Specificdomain is obviously generating random
> host names to prepend to their domain. The only way i can see to block
this
> altogether is to put in *@*.specificdomain.com. This way it doesn't
matter
> what they change the first part of the domain to, so long as the
> specificdomain.com part doesn't change. Am i understanding this
correctly?
>
>
> "Mark Fugatt [MVP]" <news@4mcts.com> wrote in message
> news:eUmeXDmdEHA.2908@TK2MSFTNGP10.phx.gbl...
> > You cannot use the asterisk in the middle of domains (*@spam*sucks.com)
> > would not be valid.
> >
> > I would imagine that *@*.domain.com would not catch that much as it
would
> > imply domains with two names (a.domain.com, b.domain.com, c.domain.com)
> and
> > this is pretty unusual.
> >
> > Sender Filtering is not a very effective way of blocking spam, I would
> > suggest you look at implementing a real anti-spam solution such as
> > MailEssentials from www.gfi.com or the Open Relay Filter from
> > www.vamsoft.com, or upgrade to Exchange 2003 and implement IMF
> >
> > --
> > Mark Fugatt
> > Exchange MVP
> > http://www.exchangetrainer.com
> > http://www.msexchange.org
> > "jim" <jim@NOSPAM.com> wrote in message
> > news:OKeum%23ldEHA.3612@TK2MSFTNGP09.phx.gbl...
> > >I don't think it works very well. I followed the instructions exactly
> and
> > > i'm still seeing mail in the queues from domains i've blocked. It
seems
> > > to
> > > be less effective when i go the *@*.domain.com as opposed to just
> > > *@domain.com.
> > >
> > > It doesn't explicitly explain this, but can i also use the asterisk
> within
> > > domain names, as in *@spam*sucks.com? Would this catch
> > > *@spamreallysucks.com, *@spammostlysucks.com, and so on?
> > >
> > >
> > > "Mark Fugatt [MVP]" <news@4mcts.com> wrote in message
> > > news:Otji9WldEHA.1952@TK2MSFTNGP11.phx.gbl...
> > >> I assume your are talking about Sender Filtering?
> > >>
> > >> Make sure you have enabled Sender Filtering on your SMTP Virtual
> Server:
> > >> http://www.msexchange.org/tutorials/MF014.html
> > >>
> > >> --
> > >> Mark Fugatt
> > >> Exchange MVP
> > >> http://www.exchangetrainer.com
> > >> http://www.msexchange.org
> > >> "jim" <jim@NOSPAM.com> wrote in message
> > >> news:Ov$hkIkdEHA.1184@TK2MSFTNGP11.phx.gbl...
> > >> > In the Ex2k System Admin console i've been filtering specific
> domains.
> > > I
> > >> > do
> > >> > this under Global Settings -> Message Delivery -> Filtering tab.
My
> > >> > question is this: If i can identify an entire domain by entering
> > >> > *@domain.com, shouldn't i be able to use the wildcard character to
> > > broaden
> > >> > my filtering range? In other words, i often get spammed from a
> domain
> > >> > that
> > >> > comes in as xyz.domain.com one day, and then abc.domain.com the
next
> > >> > ("domain.com" being the only constant in the addresses). It's
> > > impossible
> > >> > to
> > >> > keep up with the changes. I've tried entering *@*.domain.com, but
> this
> > >> > doesn't seem to work. Should this work? Am i entering this wrong?
> Is
> > >> > the
> > >> > wildcard (*) character only allowed before the @ symbol?
> > >> >
> > >> > Thanks for the help.
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: OT: Can IMF be tweaked
    ... >> is sent to other Exchange servers. ... Does Sender Filtering bypass IMF? ... >> blocked senders lists are not available. ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange and Mobil Device Spam
    ... I understand you receive spam mail on mobile ... you enable spam filter on server side. ... Exchange Server 2003 SP2 supports the following filters: ... Connection filtering ...
    (microsoft.public.windows.server.sbs)
  • Re: Reverse Lookups
    ... > incorrectly sets up their SMTP servers. ... > If you are using Exchange 2003 you have two important options of RBL ... > NOTE Exchange 2000 allows you to do RBL filtering ... > It determines whether the site in the link is a known spam site. ...
    (microsoft.public.exchange.admin)
  • Re: Distribution Group
    ... SPAM that has been filtered in case a legitimate email happens to get ... That's when you can whitelist them using IMF. ... We are using only the Intelligent Email Filtering that came with ... We are using Exchange 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: Stopping Spam
    ... >>quick and effective filtering at the receiving end. ... Correct, but since large-scale forgery is the key enabler for spam, I ... and the whitelist itself loses reputation. ... where the sender knows the source and can ...
    (comp.security.misc)

Quantcast