SSLError: bad handshake: SysCallError(104, 'ECONNRESET') about django-anymail HOT 2 CLOSED

Hmm. I think Anymail does need to re-cast that requests exception as an AnymailRequestsAPIError (in anymail.backends.BaseRequests.post_to_esp). That's required for proper fail_silently handling.

Of course, that'll still leave you with a flurry of (different) exceptions, if you're not using fail_silently.

There are several Django packages that maintain an email queue and robustly retry failed sends at a later time. Anymail should be compatible with most of them (any that let you change their email backend).

• I personally use the old Pinax django-mailer, which runs in Django's DB and works fine at my relatively-small scale. (Also, it seems to be getting maintained again -- yay!).
• Celery is popular for managing any sort of task queues in Django, and there are a bunch of Django email queues based on it.
• I'm sure there are others. (Including some interesting explorations using Django channels.)

Queue-and-resend functionality isn't built into Anymail, because there are different approaches that satisfy different needs, and the other packages cover the tradeoffs well. (Also, Anymail doesn't itself maintain any state or run any async tasks.)

from django-anymail.

Yep! I wouldn't propose a queueing system for Anymail -- edited the issue to clarify that.

This is already being fired from a Celery task where we catch most errors to turn them into a another attempt after a delay. This one bubbled up though since it was new.

from django-anymail.