public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Henry Yen <blinux-mail@AegisInfoSys.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Extracting Binaries from MIME-Encoded messages
Date: Fri, 18 Jun 2004 15:46:01 -0400	[thread overview]
Message-ID: <20040618154601.A19764@AegisInfoSys.com> (raw)
In-Reply-To: <200406181528.i5IFSd1E093655@dc.cis.okstate.edu>; from Martin McCormick on Fri, Jun 18, 2004 at 10:28:39AM -0500

It sounds to me that your issue is more of how to extract the attachments
and less of what to do with them once extracted.  As mentioned in other
threads, munpack, uudecode, etc., are various base64 decoders.

For automatic processing of attachments, I've used the "mhn" utility
with success in scripts, although it seems to be split into multiple
commands in recent releases.  It's a little more complicated than your
usual unix/linux utility, but once you've got it set up, it works fine.

Also, you might want to consider the "mutt" mail client, which
is a full-screen (not graphical) program that handles attachments
as well.  It operates similar to elm and pine.

On Fri, Jun 18, 2004 at 10:28:39AM -0500, Martin McCormick wrote:
> 	I use nmh for reading Email.  This user agent places each
> incoming message in to a directory with the name of a given folder
> such as inbox for all messages that don't belong in other folders.  Is
> there a good utility for stripping attachments out of a message when
> it may contain one or more?
> 
> 	The manual process is to copy the message to some scratch
> file, run vi on the scratch file and look for base64 which is one type
> of encoding, and then strip away all but the garbage of the 7-bit data
> which is the base64 representation of the binary.  Then, I run a perl
> script that has been out on the Internet for years which is called
> base64decode.  It's standard output is the decoded data stream.
> 
> 	I know that base64 decoding is part of many applications so I
> want simply to be able to extract attachments that aren't understood
> or can't be displayed such as sound files, etc.

-- 
Henry Yen                                       Aegis Information Systems, Inc.
Senior Systems Programmer                       Hicksville, New York


  parent reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Martin McCormick
 ` Kirk Reiser
 ` Mike Gorse
 ` Henry Yen [this message]
   ` Hart Larry
 Karl Dahlke
 Martin McCormick
 Martin McCormick
 Martin McCormick

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=20040618154601.A19764@AegisInfoSys.com \
    --to=blinux-mail@aegisinfosys.com \
    --cc=blinux-list@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).