We've just set a Linux box (Slackware 10.0).
We have lots of domains, some delivered by SMTP, some by POP3 which are presently downloaded onto an aging MS SBS 4.5 server with Exchange 5.5. We don't want to change that just yet because we're moving offices and will be getting new IP addresses and servers.
The Linux box has two NICs, one of which is connected to the LAN, the other to a DSL firewall/router. We're already using it as a proxy server.
What I'd like to also do is to configure fetchmail and Exim on the box to relay the POP3 accounts to our existing Exchange 5.5 server - we have to do this quickly because it uses the MS pop3 connector which will not be available after we retire the small business server 4.5 box. I'm also very scared of rebooting that machine (from several nasty past experiences), so I don't really want to open it up to put a second LAN card in it.
Here comes the problem:
We've downloaded Exim 4.4 and compiled it up with the following options:
EXIM_GROUP is unspecified.
I've created a user called exim. Exim is just a normal user in the "users" group, because it's the only one on the box apart from me and root.
make install has to be executed as root, so the files in the installation directories all have -rwxr-xr-x root root permissions.
This is probably all down to some stupid permissions problem because I've been working with MS for too long and almost forgotten *nix.
I've read this section on the Exim help, but it doesn't seem to make sense to me - see section 5.2. http://www.exim.org/exim-html-4.40/doc/html/spec.html
If I chown/chgrp all the files (which surely I have to because I don't want to run as root) to exim/users, su to exim and then ./exim -bd I get the following error (3 times):
"Exim configuration file /usr/exim/configure has the wrong owner group or mode"
Can somebody with a running Exim please let me know how you have set the compile options/ user permissions/groups because this is getting really frustrating.
If I try to run it as root (which I shouldn't) it does get a lot further, but won't relay because of the "never_users" of root - this isn't really the right way to do it so fixing the permissions is really the answer I'm looking for.