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
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
|
<HTML>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
<!-- Fri Mar 8 10:49:56 2002 -->
<!-- USING HT2HTML 1.2 -->
<!-- SEE http://barry.wooz.org/software/ht2html -->
<!-- User-specified headers:
Title: The Mailman Wishlist
-->
<HEAD>
<TITLE>The Mailman Wishlist</TITLE>
</HEAD>
<BODY BGCOLOR="#ffffff" TEXT="#000000"
TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
LINK="#0000bb" VLINK="#551a8b"
ALINK="#ff0000">
<!-- start of page table -->
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0>
<!-- start of banner row -->
<TR>
<!-- start of corner cells -->
<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
<center>
<a href="./index.html">
<img border=0 src="./images/logo-70.jpg"></a></center> </TD>
<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
<TD WIDTH="90%" BGCOLOR="#caa08f">
<!-- start of site links table -->
<TABLE WIDTH="100%" BORDER=0
CELLSPACING=0 CELLPADDING=0
COLS=3 ROWS=4 BGCOLOR="#ffffff">
<TR>
<TD BGCOLOR="#caa08f">
<a href="./index.html">Home</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="./users.html">Users</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="http://www.list.org/">List.Org</a>
</TD>
</TR><TR>
<TD BGCOLOR="#caa08f">
<a href="./install-start.html">Installation</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="./mgrs.html">List Managers</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
</TD>
</TR><TR>
<TD BGCOLOR="#caa08f">
<a href="./faq.html">FAQ</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="./admins.html">Site Administrators</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
</TD>
</TR><TR>
<TD BGCOLOR="#caa08f">
<a href="./lists.html">Discussion Lists</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="./devs.html">Developers</a>
</TD>
<TD BGCOLOR="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
</TD>
</TR>
</TABLE><!-- end of site links table -->
</TD><!-- end of banner -->
</TR><!-- end of banner row -->
<TR><!-- start of sidebar/body row -->
<!-- start of sidebar cells -->
<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f">
<!-- start of sidebar table -->
<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
BGCOLOR="#ffffff">
<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
Overview
</FONT></B></TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="index.html">Home</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="features.html">Features</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="download.html">Requirements, Download</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="install-start.html">Installation</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="lists.html">Discussion Lists</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="bugs.html">Bugs and Patches</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="faq.html">Frequently Asked Questions</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="inthenews.html">Mailman in Use</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<b>Wishlist!</b>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
Email Us
</FONT></B></TD></TR>
<TR><TD BGCOLOR="#caa08f">
<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
<a href="http://www.python.org/"><img border=0
src="./images/PythonPoweredSmall.png"
></a> <a href="http://sourceforge.net"><img
src="http://sourceforge.net/sflogo.php?group_id=103"
width="88" height="31" border="0"
alt="SourceForge Logo"></a>
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
</TD></TR>
<TR><TD BGCOLOR="#caa08f">
© 1998,1999,2000,2001<br>Free Software Foundation, Inc.
</TD></TR>
</TABLE><!-- end of sidebar table -->
</TD>
<TD WIDTH=15> </TD><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
<TD VALIGN=TOP WIDTH="90%"><BR>
<h3> The Mailman Wishlist
</h3>
Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<p>
<h3> Email Handling
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
</ul>
<h3> Documentation
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
</ul>
<h3> General Web UI
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
</ul>
<h3> List Administration
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
</ul>
<h3> List Membership
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
</ul>
<h3> Site Administration
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
</ul>
<h3> Other Usability Improvments
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
<li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and
authorization to modify the sub & superlists. Majordomo2 is
reported to have some good features in this regard.
<li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc).
Also, limits on mailbacks, infos, etc.
</ul>
<h3> Mailcmd interface
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
<li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and
authorization to modify the sub & superlists. Majordomo2 is
reported to have some good features in this regard.
<li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc).
Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
this. Also, adding a confirmation with click-thru confirmation
to resubscribe.
<li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation
message. Helps track down subscribe bombs.
<li> Investigate Majordomo2's email admin capabilities.
<li> Support the `which' command.
</ul>
<h3> Portability & architecture
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
<li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and
authorization to modify the sub & superlists. Majordomo2 is
reported to have some good features in this regard.
<li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc).
Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
this. Also, adding a confirmation with click-thru confirmation
to resubscribe.
<li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation
message. Helps track down subscribe bombs.
<li> Investigate Majordomo2's email admin capabilities.
<li> Support the `which' command.
<li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a
relational database, ZODB, LDAP, etc)
<li> Member profiles
<li> Do a serious and thorough security audit (ongoing)
<li> Allow lists of the same name in two different virtual domains
<li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
include URLs, etc. Should be admin configurable based on MIME
type. Check out Bill Bumgarner's work on this.
<li> Should be able to gather statistics, such as deliveries/day, performance, number of subscribers over time, etc.
<li> Implement something like Roundup's nosy lists, maybe even integrate with Roundup.
<li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects.
</ul>
<h3> Bounce handling
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
<li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and
authorization to modify the sub & superlists. Majordomo2 is
reported to have some good features in this regard.
<li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc).
Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
this. Also, adding a confirmation with click-thru confirmation
to resubscribe.
<li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation
message. Helps track down subscribe bombs.
<li> Investigate Majordomo2's email admin capabilities.
<li> Support the `which' command.
<li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a
relational database, ZODB, LDAP, etc)
<li> Member profiles
<li> Do a serious and thorough security audit (ongoing)
<li> Allow lists of the same name in two different virtual domains
<li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
include URLs, etc. Should be admin configurable based on MIME
type. Check out Bill Bumgarner's work on this.
<li> Should be able to gather statistics, such as deliveries/day, performance, number of subscribers over time, etc.
<li> Implement something like Roundup's nosy lists, maybe even integrate with Roundup.
<li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects.
<li> Add more patterns for bounce handling (never ending)
<li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it).
<li> Delete bounce disabled address after some period of retry
</ul>
<h3> Pipermail + Archiving mechanism
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
<li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and
authorization to modify the sub & superlists. Majordomo2 is
reported to have some good features in this regard.
<li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc).
Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
this. Also, adding a confirmation with click-thru confirmation
to resubscribe.
<li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation
message. Helps track down subscribe bombs.
<li> Investigate Majordomo2's email admin capabilities.
<li> Support the `which' command.
<li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a
relational database, ZODB, LDAP, etc)
<li> Member profiles
<li> Do a serious and thorough security audit (ongoing)
<li> Allow lists of the same name in two different virtual domains
<li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
include URLs, etc. Should be admin configurable based on MIME
type. Check out Bill Bumgarner's work on this.
<li> Should be able to gather statistics, such as deliveries/day, performance, number of subscribers over time, etc.
<li> Implement something like Roundup's nosy lists, maybe even integrate with Roundup.
<li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects.
<li> Add more patterns for bounce handling (never ending)
<li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it).
<li> Delete bounce disabled address after some period of retry
<li> Search engine for archives
<li> Provide downloadable tar.gz's of the html archives
<li> sort by date should go most-recent to oldest
<li> allow list owner to edit archive messages
<li> archive link should do *something* reasonable before the first message has been posted to the list.
<li> optional form front-end to public interfaces as a filter to address harvesters.
<li> In general the whole Pipermail subsystem needs a good rewrite.
</ul>
<h3> Code cleanup
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
writing 21-Jan-2002), so what's left will probably end up in a
Mailman 3.0.
Please also see the Mailman design notes wiki at
http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
<li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
(optional).
<li> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
<li> A list-admin's guide
<li> More on-line documentation and UI help
<li> A developer's guide w/ architecture and API information
<li> manpages for the scripts in bin and cron
<li> Integrate Christopher Kolar's documentation
<li> NO DEAD ENDS and every web page is reachable.
<li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using
a template language/system like Zope's Presentation Templates,
Quixote, or PHP.
<li> Default UI should add a navigation sidebar to all web pages.
<li> Web pages should never mention disabled features.
<li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the
message was edited by the moderator).
<li> Allow the admin to disable option settings by users
<li> Ability to set defaults for the various user settings from the "Membership Management" page.
<li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
very useful, but could be dangerous!)
<li> New moderation choice: archive but don't send to list.
<li> New moderation choice: annotate and send to author for resubmittal.
<li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a
secondary channel, like moderators@isc.org).
<li> Add an option to include Reply-To: header in the membership test for a members-only list posting
<li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out
duplicate deliveries.
<li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever
address they want to whichever list, with different options per
subscription.
<li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this)
<li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article)
<li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
<li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
about the list.
<li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
date they last sent a message through the list. Perhaps also
log each message they send through the list.
<li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their
list.
<li> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
by addressing it to mailman@site.dom).
<li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and
authorization to modify the sub & superlists. Majordomo2 is
reported to have some good features in this regard.
<li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc).
Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
this. Also, adding a confirmation with click-thru confirmation
to resubscribe.
<li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation
message. Helps track down subscribe bombs.
<li> Investigate Majordomo2's email admin capabilities.
<li> Support the `which' command.
<li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a
relational database, ZODB, LDAP, etc)
<li> Member profiles
<li> Do a serious and thorough security audit (ongoing)
<li> Allow lists of the same name in two different virtual domains
<li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
include URLs, etc. Should be admin configurable based on MIME
type. Check out Bill Bumgarner's work on this.
<li> Should be able to gather statistics, such as deliveries/day, performance, number of subscribers over time, etc.
<li> Implement something like Roundup's nosy lists, maybe even integrate with Roundup.
<li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects.
<li> Add more patterns for bounce handling (never ending)
<li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it).
<li> Delete bounce disabled address after some period of retry
<li> Search engine for archives
<li> Provide downloadable tar.gz's of the html archives
<li> sort by date should go most-recent to oldest
<li> allow list owner to edit archive messages
<li> archive link should do *something* reasonable before the first message has been posted to the list.
<li> optional form front-end to public interfaces as a filter to address harvesters.
<li> In general the whole Pipermail subsystem needs a good rewrite.
<li> Turn all remaining string exceptions into class exceptions
<li> Unit and system test suite!
</ul>
</TD><!-- end of body cell -->
</TR><!-- end of sidebar/body row -->
</TABLE><!-- end of page table -->
</BODY></HTML>
|
