UDR reporting columns

Column

Description

Possible values

Creation Time

Timestamp when the job request was accepted and processing started.


Message From

Sender address of the message.


Message To

Recipient address of the message.


Message From Domain

Sender domain of the message.


Message To Domain

Recipient domain of the message.


Usage - ID

Unique identifier for the individual recipient message within a job.


Message Size

Final MIME message size, in bytes.


Status

Final processing status of the message.

OK, ERROR

Substatus

Classification of the message outcome within the main processing result groups.

DELIVERED, BOUNCED, DROPPED

Status Details

Detailed information about the final processing status of the message.

VALIDATION_ERROR, INVALID_ADDRESS, FORBIDDEN_RECIPIENT, PROCESSING_FAILED, SUPPRESSED, PREVIOUSLY_BOUNCED, OK, HARD_BOUNCE, SOFT_BOUNCE

SMTP Status Code

SMTP response status code received by the Transactional Email MTAs (Mail Transfer Agents).

See full list below that table

Reference Job

Customer-defined job reference provided in the initial JobRequest.


Correlation ID

Unique identifier used to correlate the individual recipient message across processing steps and related records.


Job ID

Identifier returned by the entry interface when the JobRequest was accepted. A single Job ID can contain multiple Usage ID values.


Cost Center

Customer-defined cost center provided in the initial JobRequest.


Provisioning ID

Identifier used for billing and provisioning purposes.


Tenant

Tenant identifier.
This field will be deprecated in the near future.


Technical Account ID

Technical account under which the message was processed.


Campaign ID

Customer-defined campaign ID provided in the initial JobRequest.


Meta Data - ID

Unique identifier of the metadata record.


Version

Version number of the metadata record.


Meta Data Creation Time

Timestamp when the metadata record was created.


Entry Interface

Interface used to submit the message to the Transactional Email service.

rest, smtp

Processing Region

Retarus region in which the message was processed and sent.

DE1, DE2, US1, US2, SG1, CH1

SMTP status codes

Code

Meaning

200

Nonstandard success response (see RFC 876 for details)

211

System status message or system help response

214

Help message

220

<domain> service is ready

221

<domain> service is closing the transmission channel

250

Requested mail action completed successfully

251

User is not local; the message will be forwarded to <forward-path>

252

Cannot verify the user, but the message will be accepted and delivery will be attempted

354

Start mail input; end with <CRLF>.<CRLF>

421

<domain> service is not available; closing the transmission channel

450

Requested mail action not taken: mailbox unavailable

451

Requested action aborted: local error during processing

452

Requested action not taken: insufficient system storage

500

Syntax error: command not recognized

501

Syntax error in parameters or arguments

502

Command not implemented

503

Invalid sequence of commands

504

Command parameter not implemented

521

<domain> does not accept mail (see RFC1846 for details)

530

Access denied

550

Requested action not taken: mailbox unavailable

551

User is not local; please try <forward-path>

552

Requested mail action aborted: storage allocation exceeded

553

Requested action not taken: mailbox name not allowed

554

Transaction failed

The status codes listed above are generated by the recipient’s mail servers. While SMTP status codes follow a standardized framework defined in RFC 3463, Internet Service Providers (ISPs) and mail servers may apply and interpret them differently.