Re: [SLUG] Email hacking

2003-11-03 Thread Jamie Wilkinson
This one time, at band camp, David Kempe wrote:
- Original Message - 
From: Peter Hardy [EMAIL PROTECTED]
 I'll also be looking in to generating useful statistics from the mailman
 logs, so we can have a much firmer idea of how effective the current
 strategies are.  Is there any packages around that already do this?  Any
 advice or suggestions more than welcome.

I had an idea once that to train these type of packages easily you could put
a hyperlink at the bottom so you could train with a click. Much easier on
admins etc.
Of course it wouldn't make sense for the whole slug list to train.
If you could have a link to a script with specified the message ID which
went to a page where you could chose spam or nospam. Don't know how hard
that all is, but it seemed to me to be a simpler way to train a filter than
the current resending.

The idea Pete came up with involved forwarding the message in question back
to a spam-trainer address as an attachment, so that the message can be fed
into the spam database of the bayesian filter, and using GPG to ensure that
trusted parties do the feeding.  I imagine a single script that'd take a
message and do the right thing with it, so any list admin could bind a mutt
key to do the job, or collect a mailbox in Evolution and feed that in bulk
periodically, or similar.

-- 
[EMAIL PROTECTED]   http://spacepants.org/jaq.gpg
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-11-03 Thread Peter Vogel
With my limited knowledge of such things, it seems like a lot of spam
could be prevented by blocking all mail that does not contain a simple keyword.
This keyword could be included in the footer of all mail going to the
list as a reminder. It could even change from time to time.

Have I overlooked something?

Peter
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-11-03 Thread Benno
On Tue Nov 04, 2003 at 08:36:09 +1100, Peter Vogel wrote:
With my limited knowledge of such things, it seems like a lot of spam
could be prevented by blocking all mail that does not contain a simple keyword.
This keyword could be included in the footer of all mail going to the
list as a reminder. It could even change from time to time.

Have I overlooked something?

Ease of use. I'm sure my usual posting to slug will involve:

send e-mail
get bounce
*swear about stupid magic keyword*
look for an old email about the current magic keyword
append to e-mail
resend e-mail.

Actually on second thoughts it will probably be more like:

send e-mail
get bounce
*swear about stupid magic keyword*
give up trying to reply to someones question


Benno
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-11-03 Thread Anthony Wood
On Tue, Nov 04, 2003 at 08:45:05AM +1100, Benno wrote:
 On Tue Nov 04, 2003 at 08:36:09 +1100, Peter Vogel wrote:
 With my limited knowledge of such things, it seems like a lot of spam
 could be prevented by blocking all mail that does not contain a simple keyword.
 This keyword could be included in the footer of all mail going to the
 list as a reminder. It could even change from time to time.
 
 Have I overlooked something?
 
 Ease of use. I'm sure my usual posting to slug will involve:
 
 send e-mail
 get bounce
 *swear about stupid magic keyword*
 look for an old email about the current magic keyword
 append to e-mail
 resend e-mail.
 
 Actually on second thoughts it will probably be more like:
 
 send e-mail
 get bounce
 *swear about stupid magic keyword*
 give up trying to reply to someones question

If the s3kr1t keyword is '[SLUG]' and it has to appear in the subject,
then I think we'd block at least 95% of spam. (to start with)

plus you don't need to worry about replying, because your mailer
will include '[SLUG]' in the header automatically.

cheers,
Woody

-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-11-03 Thread Jan Schmidt
quote who=Anthony Wood
 If the s3kr1t keyword is '[SLUG]' and it has to appear in the subject,
 then I think we'd block at least 95% of spam. (to start with)
 
 plus you don't need to worry about replying, because your mailer
 will include '[SLUG]' in the header automatically.
 

The key points that people are missing here:
* We work quite hard behind the scenes to limit the amount of spam that gets 
to the SLUG lists - and we're already above 99% catch rate. Pete's proposal
is an attempt to raise this even further, not to add spam filtering where
there is none.
* We just voted on the list policy and it was decided by a large margin to 
leave it exactly as it is so as not to 'raise the barrier to entry' to new
participants.

Thank you,
Jan.
-- 
Jan Schmidt  [EMAIL PROTECTED]

-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-11-03 Thread Peter Hardy
On Tue, 2003-11-04 at 10:22, Jan Schmidt wrote:
 The key points that people are missing here:

* And nobody seems to be generating Mailman reports yet. :-(

-- 
Pete

-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


[SLUG] Email hacking

2003-10-31 Thread Peter Hardy
On Fri, 2003-10-31 at 22:45, Mary Gardiner wrote:
 If you feel absolutely compelled to discuss this any further, do so on
 slug-chat. (Unless you are asking about configuration for lists YOU
 run.)

Well, now that you mention it... ;-)
I'd just like to clear up a few things that seemed to be left hanging
after the meeting.

 Hence, SLUG admins will retain the current policy: non-subscribers
 will
 be able to post without moderation, and the admins will try and
 prevent
 spam reaching SLUG using Postfix, SpamAssassin and Mailman checks on
 content of the mails, rather than the From address.

Jamie mentioned this during sluglets, but I may as well elaborate. 
We'll soon be adding bogofilter (http://bogofilter.sourceforge.net/) in
to the mix as well.  One of my codefest projects will be writing a
useful python wrapper around bogofilter, and plugging it in to mailman. 
Nutting out the details of handling remote training nicely is making it
an interesting endeavour.

I'll also be looking in to generating useful statistics from the mailman
logs, so we can have a much firmer idea of how effective the current
strategies are.  Is there any packages around that already do this?  Any
advice or suggestions more than welcome.

-- 
Pete

-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-10-31 Thread David Kempe
- Original Message - 
From: Peter Hardy [EMAIL PROTECTED]
 I'll also be looking in to generating useful statistics from the mailman
 logs, so we can have a much firmer idea of how effective the current
 strategies are.  Is there any packages around that already do this?  Any
 advice or suggestions more than welcome.

I had an idea once that to train these type of packages easily you could put
a hyperlink at the bottom so you could train with a click. Much easier on
admins etc.
Of course it wouldn't make sense for the whole slug list to train.
If you could have a link to a script with specified the message ID which
went to a page where you could chose spam or nospam. Don't know how hard
that all is, but it seemed to me to be a simpler way to train a filter than
the current resending.

dave

-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Email hacking

2003-10-31 Thread Grant Parnell
On Sat, 1 Nov 2003, David Kempe wrote:

 I had an idea once that to train these type of packages easily you could put
 a hyperlink at the bottom so you could train with a click. Much easier on
 admins etc.
 Of course it wouldn't make sense for the whole slug list to train.
 If you could have a link to a script with specified the message ID which
 went to a page where you could chose spam or nospam. Don't know how hard
 that all is, but it seemed to me to be a simpler way to train a filter than
 the current resending.

I think you're onto something. If you added 2 hyperlinks at the bottom 
(only for admins), one for spam, one for no-spam. It would then be a 
one-click/key operation.

Another thought was to whip up some php code to display the normal headers 
 the first 10 lines of each message in batches of about 50 or 100 with 
checkboxes and one submit button at the bottom. Downside is you have to 
launch a web browser.

 -- 
---GRiP---
Electronic Hobbyist, Former Arcadia BBS nut, Occasional nudist, 
Linux Guru, SLUG/AUUG/Linux Australia member, Sydney Flashmobber,
BMX rider, Walker, Raver  rave music lover, Big kid that refuses
grow up. I'd make a good family pet, take me home today!
Do people actually read these things?

-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug