The basic functionality that the FormMail package must provide is to send an e-mail that is packaged with both an HTML and a non-HTML version of the same content, which you appear to be saying that it is correctly doing. But perhaps the configuration setting isn't inserting the proper header into the HTML, to tell the recipient to expect UTF-8. (Just as web pages should do. Same thing.) And, pragmatically speaking, it just might be simplest to insert that yourself – e.g. using a Template. You need to be sending, in that portion of the message, a complete HTML package including both header and body portions ... after verifying that your mail client isn't the actual culprit by virtue of being clueless. If you can get it to hand you the body of the message ... or telnet into the mail server and get the message for yourself ... you should immediately be able to see if the encoding-spec is present or not in what the mail server is sending you.
-
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.
|
