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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2002-2-1 (1.70)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>21. Reception mode</TITLE>
<META NAME="description" CONTENT="21. Reception mode">
<META NAME="keywords" CONTENT="sympa">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="sympa.css">
<LINK REL="next" HREF="node23.html">
<LINK REL="previous" HREF="node21.html">
<LINK REL="up" HREF="sympa.html">
<LINK REL="next" HREF="node23.html">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html1413"
HREF="node23.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1407"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1401"
HREF="node21.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1409"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1411"
HREF="node30.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1414"
HREF="node23.html">22. Shared documents</A>
<B> Up:</B> <A NAME="tex2html1408"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html1402"
HREF="node21.html">20. List configuration parameters</A>
<B> <A NAME="tex2html1410"
HREF="node1.html">Contents</A></B>
<B> <A NAME="tex2html1412"
HREF="node30.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
<UL>
<LI><A NAME="tex2html1415"
HREF="node22.html#SECTION002210000000000000000">21.1 Message topics</A>
<UL>
<LI><A NAME="tex2html1416"
HREF="node22.html#SECTION002211000000000000000">21.1.1 Message topic definition in a list</A>
<LI><A NAME="tex2html1417"
HREF="node22.html#SECTION002212000000000000000">21.1.2 Subscribing to message topic for list subscribers</A>
<LI><A NAME="tex2html1418"
HREF="node22.html#SECTION002213000000000000000">21.1.3 Message tagging</A>
</UL></UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION002200000000000000000"></A>
<A NAME="reception-mode"></A> <A NAME="4110"></A>
<BR>
21. Reception mode
</H1>
<P>
<H1><A NAME="SECTION002210000000000000000"></A>
<A NAME="msg-topics"></A><A NAME="4113"></A>
<BR>
21.1 Message topics
</H1>
<P>
A list can be configured to have message topics (this notion is different from topics used to class
mailing lists). Users can subscribe to these message topics in order to receive a subset of distributed messages :
a message can have one or more topics and subscribers will receive only messages that have been
tagged with a topic they are subscribed to. A message can be tagged automatically, by the message
sender or by the list moderator.
<P>
<H2><A NAME="SECTION002211000000000000000">
21.1.1 Message topic definition in a list</A>
</H2>
<P>
Available message topics are defined by list parameters. Foreach new message topic, create a new <A NAME="11517"></A><TT>msg_topic</TT> paragraph
that defines the name and the title of the topic. If a thread is identified for the current message then the automatic procedure is performed.
Else, to use automatic tagging, you should define keywords (See (<A HREF="node21.html#par-msg-topic">20.4.13</A>, page <A HREF="node21.html#par-msg-topic"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>)
To define which part of the message is used for automatic tagging
you have to define <A NAME="11520"></A><TT>msg_topic_keywords_apply_on</TT> list parameter (See <A HREF="node21.html#par-msg-topic-key-apply-on">20.4.14</A>,
page <A HREF="node21.html#par-msg-topic-key-apply-on"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>). Tagging a message can be optional or it can be required, depending on the
<A NAME="11523"></A><TT>msg_topic_tagging</TT> list parameter (See (<A HREF="node21.html#par-msg-topic-tagging">20.4.15</A>,page <A HREF="node21.html#par-msg-topic-tagging"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>).
<P>
<H2><A NAME="SECTION002212000000000000000">
21.1.2 Subscribing to message topic for list subscribers</A>
</H2>
<P>
This functionnality is only available via ``normal'' reception mode. Subscribers can select message topic to receive messages tagged with this topic.
To receive messages that were not tagged, users can subscribe to the topic ``other''. Message topics selected by a subscriber are stored in <I>Sympa</I>
database (subscriber_table table).
<P>
<H2><A NAME="SECTION002213000000000000000">
21.1.3 Message tagging</A>
</H2>
<P>
First of all, if one or more <A NAME="11527"></A><TT>msg_topic.keywords</TT> are defined, <I>Sympa</I> tries to tag messages automatically.
To trigger manual tagging, by message sender or list moderator, on the web interface, <I>Sympa</I> uses authorization scenarios : if the resulted action is ``editorkey''
(for example in scenario send.editorkey), the list moderator is asked to tag the message.
If the resulted action is ``request_auth'' (for example in scenario send.privatekey), the message sender is asked to tag the message.
The following variables are available as scenario variables to customize tagging : topic, topic-sender, topic-editor, topic-auto, topic-needed.
(See (<A HREF="node14.html#scenarios">13</A>, page <A HREF="node14.html#scenarios"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>) If message tagging is required and if it was not yet performed, <I>Sympa</I> will ask to the list moderator.
<P>
Tagging a message will create a topic information file in the <A NAME="11533"></A><TT>/home/sympa/spool/topic/</TT> spool. Its name is based on the listname and the Message-ID.
For message distribution, a ``X-Sympa-Topic'' field is added to the message to allow members to use mail filters.
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html1413"
HREF="node23.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1407"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1401"
HREF="node21.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1409"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1411"
HREF="node30.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1414"
HREF="node23.html">22. Shared documents</A>
<B> Up:</B> <A NAME="tex2html1408"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html1402"
HREF="node21.html">20. List configuration parameters</A>
<B> <A NAME="tex2html1410"
HREF="node1.html">Contents</A></B>
<B> <A NAME="tex2html1412"
HREF="node30.html">Index</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
root
2006-10-20
</ADDRESS>
</BODY>
</HTML>
|
