|
NAMEezmlm-limit - Limits traffic to listSYNOPSISezmlm-limit [ -f file ][ -dDF ][ -t secs ][ -n msgs ] direzmlm-limit is intended to limit traffic to a list in case an outside source sends excessive messages. Traffic is limited by converting the list to a message moderated list, or by deferring messages. ezmlm-limit reads dir/loopnum. If it does not exist or contains a time stamp more than secs seconds old, it is updated. If it exists, contains a time stamp less than secs seconds old, and msgs messages or more have passed since dir/loopnum was created, ezmlm-limit creates dir/modpost. For lists set up with ezmlm-store(1) this results in future messages being moderated. As long as dir/modpost does not exist, ezmlm-store(1) will simply forward the message to ezmlm-send(1). Once dir/modpost exists, messages will be queued for moderation. Thus, in case of error (such as misconfigured auto responders) subscribers are spared messages in excess of the limit. However, no messages are lost, since the moderator(s) can (selectively) approve queued messages. If dir/modpost already exists, ezmlm-limit will not take any action. Resetting the list requires manual removal of dir/modpost. Queued messages can be managed with regular moderation or approved in bulk with ezmlm-accept(1). ezmlm-limit is not required for normal lists, since qmail and ezmlm loop detection prevent problems caused by regular bounces. However, it affords some protection against malice, and severely misconfigured subscribers. OPTIONS
SEE ALSOezmlm-accept(1), ezmlm-make(1), ezmlm-send(1), ezmlm-store(1), ezmlm(5) Visit the GSP FreeBSD Man Page Interface. |