sisimai 4.14.2

data/set-of-emails/maildir/bsd/surfcontrol-01.eml

@@ -0,0 +1,79 @@
+Return-Path: <>
+X-Original-To: shironeko@example.jp
+Delivered-To: shironeko@example.jp
+Received: from localhost (localhost [127.0.0.1])
+    by mx4.example.co.jp (Postfix) with ESMTP id 00000000000
+    for <shironeko@example.jp>; Thu 29 Apr 2010 23:34:45 +0900 (JST)
+Received: from mx4.example.co.jp ([127.0.0.1])
+    by localhost (example.jp [127.0.0.1]) (amavisd-new, port 10000)
+    with ESMTP id 000000000000 for <shironeko@example.jp>;
+    Thu 29 Apr 2010 23:34:45 +0900 (JST)
+Received: from mx4.example.com (mx4.example.com [192.0.2.80])
+    by mx4.example.co.jp (Postfix) with ESMTP id 00000000000
+    for <shironeko@example.jp>; Thu 29 Apr 2010 23:34:45 +0900 (JST)
+From: <MAILER-DAEMON@example.com>
+To: <shironeko@example.jp>
+Date: Thu 29 Apr 2010 23:34:45 +0900
+Subject: Nyaaan
+X-Mailer: SurfControl E-mail Filter
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="--=_NextPart_XX_23_34_45_Thursday_April_29_2010_00000"
+X-SEF-0000000-0000-0000-0000-000000000000: 1
+X-SEF-NDR-0000000-0000-0000-0000-000000000000: 1
+X-SEF-ZeroHour-RefID: fgs=000000000
+X-SEF-Processed: 0_0_0_000__2010_04_29_23_34_45
+Message-Id: <20100429233445.00000000000@mx4.example.co.jp>
+
+
+----=_NextPart_XX_23_34_45_Thursday_April_29_2010_00000
+Content-Type: text/plain;
+
+Your message could not be sent.
+A transcript of the attempts to send the message follows.
+The number of attempts made: 1
+Addressed To: kijitora@example.com
+
+Thu 29 Apr 2010 23:34:45 +0900
+Failed to send to identified host,
+kijitora@example.com: [192.0.2.5], 550 kijitora@example.com... No such user
+--- Message non-deliverable.
+
+
+
+----=_NextPart_XX_23_34_45_Thursday_April_29_2010_00000
+Content-Type: message/delivery-status;
+
+
+Action: failed
+Final-Recipient: rfc822;kijitora@example.com
+Diagnostic-Code: smtp; 550 kijitora@example.com... No such user
+Status: 5.0.0
+
+
+
+
+----=_NextPart_XX_23_34_45_Thursday_April_29_2010_00000
+Content-Type: message/rfc822;
+
+Received: from Unknown [192.0.2.54] by mx4.example.com - SurfControl E-mail Filter (6.0.1); 
+    Thu 29 Apr 2010 23:34:45 +0900
+Received: from localhost (localhost [127.0.0.1])
+    by mx4.example.co.jp (Postfix) with ESMTP id 00000000000
+    for <kijitora@example.com>; Thu 29 Apr 2010 23:34:45 +0900 (JST)
+Received: by mx4.example.co.jp (Postfix, from userid 525)
+    id 00000000000; Thu 29 Apr 2010 23:34:45 +0900 (JST)
+To: <kijitora@example.com>
+Subject: Nyaaan
+From: "Shironeko" <shironeko@example.jp>
+Date: Thu 29 Apr 2010 23:34:45 +0900
+Content-Type: text/plain; charset="utf-8";
+MIME-Version: 1.0
+Message-Id: <20100429233445.00000000000@mx4.example.co.jp>
+X-SEF-0000000-0000-0000-0000-000000000000: 1
+X-SEF-ZeroHour-RefID: fgs=0
+X-SEF-Processed: 0_0_0_000__2010_04_29_23_34_45
+
+Nyaaa
+----=_NextPart_XX_23_34_45_Thursday_April_29_2010_00000--
+

data/set-of-emails/maildir/bsd/surfcontrol-02.eml

@@ -0,0 +1,70 @@
+Return-Path: <>
+X-Original-To: shironeko@example.co.jp
+Delivered-To: shironeko@example.co.jp
+Received: from mx4.example.co.jp (localhost.localdomain [127.0.0.1])
+    by mx4.example.co.jp (Postfix) with ESMTP id 00000000000
+    for <shironeko@example.co.jp>; Thu, 29 Apr 2009 23:34:45 +0900 (JST)
+Received: from relay1.ext.example.org (relay1.example.org [192.0.2.244])
+	by mx4.example.co.jp (Postfix) with ESMTP id 00000000000
+	for <shironeko@example.co.jp>; Thu, 29 Apr 2009 23:34:45 +0900 (JST)
+X-SEF-Processed: 0_0_0_429__2009_04_29_23_34_45
+X-SEF-NDR-0000000-0000-0000-0000-000000000000: 1
+X-SEF-0000000-0000-0000-0000-000000000000: 1
+From: <>
+To: <shironeko@example.co.jp>
+Date: Thu, 29 Apr 2009 23:34:45 +0900
+Subject: Nyaan
+X-Mailer: SurfControl E-mail Filter
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+    boundary="--=_NextPart_ST_00_00_00_Thursday_April_29_2009_00000"
+Message-Id: <20090429233445.00000000000@mx4.example.co.jp>
+
+
+----=_NextPart_ST_00_00_00_Thursday_April_29_2009_00000
+Content-Type: text/plain;
+
+Your message could not be sent.
+A transcript of the attempts to send the message follows.
+The number of attempts made: 1
+Addressed To: kijitora@example.org
+
+Thu, 29 Apr 2009 23:34:45 +0900
+Failed to send to identified host,
+kijitora@example.org: [192.0.2.244], 554 Service currently unavailable
+--- Message non-deliverable.
+
+
+
+----=_NextPart_ST_00_00_00_Thursday_April_29_2009_00000
+Content-Type: message/delivery-status;
+
+
+Action: failed
+Final-Recipient: rfc822;kijitora@example.org
+Diagnostic-Code: smtp; 554 Service currently unavailable
+Status: 5.0.0
+
+
+
+
+----=_NextPart_ST_00_00_00_Thursday_April_29_2009_00000
+Content-Type: message/rfc822;
+
+X-SEF-Processed: 0_0_0_000__2009_04_29_23_34_45
+X-SEF-0000000-0000-0000-0000-000000000000: 1
+Received: from unknown [192.0.2.230] by relay1.ext.example.org - SurfControl E-mail Filter ;
+    Thu, 29 Apr 2009 23:34:45 +0900
+Received: by bbx.example.co.jp (Postfix, from userid 25)
+    id 00000000000; Thu, 29 Apr 2009 23:34:45 +0900 (JST)
+Content-Type: text/plain
+MIME-Version: 1.0
+Date: Thu, 29 Apr 2009 23:34:45
+From: Shironeko <shironeko@example.co.jp>
+To: kijitora@example.org
+Message-Id: <20090429233455.99999999999@example.co.jp>
+Subject: Nyaan
+
+Nyaaan
+----=_NextPart_ST_00_00_00_Thursday_April_29_2009_00000--
+

data/set-of-emails/maildir/bsd/surfcontrol-03.eml

@@ -0,0 +1,70 @@
+Return-Path: <>
+X-Original-To: shironeko@example.jp
+Delivered-To: shironeko@example.jp
+Received: from mx03.example.jp (localhost.localdomain [127.0.0.1])
+	by mx03.example.jp (Postfix) with ESMTP id FFFFF0000000
+	for <shironeko@example.jp>; Thu, 20 Apr 2008 23:34:45 +0900 (JST)
+Received: from f0.mx4.example.net (f0.example.net [192.0.2.2])
+	by mx03.example.jp (Postfix) with ESMTP id ff000000000
+	for <shironeko@example.jp>; Thu, 20 Apr 2008 23:34:45 +0900 (JST)
+X-SEF-Processed: 0_0_0_000__2008_04_20_23_34_45
+X-SEF-NDR-0000000-0000-0000-0000-000000000000: 1
+X-SEF-0000000-0000-0000-0000-000000000000: 1
+From: <>
+To: <shironeko@example.jp>
+Date: Thu, 20 Apr 2008 23:34:45 -0600
+Subject: X
+Message-Id: <20080420000000.ff000000000@mx03.example.jp>
+X-Mailer: SurfControl E-mail Filter
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status;
+	boundary="--=_NextPart_ST_00_00_00_Thursday_April_20_2008_00000"
+X-Virus-Scanned: ClamAV using ClamSMTP
+
+
+----=_NextPart_ST_00_00_00_Thursday_April_20_2008_00000
+Content-Type: text/plain;
+
+Your message could not be sent.
+A transcript of the attempts to send the message follows.
+The number of attempts made: 1
+Addressed To: kijitora@example.net
+
+Thu, 20 Apr 2008 23:34:45 +0900
+Failed to send to identified host,
+kijitora@example.net: [192.0.2.2], 554 Service currently unavailable
+--- Message non-deliverable.
+
+
+
+----=_NextPart_ST_00_00_00_Thursday_April_20_2008_00000
+Content-Type: message/delivery-status;
+
+
+Action: failed
+Final-Recipient: rfc822;kijitora@example.net
+Diagnostic-Code: smtp; 554 Service currently unavailable
+Status: 5.0.0
+
+
+
+
+----=_NextPart_ST_00_00_00_Thursday_April_20_2008_00000
+Content-Type: message/rfc822;
+
+X-SEF-Processed: 0_0_0_000__2008_04_20_23_34_45
+X-SEF-0000000-0000-0000-0000-000000000000: 1
+Received: from host [192.0.2.120] by f0.mx4.example.net - SurfControl E-mail Filter ; Thu, 20 Apr 2008 23:34:45 +0900
+Received: by mx9.example.jp (Postfix, from userid 525)
+	id 000000000000 Thu, 20 Apr 2008 23:34:45 +0900 (JST)
+Content-Type: text/plain
+MIME-Version: 1.0
+Date: Thu, 20 Apr 2008 23:34:45 UT
+From: Sender <shironeko@example.jp>
+Message-Id: <00000000000000000000@x.example.jp>
+Reply-To: <shironeko@example.jp>
+To: kijitora@example.net
+Subject: Nyaaan
+
+Nyaan
+

data/set-of-emails/maildir/bsd/uk-messagelabs-01.eml

@@ -0,0 +1,76 @@
+Received: from [85.158.137.35] by server-17.bemta-3.messagelabs.com id A1/BA-11608-703D9945; Tue, 23 Dec 2014 20:39:35 +0000
+X-Msg-Ref: server-11.tower-143.messagelabs.com!1419367175!36473369!1
+X-Originating-IP: [10.245.230.38]
+X-StarScan-Received:
+X-StarScan-Version: 6.12.5; banners=-,-,-
+X-VirusChecked: Checked
+Received: (qmail 21907 invoked from network); 23 Dec 2014 20:39:35 -0000
+Received: from mail5.bemta3.messagelabs.com (HELO mail5.bemta3.messagelabs.com) (10.245.230.38)
+  by server-11.tower-143.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Dec 2014 20:39:35 -0000
+Received: by server-15.bemta-3.messagelabs.com id 5E/3F-17735-703D9945; Tue, 23 Dec 2014 20:39:35 +0000
+From: Mail Delivery System <MAILER-DAEMON@messagelabs.com>
+To: <user@xxxxxxxxxxxxxx.com>
+Subject: Mail Delivery Failure
+Date: Tue, 23 Dec 2014 20:39:35 +0000
+Content-Type: multipart/report; report-type=delivery-status;
+  boundary="b0Nvs+XKfKLLRaP/Qo8jZhQPoiqeWi3KWPXMgw=="
+
+--b0Nvs+XKfKLLRaP/Qo8jZhQPoiqeWi3KWPXMgw==
+Content-Type: text/plain; charset="UTF-8"
+Content-Transfer-Encoding: quoted-printable
+
+This is the mail delivery agent at messagelabs.com.
+
+I was unable to deliver your message to the following addresses:
+
+maria@dest.example.net
+
+Reason: 550 maria@dest.example.net... No such user
+
+The message subject was: Re: BOAS FESTAS!
+The message date was: Tue, 23 Dec 2014 20:39:24 +0000
+The message identifier was: DB/3F-17375-60D39495
+The message reference was: server-5.tower-143.messagelabs.com!1419367172!32=
+691968!1
+
+Please do not reply to this email as it is sent from an unattended mailbox.
+Please visit www.messagelabs.com/support for more details
+about this error message and instructions to resolve this issue.
+
+
+--b0Nvs+XKfKLLRaP/Qo8jZhQPoiqeWi3KWPXMgw==
+Content-Type: message/delivery-status
+
+Reporting-MTA: dns; server-15.bemta-3.messagelabs.com
+Arrival-Date: Tue, 23 Dec 2014 20:39:34 +0000
+
+Action: failed
+Status: 5.0.0
+Last-Attempt-Date: Tue, 23 Dec 2014 20:39:35 +0000
+Remote-MTA: dns; mail.dest.example.net
+Diagnostic-Code: smtp; 550 maria@dest.example.net... No such user
+Final-Recipient: rfc822; maria@dest.example.net
+
+--b0Nvs+XKfKLLRaP/Qo8jZhQPoiqeWi3KWPXMgw==
+Content-Type: text/rfc822-headers
+
+Return-Path: <user@xxxxxxxxxxxxxx.com>
+Received: from [85.158.137.35] by server-15.bemta-3.messagelabs.com id DB/3F-17735-603D9945; Tue, 23 Dec 2014 20:39:34 +0000
+X-Env-Sender: user@xxxxxxxxxxxxxx.com
+X-Msg-Ref: server-5.tower-143.messagelabs.com!1419367172!32961698!1
+X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
+  VHJ1c3RlZCBJUDogMjEyLjU1LjE1NC4yNCA9PiA4NjcxNw==\n
+X-StarScan-Received:
+X-StarScan-Version: 6.12.5; banners=-,-,-
+X-VirusChecked: Checked
+Date: Tue, 23 Dec 2014 20:39:24 +0000
+Message-ID: <20141223203924.Horde.aVib3NKNmpMSMBPv_KPp-w9@mail.xxxxxxxxxxxxxx.com>
+From: user@xxxxxxxxxxxxxx.com
+To: Joaquim Carreira <manuel@example.com>
+Subject: Re: BOAS FESTAS!
+Content-Type: multipart/alternative; boundary="=_Bj5UaGbJV86-J0NyTypbMg8"
+MIME-Version: 1.0
+
+
+--b0Nvs+XKfKLLRaP/Qo8jZhQPoiqeWi3KWPXMgw==--
+

data/set-of-emails/maildir/bsd/us-amazonses-01.eml

@@ -0,0 +1,59 @@
+Return-Path: <>
+Received: from a192-156.smtp-out.amazonses.com (a192-156.smtp-out.amazonses.com [199.255.192.156])
+	by nijo.example.jp (V8/cf) with ESMTP id p7V3i843003008
+	for <kijitora@example.jp>; Wed, 31 Aug 2011 12:44:08 +0900
+X-SenderID: Sendmail Sender-ID Filter v1.0.0 nijo.example.jp p7V3i843003008
+Authentication-Results: nijo.example.jp; sender-id=pass header.from=MAILER-DAEMON@email-bounces.amazonses.com
+X-Original-To: 000001321defbd2a-788e31c8-2be1-422f-a8d4-cf7765cc9ed7-000000@email-bounces.amazonses.com
+Delivered-To: 000001321defbd2a-788e31c8-2be1-422f-a8d4-cf7765cc9ed7-000000@email-bounces.amazonses.com
+Message-Id: <000001321defcde6-79aad533-d383-11e0-ba2a-37b595feadb9-000000@email.amazonses.com>
+Date: Wed, 31 Aug 2011 03:44:07 +0000
+To: kijitora@example.jp
+From: MAILER-DAEMON@email-bounces.amazonses.com
+Subject: Delivery Status Notification (Failure)
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status; boundary="JuU8e.4gyIcCrxq.1RFbQY.3Vu7Hs+"
+X-AWS-Outgoing: 199.255.192.156
+
+--JuU8e.4gyIcCrxq.1RFbQY.3Vu7Hs+
+content-type: text/plain;
+    charset="utf-8"
+Content-Transfer-Encoding: quoted-printable
+
+The following message to <shironeko@example.co.jp> was undeliverable.
+The reason for the problem:
+5.1.0 - Unknown address error 550-'5.7.1 <000001321defbd2a-788e31c8-2be1-42=
+2f-a8d4-cf7765cc9ed7-000000@email-bounces.amazonses.com>... Access denied'
+
+--JuU8e.4gyIcCrxq.1RFbQY.3Vu7Hs+
+content-type: message/delivery-status
+
+Reporting-MTA: dns; a192-79.smtp-out.amazonses.com
+
+Final-Recipient: rfc822;shironeko@example.co.jp
+Action: failed
+Status: 5.0.0 (permanent failure)
+Remote-MTA: dns; [192.0.2.222]
+Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'5.7.1 <000001321defbd2a-788e31c8-2be1-422f-a8d4-cf7765cc9ed7-000000@email-bounces.amazonses.com>... Access denied' (delivery attempts: 0)
+
+--JuU8e.4gyIcCrxq.1RFbQY.3Vu7Hs+
+content-type: message/rfc822
+
+Received: from unknown (HELO aws-bacon-dlvr-svc-na-i-8dc23dec.us-east-1.amazon.com) ([10.13.146.206])
+  by na-mm-outgoing-6102-bacon.iad6.amazon.com with ESMTP; 31 Aug 2011 03:23:15 +0000
+Return-Path: 000001321defbd2a-788e31c8-2be1-422f-a8d4-cf7765cc9ed7-000000@email-bounces.amazonses.com
+From: kijitora@example.jp
+To: shironeko@example.co.jp
+Subject: TEST
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 7bit
+Date: Wed, 31 Aug 2011 03:44:03 +0000
+Message-ID: <000001321defbd2a-788e31c8-2be1-422f-a8d4-cf7765cc9ed7-000000@email.amazonses.com>
+X-AWS-Outgoing: 199.255.192.79
+
+These are sample scripts that show how to use Amazon Simple Email Service 
+(Amazon SES) from the command line.  To learn more about these scripts, see 
+the Amazon SES Developer Guide. 
+
+--JuU8e.4gyIcCrxq.1RFbQY.3Vu7Hs+--

data/set-of-emails/maildir/bsd/us-amazonses-02.eml

@@ -0,0 +1,177 @@
+Return-Path: <>
+Received: from a192-13.smtp-out.amazonses.com (a192-13.smtp-out.amazonses.com [199.255.192.13])
+	by 3jo.example.jp (V8/cf) with ESMTP id p983Gkqb006703
+	for <shironeko@example.jp>; Sat, 8 Oct 2011 12:16:46 +0900
+X-Original-To: 00000132e188591e-2882d710-aacc-49e9-bfac-5400b02ffb9b-000000@email-bounces.amazonses.com
+Delivered-To: 00000132e188591e-2882d710-aacc-49e9-bfac-5400b02ffb9b-000000@email-bounces.amazonses.com
+Message-Id: <00000132e18869c0-f2f2c897-f15b-11e0-abc0-17dd0736b394-000000@email.amazonses.com>
+Date: Sat, 8 Oct 2011 03:16:46 +0000
+To: shironeko@example.jp
+From: MAILER-DAEMON@email-bounces.amazonses.com
+Subject: Delivery Status Notification (Failure)
+MIME-Version: 1.0
+Content-Type: multipart/report; report-type=delivery-status; boundary="QPlGA.4hi2fg4GM.1JoJoP.3UxabUS"
+X-AWS-Outgoing: 199.255.192.13
+
+--QPlGA.4hi2fg4GM.1JoJoP.3UxabUS
+content-type: text/plain;
+    charset="utf-8"
+Content-Transfer-Encoding: quoted-printable
+
+The following message to <this-local-part-does-not-exist-on-the-server@docomo.ne.jp> was undeliverable.
+The reason for the problem:
+5.3.0 - Other mail system problem 550-'Unknown user this-local-part-does-not-exist-on-the-server@docomo.=
+ne.jp'
+
+--QPlGA.4hi2fg4GM.1JoJoP.3UxabUS
+content-type: message/delivery-status
+
+Reporting-MTA: dns; a192-79.smtp-out.amazonses.com
+
+Final-Recipient: rfc822;this-local-part-does-not-exist-on-the-server@docomo.ne.jp
+Action: failed
+Status: 5.0.0 (permanent failure)
+Remote-MTA: dns; [203.138.181.240]
+Diagnostic-Code: smtp; 5.3.0 - Other mail system problem 550-'Unknown user this-local-part-does-not-exist-on-the-server@docomo.ne.jp' (delivery attempts: 0)
+
+--QPlGA.4hi2fg4GM.1JoJoP.3UxabUS
+content-type: message/rfc822
+
+Received: from unknown (HELO aws-bacon-dlvr-svc-na-i-68075b08.us-east-1.amazon.com) ([10.13.204.161])
+  by na-mm-outgoing-6102-bacon.iad6.amazon.com with ESMTP; 08 Oct 2011 02:53:28 +0000
+Return-Path: 00000132e188591e-2882d710-aacc-49e9-bfac-5400b02ffb9b-000000@email-bounces.amazonses.com
+From: shironeko@example.jp
+To: this-local-part-does-not-exist-on-the-server@docomo.ne.jp
+Subject: TEST
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 7bit
+Date: Sat, 8 Oct 2011 03:16:41 +0000
+Message-ID: <00000132e188591e-2882d710-aacc-49e9-bfac-5400b02ffb9b-000000@email.amazonses.com>
+X-AWS-Outgoing: 199.255.192.79
+
+These are sample scripts that show how to use Amazon Simple Email Service 
+(Amazon SES) from the command line.  To learn more about these scripts, see 
+the Amazon SES Developer Guide. 
+
+PREREQUISITES
+-------------
+Before running these scripts, you must fulfill the following prerequisites:
+
+* You must have an Amazon Web Services account, and must also sign up for 
+  Amazon SES.  See the Amazon SES Getting Started Guide 
+  for more information.
+
+* You must install Perl version 5.6.0 or later.  If you already have Perl 
+  installed, you can determine your version number by typing
+
+      perl -v
+
+  at the command prompt.  If you do not have Perl installed, go to 
+  http://www.perl.org for more information.
+
+* Depending on the version of Perl that you are using, you may need to install
+  some additional Perl modules.  To install these modules, run the following
+  commands:
+
+      perl -MCPAN -e 'install Digest::SHA'
+      perl -MCPAN -e 'install URI::Escape'
+      perl -MCPAN -e 'install Bundle::LWP'
+      perl -MCPAN -e 'install LWP::Protocol::https'
+      perl -MCPAN -e 'install MIME::Base64'
+      perl -MCPAN -e 'install Crypt::SSLeay'
+      perl -MCPAN -e 'install XML::LibXML'
+
+  Please ensure that you are using the latest versions of these modules.
+
+INSTALLATION
+------------
+To install these scripts, copy them to a directory of your choice.  We suggest 
+that you copy them to /opt/third-party/amazon/ses.  You might need 
+administrative privileges to do this.
+
+Help is available for these scripts - simply run one of them with the "--help"
+parameter.  Here is an example:
+
+      ses-get-stats.pl --help
+      Usage:
+         ses-get-stats.pl [--help] [-e URL] [-k FILE] [--verbose] -s | -q
+
+For more information, please refer to the Amazon SES Developer Guide.
+
+AWS CREDENTIALS FILE
+--------------------
+Each of these Amazon SES scripts requires an AWS credentials file.  To prepare 
+an AWS credentials file, follow these instructions:
+
+* Create a new text file.  In our example, we call it "aws-credentials".
+
+* Go to http://aws.amazon.com and look up your AWS credentials:  Click on 
+Account, and then Security Credentials.
+
+* Copy your Access Key ID and Secret Access Key into the "aws-credentials" file.
+
+* Change the permissions on the file so that only you have read/write access.
+(This step is *very* important, because no one else should see your Secret 
+Access Key.)
+
+* Your credentials file should look similar to the following:
+AWSAccessKeyId=022QF06E7MXBSH9DHM02
+AWSSecretKey=kWcrlUX5JEDGM/LtmEENI/aVmYvHNif5zB+d9+ct
+
+You can now use this AWS credentials file with the "-k" parameter when running
+any of the Amazon SES scripts.  For example:
+
+      ses-get-stats.pl -k aws-credentials -s
+
+TROUBLESHOOTING
+---------------
+
+* Command not found:
+
+      This means that your command line interpreter (or shell) cannot find the 
+      script.  Try running it again with a fully qualified path name, such as:
+
+         /opt/third-party/amazon/ses/bin/ses-send-email.pl 
+
+      If you change your current working directory to this location, you can 
+      run the script as follows:
+
+         ./ses-send-email.pl
+
+      Alternatively, you can include your current working directory in your 
+      PATH variable, so that you can run the script without prepending "./". 
+
+* /usr/bin/perl: bad interpreter: No such file or directory:
+
+      By default, these scripts expect the Perl interpreter to be located at 
+      "/usr/bin/perl".  If the Perl interpreter is installed elsewhere, or not
+      installed at all, you will receive the error message printed above.  
+
+      To correct this, you can edit the first line in the script so that it
+      refers to your Perl installation (for example, /opt/third-party/bin/perl).
+      You can also specify your Perl interpreter on the command line:
+
+         /opt/third-party/bin/perl ./ses-send-email.pl
+
+* Can't locate SES.pm in @INC:
+
+      Each of the Amazon SES scripts require the "SES.pm" Perl module.  This
+      error means that Perl could not find SES.pm in the list of directories 
+      where Perl modules are located.  By default, the Amazon SES scripts 
+      expect SES.pm to reside in the same directory as the scripts themselves.
+      To correct this error, try one of the following:
+
+      1) Before running the script, set the PERL5LIB variable to the directory
+      where SES.pm is located.  For example:
+         export PERL5LIB=/opt/third-party/amazon/ses
+
+      2) Modify the scripts so that they can find SES.pm in the correct
+      directory:
+         use lib '/opt/third-party/amazon/ses';
+
+      3) Use the "-I" command line switch to add the specified search path to 
+      Perl's list of module directories:
+         perl -I/opt/third-party/amazon/ses ./ses-send-email.pl 
+
+--QPlGA.4hi2fg4GM.1JoJoP.3UxabUS--