Source

xemacsweb / Lists / index.content

Full commit
  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
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
%title%
XEmacs Community Mailing Lists
%author%
john s jacobs anderson re-working old content from www.xemacs.org; author unknown
%main%

  <h1>XEmacs Mailing Lists</h1>

  <p>
    For most problems of configuration and daily usage, the best
    channel is the Usenet newsgroup
    <a href="news:comp.emacs.xemacs"><code>comp.emacs.xemacs</code></a>.
    The participants in <code>c.e.x</code> are users at every level of
    experience as well as a few developers, and they are there
    specificially for the purpose of helping each other.  For common
    problems responses are fast and accurate, and normally faster than
    they will be on the developers' mailing lists.
  </p>

  <p>
    However, if you have read the documentation, believe you
    understand it, and still don't understand why XEmacs does what it
    does, then that is most likely a bug (often in the documentation,
    but still a bug), and you should let the developers know about
    it.  The best way to do that is <code>M-x report-xemacs-bug</code>.
  </p>

  <p>
    Several mailing lists are available to facilitate development and
    discussion of XEmacs.  These mailing lists are essential to the <a
    href="#workflow">development process</a> of XEmacs.  If you wish
    to participate effectively, you should subscribe or regularly
    review the archives of the relevant lists.  Besides information
    about each list, this page provides
    <a href="#subscribing">information about subscribing</a> to XEmacs
    mailing lists (and each list description contains a link to
    facilitate subscription), <a href="#problems">help with
      list-related problems</a>, and <a href="#spam">information about
      anti-spam policy</a>.
  </p>

  <h2><a id="workflow" name="workflow">Mailing Lists and the
  Development Process</a></h2>

  <p>
    Currently, the typical workflow starts with a bug report from a
    user or a developer, which should be directed to
    <a href="#xemacs-beta">xemacs-beta</a>.
    <!--
    A complex bugfix or a new feature, which requires more than
    minimal changes to XEmacs to implement, will then be discussed on
    <a href="#xemacs-design">xemacs-design</a>.
    -->
    Any changes that arise from this discussion (or bugfixes arising
    directly from discussion on <a href="#xemacs-beta">xemacs-beta</a>)
    should then be submitted to <a href="#xemacs-patches">xemacs-patches</a>.
    Patches are vetted by the XEmacs Review Board.  Review actions
    such as approval and veto of patches will be directed to
    <a href="#xemacs-patches">xemacs-patches</a>.
    <!-- THIS IS PROBABLY BOGUS, IT NEVER WORKED.
    However, all other discussion of patches under review should be
    directed to <a href="#xemacs-design">xemacs-design</a>.
    -->
  </p>

  <p>
    This is a description of the <em>typical</em> workflow.  There are
    various other routes that code and discussion can follow.  See the
    descriptions of the various lists to decide which is most appropriate
    for your post.
  </p>

<!--
  <p>
    <strong>The list archive URLs below are temporary, and will change
    back to "lists.xemacs.org" when we have worked out virtual hosting
    and DNS issues.</strong>
  </p>
-->

  <ul>
    <li><a href="#comp-emacs-xemacs">comp.emacs.xemacs</a></li>
    <li><a href="#xemacs-announce">xemacs-announce</a></li>
    <li><a href="#xemacs-beta">xemacs-beta</a></li>
    <li><a href="#xemacs-buildreports">xemacs-buildreports</a></li>
    <li><a href="#xemacs-commits">xemacs-commits</a></li>
    <li><a href="#xemacs-patches">xemacs-patches</a></li>
  </ul>

  <p>
    The following lists are more or less obsolete, or unused, and have
    been merged into xemacs-beta.  The xemacs-users-LANG lists may be
    revived if traffic or user requests warrant.  Send requests, in
    English, to <a href="mailto:stephen@xemacs.org">Stephen Turnbull</a>.
    The xemacs-design list probably will be revived when traffic
    warrants.
  </p>

  <ul>
    <li><a href="#xemacs-beta-ja">xemacs-beta-ja</a></li>
    <li><a href="#xemacs-design">xemacs-design</a></li>
    <li><a href="#xemacs-mule">xemacs-mule</a></li>
    <li><a href="#xemacs-news">xemacs-news</a></li>
    <li><a href="#xemacs-nt">xemacs-nt</a></li>
    <li><a href="#xemacs-users-ja">xemacs-users-ja</a></li>
    <li><a href="#xemacs-users-ru">xemacs-users-ru</a></li>
  </ul>

  <p>
    An alternative to subscribing to any of the lists is to
    visit the
    <a href="http://list-archive.xemacs.org/pipermail/">Archived XEmacs Mailing Lists</a>.
    These archives are updated daily, during the period 13:00-14:00
    EST (around 18:00
    GMT).  If you don't want to stay as far as a day behind, then just
    go ahead and subscribe.</p>

  <p>
    Some (or maybe all by the time you read this) of these lists are
    available by NNTP on the bidirectional gateway gmane.org.</p>

  <ul>
    <li><a href="#subscribing">How to subscribe</a></li>
    <li><a href="#problems">Problems</a></li>
  </ul>

  <table border="1">
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p>
	  <strong>comp.emacs.xemacs</strong> is a Usenet newsgroup
	  for XEmacs users to discuss problems and issues that arise
	  for them.  It's not generally an appropriate place to ask
	  about apparent bugs (use
	  <a href="#xemacs-beta">xemacs-beta</a>).
	  <!--
	  or future plans (use <a href="#xemacs-design">xemacs-design</a>).
	  -->
	</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="comp-emacs-xemacs" name="comp-emacs-xemacs">Archive</a>:</dt>
          <dd>No archives at XEmacs; Google Groups, etc., may have them.</dd>
          <dt>Subscriptions:</dt>
          <dd>No subscription necessary; just point your newsreader at
	    <a href="news:comp.emacs.xemacs">comp.emacs.xemacs</a>.</dd>
	  <!--
          <dt>Mailing list bidirectional gateway:</dt>
          <dd><a href="#xemacs-news">xemacs-news</a>.  The gateway is
	    currently broken, so xemacs-news is a rather low-traffic
	    channel.</dd>
	  -->
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-announce</strong> is a read-only, low
          volume list for announcements concerning the XEmacs project
          and new releases of the XEmacs software.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-announce" name="xemacs-announce">Archive</a>:</dt>
          <dd><a href="http://list-archive.xemacs.org/pipermail/xemacs-announce/">http://list-archive.xemacs.org/pipermail/xemacs-announce/</a></dd>
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-announce-request@xemacs.org?body=subscribe address=...">mailto:xemacs-announce-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-announce/">http://calypso.tux.org/mailman/listinfo/xemacs-announce/</a></dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-beta</strong> is an open list for bug
        reports about beta versions of XEmacs.  This includes the bug
        reports themselves, by both users and developers, as well as
        queries, follow-ups, and discussions further determining their
        nature and status.  This is the primary channel for this kind
        of discussion; related code changes will usually not be
        applied until they have been discussed here.
	  <!--
	  When such discussions touch on significant changes to the
	  code (in particular, structural changes), or on changes to
	  API's or external functionality, they should be moved to
	  <strong>xemacs-design</strong>.  Requests and proposals for
	  non-bug-related changes do not belong on
	  <strong>xemacs-beta</strong>, and should be sent to
	  <strong>xemacs-design</strong> instead.
	  -->
	</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-beta" name="xemacs-beta">Archive</a>:</dt>
          <dd><a href="http://list-archive.xemacs.org/pipermail/xemacs-beta/">http://list-archive.xemacs.org/pipermail/xemacs-beta/</a></dd>
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-beta-request@xemacs.org?body=subscribe address=...">mailto:xemacs-beta-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-beta/">http://calypso.tux.org/mailman/listinfo/xemacs-beta/</a></dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-beta-ja</strong> is obsolete; it has been
	  merged into xemacs-beta.  Posts in Japanese are welcome on
	  xemacs-beta, but you should consider that posts in English
	  will probably receive much more prompt and accurate
	  response.  The old archives will remain available.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-beta-ja" name="xemacs-beta-ja">Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-beta-ja/</dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-buildreports</strong> is an open list for
          submission of build-reports on beta versions of XEmacs. For
          information on what the build-reports should contain, please
          see the "Beta" Info documentation node, or the man/beta.texi
	  file in the source of the beta series.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-buildreports" name="xemacs-buildreports">Archive</a>:</dt>
          <dd><a href="http://list-archive.xemacs.org/pipermail/xemacs-buildreports/">http://list-archive.xemacs.org/pipermail/xemacs-buildreports/</a></dd>
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-buildreports-request@xemacs.org?body=subscribe address=...">mailto:xemacs-buildreports-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-buildreports/">http://calypso.tux.org/mailman/listinfo/xemacs-buildreports/</a></dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-commits</strong> is a read-only list for notices
        and information on what has been committed to the XEmacs Mercurial
        repositories, by whom, and for what. (For more information on the
        XEmacs Mercurial repositories: <a href="<!-- _GP_
        relPath(qq{Develop/hgaccess.html}) -->"><!--
	    _GP_ relPath(qq{Develop/hgaccess.html}) --></a>.)</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-commits" name="xemacs-commits">Archive</a>:</dt>
          <dd><a href="http://list-archive.xemacs.org/pipermail/xemacs-commits/">http://list-archive.xemacs.org/pipermail/xemacs-commits/</a></dd>
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-commits-request@xemacs.org?body=subscribe address=...">mailto:xemacs-commits-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-commits/">http://calypso.tux.org/mailman/listinfo/xemacs-commits/</a></dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-design</strong>
	  has been merged into xemacs-beta for now.  It will be
	  revived when traffic justifies.
	  <!--
	  is an open list for
        discussing the design of XEmacs.  This includes discussion
        about planned and ongoing changes to functionality and API
        changes and additions as well as requests for them.  This is
        the primary channel for this kind of discussion; related code
        changes will usually not be applied until they have been
        discussed here.  This does not include bug reports, which go
        to <strong>xemacs-beta</strong>.
	  -->
	</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-design" name="xemacs-design">Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-design/</dd>
	  <!--
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-design-request@xemacs.org?body=subscribe address=...">mailto:xemacs-design-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-design/">http://calypso.tux.org/mailman/listinfo/xemacs-design/</a></dd>
	  -->
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-mule</strong> has been merged into
	  xemacs-beta, which is not restricted to
          English, postings in all languages are welcome.  Please
	  consider that posts in English will likely receive
	  much more prompt and accurate responses.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-mule" name="xemacs-mule">Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-mule/</dd>
	  <!--
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-mule-request@xemacs.org?body=subscribe address=...">mailto:xemacs-mule-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-mule/">http://calypso.tux.org/mailman/listinfo/xemacs-mule/</a></dd>
	  -->
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-news</strong> has been merged into
	  xemacs-beta.  If you are looking for user support, please
	  use the comp.emacs.xemacs newsgroup, which has convenient
	  web interfaces via Yahoo Groups and Google Groups.
	  </p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-news" name="xemacs-news">Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs/</dd>
	  <!--
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-news-request@xemacs.org?body=subscribe address=...">mailto:xemacs-news-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-news/">http://calypso.tux.org/mailman/listinfo/xemacs-news/</a></dd>
	  -->
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-nt</strong> has been merged into
	  xemacs-beta, as the Windows support is now a standard part
	  of XEmacs.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-nt" name="xemacs-nt">Legacy Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-nt/</dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-patches</strong> is an open, moderated
          list for submission of patches to the XEmacs distribution
          and its packages. Anyone may subscribe or submit to
          xemacs-patches, but all submissions are reviewed by the list
          moderator before they are distributed to the
          list. Discussion of substantial changes to a patch is not
	  appropriate on xemacs-patches; please try to return such
	  threads to xemacs-beta.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-patches" name="xemacs-patches">Archive</a>:</dt>
          <dd><a href="http://list-archive.xemacs.org/pipermail/xemacs-patches/">http://list-archive.xemacs.org/pipermail/xemacs-patches/</a></dd>
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-patches-request@xemacs.org?body=subscribe address=...">mailto:xemacs-patches-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-patches/">http://calypso.tux.org/mailman/listinfo/xemacs-patches/</a></dd>
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-users-ja</strong> has been merged into
	  xemacs-beta.  Japanese is welcome, but please consider that
	  posts in English are likely to receive much more timely and
	  accurate response.  If Japanese-language traffic or user
	  demand justifies it, a separate Japanese-only user-oriented
	  list may be revived.  Send comments or requests to <a
	    href="mailto:stephen@xemacs.org">Stephen Turnbull</a>
	  (Japanese is OK).</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-users-ja" name="xemacs-users-ja">Legacy Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-users-ja/</dd>
	  <!--
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-users-ja-request@xemacs.org?body=subscribe address=...">mailto:xemacs-users-ja-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-users-ja/">http://calypso.tux.org/mailman/listinfo/xemacs-users-ja/</a></dd>
	  -->
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-users-ru</strong> has been merged into
	  xemacs-beta.  Russian is welcome, but please consider that
	  posts in English are likely to receive much more timely and
	  accurate response.  If Russian-language traffic or user
	  demand justifies it, a separate Russian-only user-oriented
	  list may be revived.  Send comments or requests to <a
	    href="mailto:stephen@xemacs.org">Stephen Turnbull</a>.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-users-ru" name="xemacs-users-ru">Legacy Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-users-ru/</dd>
	  <!--
          <dt>Subscribe by E-mail:</dt>
          <dd><a href="mailto:xemacs-users-ru-request@xemacs.org?body=subscribe address=...">mailto:xemacs-users-ru-request@xemacs.org?body=subscribe address=...</a></dd>
          <dt>Subscribe or change subscription by HTTP:</dt>
          <dd><a href="http://calypso.tux.org/mailman/listinfo/xemacs-users-ru/">http://calypso.tux.org/mailman/listinfo/xemacs-users-ru/</a></dd>
	  -->
        </dl>
      </td>
    </tr>
    <tr valign="top">
      <td rowspan="1" colspan="1">
        <p><strong>xemacs-winnt</strong> has been merged into
	  xemacs-beta, as the Windows support is now a standard part
	  of XEmacs.</p>
      </td>
      <td rowspan="1" colspan="1">
        <dl>
          <!-- one of (dd dt) -->
          <dt><a id="xemacs-nt" name="xemacs-nt">Legacy Archive</a>:</dt>
          <dd>http://list-archive.xemacs.org/pipermail/xemacs-nt/</dd>
        </dl>
      </td>
    </tr>
  </table>

  <h2><a id="subscribing" name="subscribing">How To Subscribe</a></h2>
  
  <p>
    Subscription to all the lists is accomplished by use of the
    mailman links listed under <strong>Subscribe or change
    subscription by HTTP:</strong> above, or by sending an e-mail
    message to <em>LISTNAME-request@xemacs.org</em> with
    `<em>subscribe</em>' (without the quotes) as the <b>BODY</b> of
    the message.</p>

  <p>
    You will receive a subscription confirmation message, which
    contains a personal options management URL and your password.
    Please bookmark this page.  Doing it yourself is a lot faster than
    sending mail to Postmaster.</p>

  <h2><a id="problems" name="problems">Problems</a></h2>

  <p>
    Many problems can be solved by visiting your personal options page
    for the list, via the URL you were sent in the welcome notice.
    You can also reach your options page for a list by visiting the
    <strong>Subscribe or change</strong> link for the list (mentioned
    in the list's entry in the table above), and entering your
    <em>subscribed</em> e-mail address in the last field in the
    form.</p>

  <p>
    One common problem is that you stop receiving mail from a list.
    If Mailman receives too many delivery failure notices in a short
    period, it will suspend your subscription.  You can confirm this
    state, and change it, from your personal options page.</p>

  <p>
    If you lose your password, you can have it emailed to you from
    this page.  You can also change your password, which is especially
    useful if you subscribe to several lists.</p>

  <p>
    If your posts don't make it to the lists, perhaps you have run
    afoul of the <a href="#spam">anti-spam</a> policy?
  </p>

  <p>Any comments, questions, or complaints about the lists
    should be brought to the attention of the
    <a href="mailto:list-manager@xemacs.org">XEmacs Mailing List
      Manager &lt;list-manager@xemacs.org&gt;</a>.</p>

  <p>
    <strong>Note to AOL users:</strong> Because XEmacs lists are
    public, the addresses are known to many viruses and spammers, and
    therefore are likely to be used to conceal real sources of
    undesired mail.  AOL's filter is quite stupid about this.  Several
    AOL users are bouncing mail, and we have turned off delivery to
    their subscriptions, because the bounce messages annoy the XEmacs
    list managers and AOL's Postmaster does not respond to inquiries
    (we usually can't reach you!).  You will have to both fix your
    filter and restore your subscription to delivery status using the
    Mailman interfaces.  (The XEmacs policy is not going to change.
    If your ISP is unwilling to provide resources to ensure that mail
    you have requested is delivered to you, XEmacs volunteers are not
    going to make up for that lack.  <strong>Note:</strong> It is now
    over three years since the above was written; if AOL's service has
    improved, we'd like to know at <a
    href="mailto:list-manager@xemacs.org">list-manager@xemacs.org</a>)</p>

  <h2><a id="spam" name="spam">Anti-Spam Measures</a></h2>

  <p>
    You should note that <strong>XEmacs mailing lists have open
    archives</strong>, and we currently take no measures to prevent
    address harvesting.  There are three reasons for this (besides the
    fact that it would involve a fair amount of effort to redo the
    archiving system): we expect that most people who post to XEmacs
    lists have effective spam filtering anyway, it is often desirable
    to make personal replies to posts (so we don't want to sanitize
    the mailing list distribution itself), and we get very few
    complaints, none from regular posters.
  </p>

  <p>
    Currently the XEmacs mailing lists are operated as members-only-post
    lists.  Other posts are moderated, first by automatic filters, then
    by humans.  Autoresponders cannot be used because they generate huge
    number of bounces due to non-existent addresses at poorly
    configured hosts, driving the postmaster crazy.  Instead, with a
    mixture of <a href="http://spamassassin.org/">SpamAssassin</a> and
    homebrewed procmail recipes we are highly (about 99%) effective in
    blocking spam posts.
  </p>

  <p>
    Due to a dramatic increase in the amount of spam and a near
    perfect record of like 0.05% false positives, we are <em>discarding
    near-certain spam</em> without checking as of 2004-04-27.  We have
    added more categories as recently as <strong>2006-12-26</strong>.
    Here are the criteria, any of which qualifies your post for automatic
    discard:
  </p>

  <ol>
    <li>Send a message which is of MIME type "multipart/alternative"
      or "multipart/related", containing both a "text/html" type part
      and an "image/*" type part.</li>
    <li>Have a known abusive from address (eg, daemon addresses at
      Microsoft.com, used by the MS-Blaster/Nachi viruses)</li>
    <li>Send posts with unencoded 8-bit characters in the headers</li>
    <li>Send posts in unwanted MIME charsets; except for
      xemacs-patches (non-ISO-8859 charsets are held for moderation),
      the xemacs-users-ja (Japanese is permitted) and xemacs-users-ru
      (Cyrillic is permitted), only ISO-8859 charsets and Windows-1252
      are permitted.</li>
    <li>Convince SpamAssassin your post is spam (5 points, vanilla config)</li>
    <li>Send mail to majordomo@xemacs (we're a Mailman site now)</li>
    <li>
      Use implicit addresses (ie, not addressed to the list).  Either
      the <strong>To</strong> header or the <strong>Cc</strong> header
      <em>must</em> contain "xemacs.org".
    </li>
    <li>
      Use too many addresses (over 10).
    </li>
    <li>
      Include any of several drug names in the headers, including
      obfuscated versions like "V1agdra" and "c.i.a.l.i.s".
    </li>
    <li>
      Include the word "rolex" or an apparent attempt to sell watches
      in the headers.
    </li>
    <li>
      Have a From or Sender address that procmail thinks is a daemon.
      Basically that means sendmail and other MTAs, mailing list
      managers, and root.
    </li>
    <li>
      Have From, To, <em>and</em> Subject headers containing 100%
      ASCII text encoded as utf-8 quoted-printable.
    </li>
  </ol>

  <p>
    This list may be extended in the future, as we discover recipes
    that catch lots of spam with no false positives.  Of course, since
    we throw it away, we can no longer check for false positives.  If
    you think your post may have been mistakenly filtered, feel free
    to write to
    <a href="mailto:list-manager@xemacs.org">list-manager@xemacs.org</a>.
  </p>

  <p>
    Please do not write to the list.  Even resending is a bad idea
    unless you think <em>you</em> made a mistake.  Also, we request
    that you allow 4 hours for delivery before reporting a loss;
    changes in DNS configuration, server outages, and the like can
    cause delays of several hours even if other list traffic seems to
    be arriving normally.
  </p>

  <p>
    Exceptions can be made, and if you need one (for example, if your
    documentation contains the phrase "click on the link", you would
    run afoul of the "no soliciting clicks" clause---this is just an
    example, patches already have an exception for that), write to
    <a href="mailto:list-manager@xemacs.org">list-manager@xemacs.org</a>.  See
    <a href="http://spamassassin.org/">SpamAssassin's site</a> for more
    information about SpamAssassin and what it is likely to block.
  </p>

  <p>
    Other suspicious mail is held for moderation.  This causes delays
    averaging 12 hours when I've got time for it, up to 72 hours
    (especially at weekends).
  </p>

  <ol>
    <li>A message which is of MIME type "multipart/alternative"
      or "multipart/related", containing an "image/*" type part.</li>
    <li>
      Broken headers, including addresses or message IDs apparently
      munged or added by relays.
    </li>
    <li>
      Null subjects and certain single-word subjects.
    </li>
    <li>
      Implicit addresses (ie, bcc'ing a list).
    </li>
    <li>Include an attachment with an extension that IE thinks is
      executable (practically everything but .txt and .tar.gz).
    </li>
    <li>
      A large number of phrases commonly used in spamvertisements,
      including phrases referring to stocks, mortgages, diets,
      well-known proprietary software, etc.
    </li>
    <li>
      A variety of sexual or scatological terms that in my experience
      are more likely to be used literally in spamverts than
      figuratively in flames.
    </li>
    <li>
      Invitations to click on a link.  Links are OK, but
      don't include any text that would convince SpamAssassin you
      suggested clicking on it.  XEmacs users are smart enough to
      figure that out for themselves.
    </li>
    <li>
      Posts that contain <em>any</em> HTML.
    </li>
    <li>
      There are also certain restrictions on content.  Try to avoid
      phrases associated with the so-called <em>Nigerian scam</em> or
      containing <em>the seven words you cannot say on TV</em>
      (<em>i.e.</em>, your post looks like spam for a porn site or Viagra).
    </li>
    <li>
      <strong>From</strong>, <strong>To</strong>, <strong>Cc</strong>,
      or <strong>Subject</strong> containing entirely QP- or
      BASE64-encoded text with a charset of ISO-8859-1 or UTF-8.
    </li>
  </ol>

  <p>
    These posts are reviewed for false positives, which are resent to
    the list, before throwing the rest away.
  </p>

  <!-- Keep this comment at the end of the file
  Local variables:
  mode: xml
  sgml-omittag:nil
  sgml-shorttag:nil
  sgml-namecase-general:nil
  sgml-general-insert-case:lower
  sgml-minimize-attributes:nil
  sgml-always-quote-attributes:t
  sgml-indent-step:2
  sgml-indent-data:t
  sgml-parent-document:("../template.html" "html" "body" "table" "tr" "td")
  sgml-exposed-tags:nil
  sgml-local-catalogs:nil
  sgml-local-ecat-files:nil
  End:
  -->