phil_white99
31st October 2008, 11:48 AM
Microsoft has an SMTP sending bug in the WinMo 6.1 mail app, that they introduced while trying to get around carriers blocking communicating with non-carrier SMTP servers (which is one of the carriers' many methods to prevent their networks from being used for spamming). The bug can disable all outgoing SMTP communications. This is a WinMo 6.1 problem and is not specific to the awesome Kavana/Ricky ROMs!
It is fixed by adding a registry key called "Operator" (without the quotes) to HKEY_LOCAL_MACHINE\System\Inbox\Settings\
Then, inside the HKEY_LOCAL_MACHINE\System\Inbox\Settings\Operator key you add a String Value named "OutgoingServer" with value "127.0.0.1" (again, both without the quotes.) A soft reset should be done after saving this.
The post at http://forum.xda-developers.com/showthread.php?t=396126&page=9 includes an excellent description from a member named Matt, who learned from Microsoft what they were attempting with changes to WinMo 6.1 SMTP sending and what they did wrong and missed in testing.
I'm just wondering if this should be in one of the Excalibur WinMo6.1 stickies, since, apparently, anyone who has any kind of problem sending SMTP messages will see their SMTP sending essentially disabled due to this bug, unless the above registry entry is created.
Also, just some comments/opinions from me: The original poster in the linked thread went through hell with T-Mobile tech support trying to determine the problem, and he did not get to the bottom of it. It seems it was Matt who actually sent his phone to Microsoft (it must have been a device with a Microsoft-approved WinMo6.1 ROM) and had the problem researched. It's an interesting problem, because it would only happen in a non-carrier-prepared ROM or a ROM not properly prepared by the carrier. This is what happens when Microsoft tries too hard to serve the interests of the carriers. Carriers' blocking or intercepting SMTP communications is a blunderous approach to spam prevention. I think it would be better if they focused on shadowing the SMTP communications, analysed them for spammer characteristics, and then referred account holder information to proper authorities when spamming is detected.
Thanks!
Phil
It is fixed by adding a registry key called "Operator" (without the quotes) to HKEY_LOCAL_MACHINE\System\Inbox\Settings\
Then, inside the HKEY_LOCAL_MACHINE\System\Inbox\Settings\Operator key you add a String Value named "OutgoingServer" with value "127.0.0.1" (again, both without the quotes.) A soft reset should be done after saving this.
The post at http://forum.xda-developers.com/showthread.php?t=396126&page=9 includes an excellent description from a member named Matt, who learned from Microsoft what they were attempting with changes to WinMo 6.1 SMTP sending and what they did wrong and missed in testing.
I'm just wondering if this should be in one of the Excalibur WinMo6.1 stickies, since, apparently, anyone who has any kind of problem sending SMTP messages will see their SMTP sending essentially disabled due to this bug, unless the above registry entry is created.
Also, just some comments/opinions from me: The original poster in the linked thread went through hell with T-Mobile tech support trying to determine the problem, and he did not get to the bottom of it. It seems it was Matt who actually sent his phone to Microsoft (it must have been a device with a Microsoft-approved WinMo6.1 ROM) and had the problem researched. It's an interesting problem, because it would only happen in a non-carrier-prepared ROM or a ROM not properly prepared by the carrier. This is what happens when Microsoft tries too hard to serve the interests of the carriers. Carriers' blocking or intercepting SMTP communications is a blunderous approach to spam prevention. I think it would be better if they focused on shadowing the SMTP communications, analysed them for spammer characteristics, and then referred account holder information to proper authorities when spamming is detected.
Thanks!
Phil