| Author |
|
naoto
Newbie
Joined: 17 October 2011
Location: Italy
Online Status: Offline
Posts: 1
|
| Posted: 17 October 2011 at 8:48am | IP Logged
|
|
|
Hi,
Here's my issue: I need to recognize in some way incoming read message confirmation of previous sent mails.
In other words, if the receiving server allows DSN, with ConfirmRead Property set, I need to filter confirmation messages.
I noticed that from Outlook confirmation, I get a DSN report when parsing the confirmation massage by DeliveryStatusParser with a "deleted" in erased messages (no confirmation allowed from the user) and a "displayed" in effective read confirmation.
Otherwise, from other clients (e.g. web clients) I got nothing and incoming confirmation messages not even pass the DeliveryStatusParser (result of process method = nothing/null).
Hoping I was clear enough, there is an effective way of parsing read/unread confirmation message (obtained with the ConfirmRead property), either customizing the Bounce Definition Database (all.xml) or parsing the Header of the message itself?
Thanks.
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6168
|
| Posted: 18 October 2011 at 12:37am | IP Logged
|
|
|
BounceMail components allows for detecting various types of DSN messages, and you'll need to check both
Common and Detailed properties of RecipientStatus - those return CommonType and DetailedType respectively. In most cases, you'll need to check CommonType and if it returns Receipt value, check DetailedType for Delivered / Read values. Of course, the message should contain the valid DSN, identification is not guaranteed otherwise.
Hope this helps!
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: Parsing read/unread confirmation messages
Privacy policy |
Refund policy