I'm using CentOS 4.4 <snip> # cat /etc/redhat-release CentOS release 4.4 (Final) # </snip> I downloaded and installed greylistd as follows: greylistd-0.8.3.2-7.el4.at.noarch.rpm from: http://riksun.riken.go.jp/pub/pub/Linux/atrpms/rhel/4/en/i386/RPMS.at-stable/ I installed it without problems. <snip> # rpm -Uvh greylistd-0.8.3.2-7.el4.at.noarch.rpm warning: greylistd-0.8.3.2-7.el4.at.noarch.rpm: V3 DSA signature: NOKEY, key ID 66534c2b Preparing... ########################################### [100%] 1:greylistd ########################################### [100%] # </snip> But it doesn't run <frown>. I start it using "service greylistd start". I'm presuming that should work, as all the files seem to be in place for it to work. <snip> # service greylistd start Starting greylistd: [FAILED] # </snip> The message in /var/log/messages is decidedly unhelpful; all it tells me is that the program started and then stopped: <snip> Dec 31 19:43:53 da12 su(pam_unix)[11890]: session opened for user greylistd by jlasman(uid=0) Dec 31 19:43:53 da12 su(pam_unix)[11890]: session closed for user greylistd Dec 31 19:43:55 da12 greylistd: greylistd startup failed </snip> Any ideas as to what may be going on? Or where I should look? Or if there's easily installable source-code available? Thanks. Jeff -- Jeff Lasman, Nobaloney Internet Services 1254 So Waterman Ave., Suite 50, San Bernardino, CA 92408 Our blists address used on lists is for list email only Phone +1 909 266-9209, or see: "http://www.nobaloney.net/contactus.html"
> I'm using CentOS 4.4 > > <snip> > # cat /etc/redhat-release > CentOS release 4.4 (Final) > # > </snip> > > I downloaded and installed greylistd as follows: > > greylistd-0.8.3.2-7.el4.at.noarch.rpm > > from: > > http://riksun.riken.go.jp/pub/pub/Linux/atrpms/rhel/4/en/i386/RPMS.at- > stable/ > > I installed it without problems. > > <snip> > # rpm -Uvh greylistd-0.8.3.2-7.el4.at.noarch.rpm > warning: greylistd-0.8.3.2-7.el4.at.noarch.rpm: V3 DSA signature: NOKEY, > key ID 66534c2b > Preparing... ########################################### > [100%] > 1:greylistd ########################################### > [100%] > # > </snip> > > But it doesn't run <frown>. > > I start it using "service greylistd start". I'm presuming that should > work, as all the files seem to be in place for it to work. > > <snip> > # service greylistd start > Starting greylistd: [FAILED] > # > </snip> > > The message in /var/log/messages is decidedly unhelpful; all it tells me > is that the program started and then stopped: > > <snip> > Dec 31 19:43:53 da12 su(pam_unix)[11890]: session opened for user > greylistd by jlasman(uid=0) > Dec 31 19:43:53 da12 su(pam_unix)[11890]: session closed for user > greylistd > Dec 31 19:43:55 da12 greylistd: greylistd startup failed > </snip> > > Any ideas as to what may be going on? Or where I should look? > > Or if there's easily installable source-code available? > > Thanks. > > Jeffjeff You didn't mention very much about your server and which MTA (among other engineering or setup decision things) you are using nor if you want to greylistd every connection or selectively etc You are a smart guy, did you try searching the web? - rh -- Robert - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net
On Sunday 31 December 2006 10:46 pm, Jeff Lasman wrote:> I downloaded and installed greylistd as follows: > greylistd-0.8.3.2-7.el4.at.noarch.rpm<snip>> But it doesn't run <frown>. > > I start it using "service greylistd start". I'm presuming that should > work, as all the files seem to be in place for it to work. > > <snip> > # service greylistd start > Starting greylistd: [FAILED]if you check your process list, you will see that a process greylistd is running, the daemon start but, the notification for sucess have a bug with this package rpm from atrpms. For declaring success in the start, the init script search for a process greylistd active, but in the wrong way. open /etc/init.d/greylistd with any editor of your choice go to the line 25 that say ps uax | grep -v grep | grep '/usr/bin/python /usr/sbin/greylistd' > /dev/null change the /usr/bin/python word for /usr/bin/python2.3 ps uax | grep -v grep | grep '/usr/bin/python2.3 /usr/sbin/greylistd'> /dev/null(maybe my editor cut in two the lines above.) with this change, the service will report correctly that the daemon is active. happy greylisting (i have this one in tho exim systems to my charge, and i love this) -- Black Hand Amiga Addicts