Question:

How to make PocketPC2003/Smartphone2003 Push Router accept and forward
unsigned WAP push messages.

Expected Answer:

systematic and precise information what are the conditions (security
policies, workaround bugs in MS code, etc.) for this to work or reason
why it cannot work at all.
OR - as a minimum - a complete sample SMS message (=UDH and UD hex
dump) of a custom application id and content type that DOES work with
the sample code provided by MS for the push router (in pushclient.h,
see below).

Sources already consulted for information:
- MSDN
- google groups (reading AND posting)
- web (google and other search engines)

Research done:

I am trying to send a WAP push message to a PocketPC 2003 Phone Edition
(a SPV M1000) device and processing it there using the PushRouter_xxxx
API, basically following the example in the pushclient.h header file.

I tried PushRouter_RegisterClient / PushRouter_Open with all
combinations of my content type and my application ID (both, only
appid, only content type), but the application does not receive the
message, whatever I try.

I verified the message sending and formatting with another device
(Symbian based Nokia phone) which receives and processes the exact same
message ok.

The WAP push message is an unautenticated one, so I guessed that I
might need to set the SecurityPolicies accordingly.

As a first attempt, I changed the Unauthenticated Messages Policy
(4110) from its default value of SECROLE_USER_UNAUTH (64) to 0xFFFFFFFF
to grant it all roles - hoping that this would make sure the message is
processed by the Push Router. I also tried to give it only
SECROLE_USER_AUTH (16).

As a second attempt, I changed the Grant Manager Policy (4119) to
USER_UNAUTH., to grant Manager rights (=highest possible) to
unauthenticated messages, but that did not help either.

I did a test with sending a MMS notification (with content-type
application/vnd.wap.mms-message) to the device as it has the ArcSoft
MMS composer installed which registers for this content type with Push
Router. I was hoping I would see MMS composer start, but that did not
work either.

My current conclusion is that for some reason unauthenticated WAP push
messages are not delivered at all to Push Router clients (neither mine
nor, apparently,  the MMS composer), despite my changes to the security
policies.