I have a RC 1.3.3 install that serves several hundred customers. We received a call yesterday that one customer was getting a "Connection Error (Failed to reach the server)!" error when checking their email. No other reports of issues. We successfully log into RC using the customer credentials and sure enough, inbox shows 40+ messages in the folder window, but nothing displayed in the message list window and immediately get the connection error.
Eventually, we figured out the issue was caused by a couple of emails in the user's account. All of the problematic emails in this specific users account had subject lines with "=?UTF-8?Q?" or "=?UTF-32?B?" and had <style> sections containing garbage (Mailsploit?). Deleting said emails results in a working account, no connection error and message list shows the correct information. Copying a problematic email to one of our test accounts results in the same error.
I have debug level set to 8, but there is nothing relevant being outputted to the log file.
Is the connection error some kind of "fall through" error message that RC uses when no other errors are relevant? Second, is there anything we can do from the RC side of things to prevent the error (don't display message/ignore UTF encoding?).
I have attached one of the sanitized (server/account info altered) emails if someone wants to take a look. We tried altering the subject line. The only way we could get RC to work with the email was to alter the subject line *AND* remove the <style> section in the message body.
