Commit 4c92bf9c authored by Per Cederqvist's avatar Per Cederqvist
Browse files

(Aux-Item Types): Updated send-comments-to [33] so that it now allows

	an optional recipient type.
parent e3898abd
......@@ -8697,12 +8697,30 @@ email address that is used to post to the list, such as
Normally, when a comment is created, the LysKOM client adds the author
of the commented text to the recipient list if he isn't a member of
any of the recipients of the comment. By setting this aux-item on the
letterbox, a person can request different treatment. The value should
be a conference number where comments should be sent instead. The
value @samp{0} is special and means that the comment should not be
sent to any special conference, even though that means that the author
of the commented text will never see the comment. (The value @samp{0}
is useful for mail importers and other similar robots.)
letterbox, a person can request different treatment.
Data is a decimal integer (a conference number) optionally followed by
a space character and a decimal number (a recipient type). In the
future, additional data may be defined; clients must be prepared to
accept and ignore a space and any trailing data that may follow the
recipient type. Clients must be prepared to accept items of this type
that contain only the conference number.
Comments should be sent to the specified conference number instead of
to the author. The value @samp{0} is special and means that the
comment should not be sent to any special conference, even though that
means that the author of the commented text will never see the
comment. (The value @samp{0} is useful for mail importers and other
similar robots.)
The recipient type is the type of recipient to add. If the recipient
type is missing, clients should either assume recipient type zero
(@misc{recpt}) or ask the user. Legal recipient types are @samp{0}
for @misc{recpt}, @samp{1} for @misc{cc-recpt} and @samp{15} for
@misc{bcc-recpt} (these are the values used in @type{Info-Type}).
Additional recipient types may be added in the future. Clients should
treat unknown or invalid recipient types as if they were missing
(i.e. treat them as zero or ask the user).
@xref{Recipients of comments}, for more information about how the
client should select the conferences that a comment should be sent
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment