ricard33 / cloud-mailing Goto Github PK

there are mailings with total pending lesser than 0

If the mailing is in FILLING_RECIPIENTS state, test emails (sent with 'send_test' API call) aren't retried if the first tentative ended in SOFTBOUNCE.

As test emails are simple recipients with a date far away in past, they can't be identified any more after a softbounce. So, during the FILLING_RECIPIENTS phase, it is impossible to select only test emails.

We should mark test (or priority) recipients with a specific property to allow efficient retries.

If a mailing is paused, recipients "in_progress" flag should be reseted.
It seems it's not the case (observed at least once) with version 0.1.1

Currently, recipients are stored into a temp queue to improve dispatching queries. But if temp queue is full, mailings using a "fast" satellite are blocked by recipients handled by a "slow" satellite.

The temp queue has been implemented with PostgreSQL backend. Maybe it is no more useful with MongoDB ?

Without index, the queries are limited by 32M memory buffer when sorting on a column (http://stackoverflow.com/a/27024732/245945).

When receiving DSN, we can't get this error:

Error trying to update recipient status: strings in documents must be valid UTF-8

When a queue finish with errors ( connection refused, all recipients refused or at least more than 50%), put this domain into a blocking state for a configurable delay.

Maybe the delay can increase (but into reasonable limits).