OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: SOLUTION: Too many open files error when sending to large list
From: Michael Ju. Tokarev (mjttls.msk.ru)
Date: Sat Aug 26 2000 - 18:29:51 CDT

Lutz Jaenicke wrote:
>
[]
> So Walter's clean solution would be to also add "owner-" aliases for the
> sub-lists.
[]
> Due to the possibility of .forward files with an uncontroled number of
> entries, there cannot be a fixed limit that will make everybody happy.
> So, it is a design decision, a compromise to be made.
>
> Probably, the problem could be avoided by re-queuing every alias expansion,
> but then we could not detect alias or .forward loops, which would state
> a far more significant problem...

Another additional "problem"(s) to this list. I noticied that
each remote address from .forward creates separate queue file, so
that after "all" list was processed, queue looks like

  from owner-all to user1remote1
  from owner-all to user2remote2
   etc

where each pair (note the owner- part also) is in separate
mail. And it tooks some significant time to complete all
this queue on my dial-up home machine, sending the same
message 333 times to the same server at work! (I created
similar .forward files with one local and one remote address
for each of 333 "users").

I want to look to Don Knuth's "programming bibles" about
algorithms that can be used here. Not a trivial task!..

Regards,
 Michael.