Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

dealing with headers that affect how a message is replied to or bounced #22

Open
dkg opened this issue Nov 4, 2019 · 2 comments
Open

Comments

@dkg
Copy link
Member

dkg commented Nov 4, 2019

there are non-user-facing headers that are actionable during reply (e.g. that shift the behavior of the MUA somehow), like Reply-To and Mail-Followup-To. (and maybe Sender and Return-Path) ?

I worry that if we don't call these out specifically, then we are vulnerable to (at least) recipient-modification attacks.

I'm not sure how to characterize or exhaustively enumerate all such headers, or where in the spec such a mention belongs. The concept is subtly different from user-facing headers.

@dkg
Copy link
Member Author

dkg commented Nov 4, 2019

(see https://cr.yp.to/proto/replyto.html about Mail-Reply-To and Mail-Followup-To)

There is also Followup-To.

It's possible that Reply-To and Followup-To should themselves be labeled as "user-facing" as well. At least Thunderbird displays them to the user.

dkg added a commit that referenced this issue Nov 4, 2019
…rd displays them (see #22)

Signed-off-by: Daniel Kahn Gillmor <[email protected]>
@dkg
Copy link
Member Author

dkg commented Nov 4, 2019

I've included Reply-To and Followup-To as user-facing headers (because they are actually user-facing). But i am still concerned that there may be other headers that affect how replies are done but aren't actually user-facing, and we might want to handle them differently.

@dkg dkg changed the title dealing with Reply-To and Mail-Followup-To dealing with headers that affect how a message is replied to or bounced Nov 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant