Re: bounce handler - Amazon SES

 
From: "Frans Gouverne" <fransgnl@PROTECTED>
Date: May 7th 2012
2012/5/6 Justin J <justin@PROTECTED>

Can you send over a complete bounce message, headers and all?


Here it is, I only changed the email and domain names for privacy reasons. There are 3 parts: the bounced email itself and two attachments:

BOUNCED EMAIL:
Return-path: <>
Envelope-to: bounces@PROTECTED
Delivery-date: Wed, 25 Apr 2012 15:16:56 +0200
Received: from mail by server087.totalin.net with spam-scanned (Exim 4.60)
     id 1SN25W-0004RX-Up
     for bounces@PROTECTED; Wed, 25 Apr 2012 15:16:56 +0200
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on
     server087.totalin.net
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=7.5 tests=AWL,BAYES_00 autolearn=ham
     version=3.2.1
Received: from a192-141.smtp-out.amazonses.com ([199.255.192.141])
     by server087.totalin.net with esmtp (Exim 4.60)
     id 1SN25W-0004RT-R1
     for bounces@PROTECTED; Wed, 25 Apr 2012 15:16:54 +0200
X-Original-To: 00000136e9c52c44-a7f91c97-0c21-436b-b714-4227adce6415-000000@PROTECTED
Delivered-To: 00000136e9c52c44-a7f91c97-0c21-436b-b714-4227adce6415-000000@PROTECTED
Date: Wed, 25 Apr 2012 13:51:26 +0000
From: MAILER-DAEMON@PROTECTED
Subject: Undelivered Mail Returned to Sender
To: bounces@PROTECTED
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
     boundary="18381174112.1335361883/mailscan12.emaildomain.nl"
Content-Transfer-Encoding: 8bit
Message-Id: <00000136e9c5595d-bf425f38-8edd-11e1-996d-3f66f12ccaa3-000000@PROTECTED>
X-AWS-Outgoing: 199.255.192.141


This is the mail system at host mailscan12.emaildomain.nl.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<emailname@PROTECTED>: maildir delivery failed: error writing message: Disk
    quota exceeded


FIRST ATTACHMENT SUBJECT: Delivery report
Reporting-MTA: dns; mailscan12.emaildomain.nl
X-Postfix-Queue-ID: 18381174112
X-Postfix-Sender: rfc822;
00000136e9c52c44-a7f91c97-0c21-436b-b714-4227adce6415-000000@PROTECTED
Arrival-Date: Wed, 25 Apr 2012 15:51:23 +0200 (CEST)

Final-Recipient: rfc822; emailname@PROTECTED
Original-Recipient: rfc822;emailname@PROTECTED
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error


SECOND ATTACHMENT SUBJECT: Undelivered Message Headers
Received: from localhost (mailscan12 [127.0.0.1])
        by mailscan12.emaildomain.nl (Postfix) with ESMTP id 18381174112
        for <emailname@PROTECTED>; Wed, 25 Apr 2012 15:51:23 +0200 (CEST)
X-ZldNet-SpamScan: Nee
X-ZldNet-VirusScan: Nee
Received: from mail.emaildomain.nl ([192.168.201.222])
        by localhost (mailscan12.emaildomain.nl [192.168.200.35]) (amavisd-new, port 1025)
        with ESMTP id UKMer238TO09 for <emailname@PROTECTED>;
        Wed, 25 Apr 2012 15:51:22 +0200 (CEST)
X-policyd-weight: using cached result; rate: -9
Received: from a192-146.smtp-out.amazonses.com (a192-146.smtp-out.amazonses.com
[199.255.192.146])
        by mail.emaildomain.nl (Postfix) with ESMTP id 1F78B1580F0
        for <emailname@PROTECTED>; Wed, 25 Apr 2012 15:51:20 +0200 (CEST)
Date: Wed, 25 Apr 2012 13:51:15 +0000
From: "Nieuwsbrief Frans" <info@PROTECTED>
To: "emailname@PROTECTED" <emailname@PROTECTED>
Reply-To: "Nieuwsbrief Frans" <info@PROTECTED>
List-Archive: <http://www.mydomain.com/cgi-bin/dada/mail.cgi/archive/nieuwsbrief/>
List-Owner: <info@PROTECTED>
List-Subscribe:
=?ISO-8859-1?Q?=3Chttp=3A//www=2Efrans=2Enu/cgi-bin/dada/mail=2Ecgi/s/n?=
 =?ISO-8859-1?Q?ieuwsbrief/emailname/emaildomain=2Enl/=3E?=
List-Unsubscribe:
=?ISO-8859-1?Q?=3Chttp=3A//www=2Efrans=2Enu/cgi-bin/dada/mail=2Ecgi/u/n?=
 =?ISO-8859-1?Q?ieuwsbrief/emailname/emaildomain=2Enl/=3E?=
Content-type: multipart/alternative; boundary="_----------=_1335359224148830";
charset=iso-8859-1
Content-Transfer-Encoding: binary
MIME-Version: 1.0
Subject: Nieuwsbrief Frans mei 2012
Message-ID:
<00000136e9c52c44-a7f91c97-0c21-436b-b714-4227adce6415-000000@PROTECTED>
X-AWS-Outgoing: 199.255.192.146



 

Justin J: Lead Dadaist.
url:      http://dadamailproject.com
email:    justin@PROTECTED

On May 6, 2012, at 3:10 PM, Frans Gouverne wrote:

> Hi Justin,
>
> I am using Amazon SES smtp server to send emails. Recently I got several bounced messages from Amazon SES which are not recognized by the bounce handler. As far as I can see, the main problem is that the actual reason for the bounce is only listed in the message body, like:
> The users mailfolder is over the allowed quota (size).
> and no attachment is present.
>
> Or, another Amazon bounced message body says:
> maildir delivery failed: error writing message: Disk quota exceeded
>
> while the attachment of the bounced message is only mentioning:
> Reporting-MTA: dns; mailscan12.xxxxx.nl
>
> X-Postfix-Queue-ID: 18381174112
> X-Postfix-Sender: rfc822;
>
> 00000136e9c52c44-a7f91c97-0c21-436b-b714-4227adce6415-000000@PROTECTED
>
> Arrival-Date: Wed, 25 Apr 2012 15:51:23 +0200 (CEST)
>
> Final-Recipient: rfc822;
> marcano2@PROTECTED
>
> Original-Recipient:
> rfc822;marcano2@PROTECTED
>
> Action: failed
> Status: 5.2.2
> Diagnostic-Code: x-unix; input/output error
>
> Question: can I tell the bounce handler to look into the body of the bounced message to search for specific "rules"? Because my impression is that only the email header of the bounced message or its attachments can be inspected. For example, something like:
>  {
>  rule_name => {
>          Examine => {
>                 Message_Fields => {
>
> Body_regex
>  => [(qr/over the allowed quota|Disk quota exceeded/)],
>
> but of course there is no real line starting with Body: in the message so this will not work.
>
> Post:
> mailto:dadadev@PROTECTED
>
> Unsubscribe:
> http://dadamailproject.com/cgi-bin/dada/mail.cgi/u/dadadev/
>
> List Information:
> http://dadamailproject.com/cgi-bin/dada/mail.cgi/list/dadadev
>
> Archive:
> http://dadamailproject.com/cgi-bin/dada/mail.cgi/archive/dadadev
>
> Developer Info:
> http://dev.dadamailproject.com
>
> Mailing List Powered by Dada Mail
>



--

* Post:
mailto:dadadev@PROTECTED

* Unsubscribe:
http://dadamailproject.com/cgi-bin/dada/mail.cgi/u/dadadev

* List Information:
http://dadamailproject.com/cgi-bin/dada/mail.cgi/list/dadadev/

* Archive:
http://dadamailproject.com/cgi-bin/dada/mail.cgi/what_is_dada_mail/

Post:
mailto:[list_settings.discussion_pop_email]

Unsubscribe:
https://dadamailproject.com/cgi-bin/dada/mail.cgi/u/dadadev/

List Information:
[PROGRAM_URL]/list/[list_settings.list]

Archive:
[PROGRAM_URL]/archive/[list_settings.list]

Developer Info:
http://dev.dadamailproject.com

Mailing List Powered by Dada Mail

  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email: dadadev@dadamailproject.com

This is the developer discussion mailing list for Dada Mail.

If you are just looking for support Dada Mail, consult the message boards at:

https://forum.dadamailproject.com

Documentation for Dada Mail:

https://dadamailproject.com/d

Specifically, see the Error FAQ:

https://dadamailproject.com/d/FAQ-errors.pod.html

To post to this list, send a message to:

mailto:dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Topics that are welcome:

  • Constructive critiques on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

Dada Mail is on Github:

https://github.com/justingit/dada-mail/

If you would like to fork, branch, send over PRs, open up issues, etc.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.