You click Reply in a Fastmail conversation and notice more recipients than you expected. Pause before sending. The important comparison is between the people you intend to contact and the addresses actually listed in the draft, not simply the label on the button you clicked.
Read the provider’s default behavior
Fastmail’s Conversations documentation says that its default reply behavior includes everyone in the email conversation. It documents a Default reply to preference under Settings, Mail preferences, When replying, and an individual message action called Reply to sender. Check the controls in your current interface rather than assuming another mail app’s behavior applies.
That is a description of the provider’s controls, not permission to send private information to every participant. An existing conversation can include people who should not receive your next update. The draft’s recipient list still needs to match the purpose of that reply.
Make a recipient plan before editing the draft
Privately write one sentence describing who should receive the next message: “This question is only for the organizer,” for example, or “Everyone in the project exchange needs this scheduling update.” Then compare that intention with every visible recipient field. Do not rely on a familiar display name when the underlying address is different.
If you are unsure who an address belongs to, stop before sending. Ask through an established contact route or consult your own trusted records. Do not forward the entire conversation to an unfamiliar support contact just to ask whether a recipient looks correct.
A practical handoff example
Jon is discussing an event with an organizer and several volunteers. His next reply contains a personal availability detail that only the organizer needs. He opens the draft, sees the broader group and stops. His useful observation is that the current draft’s audience is broader than his intended audience. It does not mean Fastmail sent anything merely because the draft opened that way.
Jon can inspect the appropriate reply action and review the resulting draft. Before sending, he checks the recipients again and removes information that should not travel with this particular response. If he chooses a different action, he should not assume that the new draft automatically meets every privacy requirement.
Separate a one-message choice from a future preference
A setting change may affect how later replies begin; it is not a substitute for reviewing each message. Conversely, choosing a narrower reply action once does not establish that the account’s future default has changed. Record which choice you actually made if you are documenting a recurring problem.
On a shared or managed account, follow the organization’s rules before changing a preference. A colleague may expect a particular team workflow. Explain the desired behavior with a harmless example rather than silently altering the setup and discovering the difference during a sensitive exchange.
Check the whole draft before it leaves
Once the audience is correct, review the body, included history and attachments. Do not assume that narrowing a recipient list removes sensitive material from a quoted thread. Review only material you are authorized to handle, and avoid sending unnecessary private details when a concise new explanation would suffice.
Also distinguish this from a message that has already been sent. Editing a draft can change what will be sent next; it does not retract an earlier message from other people’s mailboxes. If you already sent something to an unintended audience, record what happened and follow the relevant organization’s incident process rather than promising a universal recall.
Document a recurring mismatch accurately
For a help request, record that you are using Fastmail’s own interface, the action selected, the intended audience and whether the unexpected recipients appeared before sending. A separate desktop client may have its own controls and defaults. Keep real addresses and message contents out of a public report.
The safest outcome is a repeatable review habit: define the audience, inspect the draft and then decide whether to send. No default can replace that final check for every conversation.
Source checked November 10, 2026: Fastmail’s Conversations help page. For broader independent context, see EmailSupport’s provider guide directory.
Written by Scott Jeppesen for EmailSupport. We provide independent third-party assistance and are not affiliated with Fastmail or any other email provider mentioned.
Comments (0)
Want to join the discussion?
Log In to Comment