Elim LaRoche said:
I know, and I think there is one in use at the exchange level.
However, spam still seeps through and whenever they arrive, I add the
domain to the junk list. This usually works quite well, only that at
some point it started to treat web addresses as junk, even though
they neither contain any of the words from the "Filters.txt" nor are
they or their domain part of the "Junk Senders.txt". I even tried
deleting the content of both, and it still moves files into the junk
or deleted folder. I would like to know, what it is, that triggers
the junk rule to do this, as apart from these two document I don't
know where else it looks for information on how to filter.
I checked the "Filter.txt" document, if anything in it causes the
problem, but none of these words
The hard part about rules (actually the effects of them) is knowing
which rule acted upon a message. I add the clause to categorize a
message. Each rule has its own category, like "Rule - SpamPal Trap" or
"Rule - Blank Subject". I don't use the Junk rule but I believe when
you enable it then a Junk rule appears in your rules list. If it is
editable, then add a category to it, like "Rule - Junk". Then add the
category column to whichever folder you move messages into via your
rules (I don't add it to the Inbox because rules that leave my messages
there are whitelist rules). Then you can be sure why a message got
moved into the Junk folder or into the Deleted Items folder, plus you
get to see which rule caught the spam turd. This help eliminates
thinking one rule caused the effect when in fact it was some other rule.
I've heard there is a limit to how many blocked senders there can be in
the junk list. I don't use that function so I don't know what is this
limit. However, from other users that I've seen using the Junk senders
list, it's a worthless feature because all the e-mail addresses or
domains listed there are bogus, anyway. Spammers don't use their real
e-mail address when spewing their turds, nor do they use their own
domain in their e-mail address. They pretend to be someone else, so
blocking on that bogus e-mail address or domain won't block their next
crop of turds using a different bogus e-mail address. In fact, they
probably love the idea that you are blocking e-mail addresses for
potential senders that had nothing to do with their spam. The blocked
senders list only uses the From header (and maybe the Return-Path
header) and that is so easily falsified that it is worthless for
blocking spam. Even you can change what string gets put into the From
header (but in an Exchange organization that may not be possible since
Exchange might put whatever is your account in the From header and
ignore anything your client put there, but that doesn't restrict the
spammers). Also, with the ever increasing number of trojaned home PCs
running mail daemons to spew these spam turds, you blocking them doesn't
block the same spam from another trojaned home PC, and blocking their
domain means you block all good senders from there, too, like wiping out
all customers sending from AOL or Earthlink accounts because some idiot
is using a trojaned PC from that domain. Using the blocked senders list
to avoid spam is like having a guy ring your doorbell and announce
himself as "Mark" but you don't accept housecalls from people named
Mark, so he rings your doorbell again and says he is "Steve", so you add
Steve to your block list (after having suffering his housecall), and
then he rings your doorbell and says he is from the IRS so you block the
IRS only to find out you're in deep shit when the real IRS sent you a
"request" to appear for an audit because you automatically tossed away
their notice. At this point, and with probably lots of bogus and
never-reused e-mail addresses in your list, maybe it's time to scrap the
list and start over.
