Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
lyskom-server-ceder-1616-generations-topgit
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Per Cederqvist
lyskom-server-ceder-1616-generations-topgit
Commits
595cd199
Commit
595cd199
authored
Oct 11, 1998
by
Jonas S Karlsson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Modified aux-infos according to some comments by byers in lyskom text 3393198.
parent
cd1a1209
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
58 additions
and
42 deletions
+58
-42
doc/Protocol-A.texi
doc/Protocol-A.texi
+58
-42
No files found.
doc/Protocol-A.texi
View file @
595cd199
\input
texinfo @c -*-texinfo-*-
@c
$
Id: Protocol
-
A.texi,v
1
.
3
7
1998
/
10
/
11
15
:
21
:
32
jsk Exp
$
@c
$
Id: Protocol
-
A.texi,v
1
.
3
8
1998
/
10
/
11
17
:
38
:
40
jsk Exp
$
@c
%**start of header
@setfilename protocol-a.info
@settitle LysKOM Protocol A
...
...
@@ -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
restriction.
@item x-author [1
5
] (text)
@item x-author [1
6
] (text)
For imported texts using email gateway. Data is a string with
the (readable) name of the author.
Kom clients should show this field instead of the id of the importing kom-id.
@item x-from [1
6
] (text)
@item x-from [1
7
] (text)
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.
@item x-reply-to [1
7
] (text)
@item x-reply-to [1
8
] (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 [1
8
] (text)
@item x-to [1
9
] (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
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
importer) this field is used in constructing an email, if an exporter
is present.
@item x-cc [
19
] (text)
@item x-cc [
20
] (text)
Data in the same format as for "x-to"
. U
sage the same but will
be a carbon copy instead.
Data in the same format as for "x-to"
, u
sage the same but will
be a carbon copy instead
when exported
.
@item x-date [2
0
] (text)
@item x-date [2
1
] (text)
Data is the send-date of a imported email. Can be in free format, even
Data is the send-date of a
n
imported email. Can be in free format, even
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
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
by the exporter.
@item x-m
sgid [21
] (text)
@item x-m
essage-id [22
] (text)
Data is a string which is the message id from the imported email.
Preferably the importer should only add receivers when importing the
same email more times with the same msg-id. When a text is exported,
the x-msgid is constructed as an email address which contains
the kom text number and server in an unique way.
@item x-inreplyto [22] (text)
Data is a string which stores the message id of texts commented.
For each such text a kom (comment) link should be creaeted by the
importer if these referenced emails previously has been imported.
@item x-misc [23] (text)
Data is a string with the rest of the fields from an imported
email. Is set by the importer. The fields are concatenated with
"
\n
".
@item x-allow-filter [24] (conf)
Message id does not contain the enclosing < >. Preferably the importer
should only add receivers when importing the same email more times with
the same msg-id. When a text is exported, the x-message-id is
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
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
it normally would set when importing.) Preliminary, the format is
"Text-<textno>@<lyskomserver>". Lyskom server takes the same format as
vaguely defined in aux-info pgp-public-key [12].
@item x-in-reply-to [23] (text)
Data is a string which stores one "In-Reply-To:" msg id from the
email. If several msg ids are present all of them have one x-in-reply-to
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
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
email-header) to import the message. Several can exist, it is enough if
one matches (OR) and none dissallows (AND). Can be set by an organizer
of the conference.
email-header) to import the message. If none is present, the text is
imported. Several filters can exist, however, it is enough if one
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
adding recipient of an imported text and comply. Example of usage:
"From:*.liu.se*", "From:*jsk*". Tests are not made on the text-body.
The regexp is case insensitive, and use a glob-pat style, it allows
[
^
]?*+(|) as constructs. Note that "." is literal. The importer is
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
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*".
@item x-reject-forward [2
5
] (conf)
@item x-reject-forward [2
6
] (conf)
Data is a string with either an email name on the
format
"E:email@foo.bar" or a kom-conference "C:num" number. The mail i
s
forwarded if it was rejected by "x-import-filter" to this address
.
Data is a string with either an email name on the
same format as
aux-info rediret [8]. The mail is forwarded to this address if it wa
s
rejected by "x-import-filter"
.
@end table
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment