The Residents' Association Notice That Went Wrong
The secretary of a residents' welfare association in Pune, with 60 flat owners on its list, uses a free webmail account. She sent the notice for the annual general meeting by typing all 60 addresses into the To field. Within an hour, owner no. 12 used Reply All to complain about visitor parking, and six other owners replied all to that complaint. Ten owners later said the notice had landed in their spam folder. Separately, the secretary received a message: "Mailbox alert: your storage is 99% full. Re-enter your password within 24 hours or your account will be deactivated", with a link to a login page. The same week, her 18 MB PDF of the AGM minutes bounced from three recipients with a message about exceeding the size limit.
1. Explain what was wrong with putting all 60 addresses in To, and how the secretary should send the next notice so that it reaches inboxes and protects members' addresses.
Read the worked answer
Three separate problems follow from one mistake.
First, privacy. Every recipient can see all 60 addresses in the To field. Members did not consent to having their addresses published to neighbours, and one forwarded copy puts the whole list in circulation.
Second, reply-all storms. When everyone is in To, a single complaint reaches all 60 people, and the six replies reach all 60 again. The discussion is not about the meeting at all.
Third, delivery. A free account sending an identical message to 60 recipients at once looks like bulk mail to spam filters, especially when many addresses are new to one another. That is a plausible reason ten copies went to spam.
The fix: put the secretary's own address in To, use Bcc for the 60 members (or a properly configured mailing list), and add one line - "Please do not use Reply All; write to the secretary directly." Bcc hides the list, a single To recipient keeps the message looking like ordinary mail, and members can still be reached individually. Ask members to add the secretary's address to their contacts so future notices reach the inbox.
2. Owner no. 12 pressed Reply All. Was that a reasonable judgement? Explain the etiquette and the practical consequences, and say what the secretary should do now.
Read the worked answer
It was not reasonable. Reply All sends to every address in the To and Cc fields, so a complaint about visitor parking reached 59 people who had no role in it. The consequences are concrete: six further Reply All messages, members deleting the meeting notice along with the noise, and a risk that some will filter the secretary's future mail as unwanted.
The correct choice depends on the audience, not on convenience. Reply goes to the sender only - right for a personal complaint, a correction, or a question that concerns one person. Reply All is right only when every recipient genuinely needs the answer, for example a correction to the meeting date that everyone must know.
The secretary should now send one short message: restate the meeting details, note that the parking matter will be taken up separately, and request that replies come to her alone. She should avoid re-sending to all 60 again - a single clarifying message is enough, and repeated bulk messages will worsen the spam-filtering problem.
3. Assess the "mailbox 99% full" message and the bounced 18 MB attachment. What should the secretary do in each case?
Read the worked answer
The mailbox message is a phishing attempt. The signs: it creates urgency (24 hours), threatens loss of the account, asks for a password, and provides a link rather than directing the user to the service's own website. No legitimate mail provider asks for a password by email, and storage warnings appear inside the account, not through an outside link. The correct action is to click nothing, not to reply, and to report the message as phishing; then open the mail service by typing its address directly and check the storage figure there. If in doubt, the secretary should confirm with the provider's help pages, not with the sender.
The 18 MB attachment exceeded the recipient's limit. Attachments are encoded for transport, so an 18 MB file can travel as roughly 24 MB. Options, in order of preference: upload the PDF to cloud storage and send the sharing link; reduce the PDF size by exporting at lower resolution; or split it into two parts. For an association with 60 members, a shared link is better than an attachment in any case, because it can be updated and it does not fill anyone's mailbox.