Failure types

The Failure type shows the issue with the delivery of mailings. It provides vital information that is used during troubleshooting.

Find the Failure types below:

Transient failures

Transient failures are recorded when all retry attempts have been made and delivery was unsuccessful. For example, a transient failure can occur when Aurea List Manager is unable to connect to the receiving mail server. Here are some examples of transient failures:

Wed, 05 May 2010 04:25:44 Sending email to: example@example.com
<--DNS info available for: example.com 
--> Attempting to connect to: example.com (10.20.30.40 25)
<-- Connection refused by: example.com (10.20.30.40 25)
--> No more mail servers left to try.
Wed, 05 May 2010 04:55:33 Sending email to: example@example.com
<-- DNS info available for: example.com
--> Attempting to connect to: example.com (10.20.30.40 25)
<-- Connection refused by: example.com (10.20.30.40 25)
--> No more mail servers left to try.
Wed, 05 May 2010 05:55:32
Unable to resolve DNS information for this domain
Wed, 05 May 2010 07:25:36
Unable to resolve DNS information for this domain
Wed, 05 May 2010 09:25:57 Sending email to: example@example.com
<-- DNS info available for: example.com
--> Attempting to connect to: example.com (10.20.30.40 25)
<-- Connection refused by: example.com (10.20.30.40 25)
--> No more mail servers left to try.

Permanent failures

Permanent failures are related delivery attempts that have failed due to bad email addresses. Here are some examples of permanent failures due to invalid addresses:

Mon, 03 May 2010 12:32:55 Sending email to: test1@example.com
<-- DNS info available for: example.com
--> Attempting to connect to: example.com (10.20.30.40 25)
<-- Connected to: example.com (10.20.30.40 25)
<-- 220 barracuda2.netwurx.net ESMTP (245fb80b66e3a4c59a0a3ff2553b6e66)
--> HELO lm.lyris.net
<-- 250 barracuda2.netwurx.net Hello lm.lyris.net 10.1.1.1, pleased to meet you
--> MAIL FROM: bounce-123-1@lm.lyris.net
<-- 250 Sender <bounce-123-1@lm.lyris.net> OK
--> RCPT TO:<test1@example.com>
<-- 511 cuda_nsu sorry, no mailbox here by that name (#5.1.1 - chkuser)
Mon, 03 May 2010 12:05:18 Sending email to: test2@example.com
<-- DNS info available for: example.com
--> Attempting to connect to: example.com (10.20.30.40 25)
<-- Connected to: example.com (10.20.30.40 25)
<-- 220 bay0-mc2-f43.Bay0.example.com
--> HELO lm.lyris.net
<-- 250 bay0-mc2-f43.Bay0.example.com (3.10.0.73) Hello 10.1.1.1
--> MAIL FROM: bounce-123-2@lm.lyris.net
<-- 250 bounce-123-2@lm.lyris.net....Sender OK
--> RCPT TO:<test2@example.com
<-- 550 Requested action not taken: mailbox unavailable

Bounce messages

Bounces that are sent to the bounce-messageid-memberid@servername.com address are first processed in the Incoming Mail Queue. Based on the bounce message received, the delivery status for that member is updated with either a Transient or Permanent failure. Here is an example:

Return-Path: <>Received: from example.com (1.1.1.1) by 10.20.30.40 with SMTP (Lyris ListManager WIN32 version 10.2c); 
Mon, 17 May 2010 23:20:24 -0700
To: bounce-6533058-285222935@lm.lyris.net
From: Mail Administrator <Postmaster@example.com>
Reply-To: <Postmaster@example.com>
Subject: Mail System Error - Returned Mail
Date: Tue, 18 May 2010 06:20:23 +0000
Message-ID: <20100518062023059.PPCZ2115@hrndva-imta08.example.com>
MIME-Version: 1.0
Content-Type: multipart/report;report-type=delivery-status;
Boundary="===========================_ _= 9778442(2115)1274163623"
--===========================_ _= 9778442(2115)1274163623
Content-Type: text/plain
This Message was undeliverable due to the following reason:
Each of the following recipients was rejected by a remote mail server.
The reasons given by the server are included to help you determine why
each recipient was rejected.
Recipient: <test3@example.com>
Reason: 5.1.1 unknown or illegal alias: test3@example.com