:> fetchmail now says: 'Connection refused' or
:> 'no route to host').
:> No smtp transport, or trying to run sendmail which isn't there.
: It's true that sendmail is not there, but I found some links as 'exim'
: tries to behave like it would be 'sendmail'.
Yes, but is it THERE? Is it listening on the port? Apparently not!
:> take out exim and drop in sendmail, or configure exim.
: 'exim' seems to be running, I can check it with 'telnet localhost
: smtp'.
:> : Is there a test for mail-settings ??
:> ??
: I mean like 'telnet localhost smtp', which gives a message about 'exim'
: running, and waits for SMTP commands...
That is the test. If you telnet localhost 25 and get to talk to a daemon,
then there is a daemon running.
: But how to test 'fetchmail' (or POP3 service) ?
I don't understand. Fetchmail has a debug switch and in any case it
either uses an external transport agent or connects to port 25 itself.
-v, --verbose
Verbose mode. All control messages passed between
fetchmail and the mailserver are echoed to stderr.
Overrides --silent.
The latter appears to be your case. And as for testing a service (as
opposed to a client, like fetchmail), just do what you did for the
smtp port, this time on the pop3 port.
: There should be some HOWTOs about 'mail' configuration: what files need
There are whole books written! But you haven't answered the basic
question ... do you have sendmail/exim running? I am 80% convinced that
you have, but fetchmail says that you haven't. So ask fetchmail why
it thinks so. Strace it and run with debugging on. Don't complicate
your life with weird surmises. Just tell us if the smtp daemon is there
or not.
: editing, what errors are possible,... etc.
: Maybe it's a routing problem, but I don't know where to look...
At your routes? You're the one who told fetchmail where to go!
-S host, --smtphost host
Specify a host to forward mail to (other than
localhost).
If I were you I'd set up a pop server and check your maild is OK. (I use
sslwrapped cucipop as a pop server, but the standard pop3d may be OK
for you). In any case, you need to just check the basics. Do you have
it? Is it running? Is it working? You haven't convinced me of any of
those yet. Put them beyond a doubt. I seriously doubt that your
distribution comes with a pop server already set up, for example.
It will be disabled in inetd.conf even if it is on disk.
Peter