mpHighest
mpHighest = 0
Example
procedure ConfigureUrgentMessage(Message: TIdMessage);
begin
Message.Priority := mpHighest;
end;
Usage
mpHighest selects Velox's highest mail-priority hint, generating urgent/high text headers and numeric X-Priority 1.
Additional Technical Info
mpHighest is the strongest high-priority hint in TIdMessagePriority. Generation emits Priority: urgent, X-Priority: 1 and Importance: high.
The example is source-reviewed and is not executed by the documentation workflow.
Behavior and boundaries
- A smaller enum ordinal means a higher priority; do not sort these values as though larger meant more important.
mpHighestandmpHighshare textual headers and differ only by X-Priority 1/2.- Receiving text containing
urgentorhighmaps to this extreme member, while numeric first token1also maps here. - These nonuniform, advisory headers can be ignored, rewritten or used by filters. They do not change Velox execution, SMTP delivery or business severity.
- This value does not set IMAP
\Flaggedand must not be used as a security or SLA control.
Header ownership
Normal generation derives headers from the enum and overwrites copied raw values. ExtraHeaders is appended later and can create contradictory duplicates; avoid combining it with the typed property.
Errors, performance and concurrency
Assignment is constant-time and side-effect free until generation. Message generation remains stateful and must not run concurrently with mutation.
Related entries
mpHighis numeric level 2.mpNormalemits no priority headers.TIdMessage.Prioritygives the full mapping.
External references
Created 2026-07-15