[Typo3-dev] Default mailform catched by spamfilter

[Jan-Erik Revsbech]

Hi Lars, sorry for the very late reply to this post. I have looked a little
into the base64 rencoding that emails from typo3 is usually encoded with. I
have posted some modifications to the direct_mail extension to allow direct
mails to be sent in quoted-printable encoding. Now I wanted to do the same
thing for formmails.

Looking a little into the source-code, it seems that this is already
possible, and as expected, it is configurable. This configuration of a
mailform will do the trick:

<snip>

# Example content:

Name: | *name = input,40 | Enter your name here

Email: | *email=input,40 |

Address: | address=textarea,40,5 |

Contact me: | tv=check | 1

|formtype_mail = submit | Send form!

|html_enabled=hidden | 1

|quoted_printable=hidden| 1

|subject=hidden| This is the subject

</snip>

Notice the line |quoted_printable=hidden| 1 this will skip the base64
encoding and use quoted-printable instead.

The message-id problem should is fixed in 3.7.0-dev, and I have posted the
fix in the 3.6.0 branch as well, so it should be corrected in the next patch
release (3.6.3).

/Jan-Erik

"Lars E. D. Jensen" <ledj at dcmedia.biz> wrote in message
news:mailman.1.1084278626.27960.typo3-dev at lists.netfielders.de...
> Hello devs
>
> When I have my pretty sophisticated spamfilter enabled,
> I get this score (see below) from mails sent from a standard mailform in
> 3.6.0.
>
> I would like to eliminate e.g. INVALID_MSGID, MIME_BASE64_LATIN and
> MIME_BASE64_TEXT in the scores since they score most points.
>
> Guidance to a place to look is appreciated.
>
> Thanks
> Lars
>
>
> Content analysis details:   (6.6 points, 5.0 required)
>
>  pts rule name              description
> ---- ---------------------- ----------------------------------------------
--
> --
>  0.3 NO_REAL_NAME           From: does not include a real name
>  1.8 DOMAIN_BODY            BODY: Domain registration spam body
>  1.1 MIME_BASE64_LATIN      RAW: Latin alphabet text using base64 encoding
>  1.1 MIME_BASE64_TEXT       RAW: Message text disguised using base64
> encoding
>  0.2 SUBJ_HAS_UNIQ_ID       Subject contains a unique ID
>  0.3 UPPERCASE_25_50        message body is 25-50% uppercase
>  1.8 INVALID_MSGID          Message-Id is not valid, according to RFC 2822
>
>