There are a number of neat features in sendmail that I have used in various places. Although there is documentation for this in The Sendmail FAQ and Scripts and Patches for ISP's, there always seems to be some missing details that I have to grub through the .cf source for.
This is the ability to accept mail for arbitrary mail addresses. The basics are explained in the virtual hosting page. Here's the real rules you need and why:
The flip side is that you probably want the outgoing mail for these users to have their virtual domains added on if not there already.
joe@foo.com fred@bar.comfoo.com must be in /etc/sendmail.cG.
When Outlook is setup to use SSL, it just does a normal SSL wrapped conversation for encryption, and does authentication the normal way. In other words, it does not use STARTTLS like Netscape does. On the server end, you can just use stunnel to wrap both these services on the new ports.
Some of these instructions are only applicable if you are useing self-signed certificates.
Also, I have seen mail retrieval stop working for no apparent reason. Restarting outlook seems to fix it.
When you first start outlook, it will complain that it can't verify the certificate because the root certificate is not trusted. Just click ok.
Sendmail will relay (bypassing all IP or other relay checks) if a client authenticates using an AUTH method, or by presenting a valid client certificate.
Turing on AUTH, requires sendmail be compiled with SASL (already done in RedHat 7.x).
For sendmail to use SSL requires that it be compiled with sfio and openssl, plus the generation of certificates.
To make certificate authority: mkdir CA cd CA mkdir certs crl newcerts private echo "01" > serial cp /dev/null index.txt cp /usr/local/openssl/openssl.cnf.sample openssl.cnf vi openssl.cnf (set values) openssl req -new -x509 -keyout private/cakey.pem -out cacert.pem -days 365 -config openssl.cnf To make a new certificate: cd CA (same directory created above) openssl req -nodes -new -x509 -keyout newreq.pem -out newreq.pem -days 365 -config openssl.cnf (certificate and private key in file newreq.pem) To sign new certificate with certificate authority: cd CA (same directory created above) openssl x509 -x509toreq -in newreq.pem -signkey newreq.pem -out tmp.pem openssl ca -config openssl.cnf -policy policy_anything -out newcert.pem -infiles tmp.pem rm -f tmp.pem (newcert.pem contains signed certificate, newreq.pem still contains unsigned certificate and private key)
Also check
According to http://home.netscape.com/products/security/ssl/certformat.html CN="(Uprava|SMTP).ev.co.yu" should work with Netscape. No idea if OE understands it. Of course your CA should allow you to request such a certificate.
Available as Mail::Spamassassin from CPAN. Does a ton of checks to classify mail as spam or not. Uses Razor, Pyzor, and DCC, if installed. Reqires:
A Milter to feed mail through spamassassin. Some people like to run spamassassin from Mime-Defang, but that milter won't let spamassassin re-write the message, and I find the information usefull in tuning spamassassin.
The swiss army knife of milters. It can 'defang' attachments by making them un-executable, or quarentine them. It can also run virus scanners and other stuff like spamassassin.