[exim-cvs] cvs commit: exim/exim-doc/doc-txt NewStuff

Página Inicial
Delete this message
Reply to this message
Autor: Tony Finch
Data:  
Para: exim-cvs
Assunto: [exim-cvs] cvs commit: exim/exim-doc/doc-txt NewStuff
fanf2 2005/09/22 13:03:36 BST

  Modified files:
    exim-doc/doc-txt     NewStuff 
  Log:
  Explain in the ratelimit docs how to work out the over-limit recovery time.


  Revision  Changes    Path
  1.74      +6 -1      exim/exim-doc/doc-txt/NewStuff


  Index: NewStuff
  ===================================================================
  RCS file: /home/cvs/exim/exim-doc/doc-txt/NewStuff,v
  retrieving revision 1.73
  retrieving revision 1.74
  diff -u -u -r1.73 -r1.74
  --- NewStuff    19 Sep 2005 14:01:51 -0000    1.73
  +++ NewStuff    22 Sep 2005 12:03:36 -0000    1.74
  @@ -1,4 +1,4 @@
  -$Cambridge: exim/exim-doc/doc-txt/NewStuff,v 1.73 2005/09/19 14:01:51 ph10 Exp $
  +$Cambridge: exim/exim-doc/doc-txt/NewStuff,v 1.74 2005/09/22 12:03:36 fanf2 Exp $


   New Features in Exim
   --------------------
  @@ -353,7 +353,12 @@
         updated. The effect of this is that Exim measures the client's average
         rate of attempts to send email, which can be much higher than the
         maximum. If the client is over the limit it will be subjected to
  -      counter-measures until it slows down below the maximum rate.
  +      counter-measures until it slows down below the maximum rate. The
  +      smoothing period determines the time it takes for a high sending rate
  +      to decay exponentially to 37% of its peak value, which means that you
  +      can work out the time (the number of smoothing periods) that a client
  +      is subjected to counter-measures after an over-limit burst with the
  +      formula ln(peakrate/maxrate).


         The leaky option means that the client's recorded rate is not updated
         if it is above the limit. The effect of this is that Exim measures the