DEAN LEE:/DEV/BLOG

35 EQ is an innovative & seamless integration of high class business email service and free enterprise IM service. It’s designed to bring you amazing communication experience. Incredible large capacity up to 35 GB per user and 50MB x 6 attachments per email make you able to store and deliver much larger files than ever; Creative Email-Tracking and Self-destruction features for high-secure information protection, you don’t need to be afraid of any unexpected mail reading/receiving.

35 EQ is also an Expert Instant Messenger for Enterprise, why expert? It is a Smart & direct communicator, not only covers messages but also emails directly! When a new mail arrives, it will present you the email contents directly in the POP up window, then you can read, even write a mail just with it. You don’t need to worry about delay or miss any mail. it is also compatible with MSN(MS Trade Mark) and other Jabber based IMs; Web-based administration console, offering you to manage your company private domain emails through an intuitive interface and customize the email website with your own company Banner or Logo.

35 EQ allows you to stay in touch with other members of your organization or any of your partners you added to you contact list. In addition, 35 EQ can also support your MSN contacts, that means, you can use this tool to chat with your MSN friends. Actually the 35EQ can connect with almost all Jabber based IMs, and trackable history logs are available.

Organization/Group Contact list just needs to be maintained at the system back end. Users will experienced an auto-update contact list.

Here is an example using the LogMicroscope widget on openid.35.com:

OpenId.35.com adds web snapshot to OpenId enabled sites:

We have upgraded the OpenId.35.com with OpenID 2.0 support on the development server.but some OpenID consumers always report the following error:“OpenID authentication failed: Server denied check_authentication”.This is due to a bug in JanRain OpenID Libraries that used by these consumers which were already fixed in the latest version:

This was noted in 2.1.1. The python-openid library was being used in "dumb" consumer mode, and received an authentication response that included PAPE extension parameters. The PAPE namespace parameter was included in the response signature. The check_authentication request formulated by the library included ns.pape in the signed list but did not include the openid.ns.pape parameter, so the signature check failed.