source: trunk/athena/lib/zephyr/clients/zwrite/zwrite.1 @ 12655

Revision 12655, 6.9 KB checked in by danw, 26 years ago (diff)
gratuitous automatic CC-adding flag for multiple-recipient zephyrs
Line 
1.\"     $Id: zwrite.1,v 1.22 1999-03-11 04:21:53 danw Exp $
2.\"
3.\" Copyright 1987,1988 by the Massachusetts Institute of Technology
4.\" All rights reserved.  The file /usr/include/zephyr/mit-copyright.h
5.\" specifies the terms and conditions for redistribution.
6.\"
7.\"
8.TH ZWRITE 1 "October 26, 1989" "MIT Project Athena"
9.ds ]W MIT Project Athena
10.SH NAME
11zwrite \- write to another user via Zephyr
12.SH SYNOPSIS
13.B zwrite
14[
15.BI -a
16] [
17.BI -d
18] [
19.BI -v
20] [
21.BI -q
22] [
23.BI -t
24] [
25.BI -u
26] [
27.BI -o
28] [
29.BI -n
30] [
31.BI -l
32] [
33.BI -C
34] [
35.BI -O
36opcode ] [
37.BI -s
38signature ] [
39.BI -c
40class ] [
41.BI -i
42instance ] [
43.BI -r
44realm ] [
45.BI -f
46arg ] [
47.BI user \ ...
48] [
49.BI -m
50.BI message
51]
52.SH DESCRIPTION
53.I Zwrite
54sends a message from you to another user through the
55.I zephyr(1)
56notification service.  The user must have subscribed to messages of
57the appropriate class and instance using the
58.I zctl(1)
59program.
60.PP
61.I Zwrite
62understands the following options.
63.TP 12
64.B \-a
65Causes
66.I zwrite
67to send the message authenticated, using
68.I Kerberos
69to perform the authentication.  This is the default.
70.TP
71.B \-d
72Causes
73.I zwrite
74to send the message unauthenticated.
75.TP
76.B \-v
77Causes
78.I zwrite
79to print what type of message it is sending, and whether or not it was
80successful.
81.TP
82.B \-q
83Forces
84.I zwrite
85to suppress information about whether or not the message was sent.
86.TP
87.B \-t
88Prevents
89.I zwrite
90from expanding tabs in the message into appropriate spaces.  Normally
91.I zwrite
92will expand any tabs it finds into the appropriate number of spaces to
93maintain separation based on 8-character tab stops.
94.TP
95.B \-l
96Causes
97.I zwrite
98to ignore `.' on a line by itself in the input and only end a typed
99message when the user types the end-of-file character (usually
100control-D).  When the input is not a terminal, this is the default action.
101.TP
102.B \-u
103Sends an urgent message.  This changes the
104.I zephyr
105instance of the message to ``URGENT''.
106.TP
107.B \-o
108Causes
109.I zwrite
110to ignore the Zephyr variables
111.IR zwrite-class ,
112.IR zwrite-inst ,
113and
114.I zwrite-opcode
115when picking a default class, instance, and opcode.
116.TP
117.B \-n
118prevents
119.I zwrite
120from sending a PING message to verify the recipient is subscribing to
121messages.  By default,
122.I zwrite
123will send a notice to the destination class, instance, and recipient,
124with opcode ``PING'' before sending the message.  If the PING is sent,
125and the server response indicates there are no recipients subscribed to
126your message,
127.I zwrite
128exits without sending a message.
129When the
130.B \-m
131option is used, no PING is sent.
132.TP
133.B \-C
134prepends a "CC:" line to the body of the message indicating the
135recipients of the message. This is strictly a convenience: the
136presence of a "CC:" line at the top of a zephyr body does not
137necessarily indicate that this option was used, or that the message
138really was sent to the listed users, and its lack doesn't indicate
139that the message was not sent to multiple users.
140.TP
141.B \-s \fIsignature\fR
142sets the signature to be included in the message.  This overrides both
143the user's name (as found in the password file) and any
144setting of the Zephyr variable
145.IR zwrite-signature .
146.I signature
147must
148be a single argument, hence when using a shell it should be quoted with
149double quotes.  A
150.I signature
151argument of "" leaves the signature in
152the message empty.
153.TP
154.B \-c \fIclass\fR
155Allows a user to specify a different class for the message.  This allows
156a message to be sent to a large group of people with some degree of
157security.  See
158.I zephyr(1)
159and
160.I zephyrd(8)
161for a description of how to restrict access to classes.  When this option
162is specified, the message is sent to recipient "*" unless an additional
163list of recipients is specified.
164.br
165This argument may not be used in conjunction with the -f option.
166.TP
167.B \-i \fIinstance\fR
168Allows a user to specify a different instance than the default.
169When this option is used, the message is sent to recipient "*" unless an
170additional list of recipients is specified.  This allows a message to be
171sent to a large group of people (e.g. a development group) just by having
172the members subscribe to messages of class "MESSAGE", the specified instance,
173and recipient "*".
174.br
175This argument may not be used in conjunction with the -f option.
176.TP
177.B \-r \fIrealm\fR
178Allows a user to specify a different realm for the message, if the
179server supports interrealm Zephyr.
180.TP
181.B \-F \fIformat\fR
182Allows a user to specify a different default format for the message.
183.TP
184.B \-O \fIopcode\fR
185Allows a user to specify a different opcode for the message.
186Some Zephyr notice display programs may use the opcode to decide how
187to display a notice.
188.TP
189.B \-f \fIarg\fR
190Allows a user to specify an argument to be interpreted as a filesystem
191specification.  The class is set to
192.BR FILSRV .
193he instance is set
194to
195.I arg
196as modified:
197If
198.I arg
199contains no colons (`:'), it is assumed to
200be a host name, and it is converted into an official host name via
201.I gethostbyname(3).
202If
203.I arg
204contains a colon, the portion preceding the colon is
205treated as a host name, and the colon and any trailing characters are
206appended to the offical host name returned by
207.I gethostbyname.
208If the name fails to resolve into an official host name, the instance is
209set to
210.I arg
211unmodified.
212.br
213This option may not be used in conjunction with the -c or -i option.
214.TP
215.B \-m
216.I Zwrite
217sends the remaining arguments on the command line as the message.
218.PP
219If the
220.I \-m
221option is not specified, the user is prompted for the message to be
222sent.  The message may be terminated by typing ^D or ``.'' on a line
223by itself.
224.PP
225The default class for messages is ``MESSAGE'', the default instance
226is ``PERSONAL'', andthe default opcode is ``'' (an empty string).
227These defaults can be overridden by setting the Zephyr
228variables
229.IR zwrite-class ,
230.IR zwrite-inst ,
231and
232.IR zwrite-opcode ,
233respectively.
234Command-line options can override the defaults.
235.PP
236If the class is ``MESSAGE'' and the instance is either ``PERSONAL'' or
237``URGENT'', a recipient must be specified.  These comparisons are
238case-sensitive.
239.PP
240Unless the
241.B \-s
242option is used, the contents of the Zephyr variable
243.I zwrite-signature
244are used to augment the user's username in the
245message.  If
246.I zwrite-signature
247is not set and the
248.B \-s
249option is not specified, the user's full name (as specified in the
250password file) is used instead.
251.SH BUGS
252Tab expansion should really be done by the receiver of the message.
253.br
254The \-u option is provided for compatibility with old versions of
255.I zwrite
256and is not necessarily useful for sending messages to users who do not
257have old subscription files.
258.SH SEE ALSO
259kerberosintro(1), zctl(1), zephyr(1), zwgc(1), zhm(8), zephyrd(8),
260gethostbyname(3)
261.br
262Project Athena Technical Plan Section E.4.1, `Zephyr Notification
263Service'
264.SH FILES
265/etc/passwd
266.br
267$HOME/.zephyr.vars
268.SH AUTHOR
269.PP
270.br
271Robert S. French (MIT-Project Athena)
272.SH RESTRICTIONS
273Copyright (c) 1987,1988 by the Massachusetts Institute of Technology.
274All Rights Reserved.
275.br
276.I zephyr(1)
277specifies the terms and conditions for redistribution.
Note: See TracBrowser for help on using the repository browser.