The project page says:

If connection to server fails (with code -110, 404, 408 or 500-504), message will be added to Cron Queue for later delivery (if it still fails for some another reason, it will not be added to queue again), see #4 in installation guide.

There should be an option to control this, to prevent any outbound emails from being lost.

Comments

DamienMcKenna created an issue. See original summary.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Hrm... Where to store the messages though.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Looking at the code (I didn't write this part or touch it yet), the failed messages will be saved in the queue, even if they fail again and again.

I see the problem being actually being the creation of an infinite loop. If something is really wrong, the queue could start to grow out of control.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented

For comparison, SMTP saves the messages into a secondary queue if they fail, on the next cron run they get moved to the main queue, and then on the second cron run they get sent again.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

I will check out SMTP. Reuse is good.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Well, that essentially is the same thing. An infinite loop of queue's.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Going to mark this closed. The emails stay in the queue if they do not send.

There needs to be something done about an infinite loop of messages in queue if something goes wrong.

Perignon’s picture

Perignon CreditAttribution: Perignon commented
Status: Active » Closed (works as designed)