Built from the repeated-email problem.

The problem behind the service

Blocking one address rarely ends a campaign. Senders rotate accounts, domains, hosting and display names. The useful unit of work is the case: the original message, its authenticated delivery path, every destination, the role of each provider and the replies that follow.

The operating method

Preserve the original before investigating. Separate direct observations from inference. Map services before deciding where evidence belongs. Automate collection, hashing and duplicate grouping, while keeping submissions that require judgment or an owner statement visible for review.

Why a reporting folder works

People already know how to move email on a phone. A synchronized Report to Meilo folder turns that familiar action into a deliberate instruction. Ordinary Junk stays available for normal filtering, and a personal flag remains a reminder rather than an accidental incident report.

Local-first by design

The free checker runs in the browser. The connected engine preserves evidence on owned systems and uses deterministic processing for extraction and grouping. A model can assist with explanation, but it does not replace the original message, provider evidence or a human decision about a consequential report.

Evidence before attribution

A shared IP, reused template or similar writing style can connect infrastructure or campaigns without proving a person's identity. Meilo names a technical service when the record supports it and states uncertainty where operator identity remains undisclosed.

Where Meilo works

The service is based in Vancouver and serves Canadian small businesses. Connected-mail compatibility, mailbox scope, retention, permissions and rollback are checked before activation.