Roundup Tracker - Issues

Message367

Author sheilaking
Recipients
Date 2002-10-08.22:36:50
Message-id
In-reply-to
Logged In: YES 
user_id=467955

I responded to this comment yesterday and sent my response
to the developers list. Apparently no one saw it?

Here it is again:

=======================================
This is not strictly a Mutt issue. I have encountered the same
problem on my GypsyMail form handler script.

My resolution was, to run the following function on any
input from an HTML form that was supposed to be sent via
SMTP as an email:

text = string.replace(text, '\r\n', '\n')

I put this "patch" into my cgi script as a "fix" for an issue
with Outlook (Express) mail client.

Technically, the above "fix" doesn't address line endings for
Macintosh clients. A complete fix would do the following:

text = string.replace(text, '\r\n', '\n')
text = string.replace(text, '\r', '\n')

The above two statements work as follows:

(1) If '\r\n' occurs anywhere within the message, it is a line
ending introduced by a windows client. Replace with the standard
'\n'.
(2) After completing the first statement, if there are any
remaining occurences of '\r' in the text string, these are line
endings inserted by a Macintosh client. Replace those with '\n'.

Here is a corroborating discussion of this phenomenon in
another scripting situation:

http://www.aota.net/forums/showthread.php?postid=47373#post47373

--
Sheila King
http://www.thinkspot.net/sheila/
http://www.k12groups.org
========================================

The above pasted response does give a "fix" for this
problem, as far as I know.

--Sheila King
History
Date User Action Args
2009-02-03 14:20:04adminlinkissue614072 messages
2009-02-03 14:20:04admincreate