comment on

Keep the HTML on port 80 and the SMTP on port 25 please. We have enough trouble with people misusing email already.

Many people are stripping HTML out of email anyway, server-side, with milters and other tools, because of the dangerous nature of malware, web-bugs and other malicious "crumbs" that find their way through HTML-laden email.

There's no way to reliably guarantee that the recipient is going to be displaying the email in the way you intend. Are they using Outlook? pine? mutt? Evolution? KMail? Other?

The right way to do this, is to use Text::xSV, Text::CSV, Spreadsheet::WriteExcel or similar modules. Send the data across in a way that can be used on the other side, and not just displayed in a browser on the other side.

If you must display HTML (and please, please please validate it!), just send the URL in an email, where the reader can launch it in their browser of choice to display it.

In reply to Re: Is there any way to send HTML table information by hacker
in thread Is there any way to send HTML table information by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks