BACKCLICK 5.6
ContentsIndex
PreviousUpNext
Management of the MTA-Bounces

Management of the MTA-Bounces 

Unlike standard sending, MTA sending does not result in bounce e-mails showing up in the internal MTA as hard bounces (undeliverable e-mails). The MTA already recognizes hard bounces, based on the answers from the recipient’s servers (5 xx faults) during the sending, whether or not a recipient’s address exists. To avoid the additional sending of e-mails to nonexistent e-mail addresses, these recipient addresses are removed from the system automatically. 

 

Abb. 17.4 - Rückläufer-Verwaltung 

 

17.4.1 If the nonexistent e-mail addresses are not removed: 

If this check box is marked, all of the nonexistent e-mail addresses will be removed from the system. 

17.4.2. Number of addresses that should be checked per running: 

The number of nonexistent e-mail addresses that should be removed per running (see 17.4.3) is displayed here. 

 

 

  • Default value: 200
  • Minimum value: 100
  • Maximum value: 10000

 

17.4.3. Calling interval (every n Min.): 

 

  • Default value: 1 Minute
  • Minimum value: 1 Minute
  • Maximum value: 30 Minutes

 

17.4.4. Detail level of the fault recognition: 

There are three different levels for the recognition of faults: 

17.4.4.1 - "User unknown": The clearest error message. These e-mail recipients are definitely nonexistent (probability of delivery: 0%). 

17.4.4.2 - "Mailbox full": The recipient exists, but his or her mailbox does not accept new messages. It is probably a mailbox created for receiving spam. The content of this mailbox is not accessed at any time (probability of delivery: 0–5%). 

17.4.4.3 - "Relaying denied": The recipient exists, but the MX server refuses to deliver the e-mail to the recipient. Most of the time, a wrong configuration of the MX server is responsible for this. It is nearly impossible for this wrong configuration to be changed (probability of delivery: 0–5%). 

 

  • Default value: "User unknown"

 

17.4.5. Remove server messages after revision: 

To build a basis for the recognitions in 17.4.4, the server responses are stored in the database and will be removed per 

default setting after they have been revised. This function may be activated for the use of debugging. 

 

  • Default value: aktiviert
Links
Copyright (c) 2003-2011 ATD GmbH.
ContentsIndex
What do you think about this topic? Send feedback!