Re: diabolical spam
- From: "Gary VanderMolen" <gary@xxxxxxxxxxxxxx>
- Date: Mon, 22 Jun 2009 20:05:06 -0700
If there was an easy solution to spam, it would be made widely available
by now. There is no easy solution. Deciphering the originating IP
address of a spam email is no trivial matter.
Your mail provider should be your first line of defense. Most employ
very sophisticated server filters that you can't duplicate at home.
--
Gary VanderMolen, MS-MVP (Mail)
"richardmyers" <richardmyers@xxxxxxxxxxxxxxx> wrote in message news:45B5213E-8012-4BE5-B6F4-9E5F4A29CA53@xxxxxxxxxxxxxxxx
.
"Spirit" wrote:
Make a rule to ALLOW your NewsGroup messages and BLOCK the rest
with your address as both sender and receiver.
That's a good idea, but a little cumbersome, since i subscribe to more than
fifty email lists. Granted, not all of them return with the address of the
originator as sender. But even so, it seems like a significant hassle for
some of us to accomplish.
I don't know, i've never experimented with email rules. But i'm thinking i'd
have to specifically allow each email list.
Since this spoofed spam seems like a relatively new trick, i expect we'll
all see more and more of it.
Seems to me email clients ought to have a simpler method of dealing with
such a problem. Is it impossible to block email messages by analyzing the
headers, and maybe isolating an originating IP address? It seems to me that
would be a more elegant solution, if it is possible given the email header
protocol. (I'm not an expert in such matters...)
thanks,
richard myers
- References:
- diabolical spam
- From: richardmyers
- Re: diabolical spam
- From: Spirit
- Re: diabolical spam
- From: richardmyers
- diabolical spam
- Prev by Date: RE: Fixing "Command Failed to Execute" on attachments
- Next by Date: Re: Fixing "Command Failed to Execute" on attachments
- Previous by thread: Re: diabolical spam
- Next by thread: Re: diabolical spam
- Index(es):
Relevant Pages
|