Re: does dbmail mangle the position of return-path header?

On 03/01/2017 17:33, Reindl Harald wrote:
>
>
> Am 04.12.2016 um 10:54 schrieb Paul J Stevens:
>> On 03-12-16 17:43, Reindl Harald wrote:
>>> BTW: it would also be nice when dbmail could stop reformat existing
>>> headers - spam reports are horrible to read - they are supposed to have
>>> * starting in a new line with a space before
>>
>> I dunno. This is deep gmime stuff

Easily fixed, change GMIME_FOLD_LEN in gmime-table-private.h to 
something sensible. rfc 2822 says should 76, must 998, see 
https://www.ietf.org/rfc/rfc2822.txt 2.1.1. Line Length Limits. I've 
recently been running with GMIME_FOLD_LEN 998 and all appears well.

IMO GMIME_FOLD_LEN should either be 998 or configurable.

The bug appears to be breaking the line regardless of a space or tab.

--- gmime-2.6.20/gmime/gmime-table-private.h.orig  2017-01-04 
18:01:10.047320423 +0000
+++ gmime-2.6.20/gmime/gmime-table-private.h       2017-01-04 
18:01:29.043905537 +0000
@@ -68,4 +68,4 @@
  #define CHARS_PSPECIAL "!*+-/=_"           /* encoded phrase specials 
(rfc2047 5.3) */
  #define CHARS_ATTRCHAR "*'% "              /* attribute-char from 
rfc2184 */

-#define GMIME_FOLD_LEN 76
+#define GMIME_FOLD_LEN 998

I've been hit by this bug too as I'm creating tools to implement dmarc, 
see http://dmarc.org.uk, where signature comes in ok, but can't be 
checked because barfed.

Regards,
Alan

>
> https://bugzilla.gnome.org/show_bug.cgi?id=776825
> _______________________________________________
> DBmail mailing list
> [email protected]
> http://lists.nfg.nl/mailman/listinfo/dbmail
>