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

hey reply / hey draft send report success but the message stays in Drafts (send-as address)

Abierto
  • ¿Algo no está bien?
#544 1 comentario 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
49/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go
Área
cli

Línea de trabajo

Start by tracing the hey reply and hey draft send command paths described in the report, including how each decides a send succeeded. Compare their reported success with the observed thread and Drafts state for a send-as address. Done means the message is delivered and leaves Drafts, or the command reports failure rather than success when it remains a draft.

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

Descripción

Summary

With hey-cli 1.7.0 (Linux), replying in a thread whose latest entry was sent from a send-as address reports success, but nothing is delivered: the message stays in Drafts and never appears in the thread. Running hey draft send on that draft also reports success and has the same result. Because both commands exit ok, an agent or script assumes the email went out.

Steps to reproduce

  1. Pick a thread whose latest entry you sent from a send-as address (not the primary @hey.com identity).
  2. Check the envelope: 
    hey reply <thread-id> --replace-recipients --to [email protected] --cc [email protected] --dry-run
    This resolves correctly: "from": {"email_address": "<send-as address>"}, with the right To and CC.
  3. Send it: 
    hey reply <thread-id> --replace-recipients --to [email protected] --cc [email protected] -m "..."
    Output: {"ok": true, ..., "summary": "Reply sent"}
  4. hey thread read <thread-id> --json: the entry count is unchanged, even after several minutes.
  5. hey draft list --json: the reply is there as a draft (subject Re: ..., from = the send-as address, correct To/CC and body).
  6. hey draft send <draft-id>: {"ok": true, "data": {"id": <draft-id>}, "summary": "Draft sent"}
  7. Polling for about 2 more minutes: the thread still has the same number of entries, and the draft is still in hey draft list.

Expected

Either the reply is delivered (it shows up in the thread and leaves Drafts), or the command exits non-zero with the server's reason. A success summary should only be reported once the message has actually left Drafts.

Actual

Both commands report success while the message stays an unsent draft. Sending from the HEY web app is the workaround.

Notes

  • Related but different: #483 (send-as used the wrong identity, closed), #520 (502 after a send, outcome unknown), #477 (idempotency for reruns). Here there's no error at all, just a false success.
  • A post-send check would help agents: after reply / draft send, confirm the draft is gone or the thread grew, and report something like "delivered": false otherwise.
  • I didn't retry beyond that, to avoid sending a duplicate to the recipient.
Lenguaje dominante
Go
Estrellas
409
Forks
49
Merge medio
1 d 6 h
PR fusionados (30 d)
81

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.