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

Subject is prepended with a new "Re: " and "Re [2]:" etc on each reply #202

Closed
KenBW2 opened this Issue Jun 21, 2014 · 3 comments

Comments

3 participants
@KenBW2
Contributor

KenBW2 commented Jun 21, 2014

My desired behaviour is for it to not use the "Re: " prefix at all, and just use the same subject as the received email

@AndrewSav

This comment has been minimized.

Contributor

AndrewSav commented Jun 21, 2014

This is according to RFC5322 Appendix A.2. As such this is the behaviour majority of email clients I came across implement. An option to change this would be nice but one of course have to balance the number of options you provide to un-bloated feel and streamlined experience of their product.

If I were the author I would NOT implement the option because it benefits just a few people but can add to contributing of bloated feel that can scare off many. It's just one simple thing but they do add-up. Ideally a product should concentrate on one thing but doing this one thing well. Rainloop is pretty close.

@KenBW2

This comment has been minimized.

Contributor

KenBW2 commented Jun 21, 2014

This is according to RFC5322 Appendix A.2

Ah, I didn't realise this was the case. In which case I should probably go complain at the standard :) I just read up on it and this is optional:

When used in a reply, the field body MAY start with the string "Re: " ... If this is done, only one instance of the literal string "Re: " ought to be used


can add to contributing of bloated feel that can scare off many. It's just one simple thing but they do add-up.

This I understand. I like that Rainloop is pretty straightforward. See also: Gnome vs KDE

@RainLoop

This comment has been minimized.

Owner

RainLoop commented Jun 24, 2014

It's too simple functional for additional setting.
Many users got used to the standard behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment