Log in

View Full Version : bug with Windows Mobile Email client when SMTP server requires login like '[email protected]'


The PocketTV Team
06-24-2006, 05:17 AM
we found a bug with the Smartphone Email application that prevents using some SMTP servers.

well in fact the bug is probably general to all Windows Mobile Smartphone (and maybe to all Windows Mobile devices including Pocket PCs), but we tested it and confirmed it on the Motorola Q.

the bug prevents using some login names on SMTP (i.e. outgoing email) servers that require authentication and when the SMTP login name is something like '[email protected]' i.e. when the login name contains an '@' sign.

this type of server login name is common on servers that use shared domains on a single IP address, and this is a common case. in this case, since there may be several users with the same name under different domains (on the same server), the correct user is identified by using the domain name with the '@' sign.

in fact we found that bug by trying to configure the Motorola Q to use one of our email servers to send my email.

what happens is that the Smartphone email client removes the @ sign and everything that follows it when loging to the SMTP server - we confirmed that by looking in real time in the log files produced by our SMTP server.

i am not aware of any workaround. once again, MSFT is trying to be "smart" i.e. they assume that the @xxx.yyy part in the login name of the SMPT server (i.e. outgoing) was entered by mistake by the user, but being too smart is not always a good thing.

note that using fully-qualified user-name that include a mandatory @domain part is very common and even google's gmail uses this, as you can see in the 'Account Name' section of http://mail.google.com/support/bin/answer.py?answer=13287 .

So if you use gmail to both receive and send email, it will work, but if you want to use gmail just to send (i.e. SMTP), and use another server to receive (i.e. POP3 or IMAP4), then it won't work, because of that bug. try it, you'll see...

Mike Temporale
06-24-2006, 05:59 PM
So, you're saying the login address for the SMTP server has to be [email protected] and this has to be different than the IMAP account. I'm trying to see if I got this right;

IMAP Account = [email protected]
IMAP server = mail.domain.com

SMTP Server = mail.domain.com
SMTP Account = [email protected]
SMTP Requires Authentication is turned on.

You're saying that I shouldn't be able to send email under this configuration? Let me know if that's right and I'll setup and account so I can test this.

Jerry Raia
06-24-2006, 11:16 PM
That's exactly how I read it Mike. I do have an email account like this but it uses the same Logon for both servers and works fine.

Mark Kenepp
06-24-2006, 11:42 PM
That's exactly how I read it Mike. I do have an email account like this but it uses the same Logon for both servers and works fine.

I guess it could be an issue when one is connecting to a network which requires SMTP authentication (with the user name being the email address) and the email one wants to access is on a different network and uses the network connection to authenticate the SMTP connection thus preventing sending mail while connected through another network.

This could very well be the exact situation I may encounter when I am traveling abroad. I typically use a standard GSM data connection to connect to Wanadoo (formerly Freeserve) when checking my office email via POP3.

The SMTP Server is Wanadoo's and the POP3 server is my office mail server. Both would require different username and passwords to authenticate.

The only question is, does Wanadoo's SMTP Server require authentication or does it authenticate by my connection to their network. If their SMTP Server does require authentication, is the username my Wanadoo email address?

I guess that at least, I can use my iPaq 2215 running Pocket PC 2003.

What a surprise, I will be carrying around multiple handhelds 8)

The PocketTV Team
06-25-2006, 12:21 AM
So, you're saying the login address for the SMTP server has to be [email protected] and this has to be different than the IMAP account. I'm trying to see if I got this right;

IMAP Account = [email protected]
IMAP server = mail.domain.com

SMTP Server = mail.domain.com
SMTP Account = [email protected]
SMTP Requires Authentication is turned on.

You're saying that I shouldn't be able to send email under this configuration? Let me know if that's right and I'll setup and account so I can test this.
The configs that triggers the bug include (bur are probably not limited to):

IMAP or POP Account = somename (no @ sign - i have not tried with @ sign, but probably does not matter)
IMAP or POP server = someserver.somedomain.com

SMTP Server = otherserver.anotherdomain.com
SMTP Account = [email protected]
SMTP Requires Authentication: Yes
SMTP uses SSL: Yes or No (does not matter)

By the way: Beverly Howard [MS MVP-Mobile Devices] wrote to me:

"you have rediscovered _long_ standing, ongoing issue..."

so apparently this is a well know issue, and it affects ALL Windows Mobile clients... not just Smartphones, but also Pocket PCs.

The PocketTV Team
06-25-2006, 12:28 AM
That's exactly how I read it Mike. I do have an email account like this but it uses the same Logon for both servers and works fine.

I guess it could be an issue when one is connecting to a network which requires SMTP authentication (with the user name being the email address)

the problem occurs when the user SMTP login name has a @ sign, even if it is not the real user name address. In my case, the SMTP login name on my mail server is my name followed by @somedomain.com , but this login name (syntactically a email address) is not my email.

when we tested the problem, we tried using all sort of login names that were not syntactically correct email addresses (there is no requirement that the SMTP server login name has anything to do with an email address, it can be anything!).

We tried:

SMTP login name configured in email -> login name that the SMTP server gets at login

[email protected] -> user
"[email protected]" -> "user
user\@domain.com -> user\

as soon as there is an @ sign anywhere in the SMTP login name, the Windows mobile email client removes it and all the characters that follows it. we could not find a workaround.

and the email one wants to access is on a different network and uses the network connection to authenticate the SMTP connection thus preventing sending mail while connected through another network.

This could very well be the exact situation I may encounter when I am traveling abroad. I typically use a standard GSM data connection to connect to Wanadoo (formerly Freeserve) when checking my office email via POP3.

The SMTP Server is Wanadoo's and the POP3 server is my office mail server. Both would require different username and passwords to authenticate.

The only question is, does Wanadoo's SMTP Server require authentication or does it authenticate by my connection to their network. If their SMTP Server does require authentication, is the username my Wanadoo email address?

yes, most likely your wanadoo SMTP login name is your email address. that's in general the case for service providers. for example, it's the case for gmail.

Mike Temporale
06-25-2006, 01:25 AM
By the way: Beverly Howard [MS MVP-Mobile Devices] wrote to me:

"you have rediscovered _long_ standing, ongoing issue..."

so apparently this is a well know issue, and it affects ALL Windows Mobile clients... not just Smartphones, but also Pocket PCs.

sigh.. There seems to be a lot of those with Windows Mobile. :( Well, I guess there's no reason for me to go and setup an account to test this with. Bev's a pretty knowledgeable guy.

The PocketTV Team
06-25-2006, 01:43 AM
sigh.. There seems to be a lot of those with Windows Mobile. :( Well, I guess there's no reason for me to go and setup an account to test this with. Bev's a pretty knowledgeable guy.

I just cannot believe that MSFT spends so much efforts implementing all those bells and whistles, rather than fixing basic SERIOUS bugs like this one.

The PocketTV Team
06-25-2006, 10:10 AM
I searched: SMTP wince

in the Microsoft knowledge database, and found only two articles, none of
them describing this bug.

so maybe it is not in their knowledge database, i.e. officially the bug does
not exist because it was never reported?

could someone enter it in the Microsoft knowledge database?

thanks!