7. INBOUND MESSAGES

 

SMTP-R manages received messages following sending, recorded in the message logs (cf 7.3) which can be of several types: FeedBackLoop, List-Unsubscribe by email, DMARC reports, Hard and Soft Bounces, Challenge-Response , and responses - automatic or not.

 

For each sender used, whether IP ReverseDNS, or domain names specified in the message or campaign parameters, the system creates a sub-directory of the sender's name in \REPLY\, as well as a sorting sub-tree, in which the received messages are stored according to their type, in the form of timestamped files:

 

• @CHALLENGE contains messages identified as Challenge-Response by pattern detection.

• @DMARC contains messages received on the email address of the DMARC DNS record.

• @FBL contains FeedBackLoop messages received on a notification email address declared during registration.

• @HARD contains messages identified as Hard Bounce by pattern detection.

• @SOFT contains messages identified as Soft Bounce by pattern detection.

• @UNLST contains automatic unsubscribe messages by email (Tag List-Unsubscribe).

• @VERP contains messages received on the SMTP session address (MAIL FROM) when the "envelopefrom" option is set to "@verp", and whose content could not be qualified.

• 'abuse' and 'postmaster' are static addresses associated with the sender (abuse@sender and postmaster@sender), created automatically by the system because they are often necessary for registering with FeedBackLoop programs.

​

When injecting a request, the system automatically creates a static address directory corresponding to the sender address defined in "header" "from" "addr".

​

It is possible to manually create an @CATCHALL directory that will accept all messages from the sender domain to non-existent addresses (it will probably be spam).

​

The content of the files is the raw data stream as received during the session DATA phase of the SMTP session (RFC822 message).

​