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
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
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 Monday 01 January 2007 12:15 am, R Lists06 wrote:
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
I'm not sure any of that matters since the problem is with installing a self-contained daemon which should just run.
I have discovered an alternative method that works with MySQL and doesn't require any kind of daemon. The reason I don't prefer it is that it doesn't have an automated whitelisting method; I'll have to write a program to add whitelists.
What would you need/want to know about our servers? They're fairly generic 1U systems running CentOS4. The fact that the RPM installs without any kind of prereq error says it should work. Or not?
The MTA is exim. That can't be changed, as the servers are running the DirectAdmin control panel (http://www.directadmin.com/), which requires exim. DirectAdmin is a wholly-contained compiled C++ program requiring no dependencies. But it's intimately connected with the way exim works.
Once I get greylisting working, I want to greylist selectively, if possible. First I just want to get it working <smile>.
And once it works for me I want to make it part of the exim.conf file I write for DirectAdmin servers, so others can use it.
What other kind of "setup decision things" should be considered? The version of Python should be the only dependency, but the RPM shouldn't have allowed the installation if I'm not running the right Python version.
<snip> $ python Python 2.3.4 (#1, Oct 11 2006, 06:18:43) [GCC 3.4.6 20060404 (Red Hat 3.4.6-3)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
$ </snip>
After the failed startup (please refer to my log snippet in my previous post), grepping the ps output shows python2.3 running greylistd...
<snip> $ ps waux| grep grey 104 11911 0.0 0.3 8936 3932 ? S 2006 0:00 /usr/bin/python2.3 /usr/sbin/greylistd jlasman 6485 0.0 0.0 4392 676 pts/2 S+ 05:36 0:00 grep grey $ </snip>
So maybe it is running and I should just try to use it? But I'd think a daemon should continue to run. And I don't want to break my incoming email. I'm creating a testbed to try it.
You are a smart guy, did you try searching the web?
Of course, for many hours. But how do you know I'm smart? Most of the time I don't feel that way myself <smile>.
Anyone's help is appreciated.
Thanks.
Jeff
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
Black Hand wrote:
ps uax | grep -v grep | grep '/usr/bin/python /usr/sbin/greylistd' > /dev/null
A little OT and a nitpick, but this is better:
ps uax | grep "/usr/bin/python /usr/sbin/greylist[d]" > /dev/null
It will achieve the same (eliminating your own grep process) and will save you an exec.
-
Black Hand -
Jeff Lasman -
Morten Torstensen -
R Lists06