# The mail vendor had every contractor

2026-10-21

Rakus Light Cloud says Blastmail API servers were reached and that every contractor’s records left, plus some destination lists. JAPEX, Oita, and a line of cities then counted their own rooms. The vendor is the file.

Canonical: https://www.fabiocti.com/notes/the-mail-vendor-had-every-contractor/
Author: Fabio Correia

Each sender mailed its own list. The contractor table is still one table.

Rakus Light Cloud said Blastmail’s API servers were entered and that data left the sales-management system and the service database. Every contractor is in that take. Some contractors also lost destination lists. The company has not put a public number on either slice. It stopped the service.

The tenants then started. JAPEX: a magazine and an analyst-event list, still counting. Oita: a childcare-passport magazine, still counting. Kami, Yamanashi, Yuzawa: registered disaster and city mail. Niigata Nippo, later, will put about 253,000 on its own letter. JR Shikoku, about 30,000. Those are rooms. They are not a second incident, and they are not Cuenote.

## What “all contractors” will be asked to cover

It will be briefed as every Japanese newsletter. It is this vendor’s customers, and some of their lists. A list that sat on RAIDEN last week is a different vendor. A list that sat on Cuenote on Monday is a different vendor. Do not add the ceilings. Adding Oita does not empty JAPEX.

If a sender mailed you, the fields they listed are the incident. If they have not written, you are in the contractor file until that letter arrives. Do not click a “your disaster mail has moved” that already knows the old address. The vendor asked for a stop. The cities will keep issuing their own counts.

Subtract the overlap. The contractor table does not issue a new copy each time a logo speaks.