Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In-Reply-To and References headers getting dropped when replying to public mailing list #463

Open
suhail-singh opened this issue Mar 4, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@suhail-singh
Copy link

suhail-singh commented Mar 4, 2024

Issue tracker is ONLY used for reporting bugs with technical details. "It doesn't work" or new features should be discussed with our customer support. Please use bug report function in Bridge or contact bridge@protonmail.ch.

When replying to a public mailing list that you're not subscribed to, the
In-Reply-To and References headers are dropped. I believe this is a
recurrence of #374 as noted in comments:

Expected Behavior

The In-Reply-To and References headers should remain as set by mail client.

Current Behavior

When In-Reply-To and References include message IDs that weren't received in
protonmail inbox, the headers get dropped.

Possible Solution

As noted in this comment some of the checks being done in smtp.go are
unnecessary and too stringent.

Steps to Reproduce

Compose a message with your mail client of choice with an In-Reply-To
containing a message-id that has never been received by your inbox. In the
email that gets sent, the In-Reply-To header is missing. Similarly for
References header.

See also #374.

Version Information

3.9.1

Context (Environment)

I am unable to respond to any public mailing lists that I review via Gmane, nor
am I able to effectively participate in patch submissions using Protonmail.

Detailed Description

The In-Reply-To and References headers should not be altered if set by the
mail client.

Possible Implementation

@LBeernaertProton LBeernaertProton added the bug Something isn't working label Mar 5, 2024
@LBeernaertProton
Copy link
Collaborator

Thanks for the report, Internally tracked as GODT-3297.

@suhail-singh
Copy link
Author

@LBeernaertProton you're welcome. If this is, indeed, a recurrence of #374 (GODT-2569), could its resolution also include a test to prevent such regressions in the future?

@suhail-singh
Copy link
Author

@LBeernaertProton it's been a few months. Could you please share the internal status of this issue?
Without this resolved, I am unable to use the bridge (or proton mail) for a majority of the emails I send.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants