RE: Reply all - issue
authorRobert Mast <beheerder@tekenbeetziekten.nl>
Sat, 2 Feb 2013 16:21:32 +0000 (17:21 +0100)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:53:28 +0000 (09:53 -0800)
3e/4b650da96a8881428c097e05ca14e51b68d96d [new file with mode: 0644]

diff --git a/3e/4b650da96a8881428c097e05ca14e51b68d96d b/3e/4b650da96a8881428c097e05ca14e51b68d96d
new file mode 100644 (file)
index 0000000..765b727
--- /dev/null
@@ -0,0 +1,194 @@
+Return-Path: <beheerder@tekenbeetziekten.nl>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id CD2F3431FB6\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Feb 2013 08:21:44 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.001\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.001 tagged_above=-999 required=5\r
+       tests=[HTML_MESSAGE=0.001] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id AW+EFPuKsLpp for <notmuch@notmuchmail.org>;\r
+       Sat,  2 Feb 2013 08:21:44 -0800 (PST)\r
+Received: from srv047132.webreus.nl (srv047132.webreus.nl [46.235.47.132])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id BE9B2431FAE\r
+       for <notmuch@notmuchmail.org>; Sat,  2 Feb 2013 08:21:43 -0800 (PST)\r
+Received: (qmail 16259 invoked from network); 2 Feb 2013 17:21:40 +0100\r
+Received: from ip73-109-210-87.adsl2.static.versatel.nl (HELO PCvangebruike)\r
+       (87.210.109.73)\r
+       by srv047132.webreus.nl with SMTP; 2 Feb 2013 17:21:37 +0100\r
+From: "Robert Mast" <beheerder@tekenbeetziekten.nl>\r
+To: =?utf-8?Q?'Micha=C5=82_Nazarewicz'?= <mina86@mina86.com>\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl>\r
+       <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>\r
+In-Reply-To:\r
+ <CA+pa1O0mTxkj_FMQH_jXWajmUAKHWbMsB4Yhp_4UX7hnhwgBrg@mail.gmail.com>\r
+Subject: RE: Reply all - issue\r
+Date: Sat, 2 Feb 2013 17:21:32 +0100\r
+Message-ID: <000001ce0161$5da40990$18ec1cb0$@nl>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/alternative;\r
+       boundary="----=_NextPart_000_0001_01CE0169.BF6A4650"\r
+X-Mailer: Microsoft Office Outlook 12.0\r
+Thread-Index: Ac3/oQamHj3hr98TR6O/L7L4p4FCQwBvuYIA\r
+Content-Language: nl\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 02 Feb 2013 16:21:45 -0000\r
+\r
+This is a multi-part message in MIME format.\r
+\r
+------=_NextPart_000_0001_01CE0169.BF6A4650\r
+Content-Type: text/plain;\r
+       charset="utf-8"\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Off course I=E2=80=99ll try not to hinder the current notmuch-users. My =\r
+intent is to even find some support for it.\r
+\r
+=20\r
+\r
+As far as I know Gmail was the great example of threading for the =\r
+SUP-developers, and SUP lead to Notmuch.\r
+\r
+=20\r
+\r
+So Gmail-threading is still the best I suppose, except for git =\r
+send-email-users, which happen to have quite an overlap with the =\r
+developers of nutmuch.\r
+\r
+=20\r
+\r
+Anyone interested in me patching Notmuch, or shall I keep the changes to =\r
+myself?\r
+\r
+=20\r
+\r
+Van: mnazarewicz@gmail.com\r
+=E2=80=A6\r
+\r
+This is a misfeature which only reinforces the incorrect behaviour and =\r
+one of the things I hate about Gmail. As such I hope that at the *very* =\r
+*least* there will be an option to turn this behaviour off.\r
+\r
+\r
+------=_NextPart_000_0001_01CE0169.BF6A4650\r
+Content-Type: text/html;\r
+       charset="utf-8"\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =\r
+xmlns:o=3D"urn:schemas-microsoft-com:office:office" =\r
+xmlns:w=3D"urn:schemas-microsoft-com:office:word" =\r
+xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =\r
+xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =\r
+http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =\r
+name=3DGenerator content=3D"Microsoft Word 12 (filtered =\r
+medium)"><style><!--\r
+/* Font Definitions */\r
+@font-face\r
+       {font-family:"Cambria Math";\r
+       panose-1:2 4 5 3 5 4 6 3 2 4;}\r
+@font-face\r
+       {font-family:Calibri;\r
+       panose-1:2 15 5 2 2 2 4 3 2 4;}\r
+@font-face\r
+       {font-family:Tahoma;\r
+       panose-1:2 11 6 4 3 5 4 4 2 4;}\r
+/* Style Definitions */\r
+p.MsoNormal, li.MsoNormal, div.MsoNormal\r
+       {margin:0cm;\r
+       margin-bottom:.0001pt;\r
+       font-size:12.0pt;\r
+       font-family:"Times New Roman","serif";}\r
+a:link, span.MsoHyperlink\r
+       {mso-style-priority:99;\r
+       color:blue;\r
+       text-decoration:underline;}\r
+a:visited, span.MsoHyperlinkFollowed\r
+       {mso-style-priority:99;\r
+       color:purple;\r
+       text-decoration:underline;}\r
+p\r
+       {mso-style-priority:99;\r
+       mso-margin-top-alt:auto;\r
+       margin-right:0cm;\r
+       mso-margin-bottom-alt:auto;\r
+       margin-left:0cm;\r
+       font-size:12.0pt;\r
+       font-family:"Times New Roman","serif";}\r
+span.E-mailStijl18\r
+       {mso-style-type:personal-reply;\r
+       font-family:"Calibri","sans-serif";\r
+       color:#1F497D;}\r
+.MsoChpDefault\r
+       {mso-style-type:export-only;}\r
+@page WordSection1\r
+       {size:612.0pt 792.0pt;\r
+       margin:70.85pt 70.85pt 70.85pt 70.85pt;}\r
+div.WordSection1\r
+       {page:WordSection1;}\r
+--></style><!--[if gte mso 9]><xml>\r
+<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />\r
+</xml><![endif]--><!--[if gte mso 9]><xml>\r
+<o:shapelayout v:ext=3D"edit">\r
+<o:idmap v:ext=3D"edit" data=3D"1" />\r
+</o:shapelayout></xml><![endif]--></head><body lang=3DNL link=3Dblue =\r
+vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =\r
+lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'>Off course I=E2=80=99ll try not to hinder the current notmuch-users. =\r
+My intent is to even find some support for it.<o:p></o:p></span></p><p =\r
+class=3DMsoNormal><span lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'>As far as I know Gmail was the great example of threading for the =\r
+SUP-developers, and SUP lead to Notmuch.<o:p></o:p></span></p><p =\r
+class=3DMsoNormal><span lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'>So Gmail-threading is still the best I suppose, except for git =\r
+send-email-users, which happen to have quite an overlap with the =\r
+developers of nutmuch.<o:p></o:p></span></p><p class=3DMsoNormal><span =\r
+lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'>Anyone interested in me patching Notmuch, or shall I keep the changes =\r
+to myself?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =\r
+style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=\r
+D'><o:p>&nbsp;</o:p></span></p><div =\r
+style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =\r
+0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =\r
+style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Van:</span><=\r
+/b><span lang=3DEN-US =\r
+style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =\r
+mnazarewicz@gmail.com<br></span><span lang=3DEN-US =\r
+style=3D'color:#1F497D'>=E2=80=A6</span><span =\r
+lang=3DEN-US><o:p></o:p></span></p></div><p><span lang=3DEN-US>This is a =\r
+misfeature which only reinforces the incorrect behaviour and one of the =\r
+t<span style=3D'color:#1F497D'>h</span>ings I hate about Gmail. As such =\r
+I hope that at the *very* *least* there will be an option to turn t<span =\r
+style=3D'color:#1F497D'>h</span>is behaviour =\r
+off.<o:p></o:p></span></p></div></body></html>\r
+------=_NextPart_000_0001_01CE0169.BF6A4650--\r
+\r