🚀 go-pugleaf

In article <21650@sbsvax.cs.uni-sb.de>, wilhelm.buehler@midget.saar.de (Wilhelm Buehler) writes:
|> In article <4490@babylon.rmt.sub.org>, rbabel@babylon.rmt.sub.org (Ralph Babel) writes:
|> |Content-Type: text/plain; charset=iso-8859-1
|> |Content-Transfer-Encoding: base64
|> |> TWFydGluIEhvcm5lZmZlciBzY2hyaWViIGluDQo8MTk5MlNlcDI4LjEyNDk1NS4yMjRAZGZ2LnJ3
|> Auch auf die Gefahr mich unbeliebt zu machen, WIE liest man das?

Nimm metamail. Damit kann man verdammt viel lesen! metamail kann man
(eventuell) aus seinem Elm ausbauen (so unser Admin es hier gemacht),
oder man findet es auf irgendeinem FTP-Server - z.B. auf ftp.funet.fi
in /pub/unix/mail/metamail/-.

Hier noch ein kleiner Auszug aus der manpage:

----- 8< -------------------- hier abbeissen -------------------- >8 -----

 METAMAIL(1)                 Bellcore Prototype                  METAMAIL(1)
                                  Release 2

 NAME
      metamail - infrastructure for mailcap-based multimedia mail handling

 SYNOPSIS
      metamail[-b] [-B] [-c contenttype ...] [-d] [-e] [-f from-name]  [-m
      mailer-name] [-p] [-r] [-s subject] [-q] [-x] [-z] [file-name]

 DESCRIPTION
      The metamail program reads a "mailcap" file to determine how to
      display non-text at the local site.  Every mail-reading interface
      needs to call metamail whenever non-text mail is being viewed, unless
      the mail is of a type that is already understood by the mail-reading
      program. Metamail consults the mailcap file(s) to determine what
      program to use to show the message to the user.

      [...]

      Note:  Metamail determines the type of a message using the "Content-
      type" header, as defined in RFC 1049 and RFC XXXX.  However, using the
      -b and -c options, metamail can be made to work with mail that is not
      in Internet format, including X.400 messages.  Note also that metamail
      automatically decodes mail that has been encoded for 7 bit transport
      if the mail includes a Content-Transfer-Encoding header as specified
      by RFC XXXX.

      [...]

 COPYRIGHT
      Copyright (c) 1991 Bell Communications Research, Inc. (Bellcore)

      Permission to use, copy, modify, and distribute this material for any
      purpose and without fee is hereby granted, provided that the above
      copyright notice and this permission notice appear in all copies, and
      that the name of Bellcore not be used in advertising or publicity
      pertaining to this material without the specific, prior written
      permission of an authorized representative of Bellcore.  BELLCORE
      MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY OF THIS
      MATERIAL FOR ANY PURPOSE.  IT IS PROVIDED "AS IS", WITHOUT ANY EXPRESS
      OR IMPLIED WARRANTIES.

 AUTHOR
      Nathaniel S. Borenstein

----- 8< -------------------- hier abbeissen -------------------- >8 -----

     V v
  @/@@=\   Greetings,
    00 &=-          Angela 
oOoO_/` \\_
    \ /&\     Angela Schmidt (IRC: Nessy)           | Amiga //
  |>O<|       Internet: Angela@rz.uni-karlsruhe.de  | 1000 // 
   / \_/\/\/v_   Voice: +49 731 712316  (10am-9pm)  |  \\ // since 
  /____________\ (MET)  +49 721 6904263 (12am-11pm) |   \X/ 1986