Matt Molyneaux
Matt Molyneaux
Should have been done a long time ago: * [x] How to deploy * https://github.com/Inboxen/Inboxen/issues/98 * [ ] Admin guide * [x] Update settings.ini docs
Probably best done per inbox. We should also notify users that an inbox is getting spammed and that we've taken action to prevent their account from becoming overwhelmed.
Something like https://github.com/django/djangobench would be useful
[This article makes some claims about NPM modules doing nasty stuff](https://hackernoon.com/im-harvesting-credit-card-numbers-and-passwords-from-your-site-here-s-how-9a8cb347c5b5) We already set `connect-src` to `'self'`, but I'd be interested to see if I can get that CSP bypass...
It should be possible to "claim" a ticket before replying to avoid multiple people replying to the same ticket.
As the CMS grows more complex, we're going to want a CMS that works for large and small installs. For starters, it would be incredibly handy if an admin could...
* Each email should be given some sort of unique ID (that's not easily guessable) that can be used to identify replies * Don't store the entire email as we...
Currently, users have to go looking for 2fa. Add a skippable step to user registration.
E.g. ``` Email.objects.filter(user=user).order_by("-received_date") # wrong! Email.objects.filter(user=user).order_by("-received_date", "id") # correct! ``` The first queryset won't have objects in a predictable order as `received_date` is not unique. The second guarantees predictable order...
Inboxen is intended to be a receive-only service, but sometimes a user is required to send an email from a particular address (e.g. certain mailing lists that provide no web...