Re: client requests ending \012

[Michael Scharff <[e-mail]>]

I have to chime in here and protest such a response. This sounds like a 
good reason to go back and insure that CRLF is a MUST and NOT considered 
optional in ANY CASE. I don't understand why it is so difficult to simply 
establish a consensus (which it seems pretty obvious to me that there is 
one, at least on this subject) and move forward with it. There are ALWAYS 
going to be "rogues" who choose not to adhere to, or perhaps to not even 
learn, the standards. This is not what we should be focused on, nor is it 
truly feasible either. What we should be doing is determining REAL, VALID, 
TECHNICAL reasons for or against any specific mechanism or procedure, such 
as CRLF . CRLF


At 01:57 PM 7/25/00 +0100, you wrote:

>         On Tue, 25 Jul 2000 09:43:46 +0100 (BST)
>         Philip Hazel <[e-mail]> said...
>
> >
> > i've got a problem with javamail. I discovered that all apperances of
> > the linefeed character "\n" were changed into an "\r\n" (Carriage
> > Return+Linefeed) while sending the mail to the smtpserver. I'm working
> > with S/MIME Routines and signed Mails so that all Mails had a bad digest
> > (bad signature) because of the changed Mail Body. Is there an option to
> > prevent this modification ?
>
>Which sounds like a good reason not to use S/MIME. PGP (with its '-t'
>option) is especially designed to treat all line endings as CRLF,
>and to disregard trailing whitespace (but not trailing blank lines,
>infortunately).
>
>Charles H. Lindsey ---------At Home, doing my own 
>thing------------------------
>Email:     [e-mail]  Web:   http://www.cs.man.ac.uk/~chl
>Voice/Fax: [phone]      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, 
>U.K.
>PGP: 2C15F1A9     Fingerprint: 73 6D C2 51 93 A0 01 E7  65 E8 64 7E 14 A4 
>AB A5