--Boundary-02=_Ffy7+IodUsKDf0w Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline
On Tuesday 17 June 2003 09:24 am, Craig Jackson wrote: > True, TLS on 25 doesn't make much sense for the > Cox user. Now the roving > user who has an email server at home may want > TLS-encrypted SMTP to > authenticate to and use his server at home, but > that option has been > eliminated with port 25 blocking. But how many > people use a home email > server that way -- besides me. run your TLS SMTP server with SMTP auth on 8025. point your client at it. = =20 I've done this in the past. Set up a VPN. use ssh. there are several ways = to=20 skin this particular cat. I am currently using a VPN from work to send mai= l=20 through my server at home which then goes out via cox's smtp server. I als= o=20 have a VPN to my corporate office at home and could relay through their mai= l=20 server if I so choose. =2D-=20 Scott Harney <[EMAIL PROTECTED]> "...and one script to rule them all." gpg key fingerprint=3D7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5 --Boundary-02=_Ffy7+IodUsKDf0w Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+7yfF8CR9pgvHlOURAoSAAJ4hUgNs1khIs2yP5SwNyg3dNDzz1QCfWIkr BI4E5nSSZbJlWYOJcC0108M= =IWKa -----END PGP SIGNATURE----- --Boundary-02=_Ffy7+IodUsKDf0w--
