A 240-Member Circular, a Spam Folder and a Bank Signature

Privacy first. To and Cc disclose every address to every recipient - that is the complaint already received, and it cannot be recalled once sent. Put the society's own address in To and the members in Bcc, or better, send through a proper mailing list so members never see each other's addresses. Never put "Undisclosed recipients" in To as a substitute for using Bcc.

Limits and batching. A free Gmail account allows roughly 500 recipients per day and a 25 MB attachment; 240 in one Bcc is technically possible but is exactly the pattern bulk filters look for, and if it is throttled she will not know who received it. Send in batches of about 50 with a short gap, or use a mailing service that reports bounces. Check the sending account's daily quota before starting, and never resend the whole batch to chase 20 non-responders - export the bounce list and resend only to those.

The attachment. 3.2 MB × 240 is about 770 MB leaving the building, and members on metered mobile data pay for it. Most scanned-text PDFs can be compressed to well under 1 MB at 200 dpi without losing legibility - re-scan or optimise before sending. Also put the notice text in the body of the email, so a member on a phone can read it without opening anything; attach the audited accounts rather than forcing a link that may expire.

Records. Keep the Sent copy, save the member list as a spreadsheet with columns for sent/bounced/responded, and log the date and time. If only a link is used, record the sharing permissions chosen (view-only, no download) and the expiry date.

Spam filtering is largely a question of can this mailbox prove it is authorised to speak for this domain. The society's mail fails that test on two counts:

1. The visible mismatch. The letterhead and website say [email protected]; the mail arrives from [email protected]. Recipients see "[email protected] on behalf of ..." or a bare gmail.com sender that contradicts the organisation's own paperwork, and filters score a From: address whose domain has no relationship to the links, signature or PDF branding.
2. No authentication on the society's own domain. If greenvalley.org.in publishes no SPF record (which servers may send for it), no DKIM signing key, and no DMARC policy, then anyone - including the society's own staff trying to use the official address - is unauthenticated, and receivers have no reason to trust the mail. It also means a real spoof of the society's domain could not be distinguished from the genuine article.

The fix, in order:

• Create and use the actual mailbox [email protected] at the domain's mail provider, and send all official circulars from it.
• Publish SPF (listing the provider's sending servers), enable DKIM signing at the provider, then publish a DMARC record starting at p=none to collect reports, moving to quarantine once legitimate mail passes.
• If Gmail must be used, configure it as "Send mail as" the domain address through the domain's SMTP with the correct SPF entry - an @gmail.com From: address can never be authenticated for greenvalley.org.in.
• Keep content unfussy: specific subject line, no all-caps or "URGENT!!!", no link shorteners, a real signature and an unsubscribe/contact line, and the notice as plain text rather than one large image.

Asking 240 members to mark "not spam" is a workaround, not a fix; it helps the next message only for those individuals, and does nothing for the members who never noticed.

Why a scanned signature fails. A photograph of a signature proves nothing about who attached it or whether the document changed afterwards. It can be copied onto any other page in seconds, it carries no timestamp, and if the resolution is altered the image still looks fine. For a bank, it is decoration, not authentication. The bank is asking for a signed PDF, so clarify (one phone call) whether it accepts an electronic signature - nearly all now do.

Resolution, two workable routes within 48 hours:

1. Aadhaar-based eSign through a licensed eSign Service Provider or a DigiLocker-linked flow. The treasurer verifies with an OTP from his own phone in the other city, and the PDF gains a visible signature plus a cryptographic signature and timestamp. Electronic signatures are recognised under the Information Technology Act, 2000 (Sections 3A, 4 and 5), so this is the fastest compliant route and needs no courier, printer or scanner.
2. A valid Digital Signature Certificate (Class 3) on the treasurer's USB token, applied with a PDF tool. This requires the token to be physically with him, which may rule it out at short notice. Once applied, the document is sealed - any later edit invalidates the signature.

Either way, verify the result before sending: a green/valid signature panel, "document has not been modified since signing", and a timestamp. Email it with a covering note and keep both the signed PDF and the signing log.

Loan certificate without a courier. Use DigiLocker: the member can pull issuer-signed certificates (income, caste, domicile and similar) as digitally signed documents, and a society-issued certificate can itself be eSigned and shared as a link or a signed PDF. A self-attested photocopy is acceptable only where the bank explicitly asks for one; where a verifiable document is available, send that instead.

One security note: the treasurer's DSC token PIN and any Aadhaar OTP must never be shared over email or WhatsApp - the whole point of the eSign flow is that only he can complete it.