h a l f b a k e r yEureka! Keeping naked people off the streets since 1999.
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
There are many different spam
filters. Some of them can work
independently of your other
software, acting as the
mail-server, filtering and
forwarding the mails to your
real server. Others are
plug-ins or extensions to your
server. And, still others, are
embedded components of or
plug-ins
of your e-mail client.
Not a one of these is perfect,
and getting the best
performance out of it often
requires some user feed back.
"No, my grandma's recipe for
the family secret cookies is
not spam.", "Yes, this offer
for free viagra is spam." for
example.
So it seems to make sense that
what is needed here is a common
protocol for an e-mail client
to connect to a spam filter, be
it through some IP-based
protocol, COM-like interface,
or what-have-you, to handle
such tasks in a
filter-independant manner, so
as to give each of us our
choice in spam filters, without
sacrificing the almighty
ease-of-use.
Please log in.
If you're not logged in,
you can see what this page
looks like, but you will
not be able to add anything.
Destination URL.
E.g., https://www.coffee.com/
Description (displayed with the short name and URL.)
|
| |
Sounds good, but i think we should let the free market take care of this one. Let the best standard emerge because it's the best, not because you or i think so. |
|
| |
Nothing wrong with drafting a standard.
You'd be daft not to consult major players
along the way and they'll soon let you
know if it's something they would
integrate into their product or not. |
|
| |