|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Matthias Andree (ma
dt.e-technik.uni-dortmund.de)Date: Sun Feb 11 2001 - 06:48:46 CST
wietse
porcupine.org (Wietse Venema) writes:
> The problem was: an alias expands into multiple addresses; one of
> them needs to be deferred; all addresses receive another copy of
> the mail.
>
> There is no need to drag into the discussion aliases that
> invoke other aliases.
> Pushing failed recipients to the defer queue means writing TODO
> destinations to queue file. This violates requirement number 4.
Now, if you could push
- only *mail* recipients (not files, not commands, no includes) as
"todo" on the queue file
- at most a configurable amount (like 50) of "todo" recipients to the
queue file
and resort to log the ORIGINAL (left-hand side of alias) file if at
least one of these two requirements is not met, would this meet the
"security" (#4) and "finite amount of storage" requirements? I feel it
would prevent the dupes in some cases at least, lowering the impact of
the bug.
-- Matthias Andree
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]