Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   14563 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

patch-metamail(1)					     patch-metamail(1)

NAME
       patch-metamail - Install a patch to the latest metamail release

SYNOPSIS
       patch-metamail	source-tree-root patch-number [hostname [dirname [pre‐
       fix]]]

DESCRIPTION
       The patch-metamail program will attempt to retrieve a  patch  file  for
       the metamail distribution, using anonymous ftp to a trusted server, and
       then install that patch in your local copy of the distribution.

       The first two arguments, which are required, are the root directory  of
       your local copy of the metamail source directory, and the patch number.
       The former is site-dependent, the latter is patch-dependent.

       In general, patch-metamail is intended to be called via metamail,  with
       a mailcap entry like the following:

       application/x-metamail-patch;patch-metamail  source-tree-root  %{patch‐
       number}; needsterminal

       The default values for the host	to  ftp	 to,  the  directory  name  to
       retrieve	 the  file from, and the patch file name prefix are hard-wired
       to thumper.bellcore.com, pub/nsb, and "mm.patch.".  While you can over‐
       ride these on the command line, it would be a big mistake to make these
       parameterized based on the contents of a	 mail  message,	 because  then
       someone	could spoof you into retrieving a new version of metamail with
       a Trojan horse from their site!	However, as long as you retain control
       over  what host and directory the patches are retrieved from, this pro‐
       gram is reasonably safe (as safe as the host you're depending on,  any‐
       way).

SEE ALSO
       metamail(1)

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  per‐
       taining to this material without the specific, prior written permission
       of an authorized representative of Bellcore.  BELLCORE MAKES NO	REPRE‐
       SENTATIONS  ABOUT  THE ACCURACY OR SUITABILITY OF THIS MATERIAL FOR ANY
       PURPOSE.	 IT IS PROVIDED "AS IS", WITHOUT ANY EXPRESS OR	 IMPLIED  WAR‐
       RANTIES.

AUTHOR
       Nathaniel S. Borenstein, Bellcore

				   Release 1		     patch-metamail(1)

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome