Re: Queued mail sending
Re: Queued mail sending
- Subject: Re: Queued mail sending
- From: Þór Sigurðsson <email@hidden>
- Date: Wed, 29 Jan 2014 15:08:47 +0000
- Thread-topic: Queued mail sending
Don't queue the email - that's something the mail server itself is proficient at, not the WO framework (or any framework on top of that).
Instead, log the request - an email was requested. Send the email, and once the email has been sent, mark the request as handled.
That way, if your Wapp happens to turn its toes towards the sky, it still has the current state at restart.
And keep the log small. Very small. It should be fast end efficient (e.g. USERID:REQUEST_TYPE:DATE:(BOOL)HANDLED )
/Þór
On 29.1.2014, at 14:56, Musall Maik <email@hidden> wrote:
> Hi folks,
>
> how do you queue outbound email in WO apps?
>
> We use an 10+ years old custom implementation of a WOMailDelivery replacement, and I also looked at ERJavaMail. Both seem vulnerable to the same problem: if the application composes a mail, hands it over to the mailing framework, and the instance goes down before the mail is successfully sent to the SMTP server, the mail is lost. And if using the default non-blocking mode, and the SMTP server fails to accept the mail, it’s also lost if the instance is terminated before the queue gets a chance to deliver it again. Am I right on this for ERJavaMail?
>
> How do you deal with this? Is there another framework that does it better? I think there’s no way around having a persistent queue of some kind for outbound emails.
>
> Maik
________________________________
Fyrirvari á tölvupósti / e-mail disclaimer
http://samgongustofa.is/fyrirvari/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden