Luca Fornasari:
> The problem is with missing blank line between MIME boundary and
> content in the body of the email i.e.
>
> --=boundary1=
> Content-type: multipart/related; boundary="=boundary2="
> --=boundary2=
> Content-type: text/html;charset="iso-8859-1"
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> Segue tabella HTML
> <TABLE>
> <TR><TD>1A</TD><TD>1B</TD><TD>1C</TD></TR>
> <TR><TD>2A</TD><TD>2B</TD><TD>2C</TD></TR>
> [...]
>
> In Postfix 2.3.3 the missing blank line was inserted while in Postfix
> 2.6.6 it is not.
> While looking at the source code diffs of src/global/mime_state.c I see
>
> * XXX We don't insert a blank line separator into attachments, to
> * avoid breaking digital signatures. Postfix shall not do a
> * worse mail delivery job than MTAs that can't even parse MIME.
> [...]
> * Sites concerned about MIME evasion can use a MIME normalizer.
> * Postfix has a different mission.
>
> Can you confirm this is the reason of the different behavior?
I made that change 10 years ago. At this point, all I can rely on
is what the documentation says.
> I agree the problem is not Postfix and the best solution is to
> correctly format the email, anyway as I said it is not that easy.
I looked at tyurning off MIME parsing and using body_checks, but
that prepends text, and you need to append after boundary string.
You could use an SMTP-based filter that adds a blank after a boundary
line. Google for smtpprox, and configure it as a Postfix
smtpd_proxy_filter
Better, give it to the folks up-streeam who produce the malformed
email, and ask that they send their mail through it.
Wietse
> I need a strong reason to convince the audience.
>
> Thanks in advance
> Luca
>
