On Mon, Mar 09, 2009 at 04:50:29PM +0100, Jordi Moles Blanco wrote:
> after your comments I thought I had "fixed" my filter and everything seemed
> to work fine. I only replaced \n.\n with \n..\n in the body of the message.
You don't change message bodies before transmission, you follow RFCs
821, 2821, 5321 and remove leading "." from the SMTP payload on input
(in the SMTP server) and add leading "." to the SMTP payload on output
(in the SMTP client). SMTP uses "\r\n" at the ends of lines.
> But now I've found out that when the message contains html code, it doesn't
> work properly.
This is nonsense, SMTP+MIME deliver conforming message bodies unmodified
from the sender to the recipient. It does via suitable encodings during
message preparation and transport.
Use MIME to encode content that is not printable ASCII text (with
sufficiently short lines). Use SMTP transparency to deal with lines
starting with ".".
> If you look at the content of the message, by doing "cat" for example, you
> can see a line like this <br>.<br>, which is obvious for being HTML .
You are still mightily confused. Don't modify the message or its HTML
encoding. Implement correct SMTP server and client code.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
