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
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
|
<!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>18. List creation, edition and removal</TITLE>
<META NAME="description" CONTENT="18. List creation, edition and removal">
<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="node20.html">
<LINK REL="previous" HREF="node18.html">
<LINK REL="up" HREF="sympa.html">
<LINK REL="next" HREF="node20.html">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
<!--Navigation Panel-->
<A NAME="tex2html1285"
HREF="node20.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1279"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1273"
HREF="node18.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1281"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1283"
HREF="node30.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1286"
HREF="node20.html">19. Lists Families</A>
<B> Up:</B> <A NAME="tex2html1280"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html1274"
HREF="node18.html">17. Mailing list definition</A>
<B> <A NAME="tex2html1282"
HREF="node1.html">Contents</A></B>
<B> <A NAME="tex2html1284"
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="tex2html1287"
HREF="node19.html#SECTION001910000000000000000">18.1 List creation</A>
<UL>
<LI><A NAME="tex2html1288"
HREF="node19.html#SECTION001911000000000000000">18.1.1 Data for list creation</A>
<LI><A NAME="tex2html1289"
HREF="node19.html#SECTION001912000000000000000">18.1.2 XML file format</A>
</UL>
<BR>
<LI><A NAME="tex2html1290"
HREF="node19.html#SECTION001920000000000000000">18.2 List families</A>
<LI><A NAME="tex2html1291"
HREF="node19.html#SECTION001930000000000000000">18.3 List creation on command line with <TT>sympa.pl</TT></A>
<LI><A NAME="tex2html1292"
HREF="node19.html#SECTION001940000000000000000">18.4 Creating and editing mailing using the web</A>
<UL>
<LI><A NAME="tex2html1293"
HREF="node19.html#SECTION001941000000000000000">18.4.1 List creation on the Web interface</A>
<LI><A NAME="tex2html1294"
HREF="node19.html#SECTION001942000000000000000">18.4.2 Who can create lists on the Web interface</A>
<LI><A NAME="tex2html1295"
HREF="node19.html#SECTION001943000000000000000">18.4.3 typical list profile and Web interface</A>
<LI><A NAME="tex2html1296"
HREF="node19.html#SECTION001944000000000000000">18.4.4 List edition</A>
</UL>
<BR>
<LI><A NAME="tex2html1297"
HREF="node19.html#SECTION001950000000000000000">18.5 Removing a list</A>
</UL>
<!--End of Table of Child-Links-->
<HR>
<H1><A NAME="SECTION001900000000000000000"></A>
<A NAME="ml-creation"></A>
<BR>
18. List creation, edition and removal
</H1>
<P>
The list creation can be done by two ways, according to listmaster
needs :
<UL>
<LI>instanciation family to create and manage large number of related lists.
In this case, lists are linked to their family all along their life.
</LI>
<LI>command line creation of individual list with <A NAME="10222"></A><TT>sympa.pl</TT> or on the Web
interface according to privileges defined by listmasters. Here lists are free from
their model creation.
</LI>
</UL>
Management of mailing lists by list owners is usually done via the Web interface :
when a list is created, whatever its status (<A NAME="10225"></A><TT>pending</TT> or <A NAME="10228"></A><TT>open</TT>), the owner
can use WWSympa admin features to modify list parameters, or to edit the welcome
message, and so on.
<P>
WWSympa keeps logs of the creation and all modifications to a list as part of the list's
<A NAME="10231"></A><TT>config</TT> file (old configuration files are archived).
A complete installation requires some careful planning, although default
values should be acceptable for most sites.
<P>
<H1><A NAME="SECTION001910000000000000000"></A>
<A NAME="list-creation"></A>
<BR>
18.1 List creation
</H1>
<P>
Mailing lists can have many different uses. <I>Sympa</I> offers a
wide choice of parameters to adapt a list behavior
to different situations. Users might have difficulty selecting all the
correct parameters to make the list configuration, so instead of selecting each
parameters, list configuration is made with a list profile. This is an
almost complete list configuration, but with a number of unspecified fields
(such as owner e-mail) to be replaced by <I>Sympa</I> at list creation time. It is easy to create new list
templates by modifying existing ones. (Contributions to the distribution are welcome...)
<P>
<H2><A NAME="SECTION001911000000000000000">
18.1.1 Data for list creation</A>
</H2>
<P>
To create a list, some data concerning list parameters are required :
<UL>
<LI><B>listname </B> : name of the list,
</LI>
<LI><B>subject</B> : subject of the list (a short description),
</LI>
<LI><B>owner(s)</B> : by static definition and/or dynamic definition.
In case of static definition, the parameter <B>owner</B> and its subparameter <B>email</B> are required.
For dynamic definition, the parameter <B>owner_include</B> and its subparameter <B>source</B> are required,
indicating source file of data inclusion.
</LI>
<LI><B>list creation template</B> : the typical list profile.
</LI>
</UL>
<P>
Moreover of these required data, provided values are assigned to vars being in the list creation template.
Then the result is the list configuration file :
<BR>
<P>
On the Web interface, these data are given by the list creator in the web form. On command line these
data are given by an xml file.
<P>
<H2><A NAME="SECTION001912000000000000000"></A>
<A NAME="xml-file-format"></A>
<BR>
18.1.2 XML file format
</H2>
<P>
The xml file provides information on :
<BR>
<UL>
<LI>the list name,
</LI>
<LI>values to assign vars in the list creation template
</LI>
<LI>the list description in order to be written in the list file info
</LI>
<LI>the name of the list creation template (only for list creation on command line with sympa.pl, in a family context, the template is specified by the family name)
</LI>
</UL>
<P>
Here is an example of XML document that you can map with the following example of list creation template.:
<P><PRE>
<?xml version="1.0" ?>
<list>
<listname>example</listname>
<type>my_profile</type>
<subject>a list example</subject>
<description/>
<status>open</status>
<shared_edit>editor</shared_edit>
<shared_read>private</shared_read>
<language>fr</language>
<owner multiple="1">
<email>serge.aumont@cru.fr</email>
<gecos>C.R.U.</gecos>
</owner>
<owner multiple="1">
<email>olivier.salaun@cru.fr</email>
</owner>
<owner_include multiple="1">
<source>my_file</source>
</owner_include>
<sql>
<type>oracle</type>
<host>sqlserv.admin.univ-x.fr</host>
<user>stdutilisateur</user>
<pwd>monsecret</pwd>
<name>les_etudiants</name>
<query>SELECT DISTINCT email FROM etudiant</query>
</sql>
</list>
subject [% subject %]
status [% status %]
[% IF topic %]
topics [% topic %]
[% END %]
visibility noconceal
send privateoreditorkey
Web_archive
access public
subscribe open_notify
shared_doc
d_edit [% shared_edit %]
d_read [% shared_read %]
lang [% language %]
[% FOREACH o = owner %]
owner
email [% o.email %]
profile privileged
[% IF o.gecos %]
gecos [% o.gecos %]
[% END %]
[% END %]
[% IF moderator %]
[% FOREACH m = moderator %]
editor
email [% m.email %]
[% END %]
[% END %]
[% IF sql %]
include_sql_query
db_type [% sql.type %]
host [% sql.host %]
user [% sql.user %]
passwd [% sql.pwd %]
db_name [% sql.name %]
sql_query [% sql.query %]
[% END %]
ttl 360
</PRE>
<P>
The XML file format should comply with the following rules :
<UL>
<LI>The root element is <A NAME="10236"></A><TT><list></TT>
</LI>
<LI>One XML element is mandatory : <A NAME="10239"></A><TT><listname></TT> contains the name of the list.
That not excludes mandatory parameters for list creation (<A NAME="10242"></A><TT>listname, subject,owner.email and/or
owner_include.source</TT>).
</LI>
<LI><A NAME="10245"></A><TT><type></TT> : this element contains the name of template list creation, it is used for list creation on command line with sympa.pl.
In a family context, this element is no used.
</LI>
<LI><A NAME="10248"></A><TT><description></TT> : the text contained in this element is written in list <A NAME="10251"></A><TT>info</TT> file(it can be a CDATA section).
</LI>
<LI>For other elements, its name is the name of the var to assign in the list creation template.
</LI>
<LI>Each element concerning multiple parameters must have the <A NAME="10254"></A><TT>multiple</TT> attribute set
to ``1'', example : <A NAME="10257"></A><TT><owner multiple=''1''></TT>.
</LI>
<LI>For composed and multiple parameters, sub-elements are used. Example for <A NAME="10260"></A><TT>owner</TT> parameter :
<A NAME="10263"></A><TT><email></TT> and <A NAME="10266"></A><TT><gecos></TT> elements are contained in the <A NAME="10269"></A><TT><owner></TT>element.
An element can only have homogeneous content.
</LI>
<LI>A list requires at least one owner, defined in the XML input file with one of the following elements :
<UL>
<LI><A NAME="10272"></A><TT><owner multiple=''1''> <email> ... </email> </owner></TT>
</LI>
<LI><A NAME="10275"></A><TT><owner_include multiple=''1''> <source> ... </source> </owner_include></TT>
</LI>
</UL>
</LI>
</UL>
<P>
<H1><A NAME="SECTION001920000000000000000">
18.2 List families</A>
</H1>
<P>
See chapter <A HREF="node20.html#lists-families">19</A>, page <A HREF="node20.html#lists-families"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>
<P>
<H1><A NAME="SECTION001930000000000000000"></A><A NAME="10278"></A>
<A NAME="list-creation-sympa"></A>
<BR>
18.3 List creation on command line with <TT>sympa.pl</TT>
</H1>
<P>
This way to create lists is independent of family.
<P>
Here is a sample command to create one list :.
<BLOCKQUOTE>
sympa.pl -create_list -robot my.domain.org-input_file /path/to/my_file.xml
</BLOCKQUOTE>
<P>
The list is created under the <A NAME="10281"></A><TT>my_robot</TT> robot and the list
is described in the file <A NAME="10284"></A><TT>my_file.xml</TT>. The XML file is
described before, see <A HREF="#xml-file-format">18.1.2</A>, page <A HREF="node19.html#xml-file-format"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>.
<P>
By default, the status of the created list is <A NAME="10287"></A><TT>open</TT>.
<P>
<H3><A NAME="SECTION001930100000000000000"></A>
<A NAME="typical-list-profile"></A>
<BR>
18.3.0.1 typical list profile (list template creation)
</H3>
<P>
The list creator has to choose a profile
for the list and put its name in the XML element <A NAME="10290"></A><TT><type></TT>.
<P>
List profiles are stored in <A NAME="10293"></A><TT>/home/sympa/etc/create_list_templates</TT> or in
<A NAME="10296"></A><TT>/home/sympa/bin/etc/create_list_templates</TT> (default of distrib).
<P>
You might want to hide or modify profiles (not useful, or dangerous
for your site). If a profile exists both in the local site directory
<A NAME="10299"></A><TT>/home/sympa/etc/create_list_templates</TT> and
<A NAME="10302"></A><TT>/home/sympa/bin/etc/create_list_templates</TT> directory, then the local profile
will be used by WWSympa.
<P>
<H1><A NAME="SECTION001940000000000000000"></A>
<A NAME="web-ml-creation"></A>
<BR>
18.4 Creating and editing mailing using the web
</H1>
<P>
The management of mailing lists is based on a strict definition of privileges
which pertain respectively to the listmaster, to the main list owner, and to
basic list owners. The goal is to allow each listmaster to define who can create
lists, and which parameters may be set by owners.
<P>
<H2><A NAME="SECTION001941000000000000000">
18.4.1 List creation on the Web interface</A>
</H2>
<P>
Listmasters are responsible for validating new mailing lists and, depending on the configuration chosen,
might be the only ones who can fill out the create list form.The listmaster
is defined in <A NAME="10305"></A><TT>sympa.conf</TT> and others are defined at the virtual host level. By default, any authenticated user can
request a list creation but newly created are then validated by the listmaster.
<P>
List rejection message and list creation notification message are both
templates that you can customize (<A NAME="10308"></A><TT>list_rejected.tt2</TT> and
<A NAME="10311"></A><TT>list_created.tt2</TT>).
<P>
<H2><A NAME="SECTION001942000000000000000">
18.4.2 Who can create lists on the Web interface</A>
</H2>
<P>
This is defined by the <A NAME="10314"></A><TT>create_list</TT> sympa.conf parameter (see <A HREF="node8.html#create-list">7.1.15</A>,
page <A HREF="node8.html#create-list"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>). This parameter refers to a <B>create_list</B> authorization scenario.
It will determine if the <I>create list</I> button is displayed and if it requires
a listmaster confirmation.
<P>
The authorization scenario can accept any condition concerning the [sender]
(i.e. WWSympa user), and it returns <A NAME="10317"></A><TT>reject</TT>, <A NAME="10320"></A><TT>do_it</TT>
or <A NAME="10323"></A><TT>listmaster</TT> as an action.
<P>
Only in cases where a user is authorized by the create_list authorization scenario
will the "create" button be available in the main menu.
If the scenario returns <A NAME="10326"></A><TT>do_it</TT>, the list will be created and installed.
If the scenario returns "listmaster", the user is allowed to create a list, but
the list is created with the <A NAME="10329"></A><TT>pending</TT> status,
which means that only the list owner may view or use it.
The listmaster will need to open the list of pending lists
using the "pending list" button in the "server admin"
menu in order to install or refuse a pending list.
<P>
<H2><A NAME="SECTION001943000000000000000">
18.4.3 typical list profile and Web interface</A>
</H2>
As on command line creation, the list creator has to choose a list profile and to fill in the owner's e-mail
and the list subject together with a short description. But in this case, you don't need any XML file. Concerning
these typical list profiles, they are described before, see <A HREF="#typical-list-profile">18.3</A>, page <A HREF="node19.html#typical-list-profile"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>.
You can check available profile. On the Web interface, another way
to control publicly available profiles is to
edit the <A NAME="10332"></A><TT>create_list.conf</TT> file (the default for this file is in
the <A NAME="10335"></A><TT>/home/sympa/bin/etc</TT> directory, and you may create your own customized
version in <A NAME="10338"></A><TT>/home/sympa/etc</TT>).
This file controls which of the available list templates are to be displayed. Example :<PRE>
# Do not allow the public_anonymous profile
public_anonymous hidden
* read
</PRE>
<P>
<H2><A NAME="SECTION001944000000000000000"></A>
<A NAME="list-edition"></A>
<BR>
18.4.4 List edition
</H2>
<P>
For each parameter, you may specify (via the <A NAME="10341"></A><TT>/home/sympa/etc/edit_list.conf</TT>
configuration file) who has the right to edit the parameter concerned ; the default
<A NAME="10344"></A><TT>/home/sympa/bin/etc/edit_list.conf</TT> is reasonably safe.
<P>
<PRE>
Each line is a set of 3 field
<Parameter> <Population> <Privilege>
<Population> : <listmaster|privileged_owner|owner>
<Privilege> : <write|read|hidden>
parameter named "default" means any other parameter
</PRE>
<P>
There is no hierarchical relation between populations in this
configuration file. You need to explicitely list populations.
<P>
Eg: listmaster will not match rules refering to owner or privileged_owner
<P><PRE>
examples :
# only listmaster can edit user_data_source, priority, ...
user_data_source listmaster write
priority owner,privileged_owner read
priority listmaster write
# only privileged owner can modify editor parameter, send, ...
editor privileged_owner write
send owner read
send privileged_owner,listmaster write
# other parameters can be changed by simple owners
default owner write
</PRE>
<P>
Privileged owners are defined in the list's <A NAME="10347"></A><TT>config</TT> file as follows :
<PRE>
owner
email owners.email@foo.bar
profile privileged
</PRE>
<P>
The following rules are hard coded in WWSympa :
<UL>
<LI>only listmaster can edit the "profile privileged"
owner attribute
<P>
</LI>
<LI>owners can edit their own attributes (except profile and e-mail)
<P>
</LI>
<LI>the requestor creating a new list becomes a privileged owner
<P>
</LI>
<LI>privileged owners can edit any gecos/reception/info attribute
of any owner
<P>
</LI>
<LI>privileged owners can edit owners' e-mail addresses (but not privileged owners' e-mail addresses)
<P>
</LI>
</UL>
<P>
Sympa aims to define two levels of trust for owners (some being entitled
simply to edit secondary parameters such as "custom_subject", others having
the right to manage more important parameters), while leaving control of
crucial parameters (such as the list of privileged owners and user_data_sources)
in the hands of the listmaster.
Consequently, privileged owners can change owners' e-mails,
but they cannot grant the responsibility of list management to others without
referring to the listmaster.
<P>
Concerning list edition in a family context, see <A HREF="node20.html#list-param-edit-family">19.2.8</A>, page <A HREF="node20.html#list-param-edit-family"><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]" SRC="crossref.png"></A>
<P>
<H1><A NAME="SECTION001950000000000000000"></A>
<A NAME="ml-removal"></A>
<BR>
18.5 Removing a list
</H1>
<P>
You can remove a list either from the command line or using the web interface.
<P>
<A NAME="10350"></A><TT>sympa.pl</TT> provides an option to remove a mailing list, see the example below :
<BLOCKQUOTE>
sympa.pl -remove_list=mylist@mydomain
</BLOCKQUOTE>
<P>
Privileged owners can remove a mailing list through the list admin part of the web interface. Removing the mailing list
consists in removing its subscribers from the database and setting its status to <I>closed</I>.Once removed, the list
can still be restored by the listmaster ; list members are saved in a <A NAME="10353"></A><TT>subscribers.closed.dump</TT> file.
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html1285"
HREF="node20.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html1279"
HREF="sympa.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html1273"
HREF="node18.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html1281"
HREF="node1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html1283"
HREF="node30.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1286"
HREF="node20.html">19. Lists Families</A>
<B> Up:</B> <A NAME="tex2html1280"
HREF="sympa.html">Sympa Mailing Lists Management Software version</A>
<B> Previous:</B> <A NAME="tex2html1274"
HREF="node18.html">17. Mailing list definition</A>
<B> <A NAME="tex2html1282"
HREF="node1.html">Contents</A></B>
<B> <A NAME="tex2html1284"
HREF="node30.html">Index</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
root
2006-10-20
</ADDRESS>
</BODY>
</HTML>
|
