Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, making the entire rest of the document a HTML comment and therefore empty. This malformed HTML is turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Any newlines and Unicode characters are turned into \A0 *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. We were about to submit a bug report and patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Bug 1675507 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server -- after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Any newlines and Unicode characters are turned into \A0 *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause from the symptoms that end users see. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Newlines and/or Unicode characters are turned into \A0 *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause from the symptoms that end users see. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Apparently newlines and/or Unicode characters are turned into \A0 *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause from the symptoms that end users see. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Apparently newlines and/or Unicode characters are turned into \A0 *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Apparently newlines and/or Unicode characters are turned into \A0 *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause, from the symptoms that the end users reported. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Apparently newlines and/or Unicode characters are turned into `\A0` *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause, from the symptoms that the end users reported. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).
Kai, we're hitting *exactly* this bug as described by the original description (comment 0). TB turns valid HTML `<style> <!-- foo --> </style>` into invalid HTML `<style> <!-- foo </style>`. The HTML comment is never closed, turning the entire rest of the document into a single HTML comment and therefore the document is technically empty. This malformed HTML in turn is confusing the Exchange server, after ExQuilla submits this invalid mail body to Exchange for sending. The Exchange server cannot parse the invalid HTML, and apparently starts to act strange. Apparently newlines and/or Unicode characters are turned into literal `\A0` *by the Exchange server*, but as a direct consequence of this invalid HTML that TB sends. You cannot blame Exchange for any misbehavior, because the HTML message we sent is invalid. Garbage in, garbage out. Many of our ExQuilla users are running into this, and more so as people auto-update to TB 78. We verified that if we close the HTML comment, i.e. re-add the `-->` before the `</style>` as required by HTML, the message is sent correctly. So, it's precisely this bug here at the root cause. It took us a long time to find the root cause, from the symptoms that the end users reported. We were about to submit a TB bug report and supply a patch, when we found this bug here. It appears you are working on it in bug 1680084, so please give us access to bug 1680084 (by CCing me).