Lance 2012-06-01 05:14:11
I’ve been using Exchange2003 with Always Up To Date sync for months now
with my T-Mobile PocketPC.
For some reason, in the last month or so, the Always Up To Date stopped
I’ve been digging around on this for a couple of days now. I think that
the SMTP message is getting filtered at T-Mobile (even though this has
been working for months), since if I change my “device SMS address” to
another regular email address (e.g. hotmail) the ‘sync’ message goes
out. If I use email@example.com, the SMTP message doesn’t go out
(according to the message tracker in exchange 2003, it says “Message
Sent to Badmail”. Badmail says: “This message is a delivery status
notification that cannot be delivered.”.
So, the big question I have is: Anyone else using ActiveSync always up
to date with T-Mobile USA? and is it still working for you?
And of course the second question is: Any ideas anyone?
Lance 2012-06-10 14:58:00
I’ve done some more research on this, and it appears that Exchange 2003
send always-up-to-date notifications to the provider with no FROM
address, so they get rejected by T-Mobile’s mail server.
My packet trace showed something like this:
Is there a way to make Exchange 2003 send these AUTD notifications with
a FROM address? Anyone? MS?
Lance 2012-06-10 14:58:02
OK, I’ll keep answering my own questions, since someone will find this
useful in the archives.
There’s a new hotfix for Exchange 2003 SP1 which allows you to set a
static ‘from’ in the registry:
I guess its time to add SP1 and try and get this fix…
Chris de herre 2012-06-10 14:58:22
Thanks for the update. I’ll add it as a note to the ActiveSync
Troubleshooting Guide I maintain.