Hi,

I have a customer with trouble reading emails from one business partner, all other emails comes through.

I have located the problem to an extra "\r" (Carriage Return 0x0d) i the incoming mail header.

According to RFC-2822 (http://tools.ietf.org/html/rfc2822):
* The body is simply a sequence of characters that follows the header and is separated from the header by an empty line (i.e., a line with nothing preceding the CRLF).


Part of a problem header:

Subject: KxxxxS + "\r\n"
X-PHP-Originating-Script: 508:ajax_final_step.php + "\r\n"
MIME-Version: 1.0 + "\r\r\n"
Content-type: text/html; charset=UTF-8 + "\r\r\n"
From: BxxxxxS <noreply@bxxxxxxs.dk> + "\r\n"
Message-Id: <20140801090439.77DBB3D22031@server01.lxxxx.dk> + "\r\n"
Date: Fri, 1 Aug 2014 11:04:39 +0200 (CEST) + "\r\n"


With GWIA 2012 version 12.0.2 "03/25/13" running on SLES 11 SP1, the above header translate into:

Subject: KxxxxxS + "\r\n"
X-PHP-Originating-Script: 508:ajax_final_step.php + "\r\n"
MIME-Version: 1.0 + "\r"
"\r\n"
Content-type: text/html; charset=UTF-8 + "\r"
\r\n"
From: BxxxxxS <noreply@bxxxxxxs.dk> + "\r\n"
Message-Id: <20140801090439.77DBB3D22031@server01.lxxxx.dk> + "\r\n"
Date: Fri, 1 Aug 2014 11:04:39 +0200 (CEST) + "\r\n"


This means that the header ends before "Content-type: text/html; charset=UTF-8" and the user gets an empty email.
The contents can been seen in "message source", but with all the header and HTML ****, and normal users can't decode the content.

Is this a Groupwise GWIA problem or a problem at the business partner?
The partner say outgoing email works with Gmail, Exchange, Office 365 and Notes - and will not fix.

If just RFC-2822 was more precise and did not contain the I.E. in "(i.e., a line with nothing preceding the CRLF)".

Kind regards
Uffe Bager