Hi Aaron,
--On January 21, 2009 7:37:46 AM -0800 Aaron Stone <aaron(_at_)serendipity(_dot_)cx>
wrote:
Or when you upgrade a server, the server ought to have a "sieve lint"
tool that can scan all existing scripts (as would happen during an
upload a script) and report problems that the admin can take action on.
I don't think that's realistic -- some extensions can be implemented
entirely by the interpreter, with no need for any other part of the mail
system to get involved. So if the interpreter (a shared library, let's
say) is upgraded, there's no good way to inform the mail system what
changed and to run a lint process.
Well the system administrator better read the release notes and those
better say that the interpreter was changed significantly and that all
existing scripts should be checked. An admin blindly doing upgrades without
checking release notes/instructions is asking for trouble...
--
Cyrus Daboo