Sent folder

As soon as your server accepts a message, FOLD shows it in Sent and stores a copy in the account's Sent folder on the server.

What happens after sending

1. Submission. FOLD hands the message to your SMTP server. Once the server accepts it, the message counts as sent. FOLD never submits it a second time, even if a later step fails.
2. Local copy. FOLD places the message in the Sent folder on the device right away, marked as read. You see it in Sent without waiting for the network.
3. Server copy. In the background FOLD uploads the message to the account’s Sent folder on the server, also marked as read.

If the upload fails, for example because the connection dropped or the mailbox is full, FOLD keeps the message and tries again every time it processes the outbox. There is no limit on these attempts, because giving up would lose the only server copy of a sent message. Such messages do not appear in the outbox; the send itself succeeded.

In rare cases the server stores the copy but its confirmation never reaches FOLD. FOLD then uploads it again, and you see the message twice in Sent. FOLD accepts a duplicate rather than risk losing the copy.

If the account uses Fortress encryption and is locked, the upload waits until you unlock it.

Which folder FOLD uses

FOLD looks for the Sent folder in this order:

1. A folder the server marks as Sent (special-use \Sent, RFC 6154).
2. A folder whose name contains “sent” or “gesendet”, for example Sent Messages, Sent Items, Gesendete Elemente or [Gmail]/Sent Mail.
3. If there is none, FOLD creates a Sent folder. It places it below the inbox when the server keeps all folders there, and marks it as Sent when the server supports that.

The Sent folders of all accounts appear together in the unified Sent mailbox; see Unified mailboxes.