> I think we should have some replay scripts or test to
> verify smtp auth extension, size extension and open
> relay test.
SMTP AUTH, SIZE extension and other RFC related tests should be labeled with
the RFC section being tested and the expected dialog. So if someone says
that James isn't properly implementing RFC XXXX, section aa.bb.cc, we can
verify the RFC against the test script generated from the RFC, and James'
behavior. We should not be building RFC test scripts by recording them.
The only scripts that should be build by recording them are those expressing
non-standard "real-world" behavior, where responding the same way as the
recorded session is necessary.
> It would be cool to point users to a test in response to questions like:
> Does James support SMTP Auth?
THAT script should be written from the RFC, whereas
> Is my James server configured to be open relay?
is really a suite of tests that can be adopted from real-world Open Relay
testers. Keep in mind that such test scripts can't verify anything with the
current approach. They can affect the SMTP protocol, but James rejects
relaying attempts asynchronously in the processor chain. We'd need another
means to verify that James hasn't relayed the e-mail. There are several
options for that step.
--- Noel
--
To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
