From: Lionel B. <lio...@bo...> - 2005-04-29 08:12:44
|
Michel Bouissou wrote the following on 29.04.2005 08:05 : >>Now the question for me is, if for a site like us, the use of a table >>connect_awl as the first awl would not be better (connect_awl = table with >>triple ip, originator, recipient). >> >>>From this table the from_awl would be filled by a propagation algorithm >> >> > >What would be the goal ? Have a shorter entry lifetime in connect_awl than in >from_awl ? > > No, the goal is to apply greylisting if the rcpt changes until we see enough mails from the sender to different rcpts to add him/her to the from_awl. Consider this one more stage in the current "greylist -> awl1 -> awl2" process whose purpose is to avoid nearly random but heavy spam trafic to reach the from_awl which allows more damage to be done than the would-be connect_awl. > > >>similar to the one from from_awl to domain_awl. At the end most of the >>entries in the from_awl would be the originators of mailinglists. All >>other entries would stay in connect_awl. >> >> > >But I'm not sure it would be a good idea. Most users won't mind if >mailing-lists emails may be delayed for a while, but on the contrary, most >users find extremely important that mail they receive from "real humans" >should not be delayed unless necessary, most of the times. >Users will tell that even if they receveive messages from Mr. Jones only once >a week or so, they definitely don't want Mr. Jones' mail to be delayed each >and everytime. > > The idea is that Mr. Jones' mail will be delayed only for recipients he didn't contact earlier until he successfully sent mails to <n> different recipients. Lionel. |