blob: fec2a489d6ae6f40877a92558456374a7410e7d6 (
plain)
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
|
<!--
$FML: chapter.sgml,v 1.5 2005/10/08 03:37:39 fukachan Exp $
$jaFML: chapter.sgml,v 1.3 2003/04/15 14:51:39 fukachan Exp $
-->
<chapter id="digest">
<title>
Digest Delivery
</title>
<para>
Run
<screen>
/usr/local/libexec/fml/digest $ml_name
</screen>
periodically for digest delivery. It aggregates articles into one
MIME/multipart message and send it to members defined by
$digest_recipient_maps.
</para>
<warning>
<para>
Digest delivery program is a simple version yet now.
</para>
</warning>
<sect1 id="digest.config.files">
<title>
Files Used For Digest Delivery Control
</title>
<para>
This program uses the following files under $ml_home_dir.
<screen>
seq-digest
members-digest
recipients-digest
</screen>
</para>
<para>
seq-digest holds the last sequence delivered as digest.
</para>
<para>
members-digest is dummy.
recipients-digest is a recipient list.
$digest_recipient_maps is this recipients-digest file only by default.
</para>
<para>
The argument of $digest_recipient_maps is IO::Adapter,
so you can use mysql here.
</para>
</sect1>
<sect1 id="digest.command">
<title>
Idea: Digest Related Commands
</title>
<!--
XXX-TODO digest related commands
-->
<para>
Idea on digest commands (references: fml-devel:313).
</para>
<para>
Hmm, how about the further extension?
</para>
<sect2>
<title>
makefml command
</title>
<para>
<screen>
makefml digest $ml $address on
makefml digeston $ml $address
makefml digest $ml $address off
makefml digestoff $ml $address
</screen>
(These commands are implemented already).
</para>
<para>
</para>
</sect2>
<sect2>
<title>
admin command mail
</title>
<para>
<screen>
admin digest $address on
admin digest $address off
</screen>
(These commands are implemented already).
</para>
</sect2>
<sect2>
<title>
user level command mail ?
</title>
<para>
<screen>
digest on
digest off
</screen>
</para>
<para>
The confirmation is needed ? Yes, we should need it to unify the fml
fundamental design. We should restrict address manipulation functions
as could as possible.
</para>
</sect2>
<sect2>
<title>
CGI
</title>
<para>
<screen>
digeston
digestoff
</screen>
ok?
</para>
</sect2>
</sect1>
<!-- recipies -->
<sect1 id="digest.recipes">
<title>
recipes
</title>
§.digest.recipes;
</sect1>
</chapter>
|
