|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: header_if_reject
From: Piotr KUCHARSKI (chopin
sgh.waw.pl)
Date: Mon Feb 07 2005 - 09:46:35 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Feb 07, 2005 at 09:25:01AM -0500, Wietse Venema wrote:
> In order to be technically correct:
> - Non-ASCII and control characters need to be sanitized.
printable(), done.
> - Long header lines need to be folded (as in: "broken up into
> multiple prepend records").
Hm, I don't think it is needed, important information is within
first 80 chars. I'll simply cut error_text at var_line_limit-20.
Unless there already exist some function to do such folding.
> In order to be architecturally correct:
> - The label/reject/warn action needs to be separated from the match
> operation (DNSBL, unknown helo name, etc.). so that we can avoid
> foo_if_reject madness.
I don't quite understand, could you explain?
p.
--
Beware of he who would deny you access to information, for in his
heart he dreams himself your master. -- Commissioner Pravin Lal
http://nerdquiz.sgh.waw.pl/ -- polska wersja quizu dla nerdów ;)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]