Thanks all who commented. I am very clear now on how things should proceed. I initially expected the issue to be in my code, not SDSC Syslog. I'll change my code back to include the CRLF tomorrow.
Rainer > -----Original Message----- > From: Devin Kowatch [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 24, 2003 8:18 PM > To: Rainer Gerhards > Cc: [EMAIL PROTECTED] > Subject: Re: RFC3195 RAW question > > > On Thu, Jul 24, 2003 at 11:22:49AM +0200, Rainer Gerhards wrote: > [ snip ] > > To me, this initally looked like while there is no content-type > > specified, the message still contains the (then empty) MIME header. > > Which is then terminated by CRLF. While working with SDSC, > I found that > > it does NOT expect the CRLF to be present (in fact, it > fails, if it is). > > I then looked through 3195, 3080 and 2045 and nowhere found > mentioned > > that this CRLF must be present. RFC 3080 says in 2.2: > [ snip ] > > As others have said, I believe this to be a bug in SDSC > Syslog. In fact > I think that handling of MIME headers got forgotten about, see bug > #777108 for tracking this issue. > > -- > Devin Kowatch > [EMAIL PROTECTED] >
