Comment # 16
on bug 8225
from Tyson Key
Created attachment 9874 [details]
MDaemon Router Log Example
The attached text file contains an MDaemon BES Router component debug log that
reveals some details regarding potential opcode names/descriptions + fields
(but sadly not opcode hex values), routing ID types (SRP IDs, and non-private
device UIDs/hardware PINs), and strings used in the Infrastructure-Router
mutual authentication protocol.
It seems to slightly contradict the "Phenoelit" PDF, as far as descriptions +
mappings of some opcodes are concerned (e.g. "CONNECT"/"DISCONNECT"); and I
haven't tried to configure a BlackBerry smartphone to communicate with my BES
installation - but I suppose that it's better than nothing at all.
You are receiving this mail because:
- You are watching all bug changes.