Community

DSN for SMTP software

Hello

I have a software that uses an Axigen account to authenticate with SMTP and send emails to a list of email addresses.
how can I activate DSN for this software?

I`m using axigen-10.2.2.82 on Centos-7.

That software should have the possibility to request DSN. This is a standard SMTP protocol extension. See below a description of this along with an example of an SMTP connection.

Additional Parameters for the RCPT and MAIL Commands

The extended RCPT and MAIL commands are identical to normal RCPT and MAIL commands , except that none, one or more of the following parameters appear after the sender or recipient address, respectively.

The NOTIFY parameter of the RCPT command specifies the conditions under which the SMTP server should generate DSNs for that recipient. It can either be any comma separated subset of {“success”, “failure”, “delay”} OR it can be just “never”. If NOTIFY is not present then the webadmin settings for generating temporary and permanent notification failures are used and success notifications are not generated. If NOTIFY is present then the webadmin settings for generating temporary and permanent notification failures are ignored. If the Axigen MTA relays an email to an MTA that does not support DSN, all recipients that have NOTIFY as “never” are grouped together and a separate mail is relayed that has an empty sender, to prevent failure notifications from being sent from further down the relay path.

The ORCPT parameter of the RCPT command is used to specify an “original” recipient address that corresponds to the actual recipient to which the message is to be delivered. If ORCPT is present, its value is an encoded representation of the original recipient address name, using the rules for xtext detailed in RFC3461 section 4. The ORCPT parameter may be up to 500 characters in length.

The RET parameter of the MAIL command specifies which part of the original message should be included in any failed (temporary or permanent) DSN issued for this message transmission. It can be either “full” or “hdrs”, specifying inclusion of the whole initial message, or just the headers. Note that the RET parameter only applies to DSNs that indicate delivery failure (temporary or permanent) for at least one recipient. If a DSN contains no indications of delivery failure, only the headers of the message should be returned. If the RET parameter is not present then the webadmin settings for temporary and permanent notification failures’ attachments are used. If the RET parameter is present then the webadmin settings for temporary and permanent notification failures’ attachments are ignored.

The ENVID parameter of the MAIL command is used to specify an “envelope identifier” to be transmitted along with the message and included in any DSNs issued for any of the recipients named in the SMTP transaction. The purpose of the envelope identifier is to allow the sender of a message to identify the transaction for which the DSN was issued. No meaning is assigned by the mail system to the presence or absence of this parameter; the information is used only by the sender or his user agent. The value of the ENVID parameter is encoded as xtext, similar to the ORCPT parameter. The ENVID parameter may be up to 100 characters in length.

The NOTIFY, ORCPT, RET and ENVID parameters may appear at most once in their corresponding SMTP commands. These parameters are only parsed successfully if the DSN feature is enabled.

When sending an email from the Axigen webmail, and this email requests delivery notification, the following values are used for the parameters:

  • NOTIFY=SUCCESS,FAILURE,DELAY
  • ORCPT is not used for now
  • ENVID is a string composed of 20 random ASCII letters. It is not guaranteed to be unique for each mail, though the chance of having two mails awaiting notifications while having the same envid should be very low.
  • RET is not used, so the webadmin settings should matter for failure notifications issued by the Axigen server.

When sending an email which does not request delivery notification no DSN parameters are used.

Here is an example of using these new optional parameters from the SMTP cli:

mail from:c1@sator12.ro envid=sadsad2 ret=full
250 Sender accepted
rcpt to:c2@sator12.ro notify=success,failure,delay orcpt=rfc822;ana@are.mere
250 Recipient accepted
rcpt to:c3@sator12.ro notify=never
250 Recipient accepted
data
354 Ready to receive data; remember <CRLF>.<CRLF>
Subject: x

dfasdfs
.
quit

hope this helps!