On 29/05/2006, at 4:18 PM, O Plameras wrote:
Scott Sinclair wrote:
On Mon 29 May, 2006 at 15:41:01 +1000, O Plameras wrote:
A simple solution:
Just add one activity for the poster to do, i.e., to every
posting SLUG-list
server will elicit a confirmation from the poster whereby this
confirmation is
identified by a unique-key.
The SLUG list server generates this unique-key and sent along
with the
request to the poster to confirm his/her post. If it is not
confirmed within
a specified time, the posting will be purged and hence not sent
out to the
list.
I don't think that this implementation would help at all, and
would be more
of a hinderence, and make people more annoyed with having to
confirm each
email reply, then just delete spam email as it is received.
One has to confirm only when posting to the list each time.
I received around 5 to 10 spams from SLUG daily and every one
subscribed and who
don't bother about filters too much would recevied the same number.
So,this is the number of spams I have to process every day. If
there are 700 subscribers
the total spams is about 8 (ave) times 700 times 30 or 168,000 per
month. This is not
insignificant considering the bandwidth.
The total number of postings for a month is about 1,400 or 2
postings / subscriber per month. A
subscriber would only have to reply 2 times (AVE) in one month as
against 240
times(8 times 30) per month per subscriber to process and delete
spams.
I think it's not such a bad idea for non-subscriber posts to be
filtered in this way.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
