I have noticed that sending email using php doesn't work well to users with email accounts from servers in Israel (e.g. runbox.com). One fix was to change all "\r\n" to just "\n"; which worked but doesn't work for most sites like gmail accounts.

Is there a 1 fit all kinda thing way for emails to be properly parsed by all mail servers. The first header is properly parsed by Runbox accounts but using MIME boundaries are not parsed correctly unless all "\r" are removed (except for first header is fine)? But then that screws up gmail. Has anyone had similar problems?

Thank you.

I wouldn't have thought you should be using '\r' at all, '\n' should be interpreted correctly per platform

cheers

When communicating over the internet, you can't assume things like that.

See RFC 822, section 3.2
If runbox.com doesn't work with \r\n, it has a bug; you'll have to work around it.

What I was getting at was that on Windows '\n' becomes <cr><lf>, having an extra <cr> due to '\r' is not required

cheers

That would only be the case when printing to the terminal or a file through a text-mode stream. The OP is about sending email, which means the data is going over a socket; usually neither side knows what platform the other is running, so things like line endings have to specified in the protocol.