On 01/-10/-28163 08:59 PM, [email protected] wrote:
> we have a problem with a remote destination ditching encrypted mail
> because of the header included by Djigzo. They claim that according to
> RFC 3851 the S/MIME part must not include RFC822 headers. From what i
> read in RFC 5751 section 3.1 there is a standard format to protect
> headers. Is this special format used by Djigzo or is the remote side
> right at claiming not standard conform S/MIME ?


AFAIK it's not explicitly said that you should or must not add any
headers. The receiving party is way too picky because there should be no
technical reason why the receiving server cannot validate and/or accept
the email. Do you know which S/MIME gateway this is?

Anyway, you can disable any headers being added to the signed or
encrypted part by removing or uncommenting the "protectedHeader" setting
in config.xml

so remove or uncomment in config.xml:

<protectedHeader> subject </protectedHeader>


Kind regards,

Martijn


-- 
Djigzo open source email encryption
_______________________________________________
Users mailing list
[email protected]
http://lists.djigzo.com/lists/listinfo/users

Reply via email to