http://atelier.adullact.org/plugins/mediawiki/wiki/milimail/index.php?action=history&feed=atom&title=Notification_Viewer_Technical_Documentation 2026-05-02T17:44:10Z Historique pour cette page sur le wiki MediaWiki 1.27.4 http://atelier.adullact.org/plugins/mediawiki/wiki/milimail/index.php?title=Notification_Viewer_Technical_Documentation&diff=250&oldid=prev 2010-09-03T14:42:24Z

<p>Page créée avec « {{lang|Notification Viewer Technical Documentation|Notification Viewer Technical Documentation/fr}} &gt; <a href="/plugins/mediawiki/wiki/milimail/index.php/Documentation" title="Documentation">Documentation</a> &gt; <a href="/plugins/mediawiki/wiki/milimail/index.php/Notification_Viewer" title="Notification Viewer">Add-on: Notification Viewer</a> … »</p> <p><b>Nouvelle page</b></p><div>{{lang|Notification Viewer Technical Documentation|Notification Viewer Technical Documentation/fr}}<br /> &gt; [[Documentation]] &gt; [[Notification_Viewer|Add-on: Notification Viewer]] &gt; [[Notification_Viewer_Technical_Documentation|Technical Documentation]]<br /> <br /> <br /> == Notification data management ==<br /> <br /> When a message is sent, if delivery notifications have been requested, notification data are stored in a local Sqlite database ''notifications'' created by the add-on.<br /> Each message with notification requests is identified in the database with its unique ''Message-ID'' header.<br /> <br /> When a notification is received, its data are added to the ''notifications'' database in original message's entry.<br /> Original message is identified by different ways depending on the notification type:<br /> * MDN: with the ''Original-Message-ID'' header of the notification;<br /> * DSN: with the ''Message-ID'' header in the copy of the headers of the original message attached to the notification.<br /> <br /> [[Image:MILIMAIL_Specifications_Corrélation_des_avis_v08_schéma_EN_v1.png]]<br /> <br /> ''Notifications'' Sqlite database is used to store notification data in a persistent way when messages are moved from/to IMAP folders (which doesn't happen with data stored in Thunderbird's internal message databases).<br /> Sqlite database is also useful to display consistent information when messages are duplicated.<br /> <br /> Thunderbird's internal message databases are used to store an exported view of Sqlite data to be displayed in the interface.<br /> <br /> == Notification requests ==<br /> <br /> When a message is sent, DSN request is transmitted at SMTP level. Notification request info is not stored in the message and therefore the add-on is not able to identify a DSN request.<br /> <br /> It is necessary to add a ''X‑DSN: yes'' header in the message in order to identify the request.<br /> Only ''success'' DSN requests are taken into account, because the purpose of the add-on is to count received notifications (obviously, all types of DSN responses are identified and displayed).<br /> <br /> In order to identify MDN requests, the header ''Disposition‑Notification‑To'' is already available in sent message.<br /> <br /> == Delivery delay ==<br /> <br /> A delivery delay can be set up in minutes for all messages with a DSN ''success'' request.<br /> <br /> A background task checks if elapsed time since sending time has reached maximum delivery delay for messages whose all DSN responses have not been received.<br /> A visual information for expired messages is displayed in message list.</div>

Rfairise