You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add configuration settings that allow retention to be controlled on a
per-group/pattern basis, with control over how the Expires header
is obeyed, if at all.
Efficiency at present is not great if a lot of articles are expired
at once, but this can be improved in the future.
Copy file name to clipboardExpand all lines: configs/net_nntp.conf
+21Lines changed: 21 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,9 @@ local = Local to this news server.
56
56
[articles] ; Global settings that apply to all article processing (acceptance from both readers and peers alike)
57
57
maxacceptage=10 ; Articles older than this many days will be rejected (allowing the history file to forget entries after a while, rather than growing unbounded). Default is 10, minimum is 3.
58
58
; This is equivalent to the 'artcutoff' setting in INN.
59
+
minhistory=11 ; Minimum number of days to keep history records for articles, regardless of whether they are present in the spool. If 0, expired articles are immediately removed from history.
60
+
; Best practice is to set this to maxacceptage+1, so that expired articles are not accepted again (if they were expired during a time where they could be accepted again).
61
+
; Since maxacceptage defaults to 10, this should usually be set to 11. Similar to INN's 'remember' setting in expire.ctl
59
62
maxsize=100000 ; Absolute max article size, in bytes. Default is 100000 (~100 KB). Should be at least as large as maxpostsize in [readers].
60
63
maxgroups=100 ; Absolute max number of groups for an article. Applies to local groups authorized for a sender. Should be at least as large as maxpostgroups in [readers].
61
64
;maxcrossposts=100 ; Absolute max number of groups that may appear in the Newsgroups or Xref header. 'maxgroups' doesn't need to be any larger than this value. Default is 10.
@@ -112,6 +115,24 @@ minreadpriv = 1 ; If greater than 0, further restrict reading to users with this
112
115
minpostpriv = 1 ; If greater than 0, further restrict reading to users with this privilege level (and block guests).
113
116
minapprovepriv = 2 ; Restrict Approval headers to users with this privilege level. Guests are always blocked. Minimum is 1, if set to 0, approvals will be disabled for this ACL.
114
117
118
+
; Article retention (expiration) settings. The first matching entry is used, so put your catch-all at the end!
119
+
; The format of an entry is similar to INN's expire.ctl:
120
+
; <pattern> = <min>:<default>:<max>/<flags>
121
+
; min = The minimum amount of time to retain ANY article (regardless of Expires header)
122
+
; default = The amount of time to retain articles that do NOT contain an Expires header
123
+
; max = The maximum amount of time to retain ANY article (regardless of Expires header)
124
+
; Decimal values may be specified for any of the above 3 values for fractions of a day.
125
+
; flags = Optional flags (reserved). Currently, no flags are supported.
126
+
; So to ignore the Expires header, you would set these all the same. To perfectly honor Expires, you'd set min to 0 and max to never.
127
+
; The arrival time of an article is used for expiration, not the article's Date.
128
+
; To actually expire articles, run 'rsysop "news expire"' from a cron job at a suitable interval.
;local.foo = 0:180:never ; Retain articles for local.foo for 180 days by default, but fully honor Expires headers
132
+
;misc.very.busy.group = 0.25:10:20 ; Generally delete articles after 10 days, and after no more than 20 days. Keep all articles for at least 6 hours.
133
+
;news.lists.filters = 3:3:3 ; Only keep automated filtering messages for 3 days
134
+
* = never:never:never ; the implicit default entry (never expire any articles). However, there SHOULD be at least one pattern matching every group (even just *) or you will see warnings.
135
+
115
136
; Feed configuration:
116
137
[incoming] ; Specify other news servers that can send us articles, in peer = groups[/distributions] format. These are peers that "push" articles to us (similar to incoming.conf in INN).
117
138
; You can specify a local username on this server, an IPv4 address (CIDR range allowed), or a hostname (though this may incur a performance penalty).
0 commit comments