You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

You are here: Mozilla MailNews Functional / UI Tests > Return Receipt

Feature Test Spec: Mail and News Component

Mail and News Component: Return Receipt

Written by Peter Mock
Updated by Fenella Gor and Gary Chan

References

5.0 Seamonkey:
Test case Management System: n/a

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.

MDN is only currently being supported. Read receipts notify you that the recipient has opened your message. The recipient must have a mail program that uses the Message Disposition Notification (MDN) standard. DSN (Delivery Service Notification) is not being supported. DSN are delivery receipts that notify you that your message has arrived in the recipient's inbox on the mail server

New feature is the ability to set your MDN prefs globally or per mail account.

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. Global Preferences (Preferences|Mail&Newsgroups|Return Receipts)
      1. Default settings (Return receipts are off)
        1. Unchecked: When Sending messages, always request a return receipt
        2. When a receipt arrives - Leave it in my inbox radio button is filled
        3. Allow return receipts for some messages
      2. UI
        1. Text is clear
        2. Spelling
        3. Text format within allotted space in panel
        4. Option(s) enable/disable appropriately
        5. Options stick through exit
        6. Cancel doesn't edit options
    2. Account Preferences
      1. Default settings
        1. Set to - Use my global return receipt preferences for this account.
        2. The rest of the prefs should be unchecked/grayed out
        3. If you change the pref to - Customize return receipts for this account - it should enable all checkboxes, comboboxes, and radio buttons for that particular account. And the radio button for global setting should disappear
        4. toggling between the global/customize radio buttons should have no adverse affects
      2. UI
        1. Text is clear
        2. Spelling
        3. Text format within allotted space in panel
        4. Option(s) enable/disable appropriately
        5. Options stick through exit
        6. Cancel doesn't edit options
    3. Sender:
      1. Verify for both Global & Account based prefs, that if you check the pref 'When sending messages, always request a return receipt'
        1. A return receipt request is sent to the receiver
        2. In the compose message window, the file menu item: Options|Return Receipt is checked
        3. If the pref 'When sending messages, always request a return receipt', in the Global or Account pref, is unchecked, then the compose mesg window file menu item: Options|Return Receipt is unchecked
        4. Verify you can override either the Global or Account settings for requesting a return receipt by checking/unchecking the file menu in the compose mesg window: Options|Return Receipt
      2. Verify checking the pref for "When a Receipt arrives":
        1. Leave it in my Inbox- return receipt arrives in your inbox
        2. Move it to my Sent Mail Folder - return receipt arrives in your sent folder
          1. Subset test is if the Sent folder is Under your main account or under Local Folders (currently a bug with Sent folder under Local Folders)
      3. Compose mesg
        1. Verify Return receipts work with HTML Compose window
        2. Verify Return receipts work with Plain Text Compose window
        3. Verify Return receipts work with an attachment
      4. Type of Mail messages to send
        1. New Message (MDN is assumed to be sent to original sender)
        2. Replied
        3. Forwarded: Verify that when you forward an original message as attachment (the message contained a return receipt header) , the recipient, upon reading the message (based on their prefs), doesn't get prompted for return receipts (default). Check the 2 cases below:
          1. In the compose window, check Options | Return Receipt and forward the message. Verify that when the recipient selects the message, and if they acknowledge and send the receipt, that the sender (you) receives a copy of the Return Receipt notification.
          2. In the compose window, make sure Options | Return Receipt is unchecked and forward the message. Verify that when the recipient selects the message, they don't receive any prompt to acknowledge, and nobody receives and Return Receipt notifications.
      5. Verify that you can override any Global Return receipt pref settings when you do Customize return receipts for this account
      6. 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.
    4. 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. Verify for Global prefs, Receiver selects the options from Preferences|Mail&Newsgroups|Return Receipt and verifies that each of the options works according to your selections.
        1. "When I receive a request for a return receipt "
          1. Never send a receipt
          2. Allow 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 (If the sender is outside my domain [ex. netscape.com])
            • Never Send
            • Automatically Send
            • Ask me
          3. Send a return receipt (in all other cases)
            • Never Send
            • Automatically Send
            • Ask me
        3. When you have received a message with a Return Receipt and you click on it
          1. Verify, if you have pref to "ask me", that the confirmation window
            • "The sender of this message has asked to be notified when you read this message. Do you wish to notify this sender?"
            • text is clear and spelled correctly
            • click "ok button" sends the return receipt
            • click "cancel button" doesn't send a return receipt back
      3. Verify for Account based prefs, Receiver selects the options from Mail &Newsgroup Account settings|Return Receipt and verifies that each of the options works according to your selections.
        1. "When I receive a request for a return receipt "
          1. Never send a receipt
          2. Allow 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 (If the sender is outside my domain [ex. netscape.com])
            • Never Send
            • Automatically Send
            • Ask me
          3. Send a return receipt (in all other cases)
            • Never Send
            • Automatically Send
            • Ask me
        3. When you have received a message with a Return Receipt and you click on it
          1. Verify, if you have pref to "ask me", that the confirmation window
            • "The sender of this message has asked to be notified when you read this message. "Do you wish to notify this sender?"
            • text is clear and spelled correctly
            • click "ok button" sends the return receipt
            • click "cancel button" doesn't send a return receipt back
        4. Verify that you can override any Global return receipt pref settings when you do 'Customize return receipts for this account'.
      4. 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
      5. Receive a message with a Return Receipt, in the 3 pane window, with the message pane closed (3rd pane)
        1. verify that you will not be prompted for a return receipt if you click on the message in the thread pane
        2. verify you will be prompted for a return receipt if you, double click on the message (while mesg pane still closed) and open it in a new window
        3. verify you will be prompted for a return receipt if you, reopen the message pane, and click on the message in the thread pane
    5. Verifying MDN message:
      1. Verify that when the Return Receipt message is sent back to the sender
        1. Subject line contains: Return Receipt (Displayed) - <original subject line>
        2. Verify both in the message and the message source the following:
          1. The first component of the multipart/report contains a human-readable explanation of the MDN. The general disclaimer that the mesg was displayed on the recipient's computer but not necessarily understood
          2. The second component of the multipart/report is of content-type message/disposition-notification. This includes user agent string and the following: "Disposition: manual-action/MDN-sent-manually; displayed"
          3. The third component of the multipart/report would be the original message or portion of the original message. In our case, the original header of the message. Also included is the "Disposition-Notification-To:" header.
        3. There are 2 additional attachments in the Return Receipt message:
          1. MDNPart2.txt - 2nd component of the Return Receipt
          2. MDNPart3.txt - 3rd component of the Return Receipt
          3. Note: Known bug that clicking on those attachments doesn't result in them opening.
      2. 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
      3. Security
        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
    6. Different Mail accounts
      1. Test both sending and receiving a return receipt with/from
        1. imap mail account
        2. pop mail account
    7. Filters
      1. Verify Return receipts work for filtered messages
    8. Mail Lists/Alias
      1. Verify Return Receipts works for
        1. Mail lists in your addressbook
        2. Aliases
  2. Core MDN feature for News:
    1. Setting for requesting for a Return Receipt (from Edit|Preferences|Return Receipt):
      1. DSN (A delivery receipt from the mail server, previous return receipt feature)
      2. MDN (A read receipt, notify me when recipients 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 delivery 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 4.x builds
    2. Testing 3rd party application that support MDN
      1. Eudora 4.0
      2. Outlook