Re: [Nms-cgi-devel] Suggestions for FormMail.pl

[Steven M. <nm...@ap...>]

A proposal to add a Content-type header to the mails sent by
FormMail.pm, so that the emails include the charset that the user
configured in FormMail.pl:

One of the user configurable parameters in FormMail.pl is charset.

My HTML form is written in UTF-8, I have set charset to UTF-8, and
posted data is emailed to me as UTF-8. Unfortunately, the emails do not
use the Content-type header, so my mail client displays them in a
default characterset, which is not UTF-8.

Adding these two lines of code to FormMail.pm resolve the issue:

After FormMail.pl: Line 1285
    $self->mailer->print("Content-Type: text/plain;
charset=".$self->{CFG}{charset}."\n");

After FormMail.pl: Line 1122
Content-Type: text/plain; charset=${\( $self->{CFG}{charset} )}

http://www.ietf.org/rfc/rfc1049.txt  - content type header for email
http://www.sendmail.org/rfc/0822.html#4 - headers may be in any order

This was helpful for me. is it contentious?

Steven


Jonathan Stowe wrote:

>On Thu, 2006-03-02 at 16:44, Steven Mackenzie wrote:
>  
>
>>Hello,
>>
>>I have made some small changes to my FormMail.pm installation to use the
>>configured Mailer name consistantly, avoid mails being flagged as spam
>>by SpamAssassin, and to add a content type header that respects the
>>users configured character set.
>>
>>I see the FormMail script hasn't been updated in a while though. Is
>>anyone interested in adding these changes (in while case I'll describe
>>and justify them)?
>>    
>>
>
>FormMail hasn't been changed in a while because it hasn't had any bugs
>to be fixed and we are not encouraging adding new features - we are
>concentrating any new development in TFmail as we aren't constrained by
>the legacy of compatibility with the MSA FormMail.
>
>However if you send us a patch against the modules version of FormMail
>we can take a look and discuss it.
>
>/J\
>
>  
>