PhoneBlock 3.3.0

PhoneBlock 3.3.0

2026-11-01

Server

• The search page explains why a number is not accepted. Instead of a generic "not a phone number", it names the reason: unknown country code, too few digits for the area or service code (e.g. 032), trunk prefix after the country code, missing trunk prefix in national format, or too short. For numbers that cannot exist, it hints that the caller ID was probably spoofed.
• The FTC import works again (#657). It fetches the complaints from the FTC's API, since www.ftc.gov refuses downloads from outside the US. Requires the new JNDI setting ftc/api-key.
• Link a device by code (#621). A device that cannot receive the sign-in redirect (the dongle in Home Assistant) shows a code; the user types it in on the new page /link (on any device), which links it. The link carries no code, so a forwarded link cannot confirm anything. New API endpoints /api/link/start and /api/link/poll; the link URL uses the configured oauth/callbackBase.
• The dongle page points to help instead of asking for test reports. Questions go to the GitHub Discussions (Q&A), problems to a GitHub issue form for dongle problems; the Linux hint names the uucp group used by Arch Linux (#618).
• Code mails and code fields are easier to use. The code in the login and e-mail-change mail is no longer followed by a space that came along when copying it; the code fields ask the browser for a one-time code (numeric keypad, no suggestions of old codes).
• The settings page states the confidence correctly: each complaint adds 1, not 2.

Answer Bot

• The phoneblock/answerbot Docker image is no longer published with each server release. It is being retired in favour of phoneblock/answerbot2; the workflow can still be run by hand.
• The Docker image builds without Java or Maven on the host. docker build -f phoneblock-ab/Dockerfile . from the repository root compiles the answerbot inside Docker (idea from #213); the published multi-platform image is built the same way.