Commit 595cd199 authored by Jonas S Karlsson's avatar Jonas S Karlsson
Browse files

Modified aux-infos according to some comments by byers in lyskom text 3393198.

parent cd1a1209
\input texinfo @c -*-texinfo-*- \input texinfo @c -*-texinfo-*-
@c $Id: Protocol-A.texi,v 1.37 1998/10/11 15:21:32 jsk Exp $ @c $Id: Protocol-A.texi,v 1.38 1998/10/11 17:38:40 jsk Exp $
@c %**start of header @c %**start of header
@setfilename protocol-a.info @setfilename protocol-a.info
@settitle LysKOM Protocol A @settitle LysKOM Protocol A
...@@ -884,85 +884,101 @@ The data should be the client name, a space, and the client version used ...@@ -884,85 +884,101 @@ The data should be the client name, a space, and the client version used
in the @code{set-client-version} call. The server may enforce this in the @code{set-client-version} call. The server may enforce this
restriction. restriction.
@item x-author [15] (text) @item x-author [16] (text)
For imported texts using email gateway. Data is a string with For imported texts using email gateway. Data is a string with
the (readable) name of the author. the (readable) name of the author.
Kom clients should show this field instead of the id of the importing kom-id. Kom clients should show this field instead of the id of the importing kom-id.
@item x-from [16] (text) @item x-from [17] (text)
Data is a plain email addres, the From: field from an imported email. Data is a plain email addres, the From: field from an imported email.
Used by the kom client to construct an email reply to an imported text. Used by the kom client to construct an email reply to an imported text.
@item x-reply-to [17] (text) @item x-reply-to [18] (text)
Data is a plain email addres, comes from the Reply-To: field Data is a plain email addres, comes from the Reply-To: field in the
imported email.
@item x-to [18] (text) @item x-to [19] (text)
Data is one email address can be in variable format. Multiple text-items Data is one email address can be in variable format. Multiple x-to
can be present. The format is the same as is allowed in To: fields in can be present. The format is the same as is allowed in To: fields in
emails. If the text is imported these are the other receivers as seen in emails. If the text is imported these are the other receivers as seen in
the email. If the text originates from a kom-person (and thus not an the email. If the text originates from a kom-person (and thus not an
importer) this field is used in constructing an email, if an exporter importer) this field is used in constructing an email, if an exporter
is present. is present.
@item x-cc [19] (text) @item x-cc [20] (text)
Data in the same format as for "x-to". Usage the same but will Data in the same format as for "x-to", usage the same but will
be a carbon copy instead. be a carbon copy instead when exported.
@item x-date [20] (text) @item x-date [21] (text)
Data is the send-date of a imported email. Can be in free format, even Data is the send-date of an imported email. Can be in free format, even
if a readable format, such as "YYYY-MM-DD hh:mm:ss", is preferred. Kom if a readable format, such as "YYYY-MM-DD hh:mm:ss", is preferred. Kom
client should display this date as originating date, date of the client should display this date as originating date, date of the
imported text entity in kom may be different (and can be shown as imported text entity in kom may be different (and can be shown as
received). In case of the text being exported from kom, this date is set received). In case of the text being exported from kom, this date is set
by the exporter. by the exporter.
@item x-msgid [21] (text) @item x-message-id [22] (text)
Data is a string which is the message id from the imported email. Data is a string which is the message id from the imported email.
Preferably the importer should only add receivers when importing the Message id does not contain the enclosing < >. Preferably the importer
same email more times with the same msg-id. When a text is exported, should only add receivers when importing the same email more times with
the x-msgid is constructed as an email address which contains the same msg-id. When a text is exported, the x-message-id is
the kom text number and server in an unique way. constructed as an email address which contains the kom text number and
server in an unique way. (x-message-id is generally generated by the
@item x-inreplyto [22] (text) exporter as follows. A kom text that is exported is copied to the
importer, the importer sets the fields in the originating kom text which
Data is a string which stores the message id of texts commented. it normally would set when importing.) Preliminary, the format is
For each such text a kom (comment) link should be creaeted by the "Text-<textno>@<lyskomserver>". Lyskom server takes the same format as
importer if these referenced emails previously has been imported. vaguely defined in aux-info pgp-public-key [12].
@item x-misc [23] (text) @item x-in-reply-to [23] (text)
Data is a string with the rest of the fields from an imported Data is a string which stores one "In-Reply-To:" msg id from the
email. Is set by the importer. The fields are concatenated with email. If several msg ids are present all of them have one x-in-reply-to
"\n". each. The stored msg id has the same format as x-message-id. For each such
text a kom (comment) link should be created by the importer if these
@item x-allow-filter [24] (conf) referenced emails previously has been imported. Exporters must set this
for kom texts that are exported as emails, if the text is a
comment. Multiple x-in-reply-to can exist.
@item x-misc [24] (text)
Data is a string that contains all of the headers (incl subject:),
including whose that are redundantly stored in other aux-items. It is
set by the importer. The fields are concatenated with "\n".
@item x-allow-filter [25] (conf)
Data is a regexp string which allows a sender (a field in the Data is a regexp string which allows a sender (a field in the
email-header) to import the message. Several can exist, it is enough if email-header) to import the message. If none is present, the text is
one matches (OR) and none dissallows (AND). Can be set by an organizer imported. Several filters can exist, however, it is enough if one
of the conference. positive filter matches (OR) and none negative dissallows (AND)
import. The order is of no importance. Can be set by an organizer of the
conference.
The regexp allows ^[]?* as constructs. The importer is required to check these when The regexp is case insensitive, and use a glob-pat style, it allows
adding recipient of an imported text and comply. Example of usage: [^]?*+(|) as constructs. Note that "." is literal. The importer is
"From:*.liu.se*", "From:*jsk*". Tests are not made on the text-body. required to check these when adding recipient of an imported text and
comply. Example of usage: (positive filter) "From:*.liu.se*",
"From:*jsk*". "From:*(jonas|jonka|jsk)*" Tests are not made on the
text-body.
However, if the string starts with a "!" the email will be rejected if However, if the string starts with a "!" the email will be rejected if
the rest matches, even if one of the filter allowed it. Example: the there is a match (negative filter), even if one of the filter allowed it. Example:
"!From:*aol*", "!Subject:*money*". "!From:*aol*", "!Subject:*money*".
@item x-reject-forward [25] (conf) @item x-reject-forward [26] (conf)
Data is a string with either an email name on the format Data is a string with either an email name on the same format as
"E:email@foo.bar" or a kom-conference "C:num" number. The mail is aux-info rediret [8]. The mail is forwarded to this address if it was
forwarded if it was rejected by "x-import-filter" to this address. rejected by "x-import-filter".
@end table @end table
......
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