
At 02:39 AM 10/18/1997 +0000, Attila T. Hun wrote:
as Bill also pointed out, somethings could be done via the EHLO extensions, but the limitations would be to great. secondly, as Jon Callas points out, there is the option of TLS via SSL. however, that takes the wrapper off in a store and forward situation and you can not control the hops.
** what I had in mind: ** literally a point to point, port to port daemon pair --operating in a trusted pair mode.
Besides doing things at the SMTP, IPSEC, or SSL layers, another approach is SSH. You could build an application-specific relay (e.g. something sitting on your machine receiving SMTP and something sitting on your mailhost relaying it to sendmail), but SSH does close enough to that that it may be the way to go, except for occasional annoyances about who can use Port 25. Also, there are two mail protocols to address - smtp for sending, but pop3 (or imap4) for mailbox-retrieval. Using either SSH or IPSEC or something SSL-based can help you cover the POP3 end as well. On the other hand, you can also use Hotmail or a Hotmail clone with SSL and bypass the whole process. Or you can use a PGP-equipped remailer. Thanks! Bill Bill Stewart, stewarts@ix.netcom.com Regular Key PGP Fingerprint D454 E202 CBC8 40BF 3C85 B884 0ABE 4639