Knowledge base

message-id verified

The identifier the engine assigned

MailerQ's own identifier for the message, generated when the message has none.

In detail

Generated per message and — in a cluster — kept unique across nodes by server-id, which none of our nodes sets. Until that is fixed the identifier is unique only per node, so it is not a safe primary key for telemetry across a fleet. Our own property in the job is.