Re: [Sqlgrey-users] Re: Values for throttling

[Michael S. <Mic...@lr...>]

On Sun, 12 Jun 2005, Michel Bouissou wrote:

> If you use the algorithm you propose, let's say with a domain_group_level of
> 10 and a throttling threshold of 20, and you have one MTA that sends mail for
> ONLY one domain, then this MTA will make it to domain_awl (and have only one
> entry there even though this may correspond to thousands of different
> senders), but with your algorithm this will never be enough and this MTA will
> still remain "throttleable".

If the MTA sends ONLY emails with originators from ONE domain, then there
will be en entry in domain_awl and ALL emails will immediately accepted.
There is noch chance for an email to be listed in connect and threfore
throttling will never occur.

>
> So I still think that we shouldn't mix a count of entries in from_awl and
> domain_awl, as they don't have the same meaning, and should rather use my
> algorithm : Stop throttling for an IP if it has at least 1 entry in
> domain_awl, or >= throttling threshold in from_awl.

I want to be able to specify that more than one entry in domain_awl
should be used. To have a simple configuration I thought about linking
entries in domain_awl and from_awl togther. But if you say these entries
cannot be linked together, we have to switch to explicit values. This
means we need a vector of values, where each value corresponds to the
number of entries in an awl which would prove that we trust a MTA (I call
these MTAs wellbehaved):

connect_src_throttle = (1, 10) # (value for domain_awl, value for from_awl)

Since I want to use a table for triples too, I would need a vectr with 3
elements.

>
>
> > BTW, we use the algorithm, which checks for the IP address in domain_awl
> > and from_awl, for the opposite direction and call it fast propagation.
> > That means, if an IP address is from a well behaved MTA, then we accept
> > the triple immediately. This eliminates the delay for forwarded emails,
> > because most of the time a wellbehaved MTA has an entry in domain_awl. But
> > this is done with the cost of polluting the from_awl, therefore we want
> > the additional table for forwarding.
>
> Hmmm... I'm not sure that I completely understand what you mean here...
>
>

Ok, which part can I describe better:

- how fast propagation works
- or what the relationship is between forwarding and fast propagation


Michael Storz
-------------------------------------------------
Leibniz-Rechenzentrum   !   <mailto:St...@lr...>
Barer Str. 21           !   Fax: +49 89 2809460
80333 Muenchen, Germany !   Tel: +49 89 289-28840