Quote:
Originally Posted by Ed Hansberry
"This behavior is associated with a feature that is introduced in Windows Mobile 6.1. The feature allows for mobile operators to specify an alternate SMTP server name that is used if e-mail messages cannot be sent by using the user-specified SMTP server name. If the mobile operator does not specify an alternate SMTP server name and if the Windows Mobile 6.1-based device does not connect, the e-mail account is corrupted and cannot send e-mail messages.".....The second way this blows my mind is, why in the world is Microsoft allowing the carrier to intercept SMTP messages and send them through its server? This may sound like a helpful feature if your SMTP server is down, but it isn't.
|
Well, it would add robustness to the solution of your SMTP is blocked by the carrier. What they do on a frequent basis. They really want their SMTP to be used, instead of your own.
Quote:
Originally Posted by Ed Hansberry
If I wanted my email going through my carrier's SMPT server, I'd set it to do so. There appears to be no way to block this behavior, and it strikes me as a security concern and privacy issue.
|
Don't forget, carriers reguraly reroute the SMTP traffic to their own servers regardless of what you have said in the settings. I discovered this when I got a reply from a technically oriented friend that included a full header, which indicated I had used the SMTP of T-Mobile instead of my own....
Yes, this is a huge privacy issue, but they did this anyway. It is in the fine print somewhere on that 200 page EULA for their network.
Jaap