Skip to main content

mpNormal

mpNormal = 2

Example​

procedure ConfigureNormalPriority(Message: TIdMessage);
begin
  Message.Priority := mpNormal;
end;

Usage​

mpNormal selects Velox's default normal mail priority and actively removes generated priority headers.

Additional Technical Info​

mpNormal is the default TIdMessagePriority member. New and cleared messages use it.

During normal generation Indy removes Priority, X-Priority and Importance from its generated header list instead of emitting normal/3 values. This intentionally avoids unnecessary metadata that may affect spam filtering. The example is source-reviewed and is not executed by the documentation workflow.

Behavior and quirks

  • Raw matching headers copied into the normal header list are cleared during generation.
  • ExtraHeaders is appended later and can reintroduce priority fields despite mpNormal; avoid mixing typed and raw mechanisms.
  • Incoming numeric token 3, missing priority headers, invalid/out-of-range numbers and unrecognized text all resolve to Normal.
  • The parser uses the first present header in this precedence: X-Priority, Priority, Importance, X-MSMail-Priority. A malformed higher-precedence field can therefore force Normal even when a lower field is meaningful.
  • Normal is an absence-of-hint output, not a delivery SLA or Velox processing class.

Errors, performance and concurrency

Assignment is constant-time. Generation mutates the generated-header collection and must not run concurrently with other message changes.

Related entries

External references

Created 2026-07-15