I appreciate the suggestion, Bob, and thanks for the direct answer as well, but I support the notion that SMTP is a critical infrastructure these days, and if we are offered packet-delivery service, then we should also expect decent mail-delivery along with that. If my mail gets mangled, then I'd complain as much as if I suffer power brown-outs... or dirty water from the tap. I know it is not currently a *safe* assumption, but it is one that I would like to see become status quo, like out other aspects of our infrastructure (in these united states, anyway, where we are spoiled and also expect all sorts of sanitary standards, for instance). I like to project a vision of Tomorrow which includes free network access (including 2-way email services and more than the "interweb", ie port 22 NOT blocked), although as a geek I certainly appreciate knowing how to get around the annoyances of Today. Thanks again, Bob = )
regards and shanti, via adelphia.net, Ben Barrett PS - Now I wish I had gpg/pgp setup, so I could sign this and be assured that my message is NOT mnageld... PPS - I *was* going to use ipsec while traveling this time, but... too much last-minute paid work got in my way = ( On Mon, 29 Sep 2003 11:43:01 -0700 Bob Miller <[EMAIL PROTECTED]> wrote: | Ben Barrett wrote: | | > PS - I had to do some minor sleuthing to figure out the SMTP server | > for this free wifi location; they are running InterMail | > vM.5.01.05.32 and I used both the message source of a mail I was | > able to send to myself from my home ISP's SMTP, and'dig MX<domain>' | > (then'telnet<mailhost> 25') to figure that out... glory be to FOSS! | > BTW, does anyone have any suggestions to more-easily figure out | > local SMTP's for random internet access locations? traceroute | > didn't work...(they also seem to block some pings, incidentally -- I | > couldn't ping home, even though I could access home by web -- but I | > can ping google) | | If you have a home base, use ssh to tunnel SMTP through your home base | to your normal SMTP server. | | E.g., if your home box is home.base.example.org, and your usual | mail server is mail.example.net, use this command (as root). | | # ssh -f -L 25:mail.example.net:25 home.base.example.org | | Then you never need to find the local smtp server or worry about how | it might restrict/mangle/destroy your mail. | | If you're determined to let an unknown mail server butcher your mail, | then you could start by reverse-DNS mapping your IP address, then look | for MX records for the enclosing domain. | | Another example: | | $ ifconfig eth0 | ... inet addr 1.2.3.4 ... | $ host 1.2.3.4 | 4.3.2.1.in-addr.arpa domain name pointer | dhcp-1-2-3-4.unknown-isp.net$ host -t mx unknown-isp.net | unknown-isp.net mail is handled by 10 postoffice.unknown-isp.net | $ nc postoffice.unknown-isp.net | 220 queue.unknown-isp.net -- ESMTP | ... | | And there you are (if you're lucky). | | -- | Bob Miller K<bob> | kbobsoft software consulting | http://kbobsoft.com [EMAIL PROTECTED] _______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
