Copyright (C) 2000-2012 |
Manpages metasendSection: User Commands (1)Updated: Release 1 Index Return to Main Contents NAMEmetasend - Crude interface for sending non-text mailSYNOPSISmetasend [-b] [-c cc] [-F from] [-e encoding] [-f filename] [-m MIME-type] [-s subject] [-S splitsize] [-t to] [-z] [-n] [-D content-description] [-o outputfile] [-/ multipart-subtype] [-E] [-P preamble-file]DESCRIPTIONThe metasend program will allow a user to send one or more pre-existing data file as non-text multimedia mail.With no arguments, the program will ask the user for the To, Subject, and CC fields. It will then ask for the name of a MIME content-type. Next, it will ask the user for the name of an existing file containing that type of data. After this, it will ask what encoding type, if any, should be applied to this data. Finally, it will ask if the user wants to include information from an additional file, in which case the last three questions will be repeated for the next file. Alternately, all of this information can be provided on the comand line, using the following options:
This is intended largely for mail hackers. A much friendlier interface to non-text mail is provided by mailto(1). If more than one file is given, the parts will be combined into a single multipart MIME object. The mail will be delivered using the splitmail(1) program, so if it is very long it will arrive as several pieces which can be automatically reassembled by metamail. The definition of "very long" can be altered using the -S flag or the SPLITSIZE environment variable, as described in the splitmail(1) man page. SEE ALSOaudiosend(1), mailto-hebrew(1), mailto(1), metamail(1), mmencode(1), splitmail(1)BUGSShould do a better job of choosing the encoding if you don't specify one.Should do MIME syntax checking on user-supplied content-type fields. Users are all too likely to provide bogus MIME content-type values, alas. In particular, there are various characters that are not allowed in parameters unless the parameters are enclosed in double quotes, but this sort of restriction is hard to enforce in a shell script! COPYRIGHTCopyright (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. AUTHORNathaniel S. Borenstein, Bellcore
IndexThis document was created by man2html, using the manual pages. Time: 21:24:56 GMT, November 13, 2024 |