From owner-freebsd-chat Thu Jan 7 20:51:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00523 for freebsd-chat-outgoing; Thu, 7 Jan 1999 20:51:32 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00514 for ; Thu, 7 Jan 1999 20:51:29 -0800 (PST) (envelope-from cmcurtin@cis.ohio-state.edu) Received: from gold.cis.ohio-state.edu (gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id XAA07104; Thu, 7 Jan 1999 23:50:53 -0500 (EST) Received: (from cmcurtin@localhost) by gold.cis.ohio-state.edu (8.9.1/8.9.1) id XAA03467; Thu, 7 Jan 1999 23:50:53 -0500 (EST) To: "Jason C. Wells" Cc: Graeme Cross , FreeBSD-chat Subject: Re: New Majordomo Feature References: From: Matt Curtin Date: 07 Jan 1999 23:50:53 -0500 In-Reply-To: "Jason C. Wells"'s message of "Thu, 7 Jan 1999 15:52:06 -0800 (PST)" Message-ID: Lines: 23 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jason C. Wells" writes: > Perhaps. I say that we already trust ourselves to not abuse the > lists. But there's no strong authentication feature in place. That requires overhead. As it is, someone could telnet to port 25 and pretend to be, for example, Jordan and spamthread "Re:". > Also, the description of the possible solution was incredibly > simple. As a check against abuse there could be a tally of > spamthread commands. Two strikes and your out. So you'd have to telnet to port 25 twice. :) > Nearly all of my spam comes from these lists. Granted, spam is a low > percentage of my total traffic. That can be (mostly) solved by closing the lists so that only subscribers can post... -- Matt Curtin cmcurtin@interhack.net http://www.interhack.net/people/cmcurtin/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message