replyr 0.0.1

data/test/email_reply_parser/emails/email_1_2.txt

@@ -0,0 +1,51 @@
+Hi,
+On Tue, 2011-03-01 at 18:02 +0530, Abhishek Kona wrote:
+> Hi folks
+> 
+> What is the best way to clear a Riak bucket of all key, values after 
+> running a test?
+> I am currently using the Java HTTP API.
+
+You can list the keys for the bucket and call delete for each. Or if you
+put the keys (and kept track of them in your test) you can delete them
+one at a time (without incurring the cost of calling list first.)
+
+Something like:
+
+        String bucket = "my_bucket";
+        BucketResponse bucketResponse = riakClient.listBucket(bucket);
+        RiakBucketInfo bucketInfo = bucketResponse.getBucketInfo();
+
+        for(String key : bucketInfo.getKeys()) {
+            riakClient.delete(bucket, key);
+        }
+
+
+would do it.
+
+See also
+
+http://wiki.basho.com/REST-API.html#Bucket-operations
+
+which says
+
+"At the moment there is no straightforward way to delete an entire
+Bucket. There is, however, an open ticket for the feature. To delete all
+the keys in a bucket, you'll need to delete them all individually."
+
+> 
+> -Abhishek Kona
+> 
+> 
+> _______________________________________________
+> riak-users mailing list
+> riak-users@lists.basho.com
+> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
+
+
+
+
+_______________________________________________
+riak-users mailing list
+riak-users@lists.basho.com
+http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

data/test/email_reply_parser/emails/email_1_3.txt

@@ -0,0 +1,55 @@
+Oh thanks.
+
+Having the function would be great.
+
+-Abhishek Kona
+
+On 01/03/11 7:07 PM, Russell Brown wrote:
+> Hi,
+> On Tue, 2011-03-01 at 18:02 +0530, Abhishek Kona wrote:
+>> Hi folks
+>>
+>> What is the best way to clear a Riak bucket of all key, values after
+>> running a test?
+>> I am currently using the Java HTTP API.
+> You can list the keys for the bucket and call delete for each. Or if you
+> put the keys (and kept track of them in your test) you can delete them
+> one at a time (without incurring the cost of calling list first.)
+>
+> Something like:
+>
+>          String bucket = "my_bucket";
+>          BucketResponse bucketResponse = riakClient.listBucket(bucket);
+>          RiakBucketInfo bucketInfo = bucketResponse.getBucketInfo();
+>
+>          for(String key : bucketInfo.getKeys()) {
+>              riakClient.delete(bucket, key);
+>          }
+>
+>
+> would do it.
+>
+> See also
+>
+> http://wiki.basho.com/REST-API.html#Bucket-operations
+>
+> which says
+>
+> "At the moment there is no straightforward way to delete an entire
+> Bucket. There is, however, an open ticket for the feature. To delete all
+> the keys in a bucket, you’ll need to delete them all individually."
+>
+>> -Abhishek Kona
+>>
+>>
+>> _______________________________________________
+>> riak-users mailing list
+>> riak-users@lists.basho.com
+>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
+>
+
+
+_______________________________________________
+riak-users mailing list
+riak-users@lists.basho.com
+http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

data/test/email_reply_parser/emails/email_1_4.txt

@@ -0,0 +1,5 @@
+Awesome! I haven't had another problem with it.
+
+On Aug 22, 2011, at 7:37 PM, defunkt<reply@reply.github.com> wrote:
+
+> Loader seems to be working well.

data/test/email_reply_parser/emails/email_1_5.txt

@@ -0,0 +1,15 @@
+One: Here's what I've got.
+
+- This would be the first bullet point that wraps to the second line
+to the next
+- This is the second bullet point and it doesn't wrap
+- This is the third bullet point and I'm having trouble coming up with enough
+to say
+- This is the fourth bullet point
+
+Two:
+- Here is another bullet point
+- And another one
+
+This is a paragraph that talks about a bunch of stuff. It goes on and on
+for a while.

data/test/email_reply_parser/emails/email_1_6.txt

@@ -0,0 +1,15 @@
+I get proper rendering as well.
+
+Sent from a magnificent torch of pixels
+
+On Dec 16, 2011, at 12:47 PM, Corey Donohoe
+<reply@reply.github.com>
+wrote:
+
+> Was this caching related or fixed already?  I get proper rendering here.
+>
+> ![](https://img.skitch.com/20111216-m9munqjsy112yqap5cjee5wr6c.jpg)
+>
+> ---
+> Reply to this email directly or view it on GitHub:
+> https://github.com/github/github/issues/2278#issuecomment-3182418

data/test/email_reply_parser/emails/email_1_7.txt

@@ -0,0 +1,12 @@
+:+1:
+
+On Tue, Sep 25, 2012 at 8:59 AM, Chris Wanstrath
+<notifications@github.com>wrote:
+
+> Steps 0-2 are in prod. Gonna let them sit for a bit then start cleaning up
+> the old code with 3 & 4.
+>
+> 
+> Reply to this email directly or view it on GitHub.
+>
+>

data/test/email_reply_parser/emails/email_1_8.txt

@@ -0,0 +1,6 @@
+Hello
+
+2013/1/31 Lawrence Pit <lawrence.pit@example.com>
+
+> bailter space
+> flying nun

data/test/email_reply_parser/emails/email_1_9.txt

@@ -0,0 +1,9 @@
+Foo
+
+ -Abhishek Kona
+
+
+_______________________________________________
+riak-users mailing list
+riak-users@lists.basho.com
+http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

data/test/email_reply_parser/emails/email_2_1.txt

@@ -0,0 +1,25 @@
+Outlook with a reply
+
+
+ ------------------------------
+
+*From:* Google Apps Sync Team [mailto:mail-noreply@google.com]
+*Sent:* Thursday, February 09, 2012 1:36 PM
+*To:* jow@xxxx.com
+*Subject:* Google Apps Sync was updated!
+
+
+
+Dear Google Apps Sync user,
+
+Google Apps Sync for Microsoft Outlook® was recently updated. Your computer
+now has the latest version (version 2.5). This release includes bug fixes
+to improve product reliability. For more information about these and other
+changes, please see the help article here:
+
+http://www.google.com/support/a/bin/answer.py?answer=153463
+
+Sincerely,
+
+The Google Apps Sync Team.
+

data/test/email_reply_parser/emails/email_2_2.txt

@@ -0,0 +1,10 @@
+Outlook with a reply directly above line
+________________________________________
+From: CRM Comments [crm-comment@example.com]
+Sent: Friday, 23 March 2012 5:08 p.m.
+To: John S. Greene
+Subject: [contact:106] John Greene
+
+A new comment has been added to the Contact named 'John Greene':
+
+I am replying to a comment.

data/test/email_reply_parser/emails/email_2_3.txt

@@ -0,0 +1,14 @@
+This one is from Windows 8 Mail (preview).
+
+Sent from my Windows 8 PC <http://windows.microsoft.com/consumer-preview>
+
+ *From:* Lord Nelson <bignelly@theadmiralty.com>
+*Sent:* Monday, August 20, 2012 5:08:34 PM
+*To:* boo@example.com
+*Subject:* The Royal Navy=92s Ships are like women
+
+
+My dreams are haunting with visions of lithe ships dancing over the waves,
+beckoning me to lie with them.
+
+=93MAKE IT STOP!=94

data/test/email_reply_parser/emails/email_2_4.txt

@@ -0,0 +1,14 @@
+Here's one from Outlook 2007.
+
+
+
+From: bigboo@example.com [mailto:bigboo@example.com]
+Sent: Monday, August 20, 2012 8:46 PM
+To: lilboo@example.com
+Subject: Somebody’s got the hoots
+
+
+
+I am going to include some emoji here because, well, that's what people do.
+
+“🐶”

data/test/email_reply_parser/emails/email_2_5.txt

@@ -0,0 +1,15 @@
+One from Outlook 2013?
+
+
+From: Gmail Team [mailto:gmail-noreply@google.com]
+Sent: None
+To: Mickey Bonk
+Subject: Gmail is different. Here's what you need to know.
+
+Didn't have the patience to wait for Outlook 2013 to sync my Gmail, but
+above is a reply to a different message.
+
+First off, welcome. And thanks for agreeing to help us test Gmail. By now
+you probably know the key ways in which Gmail differs from traditional
+webmail services. Searching instead of filing. A free gigabyte of storage.
+Messages displayed in context as conversations.

data/test/email_reply_parser/emails/email_2_6.txt

@@ -0,0 +1,11 @@
+Reply from the hottest mail.
+
+Date: Wed, 15 Aug 2012 17:46:32 -0700 
+From: mork@example.com 
+To: mindy@hotmail.com 
+Subject: Here's a long subject line that will likely be broken at some point
+and wrap to the next line.
+
+I'm moving into the master bedroom.
+
+Deal with it.

data/test/email_reply_parser/emails/email_2_7.txt

@@ -0,0 +1,5 @@
+Foo
+
+-------- Original Message --------
+
+THE END.

data/test/email_reply_parser/emails/email_2_7_1.txt

@@ -0,0 +1,5 @@
+Foo
+
+-------- Reply Message --------
+
+THE END.

data/test/email_reply_parser/emails/email_2_7_de.txt

@@ -0,0 +1,5 @@
+Foo
+
+-------- Ursrpüngliche Nachricht --------
+
+THE END.

data/test/email_reply_parser/emails/email_2_8.txt

@@ -0,0 +1,3 @@
+Hello
+-- 
+Rick

data/test/email_reply_parser/emails/email_2_9.txt

@@ -0,0 +1,9 @@
+Hello
+
+Mr Rick Olson
+Galactic President Superstar Mc Awesomeville
+GitHub
+
+**********************DISCLAIMER***********************************
+* Note: blah blah blah                                            *
+**********************DISCLAIMER***********************************

data/test/email_reply_parser/emails/email_2nd_paragraph_starting_with_on.txt

@@ -0,0 +1,12 @@
+This emails tests that multiline header fix isn't catching things it shouldn't.
+
+On friday when I tried it didn't work as expect.
+
+This line would have been considered part of the header line.
+
+On Wed, Apr 4, 2012 at 9:32 AM, Bob Jones <bjones@gmail.com> wrote:
+> We are still very interested in achievements you’ve had from participating
+> in our initiative.  When you have a chance, please reply to this
+> email and describe what you have done.
+>
+

data/test/email_reply_parser/emails/email_BlackBerry.txt

@@ -0,0 +1,3 @@
+Here is another email
+
+Sent from my BlackBerry

data/test/email_reply_parser/emails/email_bullets.txt

@@ -0,0 +1,22 @@
+test 2 this should list second
+
+and have spaces
+
+and retain this formatting
+
+
+   - how about bullets
+   - and another
+
+
+On Fri, Feb 24, 2012 at 10:19 AM, <examples@email.goalengine.com> wrote:
+
+> Give us an example of how you applied what they learned to achieve
+> something in your organization
+
+
+
+
+-- 
+
+*Joe Smith | Director, Product Management*

data/test/email_reply_parser/emails/email_from_address_in_quote_header.txt

@@ -0,0 +1,12 @@
+I have gained valuable experience from working with students from other cultures. They bring a significantly different perspective to the work we do. I have also had the opportunity to practice making myself very clear in discussion, so that everyone understands. I've also seen how different our culture is to them, in their reactions to what I think is a normal approach to assignments, and to life in general.
+
+
+Date: Tue, 2 Oct 2012 02:35:10 +0000 
+From: john@example.com 
+To: shelly@example.com 
+Subject: Tell us what you learned.
+
+
+
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_from_name_in_quote_header.txt

@@ -0,0 +1,12 @@
+I have gained valuable experience from working with students from other cultures. They bring a significantly different perspective to the work we do. I have also had the opportunity to practice making myself very clear in discussion, so that everyone understands. I've also seen how different our culture is to them, in their reactions to what I think is a normal approach to assignments, and to life in general.
+
+
+Date: Tue, 2 Oct 2012 02:35:10 +0000 
+From: john@example.com 
+To: Smith, Shelly 
+Subject: Tell us what you learned.
+
+
+
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_hyphens.txt

@@ -0,0 +1,5 @@
+Keep in mind that while scientific meetings of large medical societies allow for researchers and doctors to gather in one place to discuss hundreds, if not thousands, of new findings, what’s often presented may not pass muster for publication in prestigious medical journals, where they first undergo rigorous peer review. Addendum --
+
+A Danish study drawing a lot of attention, but which has not yet published in a peer-reviewed journal, suggested that common signs of aging can predict a person’s heart disease risk. The researchers analyzed data from nearly 11,000 participants over age 40 in the Copenhagen Heart Study and found that those who had three to four aging signs at the beginning of the study -- such as a receding hairline, baldness at the top of the head, creases in the earlobes, and fatty deposits around the eye -- had a 57 percent increased risk of having a heart attack and a 39 percent increased risk of being diagnosed with heart disease during the 35-year study compared with those who had none of them.
+
+“The visible signs of aging reflect physiologic or biological age, not chronological age,” the study’s senior author, Dr. Anne Tybjaerg--Hansen at the University of Copenhagen, said in a statement on the Heart Association’s website. She went on to recommend that doctors check for these aging signs as a “routine part” of their physical exam.

data/test/email_reply_parser/emails/email_iPhone.txt

@@ -0,0 +1,3 @@
+Here is another email
+
+Sent from my iPhone

data/test/email_reply_parser/emails/email_iPhone_de.txt

@@ -0,0 +1,3 @@
+Here is another email
+
+Von meinem iPhone gesendet

data/test/email_reply_parser/emails/email_iPhone_de_2.txt

@@ -0,0 +1,3 @@
+Here is another email
+
+Gesendet von meinem iPhone

data/test/email_reply_parser/emails/email_mentions_own_email_address.txt

@@ -0,0 +1,6 @@
+Hi, 
+
+My email is john.smith@gmail.com and I had a question.  
+
+What do you do?
+

data/test/email_reply_parser/emails/email_mentions_own_name.txt

@@ -0,0 +1,6 @@
+Hi, 
+
+My name is Jim Smith and I had a question.  
+
+What do you do?
+

data/test/email_reply_parser/emails/email_multi_word_sent_from_my_mobile_device.txt

@@ -0,0 +1,3 @@
+Here is another email
+
+Sent from my Verizon Wireless BlackBerry

data/test/email_reply_parser/emails/email_multiline_quote_header_de_mx.txt

@@ -0,0 +1,8 @@
+Foo!
+
+Von: Michael Tester [mailto:michael@example.de] 
+Gesendet: Samstag, 9. November 2013 10:04 
+An: stef@example.de 
+Betreff: Kein Betreff
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_es_mx.txt

@@ -0,0 +1,8 @@
+Foo!
+
+De: john@example.com
+Para: shelly@example.com
+Fecha: 01/02/2013 05:04 p.m.
+Asunto: Requerimiento #12345
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_fr.txt

@@ -0,0 +1,8 @@
+Foo!
+
+De: john@example.com
+A: shelly@example.com
+Date: 01/02/2013 05:04 p.m.
+Objet: Requerimiento #12345
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_from_first.txt

@@ -0,0 +1,11 @@
+I have gained valuable experience from working with students from other cultures. They bring a significantly different perspective to the work we do. I have also had the opportunity to practice making myself very clear in discussion, so that everyone understands. I've also seen how different our culture is to them, in their reactions to what I think is a normal approach to assignments, and to life in general.
+
+From: john@example.com 
+Sent: Tue, 2 Oct 2012 02:35:10 +0000 
+To: shelly@example.com 
+Subject: Tell us what you learned.
+
+
+
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_from_replyto_date_to_subject.txt

@@ -0,0 +1,12 @@
+Foo!
+
+From: john@example.com 
+Reply-To: john@example.com
+Sent: Tue, 2 Oct 2012 02:35:10 +0000 
+To: shelly@example.com 
+Subject: Tell us what you learned.
+
+
+
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_from_to_date_subject.txt

@@ -0,0 +1,11 @@
+Foo!
+
+From: john@example.com 
+To: shelly@example.com 
+Date: Tue, 2 Oct 2012 02:35:10 +0000 
+Subject: Tell us what you learned.
+
+
+
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_none.txt

@@ -0,0 +1,11 @@
+Foo
+
+De: john@example.com
+Para: shelly@example.com
+NotExists: hello
+De: john@example.com
+Para: shelly@example.com
+Fecha: 01/02/2013 05:04 p.m.
+Asunto: Requerimiento #12345
+
+THE END!

data/test/email_reply_parser/emails/email_multiline_quote_header_pt_br.txt

@@ -0,0 +1,8 @@
+Foo-pt-br
+
+De: john@example.com
+Enviada em: sexta-feira, 27 de julho de 2012 15:09
+Para: shelly@example.com 
+Assunto: Tell us what you learned.
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_with_asterisks.txt

@@ -0,0 +1,21 @@
+Outlook with a reply
+
+ *From:* Google Apps Sync Team [mailto:mail-noreply@google.com]
+*Sent:* Thursday, February 09, 2012 1:36 PM
+*To:* jow@xxxx.com
+*Subject:* Google Apps Sync was updated!
+
+
+Dear Google Apps Sync user,
+
+Google Apps Sync for Microsoft Outlook® was recently updated. Your computer
+now has the latest version (version 2.5). This release includes bug fixes
+to improve product reliability. For more information about these and other
+changes, please see the help article here:
+
+http://www.google.com/support/a/bin/answer.py?answer=153463
+
+Sincerely,
+
+The Google Apps Sync Team.
+

data/test/email_reply_parser/emails/email_multiline_quote_header_with_cc.txt

@@ -0,0 +1,9 @@
+Foo
+
+De: john@example.com
+Para: shelly@example.com
+cc: esther@example.com
+Fecha: 01/02/2013 05:04 p.m.
+Asunto: Requerimiento #12345
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_multiline_quote_header_with_multiline_headers.txt

@@ -0,0 +1,14 @@
+Foo
+
+Subject: 	[ERROR] Example unavailable: 
+(ExampleClassName::SomeError) "Etiam dignissim imperdiet metus.
+error, unexpected $duh near 't'"
+Date: 	Fri, 01 Feb 2013 07:50:06 +0000
+cc: esther@example.com
+            mathias@example.com
+ok@example.com
+From: 	Application Error <noreply@example.com>
+Reply-To: 	Example <noreply@example.com>
+To: 	alert@example.com
+
+Thank you for recently participating in our class. We're interested in feedback. Please reply to this email. 

data/test/email_reply_parser/emails/email_no_signature_deliminator.txt

@@ -0,0 +1,7 @@
+I don't like putting any delimiator in my signature because I think that is cool.  
+
+Really it is.
+
+Jim Smith | Enrollment Manager
+XYZ Corp
+

data/test/email_reply_parser/emails/email_no_signature_deliminator_adds_a_middle_initial.txt

@@ -0,0 +1,7 @@
+I don't like putting any delimiator in my signature because I think that is cool.  
+
+Really it is.
+
+Jim P. Smith | Enrollment Manager
+XYZ Corp
+

data/test/email_reply_parser/emails/email_one_is_not_on.txt

@@ -0,0 +1,10 @@
+Thank, this is really helpful.
+
+One outstanding question I had:
+
+Locally (on development), when I run...
+
+On Oct 1, 2012, at 11:55 PM, Dave Tapley wrote:
+
+> The good news is that I've found a much better query for lastLocation.
+>

data/test/email_reply_parser/emails/email_sent_from_my_not_signature.txt

@@ -0,0 +1,3 @@
+Here is another email
+
+Sent from my desk, is much easier then my mobile phone.

data/test/email_reply_parser/emails/email_was_showing_as_nothing_visible.txt

@@ -0,0 +1,13 @@
+On Friday, one achievement I had was learning a new technology that allows us
+to keep UI elements and events separated from the software on the
+server side, which should allow for more flexible UI code and
+decreased chances of code becoming a swarm of angry hornets.  I've
+been transparent about the initial increased development time while
+learning the technology.
+
+On Wed, Apr 4, 2012 at 9:32 AM, Bob Jones <bjones@gmail.com> wrote:
+> We are still very interested in achievements you’ve had from participating
+> in our initiative.  When you have a chance, please reply to this
+> email and describe what you have done.
+>
+

data/test/email_reply_parser/emails/new_content/email_1_2.txt

@@ -0,0 +1,28 @@
+Hi,
+
+You can list the keys for the bucket and call delete for each. Or if you
+put the keys (and kept track of them in your test) you can delete them
+one at a time (without incurring the cost of calling list first.)
+
+Something like:
+
+        String bucket = "my_bucket";
+        BucketResponse bucketResponse = riakClient.listBucket(bucket);
+        RiakBucketInfo bucketInfo = bucketResponse.getBucketInfo();
+
+        for(String key : bucketInfo.getKeys()) {
+            riakClient.delete(bucket, key);
+        }
+
+
+would do it.
+
+See also
+
+http://wiki.basho.com/REST-API.html#Bucket-operations
+
+which says
+
+"At the moment there is no straightforward way to delete an entire
+Bucket. There is, however, an open ticket for the feature. To delete all
+the keys in a bucket, you'll need to delete them all individually."