I See in this thread http://answers.microsoft.com/en-us/outlook_com/forum/opeople-ocontacts/outlookcom-moving-addresses-from-bcc-field-to-the/b4505d03-7b66-4f98-a878-f1d82fcf42a6 that Ron Summers has on Further testing determined that the outlook.com mail servers fail to be RFC compliance in that they do not send mail to BCC recipients from their SMTP service.
As this is a clear violation of the relevant RFC I was wondering
- Where Microsoft document their decision to not live up to the standard set by the RFC
- When they will be taking remedial action to restore their service to standards compliance
- When users will be advised of the limitation being placed on mail clients on the outlook.com mail service.
Those that do not use web mail are entitled to at least the courtesy of making them aware your service has been deliberately crippled. They can then make an informed decision to use or not to use your service. As it fails to meet even the minimum standards to be considered a mail provider in that it can not send.
I suggest the following from Microsoft.
Documentation of exactly what limitations they have placed on their SMTP service. These should include.
- The decision to disable POP access to all Hotmail account on transfer to outlook.com and a reason why this change to users expressly set preferences was required.
- The duplication of send mail in IMAP accounts as the client and server both save a sent copy.
- The inability of your SMTP server to use a BCC address. Instead of rejecting the mail or warning the user you simply silently drop the information and make support work for the relevant mail client.
- The inability to use your alias feature in a mail client as your SMTP server expressly changes the information the client inserts.
- Any other limitation included in the SMTP service that limit the functionality to something other than what a reasonable person would expect from someone offering a mail service.