1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
$NetBSD: patch-ah,v 1.3 2004/03/29 02:17:24 snj Exp $
--- man/mailto.1.orig 1994-02-09 12:29:12.000000000 -0800
+++ man/mailto.1 2004-03-28 18:08:59.000000000 -0800
@@ -1,6 +1,6 @@
.TH MAILTO 1 "Release 1" "Bellcore Prototype"
.SH NAME
-mailto - Simple mutlimedia mail sending program
+mailto - Simple multimedia mail sending program
.SH SYNOPSIS
.ta 8n
\fBmailto\fP [-a] [-c] [-s] [recipient name(s)]
@@ -74,7 +74,7 @@ multimedia mail generator. There are, a
Basically, mailto can include the following things in mail:
-1. Simple formatted text, using the MIME type "text/richtext". This allows you to add emphasis to your message using underlining, bold text, italic (diaplsyed as reverse video), centering, and the like.
+1. Simple formatted text, using the MIME type "text/richtext". This allows you to add emphasis to your message using underlining, bold text, italic (displayed as reverse video), centering, and the like.
2. Non-text data. Metamail can include pictures, sounds, and other non-textual data in the middle of any mail message. The mailcap configuration mechanism can even make this process reasonably user-friendly, but a knowledgable user can include non-textual data even in the absence of a proper mailcap entry.
@@ -230,7 +230,7 @@ The .mailrc file in your home directory
dot -- controls whether or not a period alone on a line
should be interpreted as terminating your mail
ignore -- controls whether or not interrupts are ignored
- verbose -- controls the verbosity of output from /usr/lib/sendmail
+ verbose -- controls the verbosity of output from /usr/sbin/sendmail
quiet -- controls the verbosity of output from the mailto program.
keepblind -- controls whether or not a 'blind' copy of the mail is kept.
commasonly -- controls whether or not a space character
@@ -275,7 +275,7 @@ The mailto program reads both the aliase
.I
Altered editing behavior:
-The ~e and ~v commands, which are used to edit the message being composed, will behave differently in mailto if the mail includes non-text portions. In such cases, each part will be edited separately, in sequence, which makes it impossble for the user to accidentally mess up the inter-part boundaries. Moreover, if the mailcap entry for a given data type includes an "edit" field, the user will be given the choice of editing with the program named there or editing with his usual (text) editor. In most cases, this will be a choice between using a structured editor or editing the raw data stream.
+The ~e and ~v commands, which are used to edit the message being composed, will behave differently in mailto if the mail includes non-text portions. In such cases, each part will be edited separately, in sequence, which makes it imposisble for the user to accidentally mess up the inter-part boundaries. Moreover, if the mailcap entry for a given data type includes an "edit" field, the user will be given the choice of editing with the program named there or editing with his usual (text) editor. In most cases, this will be a choice between using a structured editor or editing the raw data stream.
.I
Altered behavior for large messages:
@@ -283,7 +283,7 @@ Mailto delivers your message using the s
.I
New -r command-line option
-The -r comand-line option is not found in standard Berkeley mail.
+The -r command-line option is not found in standard Berkeley mail.
.SH SUMMARY OF OPTIONS
-a <charset> -- specifies an alternate character set in use. This had better be the one your terminal is actually using. Currently it must be in the iso-8859 character set family.
|
