From owner-freebsd-stable@FreeBSD.ORG Thu Aug 16 19:17:14 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F14216A418 for ; Thu, 16 Aug 2007 19:17:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0A36B13C457 for ; Thu, 16 Aug 2007 19:17:13 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id D77261CC06F; Thu, 16 Aug 2007 12:17:13 -0700 (PDT) Date: Thu, 16 Aug 2007 12:17:13 -0700 From: Jeremy Chadwick To: Reinhold Message-ID: <20070816191713.GA23955@eos.sc1.parodius.com> Mail-Followup-To: Reinhold , freebsd-stable@freebsd.org References: <56136.212.99.207.3.1187289568.squirrel@www.violetlan.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56136.212.99.207.3.1187289568.squirrel@www.violetlan.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-stable@freebsd.org Subject: Re: apache problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2007 19:17:14 -0000 On Thu, Aug 16, 2007 at 08:39:28PM +0200, Reinhold wrote: > Thanks for the reply > > I'm having some mail problems as well, today is not my day. > > I'll remove all the stuff you mentioned and change back to 4BSD > Will I have to recompile all the ports as well? Nope, you won't. > I don't think its a PF problem because I have used this rule set of mine > for a few years with no problems at all, but I'll recheck that just to > make sure. Some rules appear to work fine, but actually cause problems in certain conditions. For example, we cannot use the "reassemble tcp" feature of scrub, or else it breaks all sorts of stuff on our network. You wouldn't notice it until you did something that involves a lot of I/O via ssh, such as "while true; do dmesg; done", which after 2-3 seconds would result in a TCP connection getting severed. My point is, rule out everything if you can. :-) > Now for the mail problem I'm having its got to do with postfix sending > mail from any ip address and not from the one that I want it to, but thats > a later problem and on another box, I first want to get this apache thing > sorted.. That's an easy one: use smtp_bind_address in main.cf. I've got a little two-liner comment in my main.cf about the difference between inet_interfaces and smtp_bind_address: # inet_interfaces defines what IPs/FQDNs to bind to for listening sockets. # smtp_bind_address defines what IP to bind to when delivering mail. inet_interfaces = mx01.sc1.parodius.com, localhost smtp_bind_address = 72.20.106.3 Also, AFAIK, you have to use an IP address for smtp_bind_address but not for inet_interfaces. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |