user mailman was not found

dragon234

Member
Nov 11, 2003
6
0
151
hi,

I run /scripts/eximup --force .. but i get the error..

even upgrade whm to edge version ... still not working
how can i solve it??


May 29 10:03:07 server2 exim: exim shutdown failed
May 29 10:03:07 server2 exim: antirelayd shutdown succeeded
May 29 10:03:07 server2 exim: spamd shutdown succeeded
May 29 10:03:08 server2 exim: 2006-05-29 10:03:08 Exim configuration error in line 795 of /etc/exim.conf:May 29 10:03:08 server2 exim: user mailman was not found
May 29 10:03:08 server2 exim: exim startup failed
May 29 10:03:08 server2 exim: 2006-05-29 10:03:08 Exim configuration error in line 795 of /etc/exim.conf:May 29 10:03:08 server2 exim: user mailman was not found
May 29 10:03:08 server2 exim: exim startup failed
May 29 10:03:08 server2 exim: 2006-05-29 10:03:08 Exim configuration error in line 795 of /etc/exim.conf:May 29 10:03:08 server2 exim: user mailman was not found
May 29 10:03:08 server2 exim: exim startup failed
May 29 10:03:08 server2 exim: antirelayd startup succeeded
May 29 10:03:08 server2 exim: spamd startup succeeded
exim has failed, please contact the sysadmin.
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,437
34
473
Go on, have a guess
Appears to be a bug. The following should get you going again:

useradd mailman
/scripts/reinstallmailman
/scripts/buildeximconf
 

Mysteerie

Well-Known Member
Dec 29, 2003
128
0
166
Yes, this also solved my problem about mailman and even syntax error I was recieving. However, he asks a good question.
 

HappymanUK

Well-Known Member
May 3, 2003
255
1
168
I've tried running this, but get stuck at the first stage, I get the following error towards the end of the script:

Re-run as mailman (or root) with -f flag to fix
Warning: Private archive directory is other-executable (o+x).
This could allow other users on your system to read private archives.
If you're on a shared multiuser system, you should consult the
installation manual on how to fix this.

Is this OK ?? - I have tried running again as root with the -f flag, but it still says the same thing.

Any ideas ?

Thanks
Daniel