ezmlm-limit(1) ezmlm-limit(1) NNAAMMEE ezmlm-limit - Limits traffic to list SSYYNNOOPPSSIISS eezzmmllmm--lliimmiitt [ --ff _f_i_l_e ][ --ddDDFF ][ --tt _s_e_c_s ][ --nn _m_s_g_s ] _d_i_r eezzmmllmm--lliimmiitt 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. eezzmmllmm--lliimmiitt reads _d_i_r//llooooppnnuumm. If it does not exist or contains a time stamp more than _s_e_c_s seconds old, it is updated. If it exists, con- tains 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//llooooppnnuumm was created, eezzmmllmm--lliimmiitt creates _d_i_r//mmooddppoosstt. For lists set up with eezzmmllmm--ssttoorree((11)) this results in future messages being moderated. As long as _d_i_r//mmooddppoosstt does not exist, eezzmmllmm--ssttoorree((11)) will simply for- ward the message to eezzmmllmm--sseenndd((11)).. Once _d_i_r//mmooddppoosstt exists, messages will be queued for moderation. Thus, in case of error (such as miscon- figured 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//mmooddppoosstt already exists, eezzmmllmm--lliimmiitt will not take any action. Resetting the list requires manual removal of _d_i_r//mmooddppoosstt._Q_u_e_u_e_dmes- sages_c_a_nbe_m_a_n_a_g_e_dwith_r_e_g_u_l_a_rmoderation or approved in bulk with eezzmmllmm-- aacccceepptt((11)). eezzmmllmm--lliimmiitt 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 sub- scribers. OOPPTTIIOONNSS --dd 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. --DD (Default.) Make the list moderated once excess traffic is detected. This requires the list to be configured up with eezzmmllmm-- ssttoorree((11)) rather than eezzmmllmm--sseenndd((11)), which is easiest done by first creating a message moderated list, then removing _d_i_r//mmoodd-- ppoosstt. --nn _m_s_g_s Trigger after _m_s_g_s messages (default 30). --ff _f_i_l_e Instead of _d_i_r//llooooppnnuumm use _f_i_l_e as the time stamp. This allows the use of multiple instances of eezzmmllmm--lliimmiitt 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 rela- tive, this is relative to _d_i_r. --FF (Default.) Use _d_i_r//llooooppnnuumm as the time stamp. --tt _s_e_c_s Check the number of messages within period of _s_e_c_s seconds (default 3600 seconds). SSEEEE AALLSSOO ezmlm-accept(1), ezmlm-make(1), ezmlm-send(1), ezmlm-store(1), ezmlm(5) ezmlm-limit(1)