|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Stan Hoeppner (stan
hardwarefreak.com)
Date: Wed Jun 23 2010 - 20:10:41 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Steffan A. Cline put forth on 6/23/2010 8:39 AM:
> I am assuming from your conf file you have:
>> POSTGREY_OPTS="--inet=127.0.0.1:60000"
> From the options I see, I could put that into the startup file above by
> changing:
> OPTIONS="--unix=$SOCKET"
> To
> OPTIONS="--inet=127.0.0.1:60000"
Yeah, that's it, that's the right Postgrey file. You can use a UNIX socket or
inet. The key thing is that they must match between postgrey and postfix.
Postfix has to know how to communicate with Postgrey. Sometimes using a
socket can be problematic or more difficult, specifically in chroot
environments, IIRC. This may be why the default recommended setup for on
Debian is inet, as Debian runs Postfix in a chroot by default. For these
reasons I use the inet interface. It's just easier for me, and no real
potential gotchas.
> My question now lies in do I need to add any any additional config to
> master.cf file to take advantage of this service?
No, nothing is needed in master.cf for this, only the line in main.cf. As I
stated in a recent post, I've been using Postfix for 5 years now. I have
never edited master.cf.
--
Stan
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]