Gnus development mailing list
 help / color / mirror / Atom feed
From: Anssi Saari <as@sci.fi>
Subject: Questions about piping and unknown charsets
Date: Fri, 30 Mar 2001 14:08:13 +0300	[thread overview]
Message-ID: <20010330140813.A14970@sci.fi> (raw)


I've had some trouble with mail today. First, I got a an email with a
Framemaker document as attachment. Once upon a time I wrote a perl script
to which I can pipe such mails and attachments get printed. But with Gnus
there's this tiny little problem that I can't pipe the mail as is. If I use |
(i.e. gnus-summary-pipe-output), it doesn't pipe the attachment and if
I right click on the attachment and select pipe to command, it decodes
the attachment before piping it, which breaks my script and anyway, with
multiple attachments it's too much work to pipe them one by one.

Other problem is, I got a mail with this message on top:

This message uses a character set that is not supported by the Internet
Service.  To view the original message content,  open the attached
message. If the text doesn't display correctly, save the attachment to
disk, and then open it using a viewer that can display the original
character set. <<message.txt>> 

That idiocy was probably done by Exchange. So I have an attachment
with iso-8859-1 chars encoded to quoted-printable but content-type is
"TEXT/PLAIN; charset=X-UNKNOWN". How do I fix that in Gnus?  The mail
in on the Exchange server and accessed through IMAP, so Gnus considers
it read-only...

So, any Gnus solutions to these things? I think there should definitely
be a command to really pipe the complete article to a command. Gnus version
I have is Oort snapshot from 20010110.

Anssi Saari


             reply	other threads:[~2001-03-30 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-30 11:08 Anssi Saari [this message]
2001-03-30 23:20 ` Kai Großjohann
2001-03-31 14:10   ` Daniel Pittman
2001-04-02  8:26   ` Anssi Saari

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=20010330140813.A14970@sci.fi \
    --to=as@sci.fi \
    /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).