Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Bihlmeyer <e9426626@stud4.tuwien.ac.at>
Subject: Re: extra .ATT attachments?
Date: 16 Sep 1999 20:27:24 +0200	[thread overview]
Message-ID: <lfogf2yann.fsf@mars.zserv.tuwien.ac.at> (raw)
In-Reply-To: Nathan Williams's message of "16 Sep 1999 11:40:27 -0400"

Hi,

>>>>> On 16 Sep 1999 11:40:27 -0400
>>>>> Nathan Williams <nwilliams@primeon.com> said:

 Nathan> However, I think that in the case that brought this up, it is
 Nathan> expected that the signature be part of the traditional
 Nathan> message body.

There is no "traditional message body" per se. It is a mime message
consisting of three parts. If MS Outhouse can't dig that, I don't
know.

I think of attachments being attached to a *specific*point* in the
message. I frequently write 

,-
| blabla
|
| Here's the new version of foo.pl
|
| [MML-code that attaches foo.pl]
|
| bar.pl is unchanged, but you'll need to install the new baz.pm, too:
|
| [MML-code that attaches baz.pm]
|
| blabla, signature, end
`-

I don't want my attachments moved around, I want them exactly where
they are.

One thing that has come up before is a simple "attach this to the
message" command. This one could tack the attachment onto the end of
the message, if we want this.

        Robbe

-- 
Robert Bihlmeyer	reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>	<http://stud2.tuwien.ac.at/~e9426626/sig.html>


  reply	other threads:[~1999-09-16 18:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-16  7:19 Jaap-Henk Hoepman
1999-09-16 15:08 ` Nathan Williams
1999-09-16 15:34   ` Lee Willis
1999-09-16 15:40     ` Nathan Williams
1999-09-16 18:27       ` Robert Bihlmeyer [this message]
1999-09-25  9:28       ` Lars Magne Ingebrigtsen
1999-09-16 15:20 ` Jack Vinson
1999-09-16 16:57 ` Toby Speight
1999-09-16 17:25   ` Jody Klymak
1999-09-16 18:28     ` David S. Goldberg
1999-09-18 21:07       ` Kai Großjohann
1999-09-17 21:40 ` Jack Vinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=lfogf2yann.fsf@mars.zserv.tuwien.ac.at \
    --to=e9426626@stud4.tuwien.ac.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).