[IMC-Tech] File 13 for Email, I Give Up

[Joe Futrelle]

Thanks Dan, sounds like we're already on top of having SA process  
mail coming into the lists.

So mailman's arduous moderator interface is the issue here, not lack  
of a reasonable spam control setup or configuration.

What about majordomo? I'm clueless about it, but it appears to offer  
several means for automated rejection of spam.

--
Joe Futrelle
Person


On Oct 16, 2006, at 11:27 AM, dan blah wrote:

> On 10/16/06, Wendy Edwards <wedwards at uiuc.edu> wrote:
>> Here are some SpamAssassin/Mailman resources I found.
>>
>> Integrating SpamAssassin with Mailman
>> http://www.jamesh.id.au/articles/mailman-spamassassin/
>>
>> How do I use SpamAssassin with Mailman?
>> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.023.htp
>>
>> - Wendy
>>
>>
>> On Mon, Oct 16, 2006 at 11:17:34AM -0500, David Gehrig wrote:
>> > Is whichever server hosts these lists already running procmail?   
>> From a
>> > quick poke around, it seems like one of the standard solutions  
>> is to
>> > configure procmail to call SpamAssassin (which reads email and  
>> marks the
>> > Spam ones it finds) as part of its normal handling of mail, and  
>> then
>> > configure mailman to ignore the ones identified as spam.
>> >
>> > @%<
>> >
>> > On 10/16/06, Stuart Levy <slevy at ncsa.uiuc.edu> wrote:
>> > >
>> > >On Mon, Oct 16, 2006 at 10:34:43AM -0500, Joe Futrelle wrote:
>> > >> Mailman's issue with its crappy admin interface is  
>> longstanding and I
>> > >> don't think we can wait for it to be fixed. That said, I'm as  
>> unclear
>> > >> as Stuart about how to interpose an open-source spam filter  
>> between
>> > >> incoming mail and whatever's running the distro lists-- 
>> Mailman or its
>> > >> eventual replacement. Rolling our own spam filter with  
>> heuristics
>> > >> will only buy us time.
>> > >
>> > >True, but I'd say buying time is good.  At least we'll have
>> > >a chance to evolve as the spam climate continues to heat up.
>> > >
>> > >On the NCSA e-mail system, where the organization-wide filters  
>> detect
>> > >100-150 spam messages sent to me each day, my personal procmail  
>> filters
>> > >catch another 5-10 per day that the NCSA filters miss.  I'm  
>> regularly
>> > >adding things that legit messages just won't contain, like  
>> "st-0ck" or
>> > >"stockk" or "PH[a-z]*RMA".
>> > >_______________________________________________
>> > >IMC-Tech mailing list
>> > >IMC-Tech at lists.ucimc.org
>> > >http://lists.chambana.net/cgi-bin/listinfo/imc-tech
>> > >
>>
>> > _______________________________________________
>> > IMC-Tech mailing list
>> > IMC-Tech at lists.ucimc.org
>> > http://lists.chambana.net/cgi-bin/listinfo/imc-tech
>>
>> _______________________________________________
>> IMC-Tech mailing list
>> IMC-Tech at lists.ucimc.org
>> http://lists.chambana.net/cgi-bin/listinfo/imc-tech
>>
> current path of mail...
>
> postfix receives message -> checks against dnsbl -> passed to postgrey
> for greylisting which deffers accepting a msg for 300 seconds -> then
> sent to amavisd which sends the message to clamav then to
> spammassassin -> amavisd then sends it back to postfix for final
> delivery
>
> this was a topic on this list a couple months ago about things we can
> tweak:  adding any number of envelope checking to prevent postfix from
> every accepting connections from hosts (dnsbl), checking for non-RFC
> compliant smtp behavior, and working on spamassassins rules.
>
> -- 
> Daniel
> _______________________________________________
> IMC-Tech mailing list
> IMC-Tech at lists.ucimc.org
> http://lists.chambana.net/cgi-bin/listinfo/imc-tech