search

ronysebastian / nhin-d

Automatically exported from code.google.com/p/nhin-d
0 stars 0 forks source link

Disposition-Notification-To header not handled correctly (.NET RI) #222

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
If requesting notification with the following:

Disposition-Notification-Options: 
X-DIRECT-FINAL-DESTINATION-DELIVERY=optional,true

Then a Disposition-Notification-To must be included.  While the the RI does not 
create the Disposition-Notification-To value it is up to the client to add this 
header when requesting notifications.

Currently the MDN processor does not respect the Disposition-Notification-To 
header.  It always uses the sender as the notification address.

Original issue reported on code.google.com by joeshook@gmail.com on 23 Jul 2013 at 11:31

GoogleCodeExporter commented 9 years ago 
By adding a NotifyTo property to the MessageEnvelope we are able to track the 
Disposition-Notification-To header content and create MDNs routed to the 
correct notification address.

If a Disposition-Notification-To header does not exist we use the senders 
address.

Original comment by joeshook@gmail.com on 23 Jul 2013 at 11:40

GoogleCodeExporter commented 9 years ago 
Fixed in changeset 2365

Original comment by joeshook@gmail.com on 23 Jul 2013 at 11:41