From: Jochen_Hayek@ACM.org
Subject: Re: Pterodactyl Gnus and MIME attachments
Date: Tue, 17 Nov 1998 22:05:27 GMT [thread overview]
Message-ID: <r8zp9qhsx3.fsf@Hayek5.derwent.co.uk> (raw)
In-Reply-To: <m390havn7a.fsf@sparky.gnus.org>
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Jochen_Hayek@ACM.org writes:
>> Nowadays (I'm currently using 0.40) the mail body gets deleted,
>> if I try do change it in edit mode and save it.
LMI> Fixing article editing is something that will be done after MIME
LMI> composition has been figured out.
Sure, you have to assign priorities to tasks.
I understand that.
But some people keep sending me huge, I mean really huge attachments,
that I must get rid of, in order not to fill up my disk with garbage.
For now (and verly long) for the edit-mode
I would be glad to get the plain message with all its attachments as they are.
If I screw it up, it's my responsibility,
but I dealt with it properly before and it worked.
.
next prev parent reply other threads:[~1998-11-17 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 15:33 Jochen_Hayek
1998-11-17 6:38 ` Lars Magne Ingebrigtsen
1998-11-17 22:05 ` Jochen_Hayek [this message]
1998-11-18 1:00 ` Lars Magne Ingebrigtsen
1998-11-18 14:16 ` Jochen_Hayek
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=r8zp9qhsx3.fsf@Hayek5.derwent.co.uk \
--to=jochen_hayek@acm.org \
/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).