Mailing articles as message/rfc822

Hello to all,

I'm wondering whether it is possible to mail usenet articles as
message/rfc822 instead of simply including the whole article in the mail
body.

For example, the current (default?) behaviour is causing trouble when
the original article's character set doesn't match my local one. This
way, an incorrect charset will be specified for the whole mail.

In addition to that, wrapping the article into message/rfc822 would
enable MUAs to display only selected headers or easily operate on the
forwarded usenet article at a glance.

Since I was unable to find an appropriate configuration variable, I
digged a little in the source and modified src/post.c:mail_to_someone()
to include additional MIME headers (MIME-Version: 1.0, Content-Type:
message/rfc822, Content-Disposition: inline; Content-Transfer-Encoding:
copied from the original usenet article).
However, these settings did not prevail, as rfc15211522_encode()
(invoked from src/post.c:submit_mail_file()) decided to parse the whole
body and add the usual "Content-Type: text/plain; charset=ISO-8859-15"
again; regardless whether the mailed article was encoded in UTF-8 or
whatever.

Obviously, I have to make myself more familiar with either tin's code or
its configuration mechanisms :)

Thanks in advance for any hints or suggestions.

Regards,
Elmar

-- 
[ GnuPG: D8A88C0D / 2407 063C 1C92 90E9 4766 B170 5E95 0D7F D8A8 8C0D ]
·······································································
  What is wanted is not the will to believe, but the will to find out
  - which is the exact opposite.                  -- Bertrand Russell

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAO3ooXpUNf9iojA0RAjWEAJ9SD2dh/GhiBYb8UMjW0soQ2sm5KwCfQlzD
HHnr6P281a7RNEdTHWCjpTc=
=+mDu
-----END PGP SIGNATURE-----