|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: filter framework (long-ish)
Victor.Duchovni
morganstanley.com
Date: Thu May 01 2003 - 11:21:12 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 30 Apr 2003, Wietse Venema wrote:
> > qmgr looks up "filter rules" and overrides the transport:next-hop if required
>
> Therefore, qmgr should also ask the TRIVIAL-REWRITE DAEMON to do this.
>
If anything, I would propose a more radically streamlined queue manager,
where the trivial-rewrite lookups are performed as a last step in
"cleanup", leaving the queue manager to just schedule delivery agents,
without any need to perform external lookups of any sort.
If per-user content filtering amounted to consulting an alternate
transport table in trivial-rewrite (based on a flag in the queue manager
resolve request), I have no objections as the mechanism would have the
same queue manager latency as the current Postfix. This could again be
implemented in cleanup as above, with cleanup requesting either the
regular or the filter transport table.
--
Viktor.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]