Joerg Mayer wrote:
On Thu, Dec 19, 2002 at 10:36:14AM -0700, Tony Lambregts wrote:Since I said I would... This patch is relative to my last patch (patches.txt)
Joerg Mayer wrote:I jsut dug out the following mail:
Maybe you should include a step by step instruction for outlook usersWell I suppose I could if I had those instructions.
how to do that. It seems that outlook is the leading misattachment generator,
so instead of just telling people what NOT to do, maybe you can tell
people how to do it right.
Change Log: add instructions to allow inlining attachements in Outlook Express.
File: documentation/patches.sgml
--
Tony Lambregts
--- patches.old Thu Dec 19 14:35:41 2002 +++ patches.sgml Thu Dec 19 15:16:21 2002 @@ -133,6 +133,42 @@ </para> </listitem> </itemizedlist> + <sect2 id="Inline-Attachments-with-OE"> + <title>Inline attachments with Outlook Express</title> + <para> + Outlook Express is notorious for mangleing attachements. Giving the + patch a <filename>.txt</filename> extention and attaching will solve + the problem for most mailers including Outlook. Also, there is a way + to enable Outlook Express send <filename>.diff</filename> + attachmnets. + </para> + <para> + You need following two things to make it work. + </para> + <orderedlist> + <listitem> + <para> + Make sure that <filename>.diff</filename> files have \r\n line + ends, because if OE detects that there is no \r\n line endings it + switches to quoted-printable format attachments. + </para> + </listitem> + <listitem> + <para> + Using regedit add key "Content Type" with value "text/plain" + to the .diff extension under HKEY_CLASSES_ROOT (same as for .txt + extension). This tells OE to use Content-Type: text/plain instead + of application/octet-stream. + </para> + </listitem> + </orderedlist> + <para> + Item #1 is important. After you hit "Send" button, go to "Outbox" + and using "Properties" verify the message source to make sure that + the mail has correct format. You might want to send several test + emails to yourself too. + </para> + </sect2> </sect1> <sect1 id="patch-quality">