A quiet mailbox
A quiet mailbox is one that connects, fetches successfully and finds nothing. It is reported as a health signal rather than an error, because in most cases nothing is wrong — the address genuinely has no new mail. The point of naming it is that quiet and broken look identical from a distance, and only one of them needs you.
What quiet actually is#
Three states are easy to conflate and behave completely differently. A mailbox can fail to authenticate, in which case nothing was attempted. It can authenticate and error during a fetch, in which case something went wrong. Or it can authenticate, fetch cleanly and come back with nothing — which is quiet.
Only the third is ambiguous, and its ambiguity is the reason it has a name. Raising it as an error would train everybody to ignore it, since most quiet mailboxes are quiet for entirely ordinary reasons. Hiding it would leave the one genuinely wrong case invisible. So it is surfaced as what it is: an observation about the mailbox, offered to a person who knows whether that address should be busy.
The ordinary reasons#
- There is genuinely no new mail
- A low-traffic address, a weekend, a holiday. The commonest case by a distance, and nothing to act on.
- Mail is going elsewhere
- A provider-side rule filed it in a folder the adapter does not read, or forwarding is taking it away before it lands.
- The address is not the one people write to
- An alias that forwards into a different mailbox, or an address nobody has been given. Common immediately after a connection, when the wrong one of two similar addresses was chosen.
- Everything has already been read
- After a first sync catches up, a mailbox is quiet until the next message arrives. This is the expected steady state, not a problem.
Notice that three of the four are answered by looking at the provider, not at Connect. That is the practical value of the signal: it points you at the question "is mail arriving at this address at all?", which is not a question Connect can answer for you and is usually settled in under a minute.
Confirming it#
Send one message to the connected address from an unrelated account.
Result Within the sync interval it should appear as a thread in Conversations. If it does, the mailbox is fine and was simply idle.
If it does not appear, open the mailbox at the provider and check the message landed in the folder the adapter reads.
Result A message sitting in a provider-side folder that is not being read explains quiet completely, and is fixed at the provider.
If the message never reached the provider either, the address is not the one being written to.
Result That is a mail-routing question rather than a Connect one, and no setting here will resolve it.
When quiet is worth escalating#
| Address | Quiet for | Reading |
|---|---|---|
| A busy support address | Hours, during working hours | Investigate. Expectation and observation disagree, and that is the whole signal |
| A low-traffic finance address | Days | Probably correct. Confirm with one test message if it matters |
| A newly connected mailbox | Since connection | Check you connected the address people actually write to |
| Any address, since the allowance was spent | Since the refusal | Not quiet at all — that is metering, and the mail is waiting rather than absent |
The last row is the distinction most worth holding onto. When the daily allowance is spent, work is held rather than dropped and the read cursor deliberately does not advance, so the mail is still at the provider and will be read on a later pass. Needs You shows the refusal. That looks like silence and is not the same condition — see The daily email allowance.
Questions#
Is a quiet mailbox costing me anything?
A mailbox with no mail produces no work, so there is nothing to meter. What costs is processing messages, which is exactly what a quiet mailbox is not doing.
Will Connect keep checking a quiet mailbox?
Yes. Quiet is not a stopped state — the mailbox is fetched on the same schedule and will pick up the next message that arrives. Nothing has to be restarted.
How is quiet different from a mailbox that failed to authenticate?
A failed authentication means no fetch was attempted and the connection needs your attention; quiet means a fetch succeeded and found nothing. Mailbox health shows which of the two you are looking at.