Re: "but" Re: [PCTECH] Need firewall protection,

[Tom Liotta <qsrvbas@xxxxxxxxxxxx>]

Ken:

Sure, I understand the Windows connection to <CRLF>; but if that were 
the cause, it would seem a LOT of e-mail would get screwed up, i.e., the 
behavior would be seen all over the world. In this case, I'm simply 
using Netscape Mail 7.1.

Hmmm... I need to look at these items at the office; I don't think I see 
the same behavior though I try not to hang out in these newsgroups 
(especially CPF0000) at the office. Until David served this bunch of 
newsgroups via his newsserver, I only used Netscape webmail for them. 
Win2K and Netscape 7.1 here and there for these newsgroups now. WinXP 
and Outlook/Exchange for my office-supplied desktop system.

Primary difference is the ISP -- Earthlink here at home. But I'll be 
_VERY_ irritated if I ever find out there's any relationship.

As for whether the client is busted, the strict definition of SMTP 
headers has <CRLF> as the delimiter, so <tabNL> _should_ be okay... I 
think. Technically, if the RFC indicates that <NL> alone is sufficient, 
then YOUR client may be busted, but I highly doubt that. I didn't see 
that possibility last time I scanned through it.

As I always say sometimes, ain't computer tech grand?

Tom Liotta

Ken Sims wrote:
> Hi Tom -
>
> > It makes perfect sense, though when I look at the mail item in hex, I 
> > see <CRLF>. Somewhere between sending and getting it into my client, 
> > the <NL> seems to get changed and that probably fouls up the client.
>
>
> A CRLF is the DOS/Windows standard for a line break (whereas in 
> Linux/Unix it's just a LF and in Apples/Macs it's just a CR) so you 
> can't blame it on that. <G>  In fact, it's probably your client that's 
> converting it from a LF to CRLF.
>
> --
> Ken
> http://www.ke9nr.net/
> Opinions expressed are my own and do not necessarily represent the views 
> of my employer or anyone in their right mind.