User Commands ezmlm-limit(1) NNNNAAAAMMMMEEEE ezmlm-limit - Limits traffic to list SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt [ ----ffff _f_i_l_e ][ ----ddddDDDDFFFF ][ -tttt _s_e_c_s ][ ----nnnn _m_s_g_s ] _d_i_r eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt is intended to limit traffic to a list in case an outside source sends excessive messages. Traffic is lim- ited by converting the list to a message moderated list, or by deferring messages. eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt reads _d_i_r////llllooooooooppppnnnnuuuummmm. If it does not exist or con- tains a time stamp more than _s_e_c_s seconds old, it is updated. If it exists, contains a time stamp less than _s_e_c_s seconds old, and _m_s_g_s messages or more have passed since _d_i_r////llllooooooooppppnnnnuuuummmm was created, eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt creates _d_i_r////mmmmooooddddppppoooosssstttt. For lists set up with eeeezzzzmmmmllllmmmm----ssssttttoooorrrreeee((((1111)))) this results in future messages being moderated. As long as _d_i_r////mmmmooooddddppppoooosssstttt does not exist, eeeezzzzmmmmllllmmmm----ssssttttoooorrrreeee((((1111)))) will simply forward the message to eeeezzzzmmmmllllmmmm----sssseeeennnndddd((((1111)))).... Once _d_i_r////mmmmooooddddppppoooosssstttt 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 _d_i_r////mmmmooooddddppppoooosssstttt already exists, eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt will not take any action. Resetting the list requires manual removal of _d_i_r////mmmmooooddddppppoooosssstttt._Q_u_e_u_e_dmessages_c_a_nbe or approved in bulk with eeeezzzzmmmmllllmmmm----aaaacccccccceeeepppptttt((((1111)))). eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt 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. OOOOPPPPTTTTIIIIOOOONNNNSSSS -dddd Defer excess traffic. Excess messages are deferred and qmail will re-deliver. As a consequence, traffic will be throttled to the maximum allowed. Due to qmail delivery back-off, messages may not be disseminated in the order received. If traffic is continuously above or close to the limit, some messages may be delayed for a long time or even bounced. -DDDD (Default.) Make the list moderated once excess traffic is detected. This requires the list to be configured up with eeeezzzzmmmmllllmmmm----ssssttttoooorrrreeee((((1111)))) rather than eeeezzzzmmmmllllmmmm----sssseeeennnndddd((((1111)))), which is SunOS 5.11 Last change: 1 User Commands ezmlm-limit(1) easiest done by first creating a message moderated list, then removing _d_i_r////mmmmooooddddppppoooosssstttt. -nnnn _m_s_g_s Trigger after _m_s_g_s messages (default 30). -ffff _f_i_l_e Instead of _d_i_r////llllooooooooppppnnnnuuuummmm use _f_i_l_e as the time stamp. This allows the use of multiple instances of eeeezzzzmmmmllllmmmm----lllliiiimmmmiiiitttt for the same list. For instance, you may allow 60 messages per hour with one instance and 150 messages per day with another. If _f_i_l_e is relative, this is relative to _d_i_r. -FFFF (Default.) Use _d_i_r////llllooooooooppppnnnnuuuummmm as the time stamp. -tttt _s_e_c_s Check the number of messages within period of _s_e_c_s seconds (default 3600 seconds). SSSSEEEEEEEE AAAALLLLSSSSOOOO ezmlm-accept(1), ezmlm-make(1), ezmlm-send(1), ezmlm- store(1), ezmlm(5) SunOS 5.11 Last change: 2