Feature Test Spec

Originally document was written by: Peter Mock for 4.5 (Nova)
Modified by: Fenella Gor for 5.0 (Seamonkey)

References:
5.0 Seamonkey:
Test case Management Syetem: n/a
Approx. number of test cases: 50

This feature designed for Mail messages only and not designed for News messages. We can loosely describe MDN as a read receipt but this feature contain additional functionality.

Description of feature from RFC: The MDN can be used to notify the sender of a message of any of several conditions that may occur after successful delivery, such as display of the message contents, printing of the message, deletion (without display) of the message, or the recipient's refusal to provide MDNs.

The difference between a Return Receipt in Communicator 4.0 and a MDN in 5.0 is that a Return Receipt is generated from the Messenger Server and a MDN is generated from the client. A MDN is a short header returned and the original message is not attached to the MDN replied. The sender can "request" that a MDN message to be returned from the recipient. But the recipients has the option to send or ignore sending a MDN back to the sender.

Notation: UA stands for User Agent
MDN stands for Message Disposition Notification

Pre setup information: Majority of tests will be performed in the Inbox folder.

1. Core MDN feature for Mails:
1. Sender:
1. Compose windows (Initiated from Option|Return Receipt)
1. HTML Compose window
2. Plain Text Compose window
2. Setting for requesting a Return Receipt: ( from Edit|Preferences|Return Receipt). Verify that each of the following works according to your selections.
1. "If I request a receipt when sending a message,I want:"
1. DSN (A delevery receipt from the mail server, previous return receipt feature)
2. MDN (A read receipt, notify me when receipients display the message)
3. Both DSN and MDN
2. "When a receipt arrives: "
1. Leave in Inbox
2. Move it to my Sent Mail Folder
3. Type of Mail messages to send
1. New Message (MDN is assumed to be sent to original sender)
2. Replied (MDN is not sent if receiver replied the mail message with message pane closed)
3. Forward (MDN is not sent if receiver replied the mail message with message pane closed)
4. Sender requesting a MDN has the following characteristics
1. Message ID is different from original message.
2. MDN is NOT encrypted if the original message was encrypted.
3. A MDN is sent even if you send yourself a message
4. One MDN is sent per message
5. Sender will receive a MDN from each platform where the receiver reads the message.
2. Receiver:
1. Receiver: verify that the type of message sent is correctly displayed in the Returned Receipt.
1. HTML message
2. Plain Text message
3. Both HTML & Plain Text message
2. Receiver selects the options from Edit|Preferences|Return Receipt and verifies that each of the options works according to your selections.
1. "When I receive a message and the sender requested a receipt (MDN)"
1. Never return a receipt
2. Customize - Return receipts for some messages
2. Customizing return receipts
1. Send a return receipt (if I'm not in the To or CC list of the message (such as when I am in the mailing list alias only)):
• Never Send
• Automatically Send
• Ask me
2. Send a return receipt (when message comes from outside the domain netscape.com)
• Never Send
• Automatically Send
• Ask me
3. Send a return receipt in all cases
• Never Send
• Automatically Send
• Ask me
3. When the I have selected "Ask me" a receipt dialog should appear, verify the button works:
1. Functions allowed in the dialog (OK, Cancel)
3. When receiver receives the message, a MDN message will trigger a MDN to be sent to the sender when:
1. Receiver reads the message with the Message pane open
4. Verify that No MDN is generated when a new mail message is stored into the user's INBOX but is not read or processed such as:
1. copy/move the message
2. delete the message
3. filtere the message
3. Verifying MDN message:
1. Use the View|Page Source to verify a MDN message the correct message/disposition-notification content-type, Original-Recipient field, and error state.
1. Type of MDN ( The type depends on what the user did with the message.)
1. Displayed (The message has been displayed by the UA to someone reading the recipient's mailbox. There is no guarantee that the content has been read or understood.)
2. Dispatched (The message has been sent somewhere manner (e.g., printed, faxed, forwarded) without being displayed to the user. The user may or may not see the message later.)
3. Processed (The message has been processed in some manner (i.e., by some sort of rules or server) without being displayed to the user. The user may or may not see the message later, or there may not even be a human user associated with the mailbox.)
4. Deleted (The message has been deleted. The recipient may or may not have seen the message. The recipient might "undelete" the message at a later time and read the message.)
5. Denied (The recipient does not wish the sender to be informed of the message's disposition. A UA may also silently ignore message disposition requests in this situation.)
6. Failed (A failure occurred that prevented the proper generation of an MDN.)
2. MDN disposition modes
1. Manual-action/MDN-sent-manually
2. Automatic action/MDN-sent-automatically
2. Security (Not supported??)
1. Requesting for MDN for a signed message
2. Requesting for MDN for a encrypted message
3. Requesting for MDN for a signed and encrypted message


2. Core MDN feature for News:
1. Setting for requesting for a Return Receipt (from Edit|Preferences|Return Receipt):
1. DSN (A delevery receipt from the mail server, previous return receipt feature)
2. MDN (A read receipt, notify me when receipients display the message)
3. Both DSN and MDN
2. And verify that:
1. you will expect a return receipt (DSN) from the server
2. you will not expect a MDN from the client


3. Core DSN feature both Mail and News:
1. Select each of the following options from the Edit|Preferences|Return Receipt and send out a mail/news message:
1. DSN (A delevery receipt from the mail server, previous return receipt feature)
2. Both DSN and MDN
2. Verifying DSN message
1. You will receive a Delivery receipt from the receiving server. (eg: Mail Administrator<Postmaster@dredd.mcom.com)> with the following message: This Message was delivered to the following recipients: Mailbox userid
2. Check for server MTA(message transfer agent) information, sender and receiver id as well as content type.


4. Inter Operability
1. Cross platform testing with other Communicator 5.0 platforms
2. Testing 3rd party application that support MDN
1. Eudora 4.0