At 11:20 PM -0500 2006-08-22, Matt England wrote:

>  This is the best email I have yet to find describing how mail.python.org
>  proactive kills spam:
>
>  http://mail.python.org/pipermail/python-list/2006-March/332443.html

I've also got an article that will be going up soon on the LOPSA.org 
website that explains, in great detail, what we're doing on 
python.org and where I think we should be going.  If anyone is 
interested, I'll post the URL here when it's up.

>  I'm also considering adding these capabilities (which may or may not be
>  implicit in the above description) to combat spam:
>
>  * Don't allow email from non-subscribers
>  * Moderate email from new subscribers some period of time (probably a day
>  to a week)
>
>  Does mail.python.org do either or these things and/or is this generally a
>  good practice?

You mean, do we do these things at the MTA level?  No.  The MTA has 
no clue as to who is a subscriber and who is not.  These things could 
potentially be done at the Mailman level, however.  Unfortunately, 
while you can configure Mailman to moderate (or reject) all posts 
from non-subscribers, I don't know of any way to configure it to do 
something like what you suggest based on the time of day.

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

     -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
     Assembly to the Governor, November 11, 1755

  Founding Individual Sponsor of LOPSA.  See <http://www.lopsa.org/>.
------------------------------------------------------
Mailman-Users mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;file=faq01.027.htp

Reply via email to