Re: Mailing articles as message/rfc822

Hello!

On 25 Feb 2004 at 09:57 +0100, Urs Janßen wrote:

> On Tue, Feb 24, 2004 at 05:22:00PM +0100, Elmar W. Tischhauser wrote:
> > 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.
> 
> this is on (my) TODO-list for some time now (and IIRC Dirk already
> implemented this for the the -M/-N batchmode).

Indeed, I had a look at save.c. However, I doubt whether the
noninteractive case can easily be transferred to the interactive one.

> > 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 [...]
> 
> correct place would be inside mail_loop() (or submit_mail_file())
> around the related comment:
>             /* TODO: wrap article into message/rfc822? */
> ,-)

Thanks, I should have rgrep'ed for "message/rfc822" ;-)

But isn't mail_loop() a way too general place to do that wrapping? It
seems to be called in some very different scenarios: bugreporting,
replying by mail, mailing/forwarding articles, ...

Assuming that the latter case is the only one where tin has to use
message/rfc822, mail_loop/submit_mail_file need at least some context in
order to distinguish between a regular mail and a forwarded article to
treat them differently.

I'm a novice to tin's code, but the best place for that decision seems
to be mail_to_someone(), setting a flag or an additional parameter of
mail_loop(), indicating: "This is a forwarded article, requiring some
special treatment".

On the other hand, this flag would have impact on quite a few functions
in post.c, as submit_mail_file() cannot pass the article to
rfc15211522_encode() unconditionally: The headers of a message/rfc822
mail would require encoding, while the body should be excluded from
further modifications (e.g., conversion to quoted-printable).

Of course, even more problems arise when taking into account that the
user could edit the mail before forwarding it. Appending text below the
original article should be fine, but inserting annotations above would
probably require converting the mail to multipart/mixed, with a
text/plain part for the annotations and a message/rfc822 part for the
original article...

Regards,
Elmar

PS. I have excluded tin-users from the Mail-Followup since tin-dev seems
to be a better place for this discussion.

-- 
[ GnuPG: D8A88C0D / 2407 063C 1C92 90E9 4766 B170 5E95 0D7F D8A8 8C0D ]
·······································································
  Suchen wir unsere Zuflucht bei den Reihen!              -- L. Euler

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

iD8DBQFAPP86XpUNf9iojA0RAt2BAKCA51bJ6nj98r1WC0Cp5mYt/YgckgCcDndw
u2ntcqvz6G2cef3sH4Wa2iM=
=jah2
-----END PGP SIGNATURE-----