On Mon, 14 Jul 2008, Krystal Zipfel wrote:
The problem I see with this is much like the DNSBLs and Block lists
(spamhaus?).
As Jason put it, one person's spam could very much be another person's ham,
so mail starts getting rejected by those who outright trust such a database
and it is hell trying to get removed from those said lists.
Not to mention, there is so much forgery and many changes to spam tricks that
even SA has to keep up with it. :-(
Personally, I think spam filtering/watching/fighting should be done per
server, per user, etc. Would be real nice if the ISP's would start doing
that...
My opinion. :-)
Well, one immediate solution that helps is starting another list or two,
as a honeypot, and seeing who subscribes.
Gadi.
Jason Pruim wrote:
First, I think it would have better luck on the developers mailing list :)
But as for the idea, I think it could work, but someone would have to
provide the hosting for the database that would hold all the info. And we
would have to figure out who would be a "trusted" source to report the
spam.... My spam might be your ham... I need lunch hehe
In general though I like the idea and would love to hear from others on it
as well :)
On Jul 14, 2008, at 1:25 PM, Gadi Evron wrote:
I often see addresses popping up and subscribing to all visible lists on
my servers.
Sometimes they're a curious individual, and most times they are spammers
harversting addresses (as these are open only to admin).
I wonder what the coding "price" would be, if it can even work with
mailman, to create a central trusted DB which watched subscription trends?
1. It could be used for security.
2. It could fight spammers on the mailman front.
3. If we deal with the security and privacy implications of the first two,
or want a constructive cause--collect cool trends and provide with a
mailing lists index by tag words and activity. Think technorati..
This of course, is just a neat idea. Thoughts?
Thanks,
Gadi.
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/japruim%40raoset.com
Security Policy: http://wiki.list.org/x/QIA9
--
Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
11287 James St
Holland, MI 49424
www.raoset.com
[EMAIL PROTECTED]
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/zipfel%40greenacrestechnology.com
Security Policy: http://wiki.list.org/x/QIA9
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/ge%40linuxbox.org
Security Policy: http://wiki.list.org/x/QIA9
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
