Mailpile issues

[jonaysanz]

Solve all Mailpile related issues linked in
https://www.cageos.org/index.php?page=apps&section=SecureEmail

[jonaysanz]

mailpile/Mailpile#723
mailpile/Mailpile#720
mailpile/Mailpile#695
mailpile/Mailpile#647
mailpile/Mailpile#488
mailpile/Mailpile#385
mailpile/Mailpile#348
mailpile/Mailpile#287
mailpile/Mailpile#735
mailpile/Mailpile#714
mailpile/Mailpile#710
mailpile/Mailpile#707
mailpile/Mailpile#701
mailpile/Mailpile#687
mailpile/Mailpile#683
mailpile/Mailpile#681
mailpile/Mailpile#251
mailpile/Mailpile#220
mailpile/Mailpile#741
mailpile/Mailpile#813
mailpile/Mailpile#807
mailpile/Mailpile#805
mailpile/Mailpile#798
mailpile/Mailpile#797
mailpile/Mailpile#776
mailpile/Mailpile#774
mailpile/Mailpile#613
mailpile/Mailpile#592
mailpile/Mailpile#591
mailpile/Mailpile#569
mailpile/Mailpile#565
mailpile/Mailpile#313
mailpile/Mailpile#815
mailpile/Mailpile#55
mailpile/Mailpile#60

[BjarniRunar]

Hello! Mailpile developer here.

Thanks for considering Mailpile, sorry it's taking us so long to get it written!

However, I'd like to recommend against what you are doing here. Mailpile's issue tracker evolves over time, issues get closed and new ones opened on a nearly daily basis. Even if that list of issues is the one that mattered to you at one point in time, it is almost certainly obsolete by now. In particular, a bunch of security-related issues have been filed in the meantime.

I think it would be much more productive if you would write down what features you feel are critical for your project and submit that as a single issue to Mailpile so we are aware of your needs (maybe use the checkmark feature of Github's Markdown, example below). And please consider whether simply tracking our 1.0 milestone (or later) isn't a better approach:

• Tell us what you need
• Avoid creating your own list of issues that's sure to become obsolete

Thanks!