mail problems was Re: apache problems

[Kevin K.]

Just a FYI, its not a great idea to post your firewall rules w/
external/internal ips still intact.



-----Original Message-----
From: owner-freebsd-stable at freebsd.org
[mailto:owner-freebsd-stable at freebsd.org] On Behalf Of Reinhold
Sent: Thursday, August 16, 2007 4:46 PM
To: freebsd-stable at freebsd.org
Subject: mail problems was Re: apache problems

Thanks for the tips on postfix but they don't work for me. I have my mail
server behind a pf firewall box on a local ip

I have attached my pf.conf file so that you can see what it looks like, I
also have to tell spamd to use the hostname of the mail sever but when I use
the -h flag is sops working.

thanks for all the help

On Thu, 16 Aug 2007 12:18:35 -0700
Jeremy Chadwick <koitsu at FreeBSD.org> wrote:

> On Thu, Aug 16, 2007 at 09:16:00PM +0200, Miroslav Lachman wrote:
> > Jeremy Chadwick wrote:
> > [...]
> >>> I'm also getting this error when I do a gracful restart of apache 
> >>> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to 
> >>> enable the 'httpready' Accept Filter [Thu Aug 16 05:12:16 2007] 
> >>> [warn] (22)Invalid argument: Failed to enable the 'httpready' 
> >>> Accept Filter
> >>>
> >>> and in my /boot/loader.conf I have added accf_data_load="YES"
> >>> accf_http_load="YES"
> >> Remove those.  Here's why:
> >> The apache rc.d startup script automatically will load 
> >> accf_http.ko. I also believe if that fails, Apache will try to load 
> >> it.  From my experiences kldload/kldunload with accf_* is not very 
> >> friendly; I've seen where you can double-load the modules, and 
> >> where you can't unload the modules despite nothing using them.  If 
> >> you have them built-in to your kernel, it gets even worse.
> >
> > It is not always possible to load modules after OS startup is done
> > - when securelevel is 1 or above, you can not load kernel modules.
> 
> Okay, then the apache rc.d script needs to take this into account, 
> regardless of what rc.conf apache22_http_accept_enable is set to.
> 
> That shouldn't be too hard to fix.
> 



__________ NOD32 2466 (20070816) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com