Books On Line has bad email address for "Send Feedback"

Books On Line has bad email address for "Send Feedback" by Todd C

Closed

as By Design Help for as By Design

Type:	Suggestion
ID:	778203
Opened:	2/1/2013 5:28:17 AM
Access Restriction:	Public

Workaround(s)

view

Looking at Books On Line and wanted to send some feedback so I clicked the "Send Feedback" button. Outlook responded with a new email with the To and Subject line already filled in. After entering my text and hitting Send, I got a return email from microsoft saying that the mailbox did not exist:

*****************************
Delivery has failed to these recipients or groups:

sqldocfb@microsoft.com
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.

The following organization rejected your message: mail.microsoft.com.
(additional info here not pasted)
*********************************

Frustrating that it appears that Microsoft doesn't care enough to update the email address for this feedback, or at least put in a fowrarding address for this account on their server.

Details (expand)

English

SQL Engine

Several suggestions for this:

Either fix the email address in BOL so that it is directed at a valid email address
or
Put in a forwarding email address so that when Microsoft gets it it is forwarded to the proper address
or
Set up a connect.microsoft.com site JUST for Books On Line

Improved User Interface

None of the benefits listed above apply here, but I think the issue stands by its own merit as to why it should be addressed.

0 attachments

You are correct that this is not a great customer experience. This feedback system was discontinued quite a while ago, though we can't keep customers from seeing the old link in old content. There was a nice message to customers for a while, but that has now aged out as well. You can submit feedback via the connect system, or you can add a comment to topics as they appear in MSDN. Sorry for the less than optimal experience.