This generally means that some formatting on a particular message is tripping up surgeweb's json encoding / browsers parsing of special UTF8 characters in the message data.. Mostly this is the result of maliciously, badly encoded spam messages. Although all known issues we have had in the past are currently resolved. Try the other suggestion wrt fixing the account message downloads first. If that does not resolve matters it is likely to be one of the most recent 100 messages in the inbox. Move messages to another folder, and effectively using a binary search by moving half the messages aside you should have the problem message isolated in about 7 move operations.Marijn On Wednesday 12/07/2017 at 12:10 pm, Tom Cross wrote: HiOne of our customers is getting the following error when trying to view his mail in Surgeweb.====================================================Unknown error on ajax request. Please report this code to support: TypeError:qmsg is undefined [cmd=show&page=~msg.js&msg_id=87731&fld_id=INBOX]==================================================== He has a lot of mail in his inbox 20,000 + tom crossm: 0418 295 336partner HTMLnet. [ Image ]
HiOne of our customers is getting the following error when trying to view his mail in Surgeweb.====================================================Unknown error on ajax request. Please report this code to support: TypeError:qmsg is undefined [cmd=show&page=~msg.js&msg_id=87731&fld_id=INBOX]==================================================== He has a lot of mail in his inbox 20,000 + tom crossm: 0418 295 336partner HTMLnet. [ Image ]
Last Message | Next Message