From owner-freebsd-questions@FreeBSD.ORG Thu Mar 15 11:03:06 2007 Return-Path: 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 6BDE216A40E for ; Thu, 15 Mar 2007 11:03:06 +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 0CE1C13C4BF for ; Thu, 15 Mar 2007 11:03:05 +0000 (UTC) (envelope-from martin@dc.cis.okstate.edu) Received: from dc.cis.okstate.edu (localhost.okstate.edu [127.0.0.1]) by dc.cis.okstate.edu (8.13.3/8.13.3) with ESMTP id l2FB35l7043902 for ; Thu, 15 Mar 2007 06:03:05 -0500 (CDT) (envelope-from martin@dc.cis.okstate.edu) Message-Id: <200703151103.l2FB35l7043902@dc.cis.okstate.edu> To: freebsd-questions@freebsd.org Date: Thu, 15 Mar 2007 06:03:05 -0500 From: Martin McCormick Subject: Re: Sendmail on a new Freebsd6.2 Won't Send or Receive. Solved! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2007 11:03:06 -0000 "Ted Mittelstaedt" writes: > sendmail_enable="YES" in /etc/rc.conf? Many thanks. That's exactly what I had, but after looking at it again, I also had something much worse in the startup line. This new system is a replacement for the one I am on now and the name is similar. The rc.conf.local file was copied from the old system and this part looks like: sendmail_enable="YES" # Run the sendmail inbound daemon (YES/NO/NONE). # # If NONE, don't start any sendmail processes. sendmail_flags="-L sm-mta -bd -q15m -C/etc/mail/dc.cis.okstate.edu.cf" # Flags to sendmail (as a server) That was the problem. The file name referenced there doesn't exist on the new system. When I used the right configuration file name, all is well. Again, thanks for your help because it made me look everything over once again and find the problem.