(See Powerpoint presentation for more information.)
Please use vendoraccount/vendortesting123 as the user/pwd for authenticating to the NIST James instance.
| Email address | Test Cases | TO / FROM NIST | Description |
|---|---|---|---|
| wellformed1@hostname | 1-8, 18, 19 | TO | Successful message sent from SUT to James. |
| wellformed2@hostname | 14 | TO | Successful message sent from SUT to James on a TLS connection. |
| wellformed3@hostname | 9, 16, 20, 21, 22, 23 | FROM | Successful message sent from TTT to SUT. |
| badcommands4@hostname | 10, 11, 12, 13, 17 | FROM | TTT simulating bad commands for SMTP. |
| processedonly5@hostname | MU2-18, MU2-27, MU2-47 | TO | Provides regular processed MDN's when messages received. (No Dispatched MDN) |
| processeddispatched6@hostname | MU2-21, MU2-22, MU2-29 | TO | Provides both Processed and Dispatched MDN's when messages received. |
| processdelayeddispatch7@hostname | MU2-28 | TO | Provides Processed when message received, dispatched after 1 hour 5 minutes after message received. |
| nomdn8@hostname | MU2-4, MU2-26 | TO | No MDNs are provided. |
| noaddressfailure9@hostname | MU2-18, MU2-47 | TO | Non-existent address (Need to send Failure MDN) |
| nonpublishedcert10@hostname | MU2-3, MU2-25 | TO/FROM | email message to a valid address but the recipient’s certificates are not published. |
| untrustedhisp11@hostname | MU2-2, MU2-24 | TO/FROM | email message to a valid address but the receiving HISP is not trusted. |
| badaddress12@hostname | MU2-1, MU2-23 | TO/FROM | bad address (sent to the HISP which is unable to deliver the message) |
| no #13 | N/A | N/A | N/A |
| wellformed14@hostname | MU2-45, MU2-46 | TO | Check of unique IDs and Disposition-Notifications-Options Header |
| failure15@hostname | MU2-1, MU2-2, MU2-3, MU2-4 | TO | Failure Responses send to Address15 one for each message sent from Java Client |
("hostname" dependent on which machine ends up hosting James server.)