|
|
Posted by Tim McGurk on 12/13/06 22:02
Thank you both for your help.
Removing '\r' did the trick!
"Michael Fesser" <netizen@gmx.de> wrote in message
news:2cj0o25ne2ju10sv70sa1hg33k099e9a1p@4ax.com...
> .oO(Ric)
>
>>Mail standard is only "\r"
>
> Mail standard is "\r\n" (RFC 2822).
>
>>some email clients don't care if you send
>>\r\n but lots of providers and apps do and then the mail gets broken.
>
> It's a bit more complicated. What you send is not necessarily what the
> client will receive. The RFC describes the mail format as it should be
> handled by MTAs, but some of them have their own mind and may rewrite
> line endings. Sometimes all you can do is testing.
>
> The RFC-compliant way for example works on my host's server, but not on
> my own (or the other way round, can't remember), where a different MTA
> is running. Using CRLF there led to an additional character appended to
> each of my own header lines.
>
>>So remove the \n from all your header tags.
>
> I would rather remove the \r. From the PHP manual:
>
> | Note: If messages are not received, try using a LF (\n) only. Some
> | poor quality Unix mail transfer agents replace LF by CRLF
> | automatically (which leads to doubling CR if CRLF is used). This
> | should be a last resort, as it does not comply with RFC 2822.
>
> Micha
Navigation:
[Reply to this message]
|