From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: Remove attachments
Date: Sun, 05 Aug 2001 12:50:42 -0500 [thread overview]
Message-ID: <q6md76apf9p.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: <87puafctxz.fsf@smarttrust.com> (Nuutti Kotivuori's message of "Thu, 02 Aug 2001 01:10:48 +0300")
>>>>> On Thu, 02 Aug 2001 01:10:48 +0300,
>>>>> Nuutti Kotivuori <nuutti.kotivuori@smarttrust.com> (nk) writes:
nk> IMAP does not support article editing. The only way is to delete and
nk> create a new article.
I've noticed that when PINE does this it replaces the attachment
deleted with a little blurb that says 'attachment deleted', or
something like that. So the basic structure of the message does not
appear to be altered.
--
Amos
prev parent reply other threads:[~2001-08-05 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 14:30 Nicolas Kowalski
2001-08-01 14:45 ` Karl Kleinpaste
2001-08-01 15:18 ` Nicolas Kowalski
2001-08-01 15:38 ` Kai Großjohann
2001-08-01 19:21 ` Jon Allen Boone
2001-08-01 22:10 ` Nuutti Kotivuori
2001-08-05 17:50 ` Amos Gouaux [this message]
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=q6md76apf9p.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/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).