[exim] (no subject)

Top Page
Delete this message
Reply to this message
Author: Mathieu CATTIN
Date:  
To: exim-users
Subject: [exim] (no subject)
>> Apr 19 07:29:27 - exim[12720]: 2005-04-19 07:29:27 cannot run

>> initgroups(): no passwd entry for uid=1000


>> Apr 19 07:29:27 - exim[12722]: 2005-04-19 07:29:27 cannot run

initgroups(): no passwd

entry for uid=1000

>> Apr 19 07:29:27 - exim[12720]: 2005-04-19 07:29:27 cannot run


>> initgroups(): no passwd entry for uid=1000


>> Apr 19 07:29:27 - exim[12722]: 2005-04-19 07:29:27 cannot run


>> initgroups(): no passwd entry for uid=1000


>>


>> Apr 19 07:29:45 - exim[12753]: 2005-04-19 07:29:45 1DNnB0-0003Jh-HJ

<=

>> <mailto:root@freesco.zapto.org> root@??? U=root

P=local S=283 Apr 19 07:29:46 -

>> exim[12767]: 2005-04-19 07:29:46 1DNnB0-0003Jh-HJ => webmaster


>> < <mailto:webmaster@freesco.zapto.org> webmaster@???>

R=localuser T=local_delivery Apr 19

>> 07:29:46 - exim[12767]: 2005-04-19 07:29:46 1DNnB0-0003Jh-HJ

Completed

>>


>> Anyone having a clue what's wrong ?


>> Thanks a lot in advance,


>What happened when you tried the suggestion you received when you

posted this question

yesterday?

>Peter


Well that advice was to set the exim binary setuid to root like this :
chmod 4755 exim-4.50-2
Which I did. It worked. I could send and receive emails ( sending had
always worked).

So I decided to install it on another Box ( I'm creating a so-called
add-on package for a small Linux distrib called FREESCO).

But I realized while installing on a freshly installed system, that with
no entry in /etc/passwd for group 1000 it doesn't work.

Apparently setuid to root solved only a part of my problem that is the
user part, the group part I don't know about and have searched the exim
FAQ without success.
That's why I'm asking it again, because first I had exim running on my
box with delivery not working (refer to old post that was 4 days ago),
and now on another computer I have no exim running at all because it
won't start with this "cannot run initgroup()" issue.
So I'm wondering, is it the same problem ? I'm quiet a nooB here...if
anyone can help me, I'd be thankfull.

I have tried to chown the entire spool directory to root.root or to
chmod it to 777, but nothing !


If someone has already had something like that I'd be glad to here from
you !
Thanks again,
Mathieu CATTIN.