Junk Senders List

[Junk mail hater]

I use Outlook 2002, running on Exchange Server 2003. In
Outlook, I can quickly add to my list of junk senders. Is
there a way to easily transfer this list (potentially
updated daily) to the server, so that the specific
addresses and/or domains can be blocked before they reach
my inbox? I'd want to be able to do this myself, as
opposed to having to go through our administrator, which
is a painfully slow process. I could add the
addresses/domains one by one in OWA, but that's too time
consuming. A way to quickly transfer my list would be
preferable.

 

[Rifleman]

I use Outlook 2002, running on Exchange Server 2003. In
Outlook, I can quickly add to my list of junk senders. Is
there a way to easily transfer this list (potentially
updated daily) to the server, so that the specific
addresses and/or domains can be blocked before they reach
my inbox? I'd want to be able to do this myself, as
opposed to having to go through our administrator, which
is a painfully slow process. I could add the
addresses/domains one by one in OWA, but that's too time
consuming. A way to quickly transfer my list would be
preferable.

Search for a file called (really!) "Junk senders.txt" You should find it
somewhere in your C:\Documents and Settings\"your user name\ folders.

 

[*Vanguard*]

"Junk mail hater" said in news:[email protected]:

I use Outlook 2002, running on Exchange Server 2003. In
Outlook, I can quickly add to my list of junk senders. Is
there a way to easily transfer this list (potentially
updated daily) to the server, so that the specific
addresses and/or domains can be blocked before they reach
my inbox? I'd want to be able to do this myself, as
opposed to having to go through our administrator, which
is a painfully slow process. I could add the
addresses/domains one by one in OWA, but that's too time
consuming. A way to quickly transfer my list would be
preferable.

You really think spammers use a valid e-mail address? You think they always
use the same bogus e-mail address on every crop of crap they spew? Blocking
by the sender only works if the abusive or spamming sender is so stupid as
to always use the e-mail address (valid or bogus). Not likely. If you've
been using the Junk Senders "feature" for awhile, you must have a huge list
of superfluous bogus e-mail addresses that rarely if ever get reused.

 

[Brian Tillman]

If you've been using the Junk Senders "feature"
for awhile, you must have a huge list of superfluous bogus e-mail
addresses that rarely if ever get reused.

On the contrary, since SPAMmers often reuse the same domain, employing bogus
usernames within that domain, the junk senders list can be quite helpful if
only the domain portion of the addresses are used. For example, SPAMmers
often send mail appearing to come from (e-mail address removed), (e-mail address removed),
(e-mail address removed), etc. By adding india.com (or just plain india) to the junk
senders list, all three example addresses would be blocked.
--
Brian Tillman
Smiths Aerospace
3290 Patterson Ave. SE, MS 1B3
Grand Rapids, MI 49512-1991
Brian.Tillman is the name, smiths-aerospace.com is the domain.

I don't speak for Smiths, and Smiths doesn't speak for me.

 

[*Vanguard*]

"Brian Tillman" said in news:%[email protected]:

On the contrary, since SPAMmers often reuse the same domain,
employing bogus usernames within that domain, the junk senders list
can be quite helpful if only the domain portion of the addresses are
used. For example, SPAMmers often send mail appearing to come from
(e-mail address removed), (e-mail address removed), (e-mail address removed), etc. By adding
india.com (or just plain india) to the junk senders list, all three
example addresses would be blocked.

And you've never gotten spam with a return e-mail address from a valid
domain but obviously with a bogus username (or valid one but NOT for the
spammer)? Who cares if some spammer sends their crap from (e-mail address removed)
or (e-mail address removed)? Are you really going to block such huge domains
just because a spammer fooled you into thinking they sent their crap from
there? Only a stupid spammer is going to use a domain repeatedly that is
already statistically shown to be likely a bogus domain or one that sources
spam. And checking the Received headers will show it doesn't come from that
[valid] domain, anyway. Spammers want to use domains in the Reply-To and
From headers that look like they come from well-known and large ISPs. Only
idiot spammers would repeatedly use something like india.com (when sending
to some other country) if that is well known as a bogus domain. But then
there are lots of idiots out there and some of them are spammers. However,
adding such idiot bogus/valid spammer domains to the Junk Senders list is
relevant only if you specifically happen to get lots of them. However,
eventually even that idiot spammer will wise up and migrate to using valid
large ISP domains that you obviously cannot block since you would be
deterring e-mail from all your friends, family, coworkers, and others from
who you do want to receive e-mail. If you work at IBM, are you really going
to block ibm.com by adding it to the Junk Senders list just because some
spammer used a bogus e-mail address with (e-mail address removed)?

Instead use some decent anti-spam software. SpamPal detects spam based
primarily on *where* it originated by using the publicly available DNSBLs
(DNS blacklists) or RBLs (open relay blacklists). However, you can add
plug-ins that will also detect spam based on its content. In fact, you can
configure SpamPal to reject e-mails from several specific countries. If you
don't expect to get any e-mail outside your country then block e-mails from
all those other countries.

 

[Brian Tillman]

And you've never gotten spam with a return e-mail address from a valid
domain but obviously with a bogus username (or valid one but NOT for
the spammer)? Who cares if some spammer sends their crap from
(e-mail address removed) or (e-mail address removed)? Are you really going to
block such huge domains just because a spammer fooled you into
thinking they sent their crap from there?

You bet. There's no one of any interest to me using Yahoo! or AOL.

Only a stupid spammer is
going to use a domain repeatedly that is already statistically shown
to be likely a bogus domain or one that sources spam.

There are plenty of those.

And checking
the Received headers will show it doesn't come from that [valid]
domain, anyway.

Then use a rule to filter on the headers.
--
Brian Tillman
Smiths Aerospace
3290 Patterson Ave. SE, MS 1B3
Grand Rapids, MI 49512-1991
Brian.Tillman is the name, smiths-aerospace.com is the domain.

I don't speak for Smiths, and Smiths doesn't speak for me.

 

[*Vanguard*]

... Are you really going

You bet. There's no one of any interest to me using Yahoo! or AOL.

Must be nice to have such a limited number of friends, family, associates,
coworkers, and hobby buddies and be lucky that none of them use Yahoo,
Hotmail, AOL, Earthlink, MSN, Excite, SBC, AT&T, Comcast, and all the other
major ISPs and webmail providers from which a multitude of spam does also
originate.

And checking
the Received headers will show it doesn't come from that [valid]
domain, anyway.

Then use a rule to filter on the headers.

Since the RFC 2821 is not strict nor actually dicate the format of what is
the exact format of the Received header, and since spammers won't follow
those rules anyway if they even existed, you cannot create a rule for it
(well, not a simple rule as is possible within an e-mail client but you
could do the parsing and threshold id of what type a field was to determine
IP address noted by receiving mail server for the sender's mail server).
For example, show me a rule in Outlook (which has better rules than OE) that
lets you seach *ONLY* within a header line that begins with "Received:" (and
you'll have to test for mixed case, too) and then check the value of just
that header line. Nope, can't do it. All you can do is search for a string
*somewhere* in *any* of the headers, so searching for a domain name or IP
address somewhere in the headers and finding a match doesn't mean it was
found in the Received header. Maybe if you're running your own mail server
or proxy filter then you could use something like Perl to use regular
expression and limit the search to particular headers and be able to parse
those lines and then use dozens of algorithms to determine in which format
the header was written so you could determine the type for each token. Not
something the average e-mail client user is going to do or even have the
capability to do.