Well... the telnet link makes me think the SR on a pretty 11/70 as faster way to do it. The local at home stuff is rather odd but actually very efficient as it's edit/compose/reply is all done off line then you deliver (also fetches then). It has many things going for it, one it leaves nothing on the ISP, the connect time is minimal, all headers are visible, being slightly brain dead all worms/viri/trojans _can_ be sent through it safely and files TEXT or UUE greater than 50k are saved to disk and the first 1024 chars displayed. the interface is windows/3.1 so it isn't that bad. <> Sheesh. Plain text really sucks. Y'all prefer that someone type _like thi <> to indicate a piece of underlined text? or my habit *bolding* with <> asterisks? This message "encoded" with HTML is roughly 5% larger than it <> in plain text. Wow, now that's a waste of resources. < < I responded in kind (and also in Postscript, morse code, and uuencoded <DVI). ;) You forgot runoff and latex. Yes, html isn't that much larger but, then so is runoff(same thing really). I can read text from the Epson PX8 laptop... HTML is much to fractured looking for a 80x8 screen. Allison PS: orginal message as I initially see it in the view pane. the first 36 lines are just the header so those that never see it may have a clue. ----------------------------------------------------------------------------