2012-05-25 15:50
Hi
Periodically I find my outgong emails (via Outlook) being dumped in the Drafts folder when I send them. Some time later (might be a few seconds, sometimes longer) I find a message in the in-box which says something like 'Windows Phone is unable to send your mail'. I assume this happens in poor signal conditions altough it does happen when the phone appears to be reporting a strong signal. Once in the drafts folder, I don't seem to be able to send the mail message from there - I have to move it before I can send it.
I can't find any documentation of theis behaviour so I don't know if it's supposed to do this; the circumstances under which it happens; and whether I can configure it to do something else
This is irritating on so many levels. Why doesn't the phone just leave the message in the outbox until it has connectiviity? If it's not going to send the message, why not tell me then? As it is, I often miss the failure message so I don't realise the message has not been sent until a long time after. And why can't I simply click on the message in draft and select 'send' from there?
Is this designed behaviour? If so, can I change it or when is it going to be put right?
2012-05-25 18:19
Strange behavior, what kind of email account is this occuring with? Exchange, Hotmail......
2012-05-25 18:32
2012-05-27 15:48
AFAICT, it seems to be EXchange only. Can't send Gmail messages either in low siglnl condtiions but they just sit in the machine until they can be sent and no user intervention is required.
2012-05-27 22:36
I've read reports in the past regarding Exchange 2003, had a similar issue on my iPhone 3G when I was connecting to 2003. Do you know what service pack the exchange server is running, is it up to date as far as Exchange 2003 is concerned?
2012-05-27 23:34
SP2. Only outstanding updates are some recent security patches. I stress that this problem is unique to this phone. It doesn't happen with either of the two WM 6.5 devices, an Android phone or a more recent Android tablet (or half a dozen Windows powered laptops).
I am so frustrated by this issue I feel like throwing the phone at the wall. Not only am I having this problem (which itself is intolerable) but Nokia/Microsoft seem to be going out of their way to make this phone as useless as possible. So, the email app has a logging setting. I have set this to advanced in the hope I might get some diagnostic info. But I have no idea where the log is stored. You'd think this would be spelled out in the user manual - but there isn't one. Even if I did, it wouldn't help as I have no way of browsing the phone's filing system! On a PC, I could examine the raw message file to trace it's path through the various intermediate devices. Not only can I not do this for WP7, I can't even view the message header!
This isn't release candidate software - it's barely out of Alpa testing. I think ithe device has got to go back and be swapped for a phone that works
2012-05-28 18:37
You make it harder for anyone to offer their thoughts when you split your email with caps. Makes it hard to read....Also keep in mind you're using a legacy mail server that isn't even in full support anymore.
With that said, yes after doing some searching, yes there are apparent issues with WP7/Exchange 2003 which do not occur in 2007/2010. I can attest to both as I was connected to 2007 before rolling out to 2010.....There was a fix that was released for 7.5 to address (make things work better) with Exchange 2003, don't know if those fixes are rolled into the Lumia handsets.
2012-05-28 19:55
Strictly speaking, they were not caps - just larger font for emphasis. However, your admonition is justified. In my defence, I was letting off (rightous) steam not really expecting much help as I think this is a deeply flawed OS for which fixes are promised but don't materialise.
And I was right because, l;et's be honest, although you could comment, you couldn't offer a diagnosis, let alone a solution. I'm interested, however, to know what your source of information is. One of my complaints about this phone and this OS is the very limited amount of information there is about it but you seem to have access to more than I could find
2012-05-29 3:06
Sorry, I must be "Font" blind because I looked at it like they were caps
I understand your frustration, been there many times. Just keep in mind you're taking it out on the wrong guy. Don't mean to "irritate" you with suggestions, just trying to be helpful. Keep in mind I don't work for Nokia or MS.
There's lots of information online about Exchange 2003 sync problems. With that said, it sounds like you have Administrative access to the Exchange server and know what you are doing so here is some information that may be helpful in troubleshooting if it can be fixed on the server side. Even though it works with other devices, might still want to go through these.
Just general information about WP7 and Activesync
Exchange 2003 Active Sync FAQ (Might want to go through this)
Not exactly the same as your problem but....
This one is very intresting, sounds exactly like your problem but on Exchange 2007. Description seems to indicate some kind of corruption, may want to run eseutil/isinteg for an integrity check to validate the private store just to make sure there isn't any corruption.
http://support.microsoft.com/kb/961124/EN-US
BTW, Could be wrong but I believe extended logging goes to IIS logs on 2003.
2012-05-31 18:05
My thanks to Shoey5 for tracking down these sources. Unfortunately I can't find in any of them a solution to the problem. I don't have a generic problem in accessing my Exchange Server 2003 installation - the problem is specific to a) OTA and b) the Lumia 800. Other phones connect no problemo and the Lumia is fine via WiFi.
I've looked at the Server end of this and I can't find anything wrong nor has anything significant changed at the server end.
Is there any other approach I might try?
Paul
Shoey5 wrote:
Sorry, I must be "Font" blind because I looked at it like they were caps
I understand your frustration, been there many times. Just keep in mind you're taking it out on the wrong guy. Don't mean to "irritate" you with suggestions, just trying to be helpful. Keep in mind I don't work for Nokia or MS.
There's lots of information online about Exchange 2003 sync problems. With that said, it sounds like you have Administrative access to the Exchange server and know what you are doing so here is some information that may be helpful in troubleshooting if it can be fixed on the server side. Even though it works with other devices, might still want to go through these.
Just general information about WP7 and Activesync
Exchange 2003 Active Sync FAQ (Might want to go through this)
Not exactly the same as your problem but....
This one is very intresting, sounds exactly like your problem but on Exchange 2007. Description seems to indicate some kind of corruption, may want to run eseutil/isinteg for an integrity check to validate the private store just to make sure there isn't any corruption.
http://support.microsoft.com/kb/961124/EN-US
BTW, Could be wrong but I believe extended logging goes to IIS logs on 2003.
2012-05-31 19:23
OneMoreOne wrote: the Lumia is fine via WiFi.
So you're saying you never experience the problem over wifi (at all, ever)?
Don't know about your layout or if this would even be related but out of curiousity, is there a difference in DNS between the way you're resolving internally/externally. ie. obviously if you're hitting your FQDN to your mail server externally you're hitting an external IP. What about when you're internal on WiFi. Same IP or an internal IP? Does the reverse lookup match internal/external to the FQDN. And I'm going to guess (but just a guess) that you're using an untrusted certificate, does it match whatever your phone is resolving to for your mail server?
2012-06-12 14:48
Apologies for the the long absence. Other matters were even more pressing.
I am pretty confident that the problem never happens with a wifi internet connection. Yes, you are right that I don't have a public trusted security certificate which is why I have SSL turned off on the phone. The server address the phone is pointed at is the same one as all the other mobile devices use (including two using WM6.5) all of which use Activesync for synchronisation and none of which replicate the problem with the Lumia. The FQDN matches the external address of the Activesync server.
Do this information help with any kind of diagnosis?