Skip to content

Reconsider message archiving  #245

@iandunn

Description

@iandunn

Currently SupportFlow archives messages once they're downloaded, rather than deleting them.

One benefit of this approach is that it's safer; if something goes wrong, or if the user's workflow/use case doesn't match our assumptions, then the messages are still available on the server.

One potential downside, though, is that their mailbox could fill up and then be unable to receive new emails. The SF admin would not know that until someone contacted them through an alternate channel to let them know.

One potential solution that wouldn't impact the current approach would be to have SupportFlow check the mailbox size, and warn admins when it reaches 80%, and let them know to clear out the archive folder if they want.

We should also consider whether we should delete messages by default, though. Either way, maybe we should have a filter to control archiving vs deleting.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions