From owner-freebsd-questions@FreeBSD.ORG Fri Oct 19 23:56:44 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38E3916A41A for ; Fri, 19 Oct 2007 23:56:44 +0000 (UTC) (envelope-from rem@remdog.net) Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [204.127.225.94]) by mx1.freebsd.org (Postfix) with ESMTP id E9A4113C459 for ; Fri, 19 Oct 2007 23:56:43 +0000 (UTC) (envelope-from rem@remdog.net) Received: from remdog.net (c-67-188-231-54.hsd1.ca.comcast.net[67.188.231.54]) by comcast.net (alnrmhc14) with ESMTP id <20071019234640b1400cq20ce>; Fri, 19 Oct 2007 23:46:40 +0000 Received: by bsd.remdog.net (Postfix, from userid 1001) id E68FC1D13D; Fri, 19 Oct 2007 14:44:01 -0700 (PDT) Date: Fri, 19 Oct 2007 14:44:01 -0700 From: Rem P Roberti To: freebsd-questions@freebsd.org Message-ID: <20071019214400.GB1178@remdog.net> Mail-Followup-To: freebsd-questions@freebsd.org References: <20071019054651.GA1256@remdog.net> <36DEAEF356AC23874A9B9225@utd59514.utdallas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36DEAEF356AC23874A9B9225@utd59514.utdallas.edu> User-Agent: Mutt/1.4.2.3i Subject: Re: Postfix woes 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: Fri, 19 Oct 2007 23:56:44 -0000 On 2007.10.19 09:35:48 +0000, Paul Schmehl wrote: > --On Thursday, October 18, 2007 22:46:51 -0700 Rem P Roberti > wrote: > > >I did what you all requested and submitted my Postfix problem to the > >Postfix list. The resident guru went over my maillog and sent back his > >analysis which, in short, states that the problem has nothing to do with > >Postfix, and that I should seek help here to get to the bottom of it > >all. That reply is listed below. This is a rather strange business. > > > OK. FIrst of all, don't top post. It makes it very hard to follow a > conversation. > > When you install FreeBSD, you are the master of your own domain. That > means you are completely responsible for everything running on your box. > > When you install Postfix, it installs a startup script in > /usr/local/etc/rc.d. In order to start postfix, you must either add > postfix_enable="YES" to /etc/rc.conf or start postfix manually. If you > want postfix to start on reboot automatically, you *must* use the entry in > /etc/rc.conf. > > There are no cron jobs or scheduled tasks installed to restart, reload, > stop or do anything else to postfix. This means that you, or someone who > has access to your box, has set this up. If you don't recall doing > anything, then you're going to have to start troubleshooting. > > Places to look: > > 1) su to root and type "crontab -l" to see if there's a cron job designed > to manipulate postfix, either directly or through a script. If there is, > eliminate it. It's not needed. > > 2) Look in /etc/periodic to see if there's anything in there (although > that's highly unlikely). > > 3) Examine the postfix startup script to see if someone has altered it in > some way so that it includes a timer that starts and restarts Postfix > > 3) Write a script that monitors processes and can detect when something is > launched at the same time frame that postfix is going up and down > > 4) Get help from someone knowledgeable who has access to your box > > 5) Did you install a program (like sysutils/monitord) that checks for > running processes and attempts to restart them if they're not running? > > 6) Is there anything in root's mail that would tip you off to the cause of > the problem? > > 7) Run postfix in debug mode. Maybe that will help isolate the cause. This is a follow-up. My friend arrived back home and I explained the problems that I was having. He said, simple, remark out postfix_enable="YES" in your rc.conf. I did. Problem solved. Now I have neither postfix_enable, or sendmail_enable in my rc.conf, and everything boots without a hitch. This, of course, flies in the face of everything that I have heard or read about configuring this program. When I asked what was starting the program if those entries were no longer operating he said the shell script contained in rc.d. I need to give this a rest. Rem >