540
570
msgid "Spam Filter Regexp:"
541
571
msgstr "Uitdrukking:"
543
#: Mailman/Cgi/admin.py:762 Mailman/Cgi/admindb.py:303
544
#: Mailman/Cgi/admindb.py:362 Mailman/Cgi/admindb.py:407
573
#: Mailman/Cgi/admin.py:762
574
#: Mailman/Cgi/admindb.py:303
575
#: Mailman/Cgi/admindb.py:362
576
#: Mailman/Cgi/admindb.py:407
545
577
#: Mailman/Cgi/admindb.py:637
547
579
msgstr "Uitstellen"
549
#: Mailman/Cgi/admin.py:762 Mailman/Cgi/admindb.py:305
550
#: Mailman/Cgi/admindb.py:364 Mailman/Cgi/admindb.py:407
551
#: Mailman/Cgi/admindb.py:637 Mailman/Gui/ContentFilter.py:37
552
#: Mailman/Gui/Privacy.py:216 Mailman/Gui/Privacy.py:297
581
#: Mailman/Cgi/admin.py:762
582
#: Mailman/Cgi/admindb.py:305
583
#: Mailman/Cgi/admindb.py:364
584
#: Mailman/Cgi/admindb.py:407
585
#: Mailman/Cgi/admindb.py:637
586
#: Mailman/Gui/ContentFilter.py:37
587
#: Mailman/Gui/Privacy.py:216
588
#: Mailman/Gui/Privacy.py:297
554
590
msgstr "Weigeren"
556
#: Mailman/Cgi/admin.py:762 Mailman/Gui/Privacy.py:216
592
#: Mailman/Cgi/admin.py:762
593
#: Mailman/Gui/Privacy.py:216
557
594
#: Mailman/Gui/Privacy.py:297
559
596
msgstr "Vasthouden"
561
#: Mailman/Cgi/admin.py:763 Mailman/Cgi/admindb.py:306
562
#: Mailman/Cgi/admindb.py:365 Mailman/Cgi/admindb.py:407
563
#: Mailman/Cgi/admindb.py:637 Mailman/Gui/ContentFilter.py:37
564
#: Mailman/Gui/Privacy.py:216 Mailman/Gui/Privacy.py:297
598
#: Mailman/Cgi/admin.py:763
599
#: Mailman/Cgi/admindb.py:306
600
#: Mailman/Cgi/admindb.py:365
601
#: Mailman/Cgi/admindb.py:407
602
#: Mailman/Cgi/admindb.py:637
603
#: Mailman/Gui/ContentFilter.py:37
604
#: Mailman/Gui/Privacy.py:216
605
#: Mailman/Gui/Privacy.py:297
568
#: Mailman/Cgi/admin.py:763 Mailman/Cgi/admindb.py:407
609
#: Mailman/Cgi/admin.py:763
610
#: Mailman/Cgi/admindb.py:407
569
611
#: Mailman/Gui/Privacy.py:297
571
613
msgstr "Goedkeuren"
573
#: Mailman/Cgi/admin.py:766 Mailman/Cgi/admindb.py:643
615
#: Mailman/Cgi/admin.py:766
616
#: Mailman/Cgi/admindb.py:643
831
873
msgid "Send welcome messages to new subscribees?"
832
874
msgstr "Stuur een welkomstbericht naar nieuwe leden?"
834
#: Mailman/Cgi/admin.py:1146 Mailman/Cgi/admin.py:1155
835
#: Mailman/Cgi/admin.py:1188 Mailman/Cgi/admin.py:1196
836
#: Mailman/Cgi/confirm.py:290 Mailman/Cgi/create.py:352
837
#: Mailman/Cgi/create.py:387 Mailman/Cgi/create.py:425
838
#: Mailman/Cgi/rmlist.py:228 Mailman/Gui/Archive.py:33
839
#: Mailman/Gui/Autoresponse.py:54 Mailman/Gui/Autoresponse.py:62
840
#: Mailman/Gui/Autoresponse.py:71 Mailman/Gui/Bounce.py:77
841
#: Mailman/Gui/Bounce.py:120 Mailman/Gui/Bounce.py:146
842
#: Mailman/Gui/Bounce.py:155 Mailman/Gui/ContentFilter.py:74
843
#: Mailman/Gui/ContentFilter.py:116 Mailman/Gui/ContentFilter.py:120
844
#: Mailman/Gui/Digest.py:46 Mailman/Gui/Digest.py:62 Mailman/Gui/Digest.py:84
845
#: Mailman/Gui/Digest.py:89 Mailman/Gui/General.py:156
846
#: Mailman/Gui/General.py:162 Mailman/Gui/General.py:240
847
#: Mailman/Gui/General.py:267 Mailman/Gui/General.py:294
848
#: Mailman/Gui/General.py:305 Mailman/Gui/General.py:308
849
#: Mailman/Gui/General.py:318 Mailman/Gui/General.py:323
850
#: Mailman/Gui/General.py:329 Mailman/Gui/General.py:349
851
#: Mailman/Gui/General.py:381 Mailman/Gui/General.py:404
852
#: Mailman/Gui/NonDigest.py:45 Mailman/Gui/NonDigest.py:53
853
#: Mailman/Gui/NonDigest.py:140 Mailman/Gui/Privacy.py:110
854
#: Mailman/Gui/Privacy.py:116 Mailman/Gui/Privacy.py:149
855
#: Mailman/Gui/Privacy.py:197 Mailman/Gui/Privacy.py:312
856
#: Mailman/Gui/Privacy.py:331 Mailman/Gui/Usenet.py:52
857
#: Mailman/Gui/Usenet.py:56 Mailman/Gui/Usenet.py:93 Mailman/Gui/Usenet.py:105
876
#: Mailman/Cgi/admin.py:1146
877
#: Mailman/Cgi/admin.py:1155
878
#: Mailman/Cgi/admin.py:1188
879
#: Mailman/Cgi/admin.py:1196
880
#: Mailman/Cgi/confirm.py:290
881
#: Mailman/Cgi/create.py:352
882
#: Mailman/Cgi/create.py:387
883
#: Mailman/Cgi/create.py:425
884
#: Mailman/Cgi/rmlist.py:228
885
#: Mailman/Gui/Archive.py:33
886
#: Mailman/Gui/Autoresponse.py:54
887
#: Mailman/Gui/Autoresponse.py:62
888
#: Mailman/Gui/Autoresponse.py:71
889
#: Mailman/Gui/Bounce.py:77
890
#: Mailman/Gui/Bounce.py:120
891
#: Mailman/Gui/Bounce.py:146
892
#: Mailman/Gui/Bounce.py:155
893
#: Mailman/Gui/ContentFilter.py:74
894
#: Mailman/Gui/ContentFilter.py:116
895
#: Mailman/Gui/ContentFilter.py:120
896
#: Mailman/Gui/Digest.py:46
897
#: Mailman/Gui/Digest.py:62
898
#: Mailman/Gui/Digest.py:84
899
#: Mailman/Gui/Digest.py:89
900
#: Mailman/Gui/General.py:156
901
#: Mailman/Gui/General.py:162
902
#: Mailman/Gui/General.py:240
903
#: Mailman/Gui/General.py:267
904
#: Mailman/Gui/General.py:294
905
#: Mailman/Gui/General.py:305
906
#: Mailman/Gui/General.py:308
907
#: Mailman/Gui/General.py:318
908
#: Mailman/Gui/General.py:323
909
#: Mailman/Gui/General.py:329
910
#: Mailman/Gui/General.py:349
911
#: Mailman/Gui/General.py:381
912
#: Mailman/Gui/General.py:404
913
#: Mailman/Gui/NonDigest.py:45
914
#: Mailman/Gui/NonDigest.py:53
915
#: Mailman/Gui/NonDigest.py:140
916
#: Mailman/Gui/Privacy.py:110
917
#: Mailman/Gui/Privacy.py:116
918
#: Mailman/Gui/Privacy.py:149
919
#: Mailman/Gui/Privacy.py:197
920
#: Mailman/Gui/Privacy.py:312
921
#: Mailman/Gui/Privacy.py:331
922
#: Mailman/Gui/Usenet.py:52
923
#: Mailman/Gui/Usenet.py:56
924
#: Mailman/Gui/Usenet.py:93
925
#: Mailman/Gui/Usenet.py:105
861
#: Mailman/Cgi/admin.py:1146 Mailman/Cgi/admin.py:1155
862
#: Mailman/Cgi/admin.py:1188 Mailman/Cgi/admin.py:1196
863
#: Mailman/Cgi/confirm.py:290 Mailman/Cgi/create.py:352
864
#: Mailman/Cgi/create.py:387 Mailman/Cgi/create.py:425
865
#: Mailman/Cgi/rmlist.py:228 Mailman/Gui/Archive.py:33
866
#: Mailman/Gui/Autoresponse.py:54 Mailman/Gui/Autoresponse.py:62
867
#: Mailman/Gui/Bounce.py:77 Mailman/Gui/Bounce.py:120
868
#: Mailman/Gui/Bounce.py:146 Mailman/Gui/Bounce.py:155
869
#: Mailman/Gui/ContentFilter.py:74 Mailman/Gui/ContentFilter.py:116
870
#: Mailman/Gui/ContentFilter.py:120 Mailman/Gui/Digest.py:46
871
#: Mailman/Gui/Digest.py:62 Mailman/Gui/Digest.py:84 Mailman/Gui/Digest.py:89
872
#: Mailman/Gui/General.py:156 Mailman/Gui/General.py:162
873
#: Mailman/Gui/General.py:240 Mailman/Gui/General.py:267
874
#: Mailman/Gui/General.py:294 Mailman/Gui/General.py:305
875
#: Mailman/Gui/General.py:308 Mailman/Gui/General.py:318
876
#: Mailman/Gui/General.py:323 Mailman/Gui/General.py:329
877
#: Mailman/Gui/General.py:349 Mailman/Gui/General.py:381
878
#: Mailman/Gui/General.py:404 Mailman/Gui/NonDigest.py:45
879
#: Mailman/Gui/NonDigest.py:53 Mailman/Gui/NonDigest.py:140
880
#: Mailman/Gui/Privacy.py:110 Mailman/Gui/Privacy.py:116
881
#: Mailman/Gui/Privacy.py:149 Mailman/Gui/Privacy.py:197
882
#: Mailman/Gui/Privacy.py:312 Mailman/Gui/Privacy.py:331
883
#: Mailman/Gui/Usenet.py:52 Mailman/Gui/Usenet.py:56 Mailman/Gui/Usenet.py:93
929
#: Mailman/Cgi/admin.py:1146
930
#: Mailman/Cgi/admin.py:1155
931
#: Mailman/Cgi/admin.py:1188
932
#: Mailman/Cgi/admin.py:1196
933
#: Mailman/Cgi/confirm.py:290
934
#: Mailman/Cgi/create.py:352
935
#: Mailman/Cgi/create.py:387
936
#: Mailman/Cgi/create.py:425
937
#: Mailman/Cgi/rmlist.py:228
938
#: Mailman/Gui/Archive.py:33
939
#: Mailman/Gui/Autoresponse.py:54
940
#: Mailman/Gui/Autoresponse.py:62
941
#: Mailman/Gui/Bounce.py:77
942
#: Mailman/Gui/Bounce.py:120
943
#: Mailman/Gui/Bounce.py:146
944
#: Mailman/Gui/Bounce.py:155
945
#: Mailman/Gui/ContentFilter.py:74
946
#: Mailman/Gui/ContentFilter.py:116
947
#: Mailman/Gui/ContentFilter.py:120
948
#: Mailman/Gui/Digest.py:46
949
#: Mailman/Gui/Digest.py:62
950
#: Mailman/Gui/Digest.py:84
951
#: Mailman/Gui/Digest.py:89
952
#: Mailman/Gui/General.py:156
953
#: Mailman/Gui/General.py:162
954
#: Mailman/Gui/General.py:240
955
#: Mailman/Gui/General.py:267
956
#: Mailman/Gui/General.py:294
957
#: Mailman/Gui/General.py:305
958
#: Mailman/Gui/General.py:308
959
#: Mailman/Gui/General.py:318
960
#: Mailman/Gui/General.py:323
961
#: Mailman/Gui/General.py:329
962
#: Mailman/Gui/General.py:349
963
#: Mailman/Gui/General.py:381
964
#: Mailman/Gui/General.py:404
965
#: Mailman/Gui/NonDigest.py:45
966
#: Mailman/Gui/NonDigest.py:53
967
#: Mailman/Gui/NonDigest.py:140
968
#: Mailman/Gui/Privacy.py:110
969
#: Mailman/Gui/Privacy.py:116
970
#: Mailman/Gui/Privacy.py:149
971
#: Mailman/Gui/Privacy.py:197
972
#: Mailman/Gui/Privacy.py:312
973
#: Mailman/Gui/Privacy.py:331
974
#: Mailman/Gui/Usenet.py:52
975
#: Mailman/Gui/Usenet.py:56
976
#: Mailman/Gui/Usenet.py:93
884
977
#: Mailman/Gui/Usenet.py:105
3176
3229
" huidige wachtwoord toegestuurd. Met de argumenten <oud wachtwoord>\n"
3177
3230
" en <nieuw wachtwoord> kunt u uw wachtwoord veranderen.\n"
3179
" Als u een bericht verstuurd vanaf een ander adres dan waar u mee "
3181
" geef dan uw aangemelde adres op met `address=<adres>' (zonder "
3183
" voor en achter het e-mailadres, en zonder aanhalingstekens!). Let "
3184
"er op dat in dit geval\n"
3232
" Als u een bericht verstuurd vanaf een ander adres dan waar u mee aangemeld bent,\n"
3233
" geef dan uw aangemelde adres op met `address=<adres>' (zonder haakjes\n"
3234
" voor en achter het e-mailadres, en zonder aanhalingstekens!). Let er op dat in dit geval\n"
3185
3235
" de bevestiging altijd naar het aangemelde adres wordt verstuurd.\n"
3187
#: Mailman/Commands/cmd_password.py:51 Mailman/Commands/cmd_password.py:66
3237
#: Mailman/Commands/cmd_password.py:51
3238
#: Mailman/Commands/cmd_password.py:66
3188
3239
msgid "Your password is: %(password)s"
3189
3240
msgstr "Uw wachtwoord is: %(password)s"
3191
#: Mailman/Commands/cmd_password.py:57 Mailman/Commands/cmd_password.py:72
3192
#: Mailman/Commands/cmd_password.py:95 Mailman/Commands/cmd_password.py:121
3193
#: Mailman/Commands/cmd_set.py:149 Mailman/Commands/cmd_set.py:219
3242
#: Mailman/Commands/cmd_password.py:57
3243
#: Mailman/Commands/cmd_password.py:72
3244
#: Mailman/Commands/cmd_password.py:95
3245
#: Mailman/Commands/cmd_password.py:121
3246
#: Mailman/Commands/cmd_set.py:149
3247
#: Mailman/Commands/cmd_set.py:219
3194
3248
msgid "You are not a member of the %(listname)s mailing list"
3195
3249
msgstr "U bent geen lid van de %(listname)s maillijst"
3197
#: Mailman/Commands/cmd_password.py:85 Mailman/Commands/cmd_password.py:111
3251
#: Mailman/Commands/cmd_password.py:85
3252
#: Mailman/Commands/cmd_password.py:111
3199
3254
"You did not give the correct old password, so your password has not been\n"
3200
"changed. Use the no argument version of the password command to retrieve "
3255
"changed. Use the no argument version of the password command to retrieve your\n"
3202
3256
"current password, then try again."
3204
"U heeft niet het correcte oude wachtwoord opgegeven, uw wachtwoord is "
3258
"U heeft niet het correcte oude wachtwoord opgegeven, uw wachtwoord is derhalve\n"
3206
3259
"niet veranderd. Gebruik de wachtwoord opdracht - zonder argumenten - om uw\n"
3207
3260
"huidige wachtwoord toegestuurd te krijgen, en probeer het opnieuw."
3209
#: Mailman/Commands/cmd_password.py:89 Mailman/Commands/cmd_password.py:115
3262
#: Mailman/Commands/cmd_password.py:89
3263
#: Mailman/Commands/cmd_password.py:115
3345
3381
" set digest plain\n"
3346
3382
" set digest mime\n"
3347
3383
" set digest off\n"
3348
" Als de `digest' (verzamelmail) instelling uit (off) is, zult u "
3349
"berichten ontvangen\n"
3384
" Als de `digest' (verzamelmail) instelling uit (off) is, zult u berichten ontvangen\n"
3350
3385
" zodra deze op de maillijst zijn gepost. Gebruik `set digest plain'\n"
3351
3386
" als u gebundelde verzamelberichten wilt ontvangen in gewone tekst\n"
3352
" (i.e. RFC 1153 verzamelmail). Gebruik `set digest mime' als u in "
3353
"plaats daarvan berichten\n"
3387
" (i.e. RFC 1153 verzamelmail). Gebruik `set digest mime' als u in plaats daarvan berichten\n"
3354
3388
" wilt ontvangen die gebundeld zijn in MIME verzamelmails.\n"
3356
3390
" set delivery on\n"
3357
3391
" set delivery off\n"
3358
" Zet het ontvangen van berichten aan (on) of uit (off). Bij gebuik "
3359
"van 'off' meldt u zich niet af,\n"
3360
" maar Mailman zal u tijdelijk geen berichten toezenden. Dit is "
3362
" als u op vakantie gaat. Vergeet niet om 'set delivery on' te "
3392
" Zet het ontvangen van berichten aan (on) of uit (off). Bij gebuik van 'off' meldt u zich niet af,\n"
3393
" maar Mailman zal u tijdelijk geen berichten toezenden. Dit is nuttig\n"
3394
" als u op vakantie gaat. Vergeet niet om 'set delivery on' te gebruiken\n"
3364
3395
" als u terugkomt van vakantie!\n"
3366
3397
" set myposts on\n"
3367
3398
" set myposts off\n"
3368
" Gebruik `set myposts off' om geen berichten van de maillijst te "
3369
"ontvangen die u zelf\n"
3370
" heeft verstuurd. Dit heeft geen effect als u verzamelmails "
3399
" Gebruik `set myposts off' om geen berichten van de maillijst te ontvangen die u zelf\n"
3400
" heeft verstuurd. Dit heeft geen effect als u verzamelmails ontvangt.\n"
3373
3402
" set hide on\n"
3374
3403
" set hide off\n"
3375
" Gebruikt `set hide on' om uw e-mailadres geheim te houden als men "
3404
" Gebruikt `set hide on' om uw e-mailadres geheim te houden als men de\n"
3377
3405
" lidmaatschapslijst raadpleegt.\n"
3379
3407
" set duplicates on\n"
3380
3408
" set duplicates off\n"
3381
" Gebruik `set duplicates off' als u wilt niet wilt dat Mailman u "
3382
"berichten toestuurt\n"
3383
" als uw adres expliciet is opgenomen in de To: of Cc: velden van het "
3384
"betreffende bericht.\n"
3409
" Gebruik `set duplicates off' als u wilt niet wilt dat Mailman u berichten toestuurt\n"
3410
" als uw adres expliciet is opgenomen in de To: of Cc: velden van het betreffende bericht.\n"
3385
3411
" Dit kan voorkomen dat u hetzelfde bericht dubbel ontvangt.\n"
3387
3413
" set reminders on\n"
3388
3414
" set reminders off\n"
3389
" Gebruik `set reminders off' als u de maandelijkse "
3390
"wachtwoordherinnering\n"
3415
" Gebruik `set reminders off' als u de maandelijkse wachtwoordherinnering\n"
3391
3416
" van deze maillijst wilt uitschakelen.\n"
3393
3418
#: Mailman/Commands/cmd_set.py:122
4101
4118
"These policies control the automatic bounce processing system\n"
4102
4119
" in Mailman. Here's an overview of how it works.\n"
4104
" <p>When a bounce is received, Mailman tries to extract two "
4121
" <p>When a bounce is received, Mailman tries to extract two pieces\n"
4106
4122
" of information from the message: the address of the member the\n"
4107
" message was intended for, and the severity of the problem "
4123
" message was intended for, and the severity of the problem causing\n"
4109
4124
" the bounce. The severity can be either <em>hard</em> or\n"
4110
4125
" <em>soft</em> meaning either a fatal error occurred, or a\n"
4111
" transient error occurred. When in doubt, a hard severity is "
4126
" transient error occurred. When in doubt, a hard severity is used.\n"
4114
" <p>If no member address can be extracted from the bounce, then "
4116
" bounce is usually discarded. Otherwise, each member is assigned "
4128
" <p>If no member address can be extracted from the bounce, then the\n"
4129
" bounce is usually discarded. Otherwise, each member is assigned a\n"
4118
4130
" <em>bounce score</em> and every time we encounter a bounce from\n"
4119
" this member we increment the score. Hard bounces increment by "
4121
" while soft bounces increment by 0.5. We only increment the "
4123
" score once per day, so even if we receive ten hard bounces from "
4125
" member per day, their score will increase by only 1 for that "
4131
" this member we increment the score. Hard bounces increment by 1\n"
4132
" while soft bounces increment by 0.5. We only increment the bounce\n"
4133
" score once per day, so even if we receive ten hard bounces from a\n"
4134
" member per day, their score will increase by only 1 for that day.\n"
4128
4136
" <p>When a member's bounce score is greater than the\n"
4129
4137
" <a href=\"?VARHELP=bounce/bounce_score_threshold\">bounce score\n"
4130
" threshold</a>, the subscription is disabled. Once disabled, "
4138
" threshold</a>, the subscription is disabled. Once disabled, the\n"
4132
4139
" member will not receive any postings from the list until their\n"
4133
4140
" membership is explicitly re-enabled (either by the list\n"
4134
" administrator or the user). However, they will receive "
4141
" administrator or the user). However, they will receive occasional\n"
4136
4142
" reminders that their membership has been disabled, and these\n"
4137
4143
" reminders will include information about how to re-enable their\n"
4138
4144
" membership.\n"
4140
4146
" <p>You can control both the\n"
4141
" <a href=\"?VARHELP=bounce/bounce_you_are_disabled_warnings"
4147
" <a href=\"?VARHELP=bounce/bounce_you_are_disabled_warnings\">number\n"
4143
4148
" of reminders</a> the member will receive and the\n"
4144
" <a href=\"?VARHELP=bounce/"
4145
"bounce_you_are_disabled_warnings_interval\"\n"
4149
" <a href=\"?VARHELP=bounce/bounce_you_are_disabled_warnings_interval\"\n"
4146
4150
" >frequency</a> with which these reminders are sent.\n"
4148
4152
" <p>There is one other important configuration variable; after a\n"
4149
" certain period of time -- during which no bounces from the "
4153
" certain period of time -- during which no bounces from the member\n"
4151
4154
" are received -- the bounce information is\n"
4152
4155
" <a href=\"?VARHELP=bounce/bounce_info_stale_after\">considered\n"
4153
4156
" stale</a> and discarded. Thus by adjusting this value, and the\n"
4154
" score threshold, you can control how quickly bouncing members "
4157
" score threshold, you can control how quickly bouncing members are\n"
4156
4158
" disabled. You should tune both of these to the frequency and\n"
4157
4159
" traffic volume of your list."
4162
4164
" overzicht hoe dit werkt en hoe u het nader kunt instellen.\n"
4164
4166
" <p>Wanneer een bounce wordt ontvangen zal Mailman proberen\n"
4165
" twee soorten informatie uit het bericht te halen: het adres van "
4167
" waar het bericht voor bedoeld was en de zwaarte van het "
4169
" dat de bounce heeft veroorzaakt. De zwaarte kan <em>hard</em> "
4171
" <em>zacht</em> zijn, wat betekent dat er �f een fatale fout is "
4173
" �f een tijdelijke fout. Bij twijfel wordt een harde zwaarte "
4167
" twee soorten informatie uit het bericht te halen: het adres van het lid\n"
4168
" waar het bericht voor bedoeld was en de zwaarte van het probleem\n"
4169
" dat de bounce heeft veroorzaakt. De zwaarte kan <em>hard</em> of\n"
4170
" <em>zacht</em> zijn, wat betekent dat er �f een fatale fout is opgetreden\n"
4171
" �f een tijdelijke fout. Bij twijfel wordt een harde zwaarte gebruikt.\n"
4176
" <p>Als het niet mogelijk is om een adres van een lid te "
4178
" de bounce dan wordt de bounce genegeerd. Lukt het achterhalen "
4180
" dan wordt de bounce opgeteld bij de <em>bounceteller</em>. Bij "
4182
" bounces wordt er opgeteld met 1, bij zachte bounces met 0,5. De "
4184
" alleen eens per dag opgehoogd, dus zelfs als er 10 harde bounces "
4186
" ontvangen voor een lid in een dag, dan zal de teller maar met 1 "
4173
" <p>Als het niet mogelijk is om een adres van een lid te achterhalen uit\n"
4174
" de bounce dan wordt de bounce genegeerd. Lukt het achterhalen wel,\n"
4175
" dan wordt de bounce opgeteld bij de <em>bounceteller</em>. Bij harde\n"
4176
" bounces wordt er opgeteld met 1, bij zachte bounces met 0,5. De teller wordt\n"
4177
" alleen eens per dag opgehoogd, dus zelfs als er 10 harde bounces worden\n"
4178
" ontvangen voor een lid in een dag, dan zal de teller maar met 1 worden\n"
4188
4179
" opgehoogd.\n"
4190
4181
" <p>Als de bounceteller boven de \n"
4191
4182
" <a href=\"?VARHELP=bounce/bounce_score_threshold\">bounceteller\n"
4192
" grens</a> komt dan wordt het lidmaatschap uitgezet. Bij het "
4193
"uitzetten ontvangt\n"
4194
" het lid geen berichten meer van de lijst totdat het lidmaatschap "
4195
"weer is aangezet\n"
4196
" (door de lijstbeheerder of de gebruiker zelf). Ondertussen zal "
4197
"het lid af en toe\n"
4198
" herinneringen ontvangen dat zijn lidmaatschap is uitgeschakeld. "
4200
" herinneringen staat beschreven hoe het lid zijn lidmaatschap "
4201
"weer kan aanzetten.\n"
4183
" grens</a> komt dan wordt het lidmaatschap uitgezet. Bij het uitzetten ontvangt\n"
4184
" het lid geen berichten meer van de lijst totdat het lidmaatschap weer is aangezet\n"
4185
" (door de lijstbeheerder of de gebruiker zelf). Ondertussen zal het lid af en toe\n"
4186
" herinneringen ontvangen dat zijn lidmaatschap is uitgeschakeld. In deze\n"
4187
" herinneringen staat beschreven hoe het lid zijn lidmaatschap weer kan aanzetten.\n"
4203
4189
" <p>U kunt zowel het \n"
4204
" <a href=\"?VARHELP=bounce/bounce_you_are_disabled_warnings"
4190
" <a href=\"?VARHELP=bounce/bounce_you_are_disabled_warnings\">aantal\n"
4206
4191
" herinneringen</a> instellen dat het lid ontvangt als de \n"
4207
" <a href=\"?VARHELP=bounce/"
4208
"bounce_you_are_disabled_warnings_interval\"\n"
4192
" <a href=\"?VARHELP=bounce/bounce_you_are_disabled_warnings_interval\"\n"
4209
4193
" >frequentie</a> waarmee deze herinneringen worden verzonden.\n"
4211
" <p>Er is nog een belangrijke instelling: Na een bepaalde "
4213
" als er geen bounces van het lid zijn ontvangen, zullen de "
4195
" <p>Er is nog een belangrijke instelling: Na een bepaalde periode,\n"
4196
" als er geen bounces van het lid zijn ontvangen, zullen de bouncegegevens\n"
4215
4197
" worden beschouwd als\n"
4216
" <a href=\"?VARHELP=bounce/bounce_info_stale_after\">verlopen</"
4218
" en worden genegeerd. Door deze waarde en de bounceteller grens "
4220
" kunt u bepalen hoe snel een lidmaatschap met bounces wordt "
4221
"uitgeschakeld. Het is\n"
4222
" aan te raden om dit af te stemmen op de frequentie en de volume "
4223
"van de berichten\n"
4198
" <a href=\"?VARHELP=bounce/bounce_info_stale_after\">verlopen</a>\n"
4199
" en worden genegeerd. Door deze waarde en de bounceteller grens aan te passen\n"
4200
" kunt u bepalen hoe snel een lidmaatschap met bounces wordt uitgeschakeld. Het is\n"
4201
" aan te raden om dit af te stemmen op de frequentie en de volume van de berichten\n"
4224
4202
" voor de maillijst."
4226
4204
#: Mailman/Gui/Bounce.py:75
4260
4237
"Each subscriber is assigned a bounce score, as a floating\n"
4261
4238
" point number. Whenever Mailman receives a bounce from a list\n"
4262
" member, that member's score is incremented. Hard bounces "
4239
" member, that member's score is incremented. Hard bounces (fatal\n"
4264
4240
" errors) increase the score by 1, while soft bounces (temporary\n"
4265
4241
" errors) increase the score by 0.5. Only one bounce per day\n"
4266
4242
" counts against a member's score, so even if 10 bounces are\n"
4267
" received for a member on the same day, their score will "
4243
" received for a member on the same day, their score will increase\n"
4269
4244
" by just 1.\n"
4271
4246
" This variable describes the upper limit for a member's bounce\n"
4272
4247
" score, above which they are automatically disabled, but not\n"
4273
4248
" removed from the mailing list."
4275
"Elk lid heeft een maximum bounce score toegewezen gekregen, een getal met "
4277
" achter de punt. Als Mailman een bounce ontvangt van het lid, "
4279
" de score worden verhoogd. Harde bounces (fatale fouten) "
4281
" de score met 1.0, terwijl zachte bounces (tijdelijke fouten) "
4283
" score met 0.5 verhogen. Slechts ��n bounce per dag draagt bij "
4285
" de verhoging van de score, dus zelfs als 10 bounces op dezelfde "
4287
" worden ontvangen, zal de score met niet meer dan 1.0 worden "
4250
"Elk lid heeft een maximum bounce score toegewezen gekregen, een getal met decimalen\n"
4251
" achter de punt. Als Mailman een bounce ontvangt van het lid, zal\n"
4252
" de score worden verhoogd. Harde bounces (fatale fouten) verhogen\n"
4253
" de score met 1.0, terwijl zachte bounces (tijdelijke fouten) de\n"
4254
" score met 0.5 verhogen. Slechts ��n bounce per dag draagt bij aan\n"
4255
" de verhoging van de score, dus zelfs als 10 bounces op dezelfde dag\n"
4256
" worden ontvangen, zal de score met niet meer dan 1.0 worden verhoogd.\n"
4290
" Deze variable legt de bovenlimiet vast voor de bounce score "
4292
" een lid, waarboven het lidmaaatschap automatisch wordt "
4258
" Deze variable legt de bovenlimiet vast voor de bounce score van\n"
4259
" een lid, waarboven het lidmaaatschap automatisch wordt uitgezet,\n"
4294
4260
" maar waarbij het lid nog niet verwijderd wordt van de maillijst."
4296
4262
#: Mailman/Gui/Bounce.py:102
4350
4311
"While Mailman's bounce detector is fairly robust, it's\n"
4351
4312
" impossible to detect every bounce format in the world. You\n"
4352
" should keep this variable set to <em>Yes</em> for two reasons: "
4313
" should keep this variable set to <em>Yes</em> for two reasons: 1)\n"
4354
4314
" If this really is a permanent bounce from one of your members,\n"
4355
" you should probably manually remove them from your list, and "
4357
" you might want to send the message on to the Mailman "
4315
" you should probably manually remove them from your list, and 2)\n"
4316
" you might want to send the message on to the Mailman developers\n"
4359
4317
" so that this new format can be added to its known set.\n"
4361
4319
" <p>If you really can't be bothered, then set this variable to\n"
4362
4320
" <em>No</em> and all non-detected bounces will be discarded\n"
4363
4321
" without further processing.\n"
4365
" <p><b>Note:</b> This setting will also affect all messages "
4323
" <p><b>Note:</b> This setting will also affect all messages sent\n"
4367
4324
" to your list's -admin address. This address is deprecated and\n"
4368
" should never be used, but some people may still send mail to "
4325
" should never be used, but some people may still send mail to this\n"
4370
4326
" address. If this happens, and this variable is set to\n"
4371
" <em>No</em> those messages too will get discarded. You may "
4327
" <em>No</em> those messages too will get discarded. You may want\n"
4373
4328
" to set up an\n"
4374
" <a href=\"?VARHELP=autoreply/autoresponse_admin_text"
4329
" <a href=\"?VARHELP=autoreply/autoresponse_admin_text\">autoresponse\n"
4376
4330
" message</a> for email to the -owner and -admin address."
4378
4332
"Ondanks het feit dat de bouncedetector tamelijk robuust is, is het\n"
4379
4333
" onmogelijk om elk in de wereld bestaand bounce-format te\n"
4380
" detecteren. U wordt aangeraden deze variabele op <em>Ja</em> "
4334
" detecteren. U wordt aangeraden deze variabele op <em>Ja</em> te\n"
4382
4335
" houden om twee redenen: 1) Als het echt een permanente bounce\n"
4383
4336
" betreft van een van de leden, dan moet u deze waarschijnlijk\n"
4384
4337
" handmatig uit de lijst verwijderen, en 2) u kunt het bericht\n"
4477
4419
"Policies concerning the content of list traffic.\n"
4479
4421
" <p>Content filtering works like this: when a message is\n"
4480
" received by the list and you have enabled content filtering, "
4422
" received by the list and you have enabled content filtering, the\n"
4482
4423
" individual attachments are first compared to the\n"
4483
4424
" <a href=\"?VARHELP=contentfilter/filter_mime_types\">filter\n"
4484
" types</a>. If the attachment type matches an entry in the "
4425
" types</a>. If the attachment type matches an entry in the filter\n"
4486
4426
" types, it is discarded.\n"
4488
4428
" <p>Then, if there are <a\n"
4489
4429
" href=\"?VARHELP=contentfilter/pass_mime_types\">pass types</a>\n"
4490
4430
" defined, any attachment type that does <em>not</em> match a\n"
4491
" pass type is also discarded. If there are no pass types "
4431
" pass type is also discarded. If there are no pass types defined,\n"
4493
4432
" this check is skipped.\n"
4495
4434
" <p>After this initial filtering, any <tt>multipart</tt>\n"
4496
" attachments that are empty are removed. If the outer message "
4435
" attachments that are empty are removed. If the outer message is\n"
4498
4436
" left empty after this filtering, then the whole message is\n"
4499
4437
" discarded.\n"
4501
4439
" <p> Then, each <tt>multipart/alternative</tt> section will\n"
4502
" be replaced by just the first alternative that is non-empty "
4440
" be replaced by just the first alternative that is non-empty after\n"
4504
4441
" filtering if\n"
4505
4442
" <a href=\"?VARHELP=contentfilter/collapse_alternatives\"\n"
4506
4443
" >collapse_alternatives</a> is enabled.\n"
4976
4860
#: Mailman/Gui/General.py:80
4978
4862
"There are two ownership roles associated with each mailing\n"
4979
" list. The <em>list administrators</em> are the people who "
4981
" ultimate control over all parameters of this mailing list. "
4863
" list. The <em>list administrators</em> are the people who have\n"
4864
" ultimate control over all parameters of this mailing list. They\n"
4983
4865
" are able to change any list configuration variable available\n"
4984
4866
" through these administration web pages.\n"
4986
4868
" <p>The <em>list moderators</em> have more limited permissions;\n"
4987
" they are not able to change any list configuration variable, "
4869
" they are not able to change any list configuration variable, but\n"
4989
4870
" they are allowed to tend to pending administration requests,\n"
4990
" including approving or rejecting held subscription requests, "
4871
" including approving or rejecting held subscription requests, and\n"
4992
4872
" disposing of held postings. Of course, the <em>list\n"
4993
4873
" administrators</em> can also tend to pending requests.\n"
4995
4875
" <p>In order to split the list ownership duties into\n"
4996
4876
" administrators and moderators, you must\n"
4997
4877
" <a href=\"passwords\">set a separate moderator password</a>,\n"
4998
" and also provide the <a href=\"?VARHELP=general/moderator"
4878
" and also provide the <a href=\"?VARHELP=general/moderator\">email\n"
5000
4879
" addresses of the list moderators</a>. Note that the field you\n"
5001
4880
" are changing here specifies the list administrators."
5220
5077
"This option controls what Mailman does to the\n"
5221
5078
" <tt>Reply-To:</tt> header in messages flowing through this\n"
5222
" mailing list. When set to <em>Poster</em>, no <tt>Reply-To:</"
5079
" mailing list. When set to <em>Poster</em>, no <tt>Reply-To:</tt>\n"
5224
5080
" header is added by Mailman, although if one is present in the\n"
5225
5081
" original message, it is not stripped. Setting this value to\n"
5226
5082
" either <em>This list</em> or <em>Explicit address</em> causes\n"
5227
5083
" Mailman to insert a specific <tt>Reply-To:</tt> header in all\n"
5228
5084
" messages, overriding the header in the original message if\n"
5229
5085
" necessary (<em>Explicit address</em> inserts the value of <a\n"
5230
" href=\"?VARHELP=general/reply_to_address\">reply_to_address</"
5086
" href=\"?VARHELP=general/reply_to_address\">reply_to_address</a>).\n"
5233
5088
" <p>There are many reasons not to introduce or override the\n"
5234
5089
" <tt>Reply-To:</tt> header. One is that some posters depend on\n"
5235
5090
" their own <tt>Reply-To:</tt> settings to convey their valid\n"
5236
5091
" return address. Another is that modifying <tt>Reply-To:</tt>\n"
5237
5092
" makes it much more difficult to send private replies. See <a\n"
5238
" href=\"http://www.unicom.com/pw/reply-to-harmful.html\">`Reply-"
5240
" Munging Considered Harmful</a> for a general discussion of "
5093
" href=\"http://www.unicom.com/pw/reply-to-harmful.html\">`Reply-To'\n"
5094
" Munging Considered Harmful</a> for a general discussion of this\n"
5242
5095
" issue. See <a\n"
5243
" href=\"http://www.metasystema.net/essays/reply-to.mhtml\">Reply-"
5096
" href=\"http://www.metasystema.net/essays/reply-to.mhtml\">Reply-To\n"
5245
5097
" Munging Considered Useful</a> for a dissenting opinion.\n"
5247
" <p>Some mailing lists have restricted posting privileges, with "
5249
" parallel list devoted to discussions. Examples are `patches' "
5251
" `checkin' lists, where software changes are posted by a "
5099
" <p>Some mailing lists have restricted posting privileges, with a\n"
5100
" parallel list devoted to discussions. Examples are `patches' or\n"
5101
" `checkin' lists, where software changes are posted by a revision\n"
5253
5102
" control system, but discussion about the changes occurs on a\n"
5254
5103
" developers mailing list. To support these types of mailing\n"
5255
5104
" lists, select <tt>Explicit address</tt> and set the\n"
5259
5108
"Deze instelling regelt wat Mailman moet doen met het\n"
5260
5109
" <tt>Reply-To:</tt> adres in berichten die via deze maillijst\n"
5261
5110
" worden verstuurd. Wanneer dit op <em>Verzender</em> wordt\n"
5262
" ingesteld, zal geen <tt>Reply-To:</tt> adres worden toegevoegd "
5111
" ingesteld, zal geen <tt>Reply-To:</tt> adres worden toegevoegd door\n"
5264
5112
" Mailman, terwijl een in het oorspronkelijk bericht aanwezig\n"
5265
" adres niet wordt verwijderd. Wanneer dit op <em>Deze lijst</"
5113
" adres niet wordt verwijderd. Wanneer dit op <em>Deze lijst</em>\n"
5267
5114
" of <em>Expliciet adres</em> wordt ingesteld, zorgt Mailman\n"
5268
5115
" ervoor dat een specifiek <tt>Reply-To:</tt> adres wordt\n"
5269
" toegevoegd aan alle berichten, waarbij het oorspronkelijke "
5116
" toegevoegd aan alle berichten, waarbij het oorspronkelijke adres\n"
5271
5117
" wordt overschreven indien nodig. (<em>Expliciet adres</em>\n"
5272
5118
" voegt het onder <a\n"
5273
" href=\"?VARHELP=general/reply_to_address\">reply_to_address</"
5119
" href=\"?VARHELP=general/reply_to_address\">reply_to_address</a>\n"
5275
5120
" ingevoerde adres toe).\n"
5277
5122
" <p>Er zijn vele redenen om geen <tt>Reply-To:</tt>\n"
5278
5123
" adres toe te voegen of te overschrijven. Sommige afzenders\n"
5279
5124
" zijn afhankelijk van hun eigen <tt>Reply-To:</tt>\n"
5280
5125
" instelling om berichten op hun e-mailadres binnen te krijgen.\n"
5281
" Een andere reden is dat het aanpassen van het <tt>Reply-To:</"
5283
" het veel moeilijker maakt om priv�-antwoorden te versturen. Zie "
5285
" href=\"http://www.unicom.com/pw/reply-to-harmful.html\">`Reply-"
5287
" Munging Considered Harmful</a> voor een algemene bespreking van "
5126
" Een andere reden is dat het aanpassen van het <tt>Reply-To:</tt> adres\n"
5127
" het veel moeilijker maakt om priv�-antwoorden te versturen. Zie <a\n"
5128
" href=\"http://www.unicom.com/pw/reply-to-harmful.html\">`Reply-To'\n"
5129
" Munging Considered Harmful</a> voor een algemene bespreking van dit\n"
5289
5130
" onderwerp. Zie <a\n"
5290
" href=\"http://www.metasystema.net/essays/reply-to.mhtml\">Reply-"
5131
" href=\"http://www.metasystema.net/essays/reply-to.mhtml\">Reply-To\n"
5292
5132
" Munging Considered Useful</a> voor een tegengestelde visie.\n"
5294
5134
" <p>Sommige maillijsten hebben beperkte verzendprivileges,\n"
5318
5157
" their own <tt>Reply-To:</tt> settings to convey their valid\n"
5319
5158
" return address. Another is that modifying <tt>Reply-To:</tt>\n"
5320
5159
" makes it much more difficult to send private replies. See <a\n"
5321
" href=\"http://www.unicom.com/pw/reply-to-harmful.html\">`Reply-"
5323
" Munging Considered Harmful</a> for a general discussion of "
5160
" href=\"http://www.unicom.com/pw/reply-to-harmful.html\">`Reply-To'\n"
5161
" Munging Considered Harmful</a> for a general discussion of this\n"
5325
5162
" issue. See <a\n"
5326
" href=\"http://www.metasystema.net/essays/reply-to.mhtml\">Reply-"
5163
" href=\"http://www.metasystema.net/essays/reply-to.mhtml\">Reply-To\n"
5328
5164
" Munging Considered Useful</a> for a dissenting opinion.\n"
5330
" <p>Some mailing lists have restricted posting privileges, with "
5332
" parallel list devoted to discussions. Examples are `patches' "
5334
" `checkin' lists, where software changes are posted by a "
5166
" <p>Some mailing lists have restricted posting privileges, with a\n"
5167
" parallel list devoted to discussions. Examples are `patches' or\n"
5168
" `checkin' lists, where software changes are posted by a revision\n"
5336
5169
" control system, but discussion about the changes occurs on a\n"
5337
5170
" developers mailing list. To support these types of mailing\n"
5338
" lists, specify the explicit <tt>Reply-To:</tt> address here. "
5171
" lists, specify the explicit <tt>Reply-To:</tt> address here. You\n"
5340
5172
" must also specify <tt>Explicit address</tt> in the\n"
5341
5173
" <tt>reply_goes_to_list</tt>\n"
5683
5484
#: Mailman/Gui/General.py:382
5685
5486
"Should messages from this mailing list include the\n"
5686
" <a href=\"http://www.faqs.org/rfcs/rfc2369.html\">RFC 2369</"
5487
" <a href=\"http://www.faqs.org/rfcs/rfc2369.html\">RFC 2369</a>\n"
5688
5488
" (i.e. <tt>List-*</tt>) headers? <em>Yes</em> is highly\n"
5689
5489
" recommended."
5691
5491
"Moeten berichten van deze maillijst\n"
5692
" <a href=\"http://www.faqs.org/rfcs/rfc2369.html\">RFC 2369</"
5492
" <a href=\"http://www.faqs.org/rfcs/rfc2369.html\">RFC 2369</a>\n"
5694
5493
" (i.e. <tt>List-*</tt>) headers bevatten? <em>Ja</em>\n"
5695
5494
" wordt sterk aangeraden."
5697
5496
#: Mailman/Gui/General.py:387
5699
5498
"RFC 2369 defines a set of List-* headers that are\n"
5700
" normally added to every message sent to the list "
5702
" These greatly aid end-users who are using standards "
5499
" normally added to every message sent to the list membership.\n"
5500
" These greatly aid end-users who are using standards compliant\n"
5704
5501
" mail readers. They should normally always be enabled.\n"
5706
" <p>However, not all mail readers are standards compliant "
5503
" <p>However, not all mail readers are standards compliant yet,\n"
5708
5504
" and if you have a large number of members who are using\n"
5709
5505
" non-compliant mail readers, they may be annoyed at these\n"
5710
" headers. You should first try to educate your members as "
5712
" why these headers exist, and how to hide them in their "
5714
" clients. As a last resort you can disable these headers, "
5716
" this is not recommended (and in fact, your ability to "
5506
" headers. You should first try to educate your members as to\n"
5507
" why these headers exist, and how to hide them in their mail\n"
5508
" clients. As a last resort you can disable these headers, but\n"
5509
" this is not recommended (and in fact, your ability to disable\n"
5718
5510
" these headers may eventually go away)."
5720
5512
"RFC 2369 definieert een set van List-* headers die normaliter\n"
5899
5674
" prefix</a> even when it consists of only ASCII characters?"
5902
" <a href=\"?VARHELP=general/subject_prefix\">onderwerp-"
5677
" <a href=\"?VARHELP=general/subject_prefix\">onderwerp-voorvoegsel</a>\n"
5904
5678
" ook al bestaat dit uit alleen ASCII tekens?"
5906
5680
#: Mailman/Gui/Language.py:95
5908
5682
"If your mailing list's default language uses a non-ASCII\n"
5909
" character set and the prefix contains non-ASCII characters, "
5683
" character set and the prefix contains non-ASCII characters, the\n"
5911
5684
" prefix will always be encoded according to the relevant\n"
5912
5685
" standards. However, if your prefix contains only ASCII\n"
5913
" characters, you may want to set this option to <em>Never</em> "
5686
" characters, you may want to set this option to <em>Never</em> to\n"
5915
5687
" disable prefix encoding. This can make the subject headers\n"
5916
5688
" slightly more readable for users with mail readers that don't\n"
5917
5689
" properly handle non-ASCII encodings.\n"
5919
" <p>Note however, that if your mailing list receives both "
5691
" <p>Note however, that if your mailing list receives both encoded\n"
5921
5692
" and unencoded subject headers, you might want to choose <em>As\n"
5922
" needed</em>. Using this setting, Mailman will not encode "
5693
" needed</em>. Using this setting, Mailman will not encode ASCII\n"
5924
5694
" prefixes when the rest of the header contains only ASCII\n"
5925
5695
" characters, but if the original header contains non-ASCII\n"
5926
" characters, it will encode the prefix. This avoids an "
5928
" in the standards which could cause some mail readers to "
5696
" characters, it will encode the prefix. This avoids an ambiguity\n"
5697
" in the standards which could cause some mail readers to display\n"
5930
5698
" extra, or missing spaces between the prefix and the original\n"
6008
5775
"Normally, Mailman sends the regular delivery messages to\n"
6009
5776
" the mail server in batches. This is much more efficent\n"
6010
" because it reduces the amount of traffic between Mailman "
5777
" because it reduces the amount of traffic between Mailman and\n"
6012
5778
" the mail server.\n"
6014
" <p>However, some lists can benefit from a more "
5780
" <p>However, some lists can benefit from a more personalized\n"
6016
5781
" approach. In this case, Mailman crafts a new message for\n"
6017
5782
" each member on the regular delivery list. Turning this\n"
6018
" feature on may degrade the performance of your site, so "
6020
" need to carefully consider whether the trade-off is worth "
6022
" or whether there are other ways to accomplish what you "
5783
" feature on may degrade the performance of your site, so you\n"
5784
" need to carefully consider whether the trade-off is worth it,\n"
5785
" or whether there are other ways to accomplish what you want.\n"
6024
5786
" You should also carefully monitor your system load to make\n"
6025
5787
" sure it is acceptable.\n"
6027
5789
" <p>Select <em>No</em> to disable personalization and send\n"
6028
" messages to the members in batches. Select <em>Yes</em> "
5790
" messages to the members in batches. Select <em>Yes</em> to\n"
6030
5791
" personalize deliveries and allow additional substitution\n"
6031
5792
" variables in message headers and footers (see below). In\n"
6032
5793
" addition, by selecting <em>Full Personalization</em>, the\n"
6033
" <code>To</code> header of posted messages will be modified "
5794
" <code>To</code> header of posted messages will be modified to\n"
6035
5795
" include the member's address instead of the list's posting\n"
6038
5798
" <p>When personalization is enabled, a few more expansion\n"
6039
5799
" variables that can be included in the <a\n"
6040
" href=\"?VARHELP=nondigest/msg_header\">message header</a> "
6042
" <a href=\"?VARHELP=nondigest/msg_footer\">message footer</"
5800
" href=\"?VARHELP=nondigest/msg_header\">message header</a> and\n"
5801
" <a href=\"?VARHELP=nondigest/msg_footer\">message footer</a>.\n"
6045
" <p>These additional substitution variables will be "
6047
" for your headers and footers, when this feature is "
5803
" <p>These additional substitution variables will be available\n"
5804
" for your headers and footers, when this feature is enabled:\n"
6050
5806
" <ul><li><b>user_address</b> - The address of the user,\n"
6051
5807
" coerced to lower case.\n"
6052
" <li><b>user_delivered_to</b> - The case-preserved "
5808
" <li><b>user_delivered_to</b> - The case-preserved address\n"
6054
5809
" that the user is subscribed with.\n"
6055
5810
" <li><b>user_password</b> - The user's password.\n"
6056
5811
" <li><b>user_name</b> - The user's full name.\n"
6057
" <li><b>user_optionsurl</b> - The url to the user's "
5812
" <li><b>user_optionsurl</b> - The url to the user's option\n"
6950
6652
"Alternatieve adressen die worden geaccepteerd wanneer\n"
6951
6653
" `require_explicit_destination' is geactiveerd. Deze optie\n"
6952
" vergelijkt een lijst van reguliere uitdrukkingen, ��n per "
6654
" vergelijkt een lijst van reguliere uitdrukkingen, ��n per regel,\n"
6954
6655
" met elke ontvangstadres dat in het bericht vermeld staat. Dit\n"
6955
" gebeurt m.b.v. de functie re.match() van Python, wat inhoudt "
6656
" gebeurt m.b.v. de functie re.match() van Python, wat inhoudt dat\n"
6957
6657
" ze worden verankerd in het begin van de string.\n"
6959
" <p>Vanwege compatibiliteit met de eerdere versie 1.1 van "
6659
" <p>Vanwege compatibiliteit met de eerdere versie 1.1 van Mailman\n"
6961
6660
" zal, als de reguliere uitdrukking geen `@'-teken bevat, het\n"
6962
6661
" patroon worden vergeleken met het lokale deel van het\n"
6963
6662
" ontvangstadres. Als er geen match is, of als het patroon een\n"
6964
6663
" `@' bevat, dan wordt het patroon vergeleken met het volledige\n"
6965
6664
" ontvangstadres.\n"
6967
" <p>Het vergelijken met het lokale deel heeft inmiddels de "
6666
" <p>Het vergelijken met het lokale deel heeft inmiddels de status\n"
6969
6667
" 'deprecated' (verouderd/niet geldig) gekregen; in toekomstige\n"
6970
6668
" versies van Mailman zal het patroon altijd met het volledige\n"
6971
6669
" adres worden vergeleken."
6973
6671
#: Mailman/Gui/Privacy.py:374
6974
6672
msgid "Ceiling on acceptable number of recipients for a posting."
6976
"Het maximum aantal ontvangers dat geaccepteerd kan worden voor een bericht."
6673
msgstr "Het maximum aantal ontvangers dat geaccepteerd kan worden voor een bericht."
6978
6675
#: Mailman/Gui/Privacy.py:376
7170
6856
" <p>De bodytekst van het bericht kan eventueel ook worden\n"
7171
6857
" gecontroleerd op de aanwezigheid van <code>Subject:</code>\n"
7172
6858
" en <code>Keywords:</code> headers; dit is nader toegelicht\n"
7173
" bij de <a href=\"?VARHELP=topics/topics_bodylines_limit"
7174
"\">topics_bodylines_limit</a> instelling."
6859
" bij de <a href=\"?VARHELP=topics/topics_bodylines_limit\">topics_bodylines_limit</a> instelling."
7176
6861
#: Mailman/Gui/Topics.py:70
7177
6862
msgid "How many body lines should the topic matcher scan?"
7179
"Hoeveel regels van de bodytekst moet de onderwerpvergelijker controleren?"
6863
msgstr "Hoeveel regels van de bodytekst moet de onderwerpvergelijker controleren?"
7181
6865
#: Mailman/Gui/Topics.py:72
7183
6867
"The topic matcher will scan this many lines of the message\n"
7184
" body looking for topic keyword matches. Body scanning stops "
7186
" either this many lines have been looked at, or a non-header-"
7188
" body line is encountered. By setting this value to zero, no "
7190
" lines will be scanned (i.e. only the <code>Keywords:</code> "
7192
" <code>Subject:</code> headers will be scanned). By setting "
7194
" value to a negative number, then all body lines will be "
6868
" body looking for topic keyword matches. Body scanning stops when\n"
6869
" either this many lines have been looked at, or a non-header-like\n"
6870
" body line is encountered. By setting this value to zero, no body\n"
6871
" lines will be scanned (i.e. only the <code>Keywords:</code> and\n"
6872
" <code>Subject:</code> headers will be scanned). By setting this\n"
6873
" value to a negative number, then all body lines will be scanned\n"
7196
6874
" until a non-header-like line is encountered.\n"
7331
7001
#: Mailman/Gui/Usenet.py:68
7333
7003
"This setting determines the moderation policy of the\n"
7334
" newsgroup and its interaction with the moderation policy of "
7004
" newsgroup and its interaction with the moderation policy of the\n"
7336
7005
" mailing list. This only applies to the newsgroup that you are\n"
7337
7006
" gatewaying <em>to</em>, so if you are only gatewaying from\n"
7338
" Usenet, or the newsgroup you are gatewaying to is not "
7007
" Usenet, or the newsgroup you are gatewaying to is not moderated,\n"
7340
7008
" set this option to <em>None</em>.\n"
7342
" <p>If the newsgroup is moderated, you can set this mailing "
7344
" up to be the moderation address for the newsgroup. By "
7346
" <em>Moderated</em>, an additional posting hold will be placed "
7010
" <p>If the newsgroup is moderated, you can set this mailing list\n"
7011
" up to be the moderation address for the newsgroup. By selecting\n"
7012
" <em>Moderated</em>, an additional posting hold will be placed in\n"
7348
7013
" the approval process. All messages posted to the mailing list\n"
7349
" will have to be approved before being sent on to the "
7014
" will have to be approved before being sent on to the newsgroup,\n"
7351
7015
" or to the mailing list membership.\n"
7353
" <p><em>Note that if the message has an <tt>Approved</tt> "
7017
" <p><em>Note that if the message has an <tt>Approved</tt> header\n"
7355
7018
" with the list's administrative password in it, this hold test\n"
7356
7019
" will be bypassed, allowing privileged posters to send messages\n"
7357
7020
" directly to the list and the newsgroup.</em>\n"
7359
" <p>Finally, if the newsgroup is moderated, but you want to "
7361
" an open posting policy anyway, you should select <em>Open "
7022
" <p>Finally, if the newsgroup is moderated, but you want to have\n"
7023
" an open posting policy anyway, you should select <em>Open list,\n"
7363
7024
" moderated group</em>. The effect of this is to use the normal\n"
7364
7025
" Mailman moderation facilities, but to add an <tt>Approved</tt>\n"
7365
7026
" header to all messages that are gatewayed to Usenet."
7546
7200
#: Mailman/HTMLFormatter.py:164
7548
7202
"<p>We have received some recent bounces from your\n"
7549
" address. Your current <em>bounce score</em> is %(score)s out of "
7203
" address. Your current <em>bounce score</em> is %(score)s out of a\n"
7551
7204
" maximum of %(total)s. Please double check that your subscribed\n"
7552
" address is correct and that there are no problems with delivery "
7205
" address is correct and that there are no problems with delivery to\n"
7554
7206
" this address. Your bounce score will be automatically reset if\n"
7555
7207
" the problems are corrected soon."
7557
7209
"<p>Wij hebben recentelijk een aantal bounces ontvangen vanaf uw\n"
7558
" adres. Uw huidige <em>bounce score</em> is %(score)s; de "
7560
" score is %(total)s. Wilt u s.v.p. goed controleren of het "
7210
" adres. Uw huidige <em>bounce score</em> is %(score)s; de maximum\n"
7211
" score is %(total)s. Wilt u s.v.p. goed controleren of het adres\n"
7562
7212
" waaronder u bent aangemeld correct is, en dat er geen problemen\n"
7563
" zijn met de bezorging van mail op dit adres? Uw bounce score "
7213
" zijn met de bezorging van mail op dit adres? Uw bounce score zal\n"
7565
7214
" automatisch worden gereset als de problemen op korte termijn\n"
7566
7215
" worden opgelost."
7568
7217
#: Mailman/HTMLFormatter.py:176
7570
"(Note - you are subscribing to a list of mailing lists, so the %(type)s "
7571
"notice will be sent to the admin address for your membership, %(addr)s.)<p>"
7218
msgid "(Note - you are subscribing to a list of mailing lists, so the %(type)s notice will be sent to the admin address for your membership, %(addr)s.)<p>"
7573
7220
"(Opmerking - u meldt zich aan op een lijst van maillijsten, dus zal de\n"
7574
7221
" %(type)s melding worden verstuurd naar het admin adres voor\n"
9557
9155
"Primary start-up and shutdown script for Mailman's qrunner daemon.\n"
9559
"This script starts, stops, and restarts the main Mailman queue runners, "
9561
"sure that the various long-running qrunners are still alive and kicking. "
9157
"This script starts, stops, and restarts the main Mailman queue runners, making\n"
9158
"sure that the various long-running qrunners are still alive and kicking. It\n"
9563
9159
"does this by forking and exec'ing the qrunners and waiting on their pids.\n"
9564
9160
"When it detects a subprocess has exited, it may restart it.\n"
9566
"The qrunners respond to SIGINT, SIGTERM, and SIGHUP. SIGINT and SIGTERM "
9568
"cause the qrunners to exit cleanly, but the master will only restart "
9570
"that have exited due to a SIGINT. SIGHUP causes the master and the "
9162
"The qrunners respond to SIGINT, SIGTERM, and SIGHUP. SIGINT and SIGTERM both\n"
9163
"cause the qrunners to exit cleanly, but the master will only restart qrunners\n"
9164
"that have exited due to a SIGINT. SIGHUP causes the master and the qrunners\n"
9572
9165
"to close their log files, and reopen then upon the next printed message.\n"
9574
9167
"The master also responds to SIGINT, SIGTERM, and SIGHUP, which it simply\n"
9575
"passes on to the qrunners (note that the master will close and reopen its "
9577
"log files on receipt of a SIGHUP). The master also leaves its own process "
9168
"passes on to the qrunners (note that the master will close and reopen its own\n"
9169
"log files on receipt of a SIGHUP). The master also leaves its own process id\n"
9579
9170
"in the file data/master-qrunner.pid but you normally don't need to use this\n"
9580
9171
"pid directly. The `start', `stop', `restart', and `reopen' commands handle\n"
9581
9172
"everything for you.\n"
9591
9182
" command is given.\n"
9593
9184
" -u/--run-as-user\n"
9594
" Normally, this script will refuse to run if the user id and group "
9185
" Normally, this script will refuse to run if the user id and group id\n"
9596
9186
" are not set to the `mailman' user and group (as defined when you\n"
9597
" configured Mailman). If run as root, this script will change to "
9187
" configured Mailman). If run as root, this script will change to this\n"
9599
9188
" user and group before the check is made.\n"
9601
" This can be inconvenient for testing and debugging purposes, so the -"
9603
" flag means that the step that sets and checks the uid/gid is "
9190
" This can be inconvenient for testing and debugging purposes, so the -u\n"
9191
" flag means that the step that sets and checks the uid/gid is skipped,\n"
9605
9192
" and the program is run as the current user and group. This flag is\n"
9606
9193
" not recommended for normal production environments.\n"
9608
" Note though, that if you run with -u and are not in the mailman "
9195
" Note though, that if you run with -u and are not in the mailman group,\n"
9610
9196
" you may have permission problems, such as begin unable to delete a\n"
9611
9197
" list's archives through the web. Tough luck!\n"
9613
9199
" -s/--stale-lock-cleanup\n"
9614
9200
" If mailmanctl finds an existing master lock, it will normally exit\n"
9615
" with an error message. With this option, mailmanctl will perform "
9617
" extra level of checking. If a process matching the host/pid "
9201
" with an error message. With this option, mailmanctl will perform an\n"
9202
" extra level of checking. If a process matching the host/pid described\n"
9619
9203
" in the lock file is running, mailmanctl will still exit, but if no\n"
9620
" matching process is found, mailmanctl will remove the apparently "
9204
" matching process is found, mailmanctl will remove the apparently stale\n"
9622
9205
" lock and make another attempt to claim the master lock.\n"
9624
9207
" -q/--quiet\n"
9854
9425
"You can specify as many of the arguments as you want on the command line:\n"
9855
9426
"you will be prompted for the missing ones.\n"
9857
"Every Mailman list has two parameters which define the default host name "
9428
"Every Mailman list has two parameters which define the default host name for\n"
9859
9429
"outgoing email, and the default URL for all web interfaces. When you\n"
9860
"configured Mailman, certain defaults were calculated, but if you are "
9862
"multiple virtual Mailman sites, then the defaults may not be appropriate "
9430
"configured Mailman, certain defaults were calculated, but if you are running\n"
9431
"multiple virtual Mailman sites, then the defaults may not be appropriate for\n"
9864
9432
"the list you are creating.\n"
9866
"You also specify the domain to create your new list in by typing the "
9434
"You also specify the domain to create your new list in by typing the command\n"
9870
9437
" newlist --urlhost=www.mydom.ain mylist\n"
9872
"where `www.mydom.ain' should be the base hostname for the URL to this "
9439
"where `www.mydom.ain' should be the base hostname for the URL to this virtual\n"
9874
9440
"hosts's lists. E.g. with this setting people will view the general list\n"
9875
9441
"overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain\n"
9876
9442
"should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if\n"
9877
9443
"the email hostname to be automatically determined.\n"
9879
"If you want the email hostname to be different from the one looked up by "
9881
"VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can "
9445
"If you want the email hostname to be different from the one looked up by the\n"
9446
"VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify\n"
9883
9447
"`emailhost' like so:\n"
9885
9449
" newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist\n"
9887
"where `mydom.ain' is the mail domain name. If you don't specify emailhost "
9889
"urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST "
9451
"where `mydom.ain' is the mail domain name. If you don't specify emailhost but\n"
9452
"urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will\n"
9891
9453
"be used for the email interface.\n"
9893
9455
"For backward compatibility, you can also specify the domain to create your\n"
9951
9510
" --runner=runner[:slice:range]\n"
9952
9511
" Run the named qrunner, which must be one of the strings returned by\n"
9953
9512
" the -l option. Optional slice:range if given, is used to assign\n"
9954
" multiple qrunner processes to a queue. range is the total number "
9956
" qrunners for this queue while slice is the number of this qrunner "
9513
" multiple qrunner processes to a queue. range is the total number of\n"
9514
" qrunners for this queue while slice is the number of this qrunner from\n"
9958
9515
" [0..range).\n"
9960
" If using the slice:range form, you better make sure that each "
9962
" for the queue is given the same range value. If slice:runner is "
9517
" If using the slice:range form, you better make sure that each qrunner\n"
9518
" for the queue is given the same range value. If slice:runner is not\n"
9964
9519
" given, then 1:1 is used.\n"
9966
" Multiple -r options may be given, in which case each qrunner will "
9521
" Multiple -r options may be given, in which case each qrunner will run\n"
9968
9522
" once in round-robin fashion. The special runner `All' is shorthand\n"
9969
9523
" for a qrunner for each listed by the -l option.\n"
9973
" Run each named qrunner exactly once through its main loop. "
9975
" each qrunner runs indefinitely, until the process receives a "
9527
" Run each named qrunner exactly once through its main loop. Otherwise,\n"
9528
" each qrunner runs indefinitely, until the process receives a SIGTERM\n"
9977
9529
" or SIGINT.\n"
10233
9776
" -w[=<yes|no>]\n"
10234
9777
" Sets whether or not to send the newly added members a welcome\n"
10235
9778
" message, overriding whatever the list's `send_welcome_msg' setting\n"
10236
" is. With -w=yes or -w, the welcome message is sent. With -w=no, "
9779
" is. With -w=yes or -w, the welcome message is sent. With -w=no, no\n"
10238
9780
" message is sent.\n"
10240
9782
" --goodbye-msg[=<yes|no>]\n"
10241
9783
" -g[=<yes|no>]\n"
10242
9784
" Sets whether or not to send the goodbye message to removed members,\n"
10243
9785
" overriding whatever the list's `send_goodbye_msg' setting is. With\n"
10244
" -g=yes or -g, the goodbye message is sent. With -g=no, no message "
9786
" -g=yes or -g, the goodbye message is sent. With -g=no, no message is\n"
10248
9789
" --digest[=<yes|no>]\n"
10249
9790
" -d[=<yes|no>]\n"
10250
9791
" Selects whether to make newly added members receive messages in\n"
10251
" digests. With -d=yes or -d, they become digest members. With -"
9792
" digests. With -d=yes or -d, they become digest members. With -d=no\n"
10253
9793
" (or if no -d option given) they are added as regular members.\n"
10255
9795
" --notifyadmin[=<yes|no>]\n"
10256
9796
" -a[=<yes|no>]\n"
10257
" Specifies whether the admin should be notified for each "
9797
" Specifies whether the admin should be notified for each subscription\n"
10259
9798
" or unsubscription. If you're adding a lot of addresses, you\n"
10260
9799
" definitely want to turn this off! With -a=yes or -a, the admin is\n"
10261
" notified. With -a=no, the admin is not notified. With no -a "
9800
" notified. With -a=no, the admin is not notified. With no -a option,\n"
10263
9801
" the default for the list is used.\n"
10265
9803
" --file <filename | ->\n"