mushorg / spamcan Goto Github PK

Fetching mails should be run as a background task, decoupled from the web interface. There should be no need to look into your spam traps every day for maintenance.

With pretty graphs and the like.

Add SSL support for pop3 and imap connections.

Migrate all the configuration files to JSON files.

spamcan.cfg -> spamcan.json
accounts.cfg -> accounts.json
thug.cfg -> thug.json

These should all be in the conf directory

HPFeeds is awesome...we should support it.

Make the delete button work.
(with confirmation - javascript wizardry)

In case of fetching mails from more than one account we should do it in parallel. There is only a concurrency issue if we want to write into the same maildir in parallel.

Right now this is a less elegant POST request with a following redirect. We should catch the action and handle it using jQuery. Also add a "spinning wheel" to see that something is happening in the background.

Instead of not adding an account, mark it as mal-formed in the account list

We don't want to re-download mails all the time. If we keep track of the latest local id, we can make pulling mails more efficient.

Background tasks should be monitored and a notification send to the owner in case a task fails.

The refresh button is updating ID instead of the mail count...

./

"Fetch emails" - pull email from mail server
"Crawl URLs" - parse emails and pull out links
"Submit URLs" - submit URLs to Thug
"Submit Binaries" - submit binaries to Cuckoo

Save emails locally into a maildir: http://docs.python.org/2/library/mailbox.html#maildir

Add an option to edit an account.