From owner-freebsd-questions@FreeBSD.ORG  Thu Jan  1 10:05:56 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 454DC16A4CE
	for <freebsd-questions@FreeBSD.ORG>;
	Thu,  1 Jan 2004 10:05:56 -0800 (PST)
Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7DE8943D77
	for <freebsd-questions@FreeBSD.ORG>;
	Thu,  1 Jan 2004 10:05:21 -0800 (PST)
	(envelope-from freebsd-questions-local@be-well.ilk.org)
Received: by be-well.no-ip.com (Postfix, from userid 1147)
	id 7F8F559; Thu,  1 Jan 2004 13:05:21 -0500 (EST)
Sender: lowell@be-well.ilk.org
To: cb.z.ds@spamgourmet.com
References: <TSTO1XEB97DRMPJ436476PSP95HERL.3ff3b18a@zzz>
From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
Date: 01 Jan 2004 13:05:21 -0500
In-Reply-To: <TSTO1XEB97DRMPJ436476PSP95HERL.3ff3b18a@zzz>
Message-ID: <447k0blf32.fsf@be-well.ilk.org>
Lines: 8
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: getting rid of cron-sendmail messages
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
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: Thu, 01 Jan 2004 18:05:56 -0000

cb.z.ds@spamgourmet.com writes:

> After the upgrade I get now 2 messages from sendmail daily when cron runs.
> What's happened? Also, is there other/better solution?

According to periodic.conf(5), daily_status_security_output is only
meaningful "if daily_status_security_inline is set to ``NO''"