Skip to content
Snippets Groups Projects
Commit f25dd6e8 authored by Karl Fogel's avatar Karl Fogel
Browse files

Add test data for a WIP bugfix

While this new test data is ready, the bug that it reproduces is not
yet fixed.  Therefore the test data has a ".wip" suffix, so it won't
be included in the default './check' run.  We'll remove that suffix
when we fix the bug.  To reproduce the bug, do

  $ ./mailaprop.py --suppress-header              \
    < test-data/bonkers-backslashes-etc.mbox.wip  \
    > foo.out

followed by `(mailaprop-reload-addresses "foo.out")' in Emacs, and you
should see an error that looks something like this:

  +: Wrong type argument: number-or-marker-p, " \
  <someone@michaellacroix.com> <levinson@domaintwo.edu>"
parent 449c200e
No related branches found
No related tags found
No related merge requests found
From jrsender@sender.example.com Sat Dec 24 15:19:08 2011
Message-ID: <1324752864.68726.YahooMailNeo@web36708.mail.mud.yahoo.com>
Date: Sat, 24 Dec 2011 10:54:24 -0800 (PST)
From: J. Random Sender <jrsender@sender.example.com>
Subject: Wikman on WGN Radio: Time Correction
To: "\"leifer@domainone.com\"" <leifer@domainone.com>,
"\"levinson@domaintwo.edu\"" <levinson@domaintwo.edu>
Cc: "To: \"someone@michaellacroix.com\"" <someone@michaellacroix.com>,
"\"michael@example.com\"" <michael@example.com>,
"\"kfogel@example.com\"" <kfogel@example.com>,
"\"someone@uic.edu\"" <someone@uic.edu>,
"\"jrandom@gexample.com\" Cc: \"jrandom@binnys.com\" <jrandom@binnys.com>" <jrandom@gexample.com>,
"\"victoria@domainthree.com\"" <victoria@domainthree.com>,
"\"singsbach@anotherdomain.com\"" <singsbach@anotherdomain.com>,
"To: \"misha@gexample.com\"" <misha@gexample.com>,
"\"jaaron@gexample.com\"" <jaaron@gexample.com>,
"\"hankam@domainone.com\"" <hankam@domainone.com>,
"\"jrandom108@examplehoo.com\" Cc: \"jrandom@examplemsn.com\" <jrandom@examplemsn.com>" <jrandom108@examplehoo.com>,
"\"jbob@aolexample.com\"" <jbob@aolexample.com>,
"\"jordan@gexample.com\"" <jordan@gexample.com>
This is derived from ~/mail/andrea-holliday/21.gz. In addition to the
backslash whackage, notice the interspersed "CC:" and "To:" strings
*within* the actual Cc: field. This message's recipient headers are
indeed well and truly whacked.
In both this email and the next one, I've tried to preserve the
structure of the weirdness, while removing large numbers of addresses
that had basically the same format (and so shouldn't make any
difference) and pseudonymizing the rest.
From jrsender@sender.example.com Thu Dec 29 20:58:14 2011
Message-ID: <1325207237.36447.YahooMailNeo@web36707.mail.mud.yahoo.com>
Date: Thu, 29 Dec 2011 17:07:17 -0800 (PST)
From: J. Random Sender <jrsender@sender.example.com>
Subject: On Demand: Wikman Christmas Podcast
To: "\"\"jdolly@sbcglobal.net\"\"" <jdolly@sbcglobal.net>,
"\"\"jkozolek@someacademy.com\" Cc: \"jviola@sbcglobal.net\" \" <jkozolek@someacademy.com>" <jviola@sbcglobal.net>,
"\"\"leifer@mac.com\"\"" <leifer@mac.com>,
"\"\"levinson@domaintwo.edu\"\" Cc: \"To: \"someone@michaellacroix.com\"\" <someone@michaellacroix.com>" <levinson@domaintwo.edu>,
"\"\"kfogel@example.com\"\"" <kfogel@example.com>,
"\"\"someone@uic.edu\"\"" <someone@uic.edu>,
"\"\"jrandom@gexample.com\" Cc: \"jrandom@binnys.com\" \" <jrandom@gexample.com>" <jrandom@binnys.com>,
"\"\"singsbach@anotherdomain.com\"\"" <singsbach@anotherdomain.com>,
"\"To: \"misha@gexample.com\"\"" <misha@gexample.com>,
"\"\"jaaron@gexample.com\"\"" <jaaron@gexample.com>,
"\"\"hankam@domainone.com\"\"" <hankam@domainone.com>,
"\"\"jrandom108@examplehoo.com\" Cc: \"jrandom@examplemsn.com\" \" <jrandom108@examplehoo.com>" <jrandom@examplemsn.com>,
"\"\"jbob@aolexample.com\"\"" <jbob@aolexample.com>,
"\"\"jordan@gexample.com\"\"" <jordan@gexample.com>
Cc: j j <jarvis@examplecast.com>, j miller <jmiller@examplecast.com>
This is derived from ~/mail/andrea-holliday/23.gz. In addition to the
sharing all the whackage of the previous message, this one also has
that weird standalone \" on the second line of the To: header. That's
why I included this message in addition to the previous one.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment