cannotSend

Cannotsend is a software term used to indicate that a send operation cannot be completed. It is typically conveyed as a status flag, an error code, or a message in user interfaces and system logs. While not a formal standard, cannotsend functions as a concise indicator that dispatch of a communication or task should not proceed.

In messaging, email, or notification systems, cannotsend may appear as a boolean field (e.g., canNotSend = true) or as a code such as CANNOT_SEND. It helps distinguish between messages that are queued and those that will never be sent unless conditions change.

Common causes include policy constraints (spam detection, content restrictions), missing or invalid recipient data, insufficient user permissions, or infrastructure issues such as offline status or network outages. Some platforms reserve cannotsend for conditions requiring user action or policy review rather than temporary failures that might be retried automatically.

Handling typically involves returning an error to the caller, presenting a user-facing message with guidance, logging the condition, and offering remediation paths such as correcting recipient details, adjusting content, or retrying later. In queue-based systems, cannotsend may be escalated to a manual review or a scheduled retry based on policy.

Naming varies across platforms. Cannotsend is one possible label; others use cannot_send, cannotSend, or a dedicated error code. The term is largely descriptive and should be understood in the context of the system’s error model. It is usually distinct from states such as unsent pending retries or failed deliveries after dispatch attempts.

See also: cannot_send; blocked; bounce; retry; queue.