~ulrith/mailman/russian-2.1.20 : revision 1538

1

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

2

<html>

3

<head>

4

5

6

7

8

9

10

11

12

13

14

15

<title>2.7.2 Sender filters</title>

16

</head>

17

<body>

18

19

20

21

<tr>

22

<td class='online-navigation'><a rel="prev" title="2.7.1 subscription rules"

23

href="node21.html"><img src='previous.png'

24

border='0' height='32' alt='Previous Page' width='32' /></a></td>

25

<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options"

26

href="node20.html"><img src='up.png'

27

border='0' height='32' alt='Up one Level' width='32' /></a></td>

28

<td class='online-navigation'><a rel="next" title="2.7.3 recipient Filters"

29

href="node23.html"><img src='next.png'

30

border='0' height='32' alt='Next Page' width='32' /></a></td>

31

<td align="center" width="100%">GNU Mailman - List Administration Manual</td>

32

<td class='online-navigation'><a rel="contents" title="Table of Contents"

33

href="contents.html"><img src='contents.png'

34

border='0' height='32' alt='Contents' width='32' /></a></td>

35

<td class='online-navigation'><img src='blank.png'

36

border='0' height='32' alt='' width='32' /></td>

37

<td class='online-navigation'><img src='blank.png'

38

border='0' height='32' alt='' width='32' /></td>

39

</tr></table>

40

41

Previous:

42

<a class="sectref" rel="prev" href="node21.html">2.7.1 Subscription rules</a>

43

Up:

44

<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a>

45

Next:

46

<a class="sectref" rel="next" href="node23.html">2.7.3 Recipient Filters</a>

47

</div>

48

49

</div>

50

51

52

53

54

2.7.2 Sender filters

55

</h3>

56

57

58

When a message is posted to the list, a series of moderation criteria are

59

applied to determine the disposition of the message. This section

60

contains the modeation controls for postings from both members and

61

non-members.

62

63

64

<dl>

65

<dt>default_member_moderation</dt>

66

<dd>Member postings are held for moderation if their moderation

67

flag is turned on. Note that only the list administrators can

68

change the value of a member's moderation flag.

69

70

71

You can control whether new members get their moderation flag

72

turned on or off by default when they subscribe to the list. By

73

turning this flag off by default, postings by members will be

74

allowed without further intervention (barring other restrictions

75

such as size or implicit recipient lists - see below). By

76

turning the flag on, you can quarantine new member postings to

77

make sure that they meet your criteria for netiquette, topicality,

78

etc. Once you determine that the new member understands the

79

community's posting rules, you can turn off their moderation flag

80

and let their postings go through unstopped.

81

82

83

E-newsletter style lists can also be set up by using the

84

moderation flag. By setting the <code>member_moderation_action</code>

85

to Reject, and by turning off the moderation flag for just

86

the few approved senders, your list will operate in essentially a

87

one-way direction. Note that you'd also need to reject or discard

88

postings from non-members.

89

90

91

</dd>

92

<dt>member_moderation_action</dt>

93

<dd>This is the action to take for postings from a member who's

94

moderation flag is set. For typical discussion lists, you'll

95

likely set this to Hold so that the list moderator will get

96

a chance to manually approve, reject, or discard the message. For

97

e-newsletter and announcement lists, you might want to set this to

98

Reject or Discard.

99

100

101

Note that when a moderated member posts to your list, and the

102

<code>member_moderation_action</code> is set to Hold, the message

103

will appear on the administrative requests page. When you dispose

104

of the message, you will be given an opportunity to clear the

105

moderation flag at the same time. If you're quarantining new

106

posts, this makes it very convenient to both approve a new

107

member's post and de-moderate them at the same time.

108

109

110

</dd>

111

<dt>member_moderation_notice</dt>

112

<dd>When a member's moderation flag is turned on and

113

<code>member_moderation_action</code> is Reject, this variable

114

contains the text sent in the rejection notice.

115

</dd>

116

</dl>

117

118

119

The next group of settings control messages whose From:

120

domain publishes a DMARC <code>p=reject</code> or <code>p=quarantine</code> policy.

121

122

123

<dl>

124

<dt>dmarc_moderation_action</dt>

125

<dd>These actions, Accept, Munge From, Wrap Message,

126

Reject and Discard apply only to messages whose

127

From: domain publishes a DMARC <code>p=reject</code> or optionally

128

(see the next setting) <code>p=quarantine</code> policy. If the message is

129

From: such a domain and this action is other than

130

Accept, this action applies to the message. Otherwise the

131

<code>from_is_list</code> setting in section <a href="general-personality.html#general-personality">2.1</a>

132

applies. See the <code>from_is_list</code> setting in section

133

<a href="general-personality.html#general-personality">2.1</a> for a description of the Munge From

134

and Wrap Message actions.

135

</dd>

136

<dt>dmarc_quarantine_moderation_action</dt>

137

<dd>If this is set to Yes, the above <code>dmarc_moderation_action</code>

138

applies to messages with From: domain DMARC policy

139

<code>p=quarantine</code> as well as <code>p=reject</code>.

140

</dd>

141

<dt>dmarc_moderation_notice</dt>

142

<dd>When <code>dmarc_moderation_action</code> applies and is Reject,

143

this variable contains the text sent in the rejection notice. If

144

empty, a generic notice mentioning DMARC is sent.

145

</dd>

146

</dl>

147

148

149

The next batch of variables controls what happens when non-members

150

post messages to the list. Each of these accepts one email address

151

per line; regular expressions are allowed if the line starts with the

152

(caret) character. These address lists are always consulted in the

153

order in which they're presented on this page (i.e. accepts first,

154

followed by holds, rejections, and discards).

155

156

157

<dl>

158

<dt>accept_these_nonmembers</dt>

159

<dd>Postings from non-members whose addresses match this list are

160

accepted, barring other list restrictions due to size, implicit

161

recipients, etc. You might want to add alternative addresses of

162

approved posters to this list.

163

164

165

</dd>

166

<dt>hold_these_nonmembers</dt>

167

<dd>Postings from non-members whose addresses match this list are

168

held for moderator approval.

169

170

171

</dd>

172

<dt>reject_these_nonmembers</dt>

173

<dd>Postings from non-members whose addresses match this list are

174

rejected, i.e. bounced back to the original sender. There

175

currently is no way to add additional text to the rejection

176

message.

177

178

179

</dd>

180

<dt>discard_these_nonmembers</dt>

181

<dd>Postings from non-members whose addresses match this list are

182

discarded, with no bounce back message. You might want to add the

183

addresses of known spammers to this list.

184

185

186

</dd>

187

<dt>generic_nonmember_action</dt>

188

<dd>This variable controls what happens to non-member posts when the

189

address of the sender doesn't match any of the above four lists.

190

If you set this to Hold, the posting will appear on the

191

administrative requests page, and you will be given an opportunity

192

to add the non-member to one of the above four lists at the same

193

time you dispose of the held message.

194

195

196

</dd>

197

<dt>forward_auto_discards</dt>

198

<dd>When messages from non-members are discarded, either because the

199

sender address matched <code>discard_these_nonmembers</code>, or because

200

<code>generic_nonmember_action</code> is Discard, you can choose

201

whether such messages are forwarded to the lsit administrators or

202

not.

203

</dd>

204

</dl>

205

206

207

208

209

210

<hr />

211

212

<tr>

213

<td class='online-navigation'><a rel="prev" title="2.7.1 subscription rules"

214

href="node21.html"><img src='previous.png'

215

border='0' height='32' alt='Previous Page' width='32' /></a></td>

216

<td class='online-navigation'><a rel="parent" title="2.7 the Privacy Options"

217

href="node20.html"><img src='up.png'

218

border='0' height='32' alt='Up one Level' width='32' /></a></td>

219

<td class='online-navigation'><a rel="next" title="2.7.3 recipient Filters"

220

href="node23.html"><img src='next.png'

221

border='0' height='32' alt='Next Page' width='32' /></a></td>

222

<td align="center" width="100%">GNU Mailman - List Administration Manual</td>

223

<td class='online-navigation'><a rel="contents" title="Table of Contents"

224

href="contents.html"><img src='contents.png'

225

border='0' height='32' alt='Contents' width='32' /></a></td>

226

<td class='online-navigation'><img src='blank.png'

227

border='0' height='32' alt='' width='32' /></td>

228

<td class='online-navigation'><img src='blank.png'

229

border='0' height='32' alt='' width='32' /></td>

230

</tr></table>

231

232

Previous:

233

<a class="sectref" rel="prev" href="node21.html">2.7.1 Subscription rules</a>

234

Up:

235

<a class="sectref" rel="parent" href="node20.html">2.7 The Privacy Options</a>

236

Next:

237

<a class="sectref" rel="next" href="node23.html">2.7.3 Recipient Filters</a>

238

</div>

239

</div>

240

<hr />

241

Release 2.1, documentation updated on January 29, 2015.

242

</div>

243

244

245

</body>

246

</html>