-
Notifications
You must be signed in to change notification settings - Fork 15
/
FAQ
6065 lines (4089 loc) · 275 KB
/
FAQ
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
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
EZFAQ 0.40 - ezmlm-idx and ezmlm FAQ
Fred Lindberg, lindberg@id.wustl.edu, Fred B. Ringel,
fredr@rivertown.net, & Bruce Guenter bruce@untroubled.org
2006-11-24
This document is a collection of frequently asked questions about
ezmlm-idx. Where applicable, ezmlm itself is also covered. This FAQ
presumes familiarity with Unix, and with the basic concepts of E-mail
and mailing lists. This FAQ is updated for ezmlm-0.53 and ezmlm-
idx-0.40.
______________________________________________________________________
Table of Contents
1. General Information
1.1 Acknowledgements
1.2 What is this document?
1.3 Terminology
1.4 What is the difference between ezmlm and ezmlm-idx?
1.5 Where can I get all of the ezmlm-related programs?
1.6 Where can I find documentation for ezmlm and patches?
1.7 Where do I send comments on this document?
1.8 How to experiment with new versions of ezmlm-idx.
2. Quick start
3. Overview of mailing list management and mailing list managers
4. Overview of ezmlm function
4.1 The basic setup.
4.2 Inventions in ezmlm.
4.3 The qmail delivery mechanism.
4.4 What the different programs do.
4.5 What the different files in the list directory do.
4.6 The paper path for posts.
4.7 The ezmlm path for moderation messages.
4.8 The ezmlm path for administrative messages.
4.9 The ezmlm path for bounces.
4.10 Messages to list-owner and list-digest-owner.
4.11 Structure of subscriber databases.
4.12 Local case in E-mail addresses.
4.13 Testing SENDER to allow posts only from list subscribers.
4.14 How cookies work.
4.15 How moderator E-mail addresses are stored.
4.16 How subscription moderation works.
4.17 How remote administration works.
4.18 How message moderation works.
4.19 How QMQP support works
4.20 How messages are stored in the archive.
4.21 How the message index works.
4.22 How threading works.
4.23 How digests work.
4.24 How WWW archive access works.
4.25 How ezmlm-tstdig works.
4.26 How sublists work.
4.27 How sublisting can be made transparent to the user.
4.28 How to service commands in the subject line.
4.29 How to support alternative command names.
4.30 How to add your own commands.
4.31 How remote administrators can retrieve a subscriber list
4.32 How remote administrators can determine the number of subscribers
4.33 How remote admins can see if an address is a subscriber or not
4.34 How remote administrators can search the subscription log
4.35 How text file editing works.
4.36 How subject line prefixes work.
4.37 How bounces are handled.
4.38 How the info and faq commands work.
4.39 How the global ezmlm list address works.
4.40 How ezmlm-cron works.
4.41 How ezmlm-make works.
4.42 What names can I use for my lists?
4.43 Lists in virtual domains
4.44 How do I make customization simple for me/my users?
5. ezmlm support for SQL databases.
5.1 Why use an SQL database with ezmlm?
5.2 Why not to use an SQL database with ezmlm.
5.3 Tables used for (My)SQL support.
5.3.1 Address tables.
5.3.2 Subscriber log tables.
5.3.3 Message logging tables.
5.4 How to set up a simple list with SQL support.
5.4.1 Helper programs for SQL-enabled lists.
5.5 Manually manipulating the subscribers of a SQL-enabled list.
5.6 Converting to and from and SQL database.
5.7 Optimizing MySQL for ezmlm.
5.7.1 Address SELECTs, additions, removals.
5.8 Maintenance of the MySQL database.
6. Possible error conditions in ezmlm lists.
6.1 What do I do if ezmlm doesn't work?
6.2 How do I report ezmlm bugs?
6.3 Where do I send suggestions for ezmlm-idx improvements?
6.4 Using ezmlm-test to check the ezmlm(-idx) programs.
6.5 Using ezmlm-check to find setup errors.
6.6 Posts are rejected: Sorry, no mailbox here by that name (#5.1.1).
6.7 Post are not sent to subscribers.
6.8 ezmlm-make fails: usage: ezmlm-make ...
6.9 ezmlm-make fails: Unable to create ...
6.10 ezmlm-make fails: ... ezmlmrc does not exist
6.11 Index/get/thread requests fail quietly or with errors from ezmlm-manage.
6.12 Digest triggering requests fail.
6.13 Remote administration (un)subscribe confirm requests go to the user, not the moderator.
6.14 (Un)subscribers does not receive a (un)subscribe acknowledgement
6.15 Messages posted to a moderated list are sent out without moderation.
6.16 Messages posted to a moderated list do not result in moderation requests.
6.17 Moderation request replies do not result in the appropriate action.
6.18 Moderator comments with moderation request replies are not added to the post/sent to the poster.
6.19 Some headers are missing from messages in the digest.
6.20 Some Received: headers are missing from messages.
6.21 My Mutt users cannot thread their digest messages.
6.22 Posts fail: Message already has Mailing-List (#5.7.2).
6.23 The last line of a
6.24 No CONFIRM requests are sent to moderators.
6.25 Deliveries fail ``temporary qmail-queue error''
6.26 How to deal with corrupted subscriber lists
6.27 Vacation program replies are treated as bounces by ezmlm.
6.28 Digests do not come at regular hours.
6.29 Preventing loops from misconfigured subscriber addresses.
6.30 A user can subscribe and receives warning and probe messages, but no messages from the list.
7. Customizing ezmlm-make operation via ezmlmrc
7.1 Using ezmlm-make to edit existing lists.
7.2 What is ezmlmrc?
7.3 Changing defaults for
7.4 Changing default moderator directories.
7.5 Adapting ezmlm-make for virtual domains.
7.6 Setting up ezmlm-make for special situations.
8. Restricting message posting to the list.
8.1 Requiring the list address in To:/Cc: headers.
8.2 Rejecting messages sent from other mailing lists.
8.3 Restricting posts based on the Subject line.
8.4 Restricting the size of posts.
8.5 Restricting posts based on MIME content-type.
8.6 Restricting posts to list subscribers.
8.7 Restricting posts to an arbitrary set of E-mail addresses (higher security option).
8.8 Completely restricting posts.
8.9 A general solution to restricting posts based on SENDER.
9. Customizing outgoing messages.
9.1 Adding a trailer to outgoing messages.
9.2 Adding a subject prefix to outgoing messages.
9.3 Adding a header to outgoing messages.
9.4 Adding a message number header.
9.5 Removing headers from outgoing messages.
9.6 Removing MIME parts from messages.
9.7 Limiting ``Received:'' headers in outgoing messages.
9.8 Setting ``Reply-To: list@host''.
9.9 Configuring the list so posts are not copied to the original sender.
9.10 Customizing ezmlm notification messages.
9.11 Specifying character set and content-transfer-encoding for outgoing ezmlm messages.
10. Customizing archive retrieval.
10.1 Specifying the format for retrieved messages.
10.2 Specifying the default format for digests and archive retrieval.
10.3 Limiting the number of messages per -get/-index request.
11. Restricting archive retrieval.
11.1 Restricting archive access to subscribers.
11.2 Restricting available archive retrieval commands.
11.3 Restricting archive retrieval to moderators.
11.4 Allowing archive retrieval from a non-public list.
12. Customizing digests.
12.1 Setting up a digest list.
12.2 Generating daily digests.
12.3 Generating the first digest.
12.4 Adding standard administrative information to digests.
12.5 Controlling the digest format.
12.6 Customizing bounce handling.
13. Remote administration.
13.1 How can I remotely add moderators, subscriber aliases, etc?
13.2 Moderating posts from a secondary account.
13.3 Moderating subscription from a secondary account.
13.4 Automatically approving posts or subscriptions.
13.5 Allowing remote administrators to get a subscriber list.
13.6 Allowing remote administrators to retrieve or search a subscription log.
13.7 Allowing users to get a subscriber list.
13.8 Changing the timeout for messages in the moderation queue.
13.9 Finding out how many messages are waiting for moderation.
13.10 Using the same moderators for multiple lists.
13.11 Using different moderators for message and subscription moderation.
13.12 Setting up moderated lists with the list owner as the ``super moderator'' able to add/remove moderators remotely.
13.13 Customizing ezmlm administrative messages.
13.14 Manually approving a message awaiting moderation.
13.15 Manually rejecting a message awaiting moderation.
14. Sublists.
14.1 Sublists of ezmlm lists.
14.2 Sublists of non-ezmlm lists.
14.3 How to set up a cluster of list and sublists with standard databases.
15. Migration to Ezmlm from other Mailing List Managers.
15.1 Basic Concepts.
15.2 Setting up ezmlm to respond to host-centric commands.
15.3 Commands of other mailinglist managers recognized by ezmlm.
15.3.1 Listproc/Listserv.
15.3.2 Majordomo.
15.3.3 Smartlist.
16. Optimizing list performance.
16.1 Crond-generated digests for better performance.
16.2 Optimizing execution of ezmlm-warn(1).
16.3 Decreasing ezmlm-warn time out to increase performance.
16.4 Use ezmlm without ezmlm-idx for maximum performance.
16.5 Not archiving to maximize performance.
16.6 Sublists to maximize performance.
17. Miscellaneous.
17.1 How do I quickly change the properties of my list?
17.2 Open archived list with daily digests.
17.3 Variations in moderation
17.4 Lists that allow remote admin, but not user initiated subscription or archive retrieval.
17.5 Lists that allow remote admin, user archive retrieval, but not user-initiated subscription.
17.6 Lists that restrict archive retrieval to subscribers.
17.7 Lists that do not allow archive retrieval at all.
17.8 Lists that do not allow archive retrieval and do not allow digest triggering per mail.
17.9 Lists that allow archive retrieval only to moderators, but allow user-initiated subscription.
17.10 Lists that do not require user confirmation for (un)subscription.
17.11 Announcement lists for a small set of trusted posters
17.12 Announcement lists allowing moderated posts from anyone.
17.13 Announcement lists with less security and more convenience.
18. Ezmlm-idx compile time options.
18.1 Location of binaries.
18.2 Location of man pages.
18.3 Base directory of qmail-installation.
18.4 Short header texts, etc.
18.5 Arbitrary limits.
18.6 Command names.
18.7 Error messages.
18.8 Paths and other odd configuration items.
19. Multiple language support.
19.1 Command names.
19.2 Text files.
19.3 Multi-byte character code support.
20. Subscriber notification of moderation events.
20.1 General opinions.
20.2 Users should know that the list is subscription moderated.
20.3 Subscribers should know that posts are moderated.
20.4 Senders of posts should be notified of rejections.
21. Ezmlm-idx security.
21.1 General assumptions.
21.2 SENDER manipulation.
21.3 ezmlm cookies.
21.4 Lists without remote admin/subscription moderation.
21.5 Message moderation.
21.6 Subscription moderation.
21.7 Remote administration.
21.8 Remote editing of ezmlm text files.
21.9 Digest generation and archive retrieval.
21.10 Convenience for security: the ezmlm-manage ``-S'' and ``-U'' switches.
21.11 Denial of service.
21.12 Moderator anonymity.
21.13 Confidentiality of subscriber E-mail addresses.
21.14 Help message for moderators.
21.15 Sublists.
21.16 SQL databases.
21.17 Reporting security problems.
______________________________________________________________________
11.. GGeenneerraall IInnffoorrmmaattiioonn
11..11.. AAcckknnoowwlleeddggeemmeennttss
Many ezmlm users have contributed to improvements in ezmlm-idx. These
are listed in the RREEAADDMMEE..iiddxx file in the ezmlm-idx distribution.
Others have through questions and suggestions inspired parts in this
FAQ, or pointed out errors or omissions. Thanks! Direct contributions
are attributed to the respective authors in the text. Thanks again!
11..22.. WWhhaatt iiss tthhiiss ddooccuummeenntt??
This FAQ contains answers to many questions that arise while
installing ezmlm, ezmlm-idx, and while setting up and managing ezmlm
mailing lists. See ``'' for a brief summary of what is ezmlm and what
is ezmlm-idx.
Many aspects of ezmlm are covered in several places in this FAQ. The
early sections explain how ezmlm works. Later sections discuss how to
deal with possible errors/problems. Subsequent sections discuss
details of customization and list setup in a _H_O_W_T_O form. Finally,
there are sections on information philosophy for moderated lists and
on security aspects on ezmlm lists.
This is an evolving document. If you find any errors, or wish to
comment, please do so to the authors. This FAQ is currently aimed at
system administrators and knowledgeable users, and heavily weighted
towards questions specific to the ezmlm-idx add-on.
If you have problems with the ezmlm-idx package, please start by
reading the ``man'' pages which come with each program, then this
document and other ezmlm documentation which is identified here. If
you have exhausted these resources, try the ezmlm and qmail mailing
lists and their respective mailing list archives. If you have solved a
problem not in the documentation, write it up as a proposed section of
a FAQ and send it to the authors. This way, it can be added to the
next version of this FAQ.
11..33.. TTeerrmmiinnoollooggyy
This document uses a number of terms. Here are the meanings ascribed
to them by the authors.
DDIIRR
The base directory of the list.
SSEENNDDEERR
The envelope sender of the message, as passed to ezmlm by qmail
via the $SENDER environment variable.
LLOOCCAALL
The local part of the envelope recipient. For list-get-1@host,
it is usually _l_i_s_t_-_g_e_t_-_1. If host is a virtual domain,
controlled by _u_s_e_r_-_s_u_b, then local would be _u_s_e_r_-_s_u_b_-_l_i_s_t_-_g_e_t_-_1.
mmooddddiirr
Base directory for moderators. Moderator E-mail addresses are
stored in a hashed database in mmooddddiirr//ssuubbssccrriibbeerrss//. By default,
``moddir'' is DDIIRR//mmoodd//.
To add or remove moderators:
% ezmlm-sub DIR moddir moderator@host.domain
% ezmlm-unsub DIR moddir moderator@host.domain
ddoottddiirr
The second argument of ezmlm-make is the main .qmail file for
the list. dotdir is the directory in which this ``dot file''
resides, i.e. the directory part of the ``dot'' argument. This
is usually the home directory of the user controlling the list
(but NOT necessarily of the one creating the list). Thus, _d_o_t_d_i_r
is ~~aalliiaass// if ``root'' creates a list:
# ezmlm-make ~alias/list ~alias/.qmail-list ...
_d_o_t_d_i_r is where the ..eezzmmllmmrrcc file is expected when the ezmlm-
make(1) ``-c'' switch is used (see ``Customizing ezmlm-make opera-
tion'').
eezzmmllmm bbiinnaarryy ddiirreeccttoorryy
The directory where the ezmlm-binaries are normally stored, as
defined at compile time in ccoonnff--bbiinn. This is compiled into the
programs and does not change just because you have moved the
program.
eezzmmllmm--ggeett((11))
This is a reference to the ezmlm-get.1 man page. Access it with
one of the following:
% man ezmlm-get
% man 1 ezmlm-get
or if you have not yet installed ezmlm-idx (replace ``xxx'' with
the version number):
% cd ezmlm-idx-0.xxx
% man ./ezmlm-get.1
bbaasseeddiirr
The list directory when referencing the list subscriber address
database. For E-mail addresses stored in a set of files within
DDIIRR//ssuubbssccrriibbeerrss//, the ``basedir'' is ``DIR''.
aaddddrreessss ddaattaabbaassee
A collection of E-mail addresses stored in a set of files within
the ``subscribers'' subdirectory of the basedir,
DDIIRR//ssuubbssccrriibbeerrss//.
mmeessssaaggee mmooddeerraattoorr
An address to which moderation requests for posts to the list
are sent. The moderation requests are formatted with
``From:''-``reject'' and a ``To:''-``accept'' default headers
for moderator replies. A reply to the ``reject'' address leads
to the rejection of the post. A reply to the ``accept'' address
leads to the acceptance of the post. Any E-mail address can be a
moderator E-mail address. Any number of moderator E-mail
addresses can be used. If a post is sent from a moderator E-mail
address, the moderation request is sent to that E-mail address
only. If a post is sent from an E-mail address that is not a
moderator, a moderation request is sent to all moderators.
The first reply to the moderation request determines the fate of
the message. Further requests for the action already taken are
silently ignored, while a request for the contrary action
results in an error message stating the actual fate of the
message. Thus, if you want to ``accept'' the message and it has
already been accepted, you receive no reply, but if you attempt
to ``reject'' it, you will receive an error message stating that
the message already has been accepted.
Most lists are not message moderated. If they are, the owner is
usually a ``message moderator'', sometimes together with a few
other trusted users.
For an announcement list, it is common to make all the
``official announcers'' ``message moderators''. This way, they
can post securely and ``accept'' their own posts, while posts
from other users will be sent to this set of ``official
announcers'' for approval.
ssuubbssccrriippttiioonn mmooddeerraattoorr
An E-mail address where subscription moderation requests are
sent. A subscription moderation request is sent after a user has
confirmed her intention to subscribe. The subscription
moderation request is sent to all moderators. As soon as a reply
to this message is received, the user is subscribed and
notified. Any E-mail address can be a subscription moderator and
any number of subscription moderators can be used.
Unsubscribe requests are never moderated (except when the ezmlm-
manage(1) ``-U'' flag is used and the sender attempts to remove
an address other than the one s/he is sending from). It is hard
to imagine a legitimate mailing list that would want to prevent
unsubscriptions.
rreemmoottee aaddmmiinniissttrraattoorr
When a remote administrator subscribes or unsubscribes a list
member, the ``confirm'' request is sent back to the remote
administrator, rather than to the subscriber's E-mail address.
This allows the remote administrator to (un)subscribe any list
member without the cooperation of the subscriber at that
address. Any E-mail address can be a remote administrator and
any number of E-mail addresses can be remote administrators.
The set of E-mail addresses that are ``remote administrators''
and ``subscription moderators'' are always the same. This set of
E-mail addresses can be ``remote administrators'',
``subscription moderators'' or both.
For most lists, the owner would be the ``remote administrator'',
if s/he wishes to moderate messages, the owner would be the
``message moderator'' and if s/he wishes to moderate
subscriptions the owner would also be the ``subscription
moderator''.
The list's ``message moderator(s)'' can be the same, but can
also be set up to be completely different.
CChhaannggiinngg lliisstt ````oowwnneerrsshhiipp''''
Within this FAQ there are references to the need to check or
change the list ``ownership.'' This is not a reference to the
individual user who is the ``list-owner'', but a reference to
the ownership of the files by your operating system which make
up the list and reside in DDIIRR//.
To change the ownership of DDIIRR// and everything within:
% chown -R user DIR
% chgrp -R group DIR
Depending on your system/shell, it may be possible to combine these
commands into either:
% chown -R user.group DIR
% chown -R user:group DIR
11..44.. WWhhaatt iiss tthhee ddiiffffeerreennccee bbeettwweeeenn eezzmmllmm aanndd eezzmmllmm--iiddxx??
ezmlm-0.53 is a qmail-based mailing list manager written by Dan J.
Bernstein. It has all the basic functionality of a mailing list
manager, such as subscriber address management including automated
bounce handling as well as message distribution and archiving.
ezmlm-idx is an add-on to ezmlm. It adds multi-message threaded
message retrieval from the archive, digests, message and subscription
moderation, and a number of remote administration function. It
modifies the configuration program ezmlm-make(1) so that it uses a
text file template rather than compiled-in texts in list creation. In
this manner, ezmlm-idx allows easy setup of lists in different
languages and customization of default list setup. ezmlm-idx also adds
MIME handling, and other support to streamline use with languages
other than English. As an ezmlm add-on, ezmlm-idx does not work
without ezmlm and tries to be compatible with ezmlm as much as
possible. ezmlm-idx also modifies the ezmlm subscriber database to be
case insensitive to avoid many unsubscribe problems.
New in ezmlm-idx-0.40 are better support for announcement lists,
support for QMQP to offload message distribution onto external hosts,
simplified optional SQL database use (MySQL or PostgreSQL), more
flexibility in determining which messages should be moderated, a WWW
interface to the list archives, and many small improvements.
ezmlm-idx-0.32 adds improved handling of very large lists with
optimized bounce handling, ezmlm-split(1) for forwarding (un)subscribe
requests to sublists to allow sublisting transparent to the
subscriber, and SQL support to allow sublisting with improved message
authentication and monitoring of list function, as well as dynamic
addition/removal/reconfiguration of sublists. Also, subscriber
``From:'' lines are logged with support for finding a subscription
address from a name. The qmail DEFAULT variable is used, if present.
Together, these additions eliminate the most common problems making
ezmlm use and administration even easier.
This document is a FAQ for ezmlm-idx. However, many of the basic items
that are discussed also apply to ezmlm per se. Referring to the two
paragraphs above, it should be relatively easy to figure out which
features require ezmlm-idx.
11..55.. WWhheerree ccaann II ggeett aallll ooff tthhee eezzmmllmm--rreellaatteedd pprrooggrraammss??
We have now registered ezmlm.org to make access to ezmlm-idx and
related programs/documentation easier.
DDaann JJ.. BBeerrnnsstteeiinn''ss eezzmmllmm--00..5533
+o <ftp://cr.yp.to/pub/software/ezmlm-0.53.tar.gz>
+o <ftp://ftp.ezmlm.org/pub/qmail/ezmlm-0.53.tar.gz>
+o <ftp://ftp.ntnu.no/pub/unix/mail/qmail/ezmlm-0.53.tar.gz>
+o <ftp://ftp.pipex.net/mirrors/qmail/ezmlm-0.53.tar.gz>
+o <ftp://ftp.jp.qmail.org/qmail/ezmlm-0.53.tar.gz>
+o <ftp://ftp.rifkin.technion.ac.il/pub/qmail/ezmlm-0.53.tar.gz>
+o <ftp://ftp.mira.net.au/unix/mail/qmail/ezmlm-0.53.tar.gz>
+o <http://www.qmail.org/>
TThhee llaatteesstt vveerrssiioonn ooff eezzmmllmm--iiddxx
ezmlm-idx releases are numbered ``ezmlm-idx-0.xy[z]''. Versions
with the same ``x'' are backwards compatible. A change in ``x''
signifies major changes, some of which _m_a_y require list changes
(see UPGRADE). However, backwards compatibility with
ezmlm-0.53 list will be maintained. Thus, this is an issue only
if you are already using an older version of ezmlm-idx.
Addition of ``z'' are bug fixes only. Thus, ezmlm-idx-0.301 is
ezmlm-idx-0.30 with known bugs fixed (but no other significant
changes). When available, patches are named
``filename-0.xy[z].diff'', where ``0.xy[z]'' corresponds to the
release to which they apply. When a number of bugs (or a
significant bug) are found a bug-fix release is made
incorporating all the patches for the previous version.
To get the latest features, look for the highest number (``e.g.
ezmlm-idx-0.40''). Any bugs in versions with new features are
expected to be limited to the new features.
To get the most solid version, get the highest 3-digit number,
i.e. a bug fix. If you already run a version in that series and
a new bug fix is released, see CHANGES to determine if it is
worthwhile to upgrade. Most bugs so far have been relevant only
when using lists in very unusual ways or with rarely used
options.
+o <ftp://ftp.ezmlm.org/pub/patches/>
+o <ftp://gd.tuwien.ac.at/infosys/mail/qmail/ezmlm-patches/> ftp
mirror in Austria.
+o <http://gd.tuwien.ac.at/infosys/mail/qmail/ezmlm-patches/> http
access to the same mirror.
+o <ftp://ftp.win.or.jp/pub/network/mail/qmail/ezmlm-idx/> ftp
mirror in Japan.
eezzmmllmmrrcc((55)) ffiilleess ffoorr ddiiffffeerreenntt llaanngguuaaggeess
The latest versions at the time of release of a package are
included in that package. Thus, this directory will have a file
labeled with the current ezmlm-idx version number only if it has
been updated later than the package. ezmlmrc(5) files are
updated and new ones are added all the time, also with bug fix
releases. Therefore, always look at the latest package. Please
note that ezmlmrc may change significantly between versions.
Thus, do not expect the ezmlm-idx-0.324 ezmlmrc.es to work with
ezmlm-idx-0.40.
ezmlmrc(5) files contain some release-specific configurations.
Do not use a later file (other than from bug fix releases) with
an earlier version of the programs. It is usually OK to use a
version from an earlier package (see UPGRADE), but some new
functionality may nor be available.
To contribute an ezmlmrc(5) file in a new language, start with
the en_US version from the latest package, and send the gzipped
file to bruce@untroubled.org. Please leave comments intact and
in English and do not change the order of items in the file.
This will facilitate maintenance.
+o <ftp://ftp.ezmlm.org/pub/patches/ezmlmrc/>
+o <ftp://gd.tuwien.ac.at/infosys/mail/qmail/ezmlm-
patches/ezmlmrc/>
+o <http://gd.tuwien.ac.at/infosys/mail/qmail/ezmlm-
patches/ezmlmrc/>
+o <ftp://ftp.win.or.jp/pub/network/mail/qmail/ezmlm-idx/ezmlmrc/>
eezzmmllmm--iissssuubb--00..0055
+o <ftp://ftp.ezmlm.org/pub/patches/ezmlm-issub-0.05.tar.gz>. Use
ezmlm-issub only if you do not use ezmlm-idx. The same
functionality is available in ezmlm-idx and the packages are not
compatible.
+o Also via mirrors mentioned above.
RRPPMMss aanndd SSRRPPMMSS ooff qqmmaaiill,, eezzmmllmm aanndd eezzmmllmm--iiddxx
+o <ftp://ftp.ezmlm.org/pub/patches/>
+o <ftp://summersoft.fay.ar.us/pub/qmail/>
11..66.. WWhheerree ccaann II ffiinndd ddooccuummeennttaattiioonn ffoorr eezzmmllmm aanndd ppaattcchheess??
mmaann ppaaggeess
All ezmlm component programs come with their own man pages.
Thus, for info on _e_z_m_l_m_-_s_e_n_d, type:
% man ezmlm-send
or if you have unpacked ezmlm, but not made it or installed it:
% cd ezmlm-0.53
% man ./ezmlm-send.1
eezzmmllmm((55))
General info on ezmlm and list directories is in eezzmmllmm..55:
% man ezmlm
or
% cd ezmlm-0.53
% man ./ezmlm.5
_N_O_T_E_: Installation of the ezmlm-idx package updates some existing
man pages to reflect changes made by the patch (e.g. ezmlm-
send(1), ezmlm(5)).
TTeexxtt ffiilleess iinn tthhee ddiissttrriibbuuttiioonn
ezmlm comes with a RREEAADDMMEE file with general instructions, an
IINNSSTTAALLLL file with installation instructions, an UUPPGGRRAADDEE file for
upgrading from a previous version and a CCHHAANNGGEESS file with
information on changes from previous versions. ezmlm-idx comes
with similar files suffixed with ``..iiddxx''. Most other patches or
add-ons contain similar files and man pages and should contain
identifying suffixes (.iss for ezmlm-issub, for example). For a
discussion of the authors' understanding of ezmlm security, see
``Ezmlm-idx security''.
````EEzzmmaann'''',, aann eezzmmllmm//iiddxx mmaannuuaall
The ezmlm manual is a brief manual that is meant for list
subscribers, list moderators and remote administrators, and as
an introduction for list owners. It is useful even if you do not
use ezmlm-idx. Features requiring ezmlm-idx are marked as such.
The manual is available as a set of html files, as a text file,
and in a ``letter'' and ``A4'' postscript version:
+o ezman for download <ftp://ftp.ezmlm.org/pub/patches/ezman/>
+o An on-line html version <http://www.ezmlm.org/ezman>
TThhiiss FFAAQQ
This FAQ is built from a sgml source. It is available in the
following formats:
+o A text file <ftp://ftp.ezmlm.org/pub/patches/ezfaq.txt.gz>
+o An on-line html version <http://www.ezmlm.org/>
+o Html for download
<ftp://ftp.ezmlm.org/pub/patches/ezfaq.html.tar.gz>
+o A postscript (letter) version
<ftp://ftp.ezmlm.org/pub/patches/ezfaq.ps.gz>
+o A postscript (A4) version
<ftp://ftp.ezmlm.org/pub/patches/ezfaq.ps4.gz>
+o Via mirrors mentioned for the ezmlm-idx package.
+o An up-to-date text version,FFAAQQ..iiddxx, included with the ezmlm-idx
package.
WWWWWW rreessoouurrcceess
AAnn oonn--lliinnee vveerrssiioonn ooff tthhiiss FFAAQQ
<http://www.ezmlm.org/>The main site with an up-to-date
mirror list. <http://www.de.ezmlm.org/>German mirror.
<http://www.pl.ezmlm.org/www.ezmlm.org/>Polish mirror.
<http://www.jp.ezmlm.org/>Japanese mirror.
<http://www.pt.ezmlm.org/>Portuguese mirror.
<http://www.at.ezmlm.org/>Austrian mirror.
<http://www.ca.ezmlm.org/ezmlm/>Canadian mirror.
GGeenneerraall qqmmaaiill aanndd eezzmmllmm iinnffoo
+o Dan J. Bernstein's qmail page
<http://www.pobox.com/~djb/qmail.html>
+o Dan J. Bernstein's ezmlm page
<http://www.pobox.com/~djb/ezmlm.html>
+o Russell Nelson's qmail page <http://www.qmail.org>
+o Mirrors of www.qmail.org <http://www.ISO.qmail.org>.
Substitute your two-letter country abbreviation for ``ISO''.
TThhee qqmmaaiill mmaaiilliinngg lliisstt aarrcchhiivvee
+o <http://www.ornl.gov/cts/archives/mailing-lists/qmail/>
TThhee eezzmmllmm mmaaiilliinngg lliisstt aarrcchhiivvee
+o <http://sunsite.auc.dk/mhonarc-archives/ezmlm/>
<http://www.ezmlm.org/archive/> This archive of the ezmlm
list is searchable from 11/97-present. ezmlm-cgi(1) is used
to allow direct access to the sublist archive.
MMaaiilliinngg lliissttss
Please read other documentation and mailing list archives before
posting questions to the lists. It's also useful to ``lurk'' on
the list for a few days, (i.e. to subscribe and read without
posting) before asking your questions on the list.
To subscribe, send mail to the E-mail addresses listed:
+o Dan Bernstein's ezmlm list: ezmlm-subscribe@list.cr.yp.to
+o A digest version of the ezmlm list fredr-ezmlm-digest-
subscribe@rivertown.net
+o Dan Bernstein's qmail list: qmail-subscribe@list.cr.yp.to
+o The Japanese ezmlm list: ezmlm-subscribe@jp.qmail.org
+o The Japanese qmail list: qmail-subscribe@jp.qmail.org
11..77.. WWhheerree ddoo II sseenndd ccoommmmeennttss oonn tthhiiss ddooccuummeenntt??
To the authors via E-mail:
+^Ho Bruce Guenter, bruce@untroubled.org
+o Fred Lindberg, lindberg@id.wustl.edu
+o Fred B. Ringel, fredr@rivertown.net
11..88.. HHooww ttoo eexxppeerriimmeenntt wwiitthh nneeww vveerrssiioonnss ooff eezzmmllmm--iiddxx..
ezmlm-idx>=0.23 writes DDIIRR//ccoonnffiigg in a standard format. If ezmlm-
make(1) is invoked with the ``-e'' or ``-+'' switch and the ``DIR''
argument only, ezmlm-make(1) will read other arguments from this file.
The difference between the switches is that with ``-e'' the options
used are the ones specified on the command line, whereas with ``-+''
they are the ones currently active for the list, as overridden by any
command line options. Thus, with just:
% ezmlm-make -+ DIR
you can rebuild the list, without affecting any archives, list state
variables, etc. You will _l_o_s_e _m_a_n_u_a_l _c_u_s_t_o_m_i_z_a_t_i_o_n_s _t_o _s_o_m_e _o_f _y_o_u_r
_f_i_l_e_s. However, text files and DDIIRR//hheeaaddeerraadddd are protected against
being overwritten, so that your manual customizations of these files
are retained. To override this protection, simply specify the used
edit switch twice, e.g. ``-ee'' and ``-++'', respectively. This is a
feature introduced in ezmlm-idx-0.40.
To test a new version of ezmlm-idx or to run several version, make the
new version as per IINNSSTTAALLLL..iiddxx (if you haven't used ezmlm-idx before)
or UUPPGGRRAADDEE..iiddxx (if you've got a previous version of ezmlm-idx
installed), setting ccoonnff--bbiinn to a new directory. You can use either
the current directory or any other directory. If not using the current
dir, you also have to:
% make install
If you now edit the list using the new ezmlm-make program, the list
will automatically be configured to use the new binaries. To change
back to the ``default'' installation, just edit the list again, this
time with the old ezmlm-make(1).
If your system has an //eettcc//eezzmmllmmrrcc file, you may need to temporarily
place the eezzmmllmmrrcc((55)) file for the ezmlm version you want to test in
ddoottddiirr of the list and use the ezmlm-make(1) ``-c'' switch (see
``Terminology: dotdir'').
ezmlm-idx>=0.314 comes with ezmlm-test(1), a program that tests most
functions of ezmlm+idx and can be used before installation.
22.. QQuuiicckk ssttaarrtt
1. Create a use ``eztest'' for testing. If you use another name, add
the switch ``-u another_name'' to the ezmlm-test(1) line below.
(The space between the switch and the argument is required.)
2. Unpack the ezmlm-0.53 distribution.
3. Unpack the ezmlm-idx distribution.
4. Move the ezmlm-idx files to the ezmlm-0.53 directory.
5. Edit ccoonnff--bbiinn and ccoonnff--mmaann to reflect the target directories.
6. build and install:
% cd ezmlm-0.53
% patch < idx.patch
% make; make man
% su
# su eztest
% ./ezmlm-test
% exit
# make install
# exit
7. Make a list and digest list
% ezmlm-make -rdugm -5 me@host ~/list ~/.qmail-list me-list host
% ezmlm-sub ~/list me@host
% ezmlm-sub ~/list digest me@host
% ezmlm-sub ~/list mod me@host
where ``me'' is your user name and ``host'' the host your list is on.
Now, you are the owner, remote administrator, and subscriber of both
list@host and the accompanying digest list list-digest@host. Only
subscribers are allowed to access the archive and to post. To post to
the list, mail to list@host. For a user to subscribe, s/he should mail
to list-subscribe@host and for help to list-help@host.