ProposalUsingMailDSNs

[Development]

Using E-Mail Delivery Status Notifications

Examples

In Sent Notification

Message-ID: <20141126152642.Horde.ZUvk5y1O5grVbHRxmqXwmg1@horde.cis.example.com>
From: Adam Tauno Williams <adam@example.com>
To: cisstaff <cisstaff@example.com>
Subject: FYI, Hedera [and other] workflow diagram/documentation updated
Disposition-Notification-To: Adam Tauno Williams <adam@example.com>

The received notification

Return-Path: <cleslie@example.com>
Received: from kyack.example.com (KYACK.example.com [192.168.1.8])
    by imap.example.com (Cyrus v2.4.12-Invoca-RPM-2.4.12-2) with LMTPA;
    Wed, 26 Nov 2014 15:30:59 -0500
X-Sieve: CMU Sieve 2.4
Received: from [192.168.1.172] (unknown [192.168.1.172])
    (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
    (No client certificate requested)
    (Authenticated sender: cleslie)
    by kyack.example.com (Postfix) with ESMTP id A99D420014
    for <adam@example.com>; Wed, 26 Nov 2014 15:30:59 -0500 (EST)
Content-Type: multipart/report; report-type="disposition-notification"; boundary="=-lofXS7/srtrs8IaHlEKq"
Subject: Delivery Notification for "FYI, Hedera [and other] workflow diagram/documentation updated"
From: cleslie@example.com
To: Adam Tauno Williams <adam@example.com>
Auto-Submitted: auto-replied
Date: Wed, 26 Nov 2014 15:30:59 -0500
Message-ID: <1417033859.2190.1.camel@restituere.BACKBONE>
Mime-Version: 1.0
X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20)

--=-lofXS7/srtrs8IaHlEKq
Content-Type: text/plain; format="flowed"; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Your message to cleslie@example.com about "FYI, Hedera [and other] workflow diagram/documentation updated" on Wed, 26 Nov 2014 15:26:42 -0500 has been read.
--=-lofXS7/srtrs8IaHlEKq
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit

Reporting-UA: restituere.BACKBONE; Evolution 3.10.4 (3.10.4-4.fc20) 
Final-Recipient: rfc822; cleslie@example.com
Original-Message-ID: <20141126152642.Horde.ZUvk5y1O5grVbHRxmqXwmg1@horde.cis.example.com>
Disposition: manual-action/MDN-sent-manually;displayed

--=-lofXS7/srtrs8IaHlEKq--

Notes

So you get back the message id of the original message and a recipient. Recipients would have to be resolved back into a user - possibly from a list of user's you expect to have gotten a notification - and then appended to the list of people of people who have acknowledged the notification.