Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Feature request: domain-level screening (screen a whole domain in or out)

Abierto
  • ¿Algo no está bien?
#582 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli

Línea de trabajo

Start by reading the CLI command implementations for hey screener approve, hey screener history, hey contact show, and hey contact deliver, then inspect how the web app stores and applies its @domain screening rule. Decide which proposed command or flag fits the existing CLI patterns and how it should report rules that apply. Done means domain level screening can be configured from the CLI and applicable rules appear in the requested show and history output.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

Some services send every email from a new, randomized address on the same domain. Anthropic's sign-in links are one example: each one comes from no-reply-<random>@mail.anthropic.com, such as [email protected]. Each one lands in The Screener as a new sender, so hey screener approve and hey contact deliver never stick.

The web app handles this with the contact page's @domain button → "Automatically screen them to the Imbox". The CLI has no equivalent, so this setting can't be scripted or done by an agent.

Proposal

Something like:

hey screener domain list [--json]
hey screener domain set mail.anthropic.com --to imbox|feed|papertrail|screened-out|individually

and/or a --domain flag on hey screener approve <clearance_id> that applies the decision to the sender's whole domain.

It would also help if hey contact show and hey screener history reported a domain-level rule when one applies.

Why

  • Sign-in links and verification codes are time-sensitive. When they get stuck in The Screener, you have to approve a new sender every time.
  • This pairs with hey contact deliver and the open auto-label request (#577) to configure senders entirely from the CLI.

Checked against hey-cli 1.9.0 (no domain-level screening in screener or contact).

Lenguaje dominante
Go
Estrellas
414
Forks
53
Merge medio
1 d 7 h
PR fusionados (30 d)
74

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de basecamp/hey-cli

Todos los issues de basecamp/hey-cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.