On Tue, Jul 11, 2006 at 06:08:47PM +0200, Kjetil Torgrim Homme wrote:
possibly not, but how do you suggest the server should handle it?
flatly ignore all tests which require unavailable information? if so,
if a user writes a script with lots of explicit tests and an
unconditional "reject" at the end, you get disaster.
one other option is to make it explicit with different scripts for the
two situations.
Or.. a good use for that "mode" variable, so the script can tell the
circumstance under which it is being executed.
Or.. a draft specifying how 'header' et al (anything requiring the
message to be present) should behave if the message isn't yet there.
Or.. a test that will see if the message is available for examination.
(e.g. via some read-only variable.)
But really, a problem is that support for RCPT-TO (and other) scripting
probably needs more fleshing out anyway, since RCPT-TO wants to see more
states and more information returned from a script than simply "accept"
or "reject." To me, this suggests having a separate scripts, or at
least script fragments, for each mode.
mm