On Sat, 4 Oct 2008, UUN Hostmaster wrote: > Each continuation line is preceded by a return (/n) and tab (/t). > However, the value for h= has a extra space in front of Content-Type: > and MIME-Version.
Yep, this is intentional. I wanted continued values within the header to be indented a bit more to show that it's a continued value within a continued value. In fact, I'd like to add that for other values that might wrap, such as bh=, b= and z=. > I run milter-null and it looks for Date: and Message-ID:, followed by a > space, anywhere in a bounce message. It is confusing the DKIM-Signature > continuation line as part of the Message-ID: Sounds more like an issue with milter-null. Shouldn't it be looking for lines that start with "Date: " and "Message-ID: " rather than for those strings anywhere in the message? As it is right now (based on your description) this won't be the last instance of it mis-identifying a message. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
