Simulating Errors in our Virtual Email Simulation

To avoid problems with your HTML/CSS email, we recommend that you test in the popular web browsers first.

When we initially built this tool for developers, we decided to include a "Code Analysis" feature which identifies which lines of code are not supported by each email client. This feature is not to be confused with an email validator. A code validator would identify issues with your HTML or CSS such as unfinished or invalid div and table elements.

It is very difficult to "simulate" errors in our acid test exactly the way they might appear in each desktop email client because many of them are using different engines. Each engine has its own rules for handling errors. When running our Email Acid Test, you are using a single web browser with its own rules for rendering errors.

In the future, we may choose include some type of code validation tool so that our Code Analysis not only identifies unsupported CSS but it also highlights errors in your code. However, for the short term, please test your email in the following order:

Step1.) First, test your email in all the popular web browsers (IE 6, 7, 8, FF, Safari, Opera, and Chrome)
Step 2.) Then run your email through our Email Test using Firefox. For even better end results, re-run the Acid Test in IE as well.

Please note: at this time, we cannot be held responsible for discrepancies if your code is invalid. If you find a possible discrepancy, be sure to test your email in various web browsers before submitting a ticket.