[GH-ISSUE #48] [Bug] Email reply to Github issue notifications is not showing up on Github #46

Closed
opened 2026-03-03 01:19:22 +03:00 by kerem · 5 comments
Owner

Originally created by @Kabouik on GitHub (Jun 20, 2020).
Original GitHub issue: https://github.com/d99kris/nmail/issues/48

Originally assigned to: @d99kris on GitHub.

I tested the account by sending regular emails to a secondary account, sending works perfectly. When replying to a Github issue notification, the message seems to send correctly too (no failure message), but it will never show up on Github.

Originally created by @Kabouik on GitHub (Jun 20, 2020). Original GitHub issue: https://github.com/d99kris/nmail/issues/48 Originally assigned to: @d99kris on GitHub. I tested the account by sending regular emails to a secondary account, sending works perfectly. When replying to a Github issue notification, the message seems to send correctly too (no failure message), but it will never show up on Github.
kerem closed this issue 2026-03-03 01:19:22 +03:00
Author
Owner

@d99kris commented on GitHub (Jun 24, 2020):

I can reproduce this problem. I suspect there is some header that nmail is not copying when constructing a reply message. I will need to do some testing and compare headers with Github replies sent from Gmail.

<!-- gh-comment-id:648878223 --> @d99kris commented on GitHub (Jun 24, 2020): I can reproduce this problem. I suspect there is some header that `nmail` is not copying when constructing a reply message. I will need to do some testing and compare headers with Github replies sent from Gmail.
Author
Owner

@d99kris commented on GitHub (Jun 24, 2020):

This is a test reply sent using Gmail Web.
Seems it will be sent to a special recipient (
reply+AAF...........@reply.github.com).
Possibly nmail is not respecting "reply-to" headers.

On Sun, Jun 21, 2020 at 4:53 AM Kabouik notifications@github.com wrote:

I tested the account by sending regular emails to a secondary account,
sending works perfectly. When replying to a Github issue notification, the
message seems to send correctly too (no failure message), but it will never
show up on Github.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/d99kris/nmail/issues/48, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAF75ZVMFUPZ6REQCUWT6A3RXUOTDANCNFSM4ODRG66A
.

<!-- gh-comment-id:648879910 --> @d99kris commented on GitHub (Jun 24, 2020): This is a test reply sent using Gmail Web. Seems it will be sent to a special recipient ( reply+AAF...........@reply.github.com). Possibly nmail is not respecting "reply-to" headers. On Sun, Jun 21, 2020 at 4:53 AM Kabouik <notifications@github.com> wrote: > I tested the account by sending regular emails to a secondary account, > sending works perfectly. When replying to a Github issue notification, the > message seems to send correctly too (no failure message), but it will never > show up on Github. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/d99kris/nmail/issues/48>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAF75ZVMFUPZ6REQCUWT6A3RXUOTDANCNFSM4ODRG66A> > . >
Author
Owner

@d99kris commented on GitHub (Jul 5, 2020):

Testing potential bug fix for issue #48.

<!-- gh-comment-id:653869501 --> @d99kris commented on GitHub (Jul 5, 2020): Testing potential bug fix for issue #48.
Author
Owner

@d99kris commented on GitHub (Jul 5, 2020):

Hi @Kabouik - thanks for reporting this bug. I've implemented a fix now. Let me know if you still encounter issues replying to Github issue notifications. Thanks!

<!-- gh-comment-id:653869800 --> @d99kris commented on GitHub (Jul 5, 2020): Hi @Kabouik - thanks for reporting this bug. I've implemented a fix now. Let me know if you still encounter issues replying to Github issue notifications. Thanks!
Author
Owner

@Kabouik commented on GitHub (Jul 12, 2020):

I can confirm it works for me too now!

On 2020-07-05 12:20 Kristofer Berggren notifications@github.com wrote:

Hi @Kabouik - thanks for reporting this bug. I've implemented a fix now. Let me know if you still encounter
issues replying to Github issue notifications. Thanks!

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/d99kris/nmail/issues/48#issuecomment-653869800

<!-- gh-comment-id:657228901 --> @Kabouik commented on GitHub (Jul 12, 2020): I can confirm it works for me too now! On 2020-07-05 12:20 Kristofer Berggren <notifications@github.com> wrote: > Hi @Kabouik - thanks for reporting this bug. I've implemented a fix now. Let me know if you still encounter > issues replying to Github issue notifications. Thanks! > > -- > You are receiving this because you were mentioned. > Reply to this email directly or view it on GitHub: > https://github.com/d99kris/nmail/issues/48#issuecomment-653869800 >
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nmail#46
No description provided.