Hi,
* Meng Wong Wong via RT <bug-Mail-Audit@rt.cpan.org> [02-01-15 07:26]:
Show quoted text>[yooden@vranx.de - Thu Jan 3 19:00:11 2002]:
>
>> if the mail is changed mith fix_pgp_headers() before that,
>> the Content-type: header is only /added/, not replaced, leaving the
>> old text/plain header intact.
>>
>> I therefore propose to replace the put_header() in fix_pgp_headers()
>> with replace_header().
>>
>
>I am developing v2.1 of Mail::Audit. I have added MIME support.
Would that include RFC 2015? Do you know about my patch to ignore RFC
2015 compliant mails in Mail::Audit::PGP?
We're talking about encrypted mails here, and my limited knowledge
about MIME is mostly about the structure of encrypted mails, and
patchy at that.
What happens is that Mail::Audit::PGP adds a Content-Type header that
says 'application/pgp'. The problem is the 'add', because the
Mail::Audit::get() (using Mail::Header::get()) returns the first
Content-Type header it finds, which is the original one. (It is also
possible that it returns an undetermined header, sometimes the first,
sometimes another one, which wouldn't help.)
Mail::Audit::PGP adds a second Content-Type header, which may even be
legal, but is a bad idea in any case.
Show quoted text>1) if the message is not MIME, upgrade it to mime by adding a MIME-Version header.
I guess it needs more than a header to make a mail MIME.
Show quoted text>2) if the message is MIME and has only one part whose content-type is plain/text, but contains a PGP message,
>
>3) mark it up with the appropriate MIME headers to indicate PGP content.
That would be the easiest case, and that would work. There will
probably be problems with encrypted attachements or more complicated
MIME structures.
Please tell me if I can be of any help.
Thorsten
--
The privacy of correspondence, posts and telecommunications shall be inviolable.
- Grundgesetz, Artikel 10, Abs. 1
