On Wed, 2008-10-01, Tim Hamm wrote:
> I can appreciate what you are saying, from what I know on my end, > these features have never worked as long as I have had TB. I would > think by now of the thousands of emails I have sent, at least one > recipient's email client should be able to send read receipts. Tim, One possibility not to be overlooked, your ISP. When Delivery Status Notifications (as Confirm Receipts are officially known) are requested, each mail server on the path to the recipient's mail server is supposed to notice that the previous server (or your client) has requested a "DSN" be sent and pass that on to the next mail server. If that next mail server does not allow DSNs the current server is supposed to send back instead a DSN to effect that no "final" DSN will be sent. Notice that any mail server along the way "dropping the ball" will cause no DSN to be sent at all. The fact that no Confirm Receipts of yours have ever been honored makes me suspect a mail server near the beginning of the chain--at your ISP. Since DSNs and MDNs (Message Disposition Notices (Reading Receipts from the recipent's client)) are both a standardized specially formatted message, it is possible that your ISP is doing you the "favor" of deleting these as some sort of spam. Note that this is not necessarily the actual explanation, but it is something to consider if no other explanation turns out to be better. Good luck, -- Bill McQuillan <[EMAIL PROTECTED]> Using The Bat! 2.11 on Windows XP 5.1 build 2600-Service Pack 2 ________________________________________________ Current version is 4.0.24.0 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
