[SpamCop-List] Re: Here's another spam that won't process correctly

[Mike Easter]

Chris F. Willoughby wrote:

> Now, why doesn't it wrap on your system?  Shouldn't your program be
> able to handle the wrapping on its own?  It doesn't make any sense
> that it would wrap HERE and not THERE. =/

http://mailformat.dan.info/body/linelength.html  Dan's Mail Format Site:
Body: Line Length  - How Long Should Lines Be? - The standards document
for the format of e-mail messages, RFC 2822 [...]  SHOULD be no more
than 78 characters, [...]  For practical purposes, lines should be
broken at even less than 78 characters [...]  Line Length of Incoming
Messages [...]  Here is a screenshot showing what a message violating
line-length standards might look like to a reader:[...]

// Quoted Printable Encoding :[...]  Some people think that the use of
Quoted Printable encoding (mentioned in the MIME, character sets, and
attachments sections) is a "solution" to this line-length problem,
because it will put in line breaks to bring the message in line with the
standards, with an equal sign (=) at the end of each such broken line to
indicate that it is a "soft" line break. :[...]  However, once the
receiving mail program decodes the encoding (assuming it supports Quoted
Printable; if not, you end up with a somewhat messy, though readable,
message with lots of equal signs in it), the soft breaks are taken back
out again, and you're left with the standards-noncompliant long-line
message format. :[...]  So don't rely on Quoted Printable encoding to
solve a line length problem;

// What Should I Do? - To ensure that your outbound mail follows the
proper line length conventions, take a look at the configuration
settings of your mail program. Often, there will be an item somewhere in
there that says how lines are to be wrapped; be sure it's set to wrap at
70 characters or less. //

<ME:  I disagree with that small value for OE without QF quotefix>


-- 
Mike Easter
kibitzer, not SC admin