chronic irritation : pine making attachments
beartooth
only as an attachment. Why does it do it, and how can this treatment be
suppressed??
With all the cautions against opening attachments, I normally just forgo
forwarding such items.
Today my wife had gotten something with a list of recent retirees from
where we used to work. I gritted my teeth and asked her to forward it,
despite her report that pine was "refusing to forward." (She hadn't
noticed the attachment header it added.)
Much to my surprise, I could read it all without taking special measures;
but I still find it very obnoxious.
--
Beartooth Oldfart, Neo-Redneck, Linux Convert
FC4; Pine 4.63, Pan 0.14.2.91; Privoxy 3.0.3;
Dillo 0.8.5, Opera 8.02, Firefox 1.0.6, Epiphany 1.6.1
Remember I have little idea what I am talking about.
Mario F. Duhanic
> Ever since about 4.4, Pine occasionally insists on forwarding something
> only as an attachment. Why does it do it, and how can this treatment be
> suppressed??
Hm. Doesn't Pine only ask to forward as attachment when
headers are set to "on"?
Regards,
Mario
Eduardo Chappa
:) Ever since about 4.4, Pine occasionally insists on forwarding something
:) only as an attachment. Why does it do it, and how can this treatment
:) be suppressed??
That's because the message was in an attachment to start with. Pine
normally adds all attachments that you received when you forward a
message.
What you see, though, is a feature and a shortcoming of Pine. Let me
explain.
On the one hand, Pine displays for you all attachments of text type when
you read a message. Sometimes, such attachments contain the message you
are being sent. Pine makes it easy for you to read such message. That's a
good thing, I think.
When you forward a message, Pine includes in the attachment field, all
attachments that you received, it includes also the "body" of the original
message. Think of the body of the message, as the "text of the message",
like in this message, the text that you are reading is the message. In the
case of the messages that your wife is forwarding, the person that sent
that message did not write anything in that body (or maybe did, but the
other program sent it as an attachment). Nevertheless, the part, where the
message of the person should have been is empty (or maybe just contains
the signature of such person). This is the bad thing, and this is where
your problem comes in.
An easy (but tiresome) way in which you can solve this problem is by a two
step process. First save the content of the attachment to a file, and then
include the file where the attachment was saved in the forwarded message
(using the ^R command), then delete the attachment from the attachment
field.
Nevertheless, you have to understand, that even though you see no message
in the composer, the message is in the attachemt (in the attachment
field), so the message that you intend to forward is being forwarded, just
not as you thought it would be sent.
I hope this makes sense and helps you understand what's going on.
--
Eduardo
Patches/Help: http://www.math.washington.edu/~chappa/pine/
XML/RSS feed: http://www.math.washington.edu/~chappa/pine/pine.xml
Please send spam to webmaster@localhost
beartooth
That's a different feature -- one I'm used to and like, even though about
the only person I ever forward full headers to prefers them not as an
attachment.
See Eduardo Chappa's message of 12/14/05 -- just above yours in my
reader; I need to study it a while, but I'm sure anything he says is
right. I do know the behavior I'm talking about does not involve full
headers.
Beartooth
> On Wed, 14 Dec 2005 20:06:46 +0100, Mario F. Duhanic wrote:
>
>> On Wed, 14 Dec 2005, beartooth wrote:
>>> Ever since about 4.4, Pine occasionally insists on forwarding something
>>> only as an attachment. Why does it do it, and how can this treatment be
>>> suppressed??
>>
>> Hm. Doesn't Pine only ask to forward as attachment when
>> headers are set to "on"?
>
> That's a different feature -- one I'm used to and like, even though about
> the only person I ever forward full headers to prefers them not as an
> attachment.
I vass rrronnggg, Sharlie! Today I got an odd bounce, told it H (I do have
full headers enabled), got the question you mention, told it NO -- and it
made an attachment. <gnash, snarl>
Apparently the bounce message itself had attachments, and I didn't realize
that, because they were text, so that pine made nice and showed them to
me. And then attached the attachments to my forward, instead of showing
them to my addressee, as I had expected it to do. <sigh>
So Eduardo, if you're still there (i.e., will see this follow-up -- it's
been nearly three months ...), can I do it the easy way?
IOW, once I know something like a bounce message does contain attachments,
and want to forward them with full headers to somebody who can read a lot
more headers than I can hope to, can I just export the whole shebang --
say from my inbox message list -- to shell (*after* turning on full
headers, that is!); start a new message; hit ^R; and import the whole
shebang -- a real message and all attachments -- back into the body of
that new message?
Or do I have to do something tedious?
--
Beartooth Staffwright, PhD Neo-Redneck Linux Convert
Pine 4.64, Pan 0.14.2.91; Privoxy 3.0.3; Dillo 0.8.5
Galeon 2.0.0, Epiphany 1.6.5, Opera 8.52, Firefox 1.0.7
Remember I know precious little of what I am talking about.