You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java Mail API doesn't provide a way to request "different DSN(Delivery Status Notification)s per-recipient" as explained by RFC1891. There is SMTPMessage.setNotifyOptions(int options) but it applies to all recipients in the message.
Suggested workaround is sending multiple 'copies' of the message with a single recipient and desired DSN for that recipient. This is inconvenient because:
Number of recipients and/or message size may be considerably high
Sending multiple messages will create different instances (with different Message-IDs) that will be harder to track (mainly for administration purposes on server and client)
Requested enhancement is to allow specifying DSN for each recipient.
@glassfishrobot Commented @bshannon said:
A similar request was filed in the old Sun bug system, and included this
suggestion:
When sending rcpt commands use the dsn notification properties specified for
the receipient currently processing.
To implement this in backward compatible way something like this:
when the value starts with a '[' than get the DSN properties per receipient
else use fallback to the old way. In this way no code that uses the mail api
should break.
@glassfishrobot Commented @bshannon said:
A clean way to do this might be to add a DSNInternetAddress class
that allows DSN information to be specified for each address, but
that would require MimeMessage to keep track of the original Address
objects instead of immediately serializing them to the headers.
A simple solution as proposed above might be easier in the short term.
Java Mail API doesn't provide a way to request "different DSN(Delivery Status Notification)s per-recipient" as explained by RFC1891. There is SMTPMessage.setNotifyOptions(int options) but it applies to all recipients in the message.
Suggested workaround is sending multiple 'copies' of the message with a single recipient and desired DSN for that recipient. This is inconvenient because:
Requested enhancement is to allow specifying DSN for each recipient.
Please see:
https://forums.oracle.com/forums/thread.jspa?threadID=2493438&tstart=0
Affected Versions
1.4.5
Environment
All
All
The text was updated successfully, but these errors were encountered: