Alec Berryman said:
> ...
> I've never used SSMTP, but doesn't it need to be started with
> `/etc/init.d/ssmtp start` before it can actively send mail?
>From `man ssmtp`:
SSMTP(8)
NAME
ssmtp, sendmail - send a message using smtp
SYNOPSIS
ssmtp [ flags ] [ address ... ]
/usr/lib/sendmail [ flags ] [ address ... ]
DESCRIPTION
ssmtp is a send-only sendmail emulator for machines which normally pick
their mail up from a centralized mailhub (via pop, imap, nfs mounts or
other means). It provides the functionality required for humans and
programs to send mail via the standard or /usr/bin/mail user agents.
It accepts a mail stream on standard input with recipients specified on
the command line and synchronously forwards the message to the mail
transfer agent of a mailhub for the mailhub MTA to process...
Since ssmtp is a "send-only emulator" it does not need to listen on any
port, but instead "accepts a mail stream on standard input". The port 25
on which it s failing to open a connection is on the *upstream* server,
then.
See my previous posting or the man page to find out where ssmtp.conf is
cunningly concealed. In that file it is possible to configure the upstream
mailserver which ssmtp will try to connect to.
I suggest the OP runs ssmpt with the -v (verbose, like me) flag until he
sure he is able to send mail sucessfully. The command:
$ ls | sstmp -v [EMAIL PROTECTED]
works very satisfactorily on my system - I am able to check my pop3
account a few minutes later to see a directory listing.
Use the /etc/ssmtp/revaliases to enable the cron daemon to deliver the
results of its schedule by email B-].
Hope this is of help to someone,
Stroller.
--
[EMAIL PROTECTED] mailing list
