On Tue, 6 Feb 2007 22:35:05 +0100

As a previous poster has surmised your port 25 may be blocked. That is
not your only problem. Many many systems will (correctly) refuse port
25 SMTP sessions from end-user accounts, as those sessions are almost
always 100% spam.
The solution is to use a smarthost for your outbound mail. Using a
smart host via SMTP AUTH on ports 465 or 587 gets you around the port
25 blocks.
Gmail will allow SMTP AUTH connections, and will relay your mail for
you. Set your smart host to smtp.gmail.com use STARTTLS to initiate the
SSL connection; use your Gmail username (including @gmail.com) and your
Gmail password. 

You will have to read up on Sendmail and SSL, but basically you will
need entries similar to these in your local.mc file:

FEATURE(`authinfo',`hash /etc/mail/auth/client-info')dnl
define(`CERT_DIR', `MAIL_SETTINGS_DIR`'certs')
define(`confCACERT_PATH', `CERT_DIR')
define(`confCACERT', `CERT_DIR/CAcert.pem')
define(`confSERVER_CERT', `CERT_DIR/mycert.pem')

I have had mixed luck using smtp.gmail.com reaching systems which use
some rbls for spam blocking, as gmail gets listed often as a spam
However, there are some excellent third party systems out there
specifically designed to provide the very SMTP service you need. The one
I have direct experience with is dyndns.com. You can set up your
sendmail to use them to relay for you. Their service is called MailHop
Relay https://www.dyndns.com/services/mailhop/relay.html and goes for
about $40/Year
Best Regards


\ /    ASCII Ribbon Campaign        -  Motor Vessel Tamara B
 X   against HTML email & vCards    -  http://www.tamara-b.org
/ \

Attachment: signature.asc
Description: PGP signature

Reply via email to