From owner-freebsd-questions@FreeBSD.ORG  Wed Apr  4 13:13:32 2007
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C50B216A402
	for <freebsd-questions@freebsd.org>;
	Wed,  4 Apr 2007 13:13:32 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219])
	by mx1.freebsd.org (Postfix) with ESMTP id 9BB6C13C459
	for <freebsd-questions@freebsd.org>;
	Wed,  4 Apr 2007 13:13:32 +0000 (UTC)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.13.8/8.13.8) with ESMTP id l34DDWuF044355
	for <freebsd-questions@freebsd.org>;
	Wed, 4 Apr 2007 08:13:32 -0500 (CDT)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <200704041313.l34DDWuF044355@dc.cis.okstate.edu>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <44353.1175692412.1@dc.cis.okstate.edu>
Date: Wed, 04 Apr 2007 08:13:32 -0500
From: Martin McCormick <martin@dc.cis.okstate.edu>
Subject: Any Way to Plug This Hole in Local Sendmail Delivery?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Apr 2007 13:13:32 -0000

	First of all, I think sendmail is great, so this is a
minor issue.  The problem is that the spammers can cause local
delivery of their junk by using the name of an account on the
system.  As an example, I just received some junk that a human
being can instantly tell is bogus.  It's from 
line is the usual sort of bogus hotmail, or AOL or MSN, forgery
but then there is this line which is, I am sure, how it got in.

From: Weekly News <martin@dc.cis.okstate.edu>

	Milter-sender used to catch these constantly, but that
filter is no longer available.  Is there anything else that is
useful, but not too disruptive that can either refuse delivery
or send it to spam to die?

	I already run bogofilter which I trained with about
12,000 or more spam messages and which does a good to excellent
job of catching most of this, but messages that claim to be
local but aren't should be mechanically testable.

Thanks.

Martin McCormick WB5AGZ  Stillwater, OK 
Systems Engineer
OSU Information Technology Department Network Operations Group