Commit | Line | Data |
---|---|---|
f8beb284 MW |
1 | #$Id: ezmlmsubrc,v 1.8 1999/05/11 02:32:40 lindberg Exp $ |
2 | #$Name: ezmlm-idx-040 $ | |
3 | # ezmlm-make -C ezmlmsubrc dir dot local host | |
4 | # Options: | |
5 | # -3 mainlist local (required) | |
6 | # -4 mainlist host (required) | |
7 | # -6 sql connect info. Format: 'host:port:user:pw:db:table' | |
8 | # -A main list not archived (affects only bounce texts) | |
9 | # -I main list not indexed (affects only bounce texts) | |
10 | # -d this sublist is for a digest list | |
11 | # | |
12 | # NOTE: For sublists of a digest list use the list local name for -3, _not_ | |
13 | # the digest list. Thus, to set up a sublist for list-digest@host, use | |
14 | # -d -3 list -4 host. This is needed to make the texts refer correctly. | |
15 | # Also, the "table" in the SQL connect info | |
16 | # Should be root, where "root" is the table name used for the main list. | |
17 | # A digest sublist is just like any other sublist, but the parent is | |
18 | # list-digest, rather than list. You need separate sublists for each and they | |
19 | # are independent. However, it's convenient to set them up in parallel, and | |
20 | # they will not interfere with one another. | |
21 | # | |
22 | # NOTE: The list address is always added to the SQL connect info to restrict | |
23 | # addresses to those serviced by this sublist. | |
24 | # | |
25 | # For memory | |
26 | </config/> | |
27 | F:<#F#> | |
28 | D:<#D#> | |
29 | T:<#T#> | |
30 | L:<#L#> | |
31 | H:<#H#> | |
32 | C:<#C#> | |
33 | 0:<#0#> | |
34 | 3:<#3#> | |
35 | 4:<#4#> | |
36 | 5:<#5#> | |
37 | 6:<#6#> | |
38 | 7:<#7#> | |
39 | 8:<#8#> | |
40 | 9:<#9#> | |
41 | ########## real stuff starts here | |
42 | </sublist/> | |
43 | <#3#>@<#4#> | |
44 | </+subscribers/> | |
45 | </+bounce/> | |
46 | </+text/> | |
47 | </lock/> | |
48 | </lockbounce/> | |
49 | </-sql/> | |
50 | </sql#6D/> | |
51 | <#6#>:<#L#>@<#H#> | |
52 | </sql#6d/> | |
53 | <#6#>_digest:<#L#>_digest@<#H#> | |
54 | # links: dot -> dir/editor | |
55 | </:/editor/> | |
56 | </:-return-default/bouncer/> | |
57 | </editor/> | |
58 | |<#B#>/ezmlm-send '<#D#>' | |
59 | |<#B#>/ezmlm-warn '<#D#>' || exit 0 | |
60 | </bouncer/> | |
61 | |<#B#>/ezmlm-weed | |
62 | </bouncer#D/> | |
63 | |<#B#>/ezmlm-return -D '<#D#>' | |
64 | </bouncer#d/> | |
65 | |<#B#>/ezmlm-return -d '<#D#>' | |
66 | </inhost/> | |
67 | <#H#> | |
68 | </outhost/> | |
69 | <#H#> | |
70 | </inlocal/> | |
71 | <#L#> | |
72 | </outlocal/> | |
73 | <#L#> | |
74 | </mailinglist/> | |
75 | contact <#3#>-help@<#4#>; run by ezmlm | |
76 | </headeradd/> | |
77 | Precedence: bulk | |
78 | </headerremove/> | |
79 | return-path | |
80 | return-receipt-to | |
81 | content-length | |
82 | precedence | |
83 | </text/top/> | |
84 | Hi! This is the ezmlm program. | |
85 | I'm managing the <#3#>@<#4#> | |
86 | </#D/> | |
87 | and <#3#>-digest@<#4#> | |
88 | mailing lists. | |
89 | ||
90 | </#d/> | |
91 | mailing list. | |
92 | </text/bounce-bottom/> | |
93 | ||
94 | --- Enclosed is a copy of the bounce message I received. | |
95 | ||
96 | </text/bounce-num/> | |
97 | ||
98 | </#D/> | |
99 | I've kept a list of which messages from the <#3#>@<#4#> | |
100 | mailing list have bounced from your address. | |
101 | ||
102 | </#d/> | |
103 | I've kept a list of which messages from | |
104 | the <#3#>-digest@<#4#> | |
105 | digest list have bounced from your address. In each case, the number | |
106 | is the number of the first message in the digest. | |
107 | ||
108 | </#a/> | |
109 | Copies of the messages may be in the archive. | |
110 | ||
111 | To get message 12345 from the archive, send an empty message to: | |
112 | <<#3#>-get.12345@<#4#>> | |
113 | ||
114 | To retrieve a set of messages 123-145 (a maximum of 100 per request), | |
115 | send an empty message to: | |
116 | <<#3#>-get.123_145@<#4#>> | |
117 | ||
118 | To receive a subject and author list for the last 100 or so messages, | |
119 | send an empty message to: | |
120 | <<#3#>-index@<#4#>> | |
121 | ||
122 | To receive the thread of messages including message 123, | |
123 | send an empty message to: | |
124 | <<#3#>-thread.123@<#4#>> | |
125 | ||
126 | <//> | |
127 | Here are the message numbers: | |
128 | ||
129 | </text/bounce-probe/> | |
130 | ||
131 | </#D/> | |
132 | Messages to you from the <#3#>@<#4#> mailing list | |
133 | </#d/> | |
134 | Messages to you from the <#3#>-digest@<#4#> list | |
135 | <//> | |
136 | seem to have been bouncing. I sent you a warning message, but it bounced. | |
137 | I've attached a copy of the bounce message. | |
138 | ||
139 | This is a probe to check whether your address is reachable. If this | |
140 | probe bounces, I will remove your address from the list | |
141 | without further notice. You can re-subscribe | |
142 | by sending an empty message to the following address: | |
143 | </#D/> | |
144 | <<#3#>-subscribe@<#4#>> | |
145 | ||
146 | </#d/> | |
147 | <<#3#>-digest-subscribe@<#4#>> | |
148 | ||
149 | </text/bounce-warn/> | |
150 | ||
151 | Messages to you from the | |
152 | </#D/> | |
153 | <#3#>@<#4#> mailing list seem to | |
154 | </#d/> | |
155 | <#3#>-digest@<#4#> digest list seem to | |
156 | <//> | |
157 | have been bouncing. I've attached a copy of the first bounce | |
158 | message I received. | |
159 | ||
160 | If this message bounces too, I will send you a probe. If the probe bounces, | |
161 | I will remove your address from the mailing list, without further notice. | |
162 | # End of minimal sublist setup. |