Re: Queued mail sending
Re: Queued mail sending
- Subject: Re: Queued mail sending
- From: Samuel Pelletier <email@hidden>
- Date: Wed, 29 Jan 2014 17:23:50 -0500
Maik,
Your queue processor is responsible to ensure the message is passed to the next step (the SMTP server). It may even have multiple options available like a secondary server.
The point about storing only meta data is to save space, batch emails send information already in the system. For manual message, te message itself need to be stored but in this case, it is part of the required parameters for the template…
Here is an example of large saving: I had to send pdf invoices and statements produced by an external system, these PDF where available on the web and we needed some trace of when they where sent to who. If the file content where stored in the queue, it would have created copy of all the PDF for each recipient encoded in Base 64 (about 30% larger than binary). For 2000 PDFs per month, it represent a big space saving. BTW, this was a php system.
I will check the Ramsey frameworks next time I need to send email.
Samuel
Le 2014-01-29 à 15:54, Musall Maik <email@hidden> a écrit :
>
> Am 29.01.2014 um 17:58 schrieb Samuel Pelletier <email@hidden>:
>
>> Usually, I prefer to create some sort of persistent queue that contains only meta data about the email to send. The application code fill the queue to create message to send. This queue can manage the SMTP failure and also the flow. Sending 1000s of email in a batch process can trigger many load problems and some system may impose some rate limit.
>>
>> The meta data should contains only the information required to send the message, for example, the "to" email address, a class name or any other name that point to the template or code that will build the message and any parameters required by the template/code. For example, an account statement will require an account number or customer id.
>
> Metadata isn’t good enough. Consider the following scenario:
>
> 1. application generates emails normally, hands them over to smtp server
> 2. smtp server’s filesystem gets full and starts rejecting mail jobs
> 3. application continues to generate mails and hands them over, ignores rejection
>
> Until you discover what’s going on, there can hundreds or thousands of emails be generated and lost. And we don’t only generate emails automatically, there are also applications where users write them by hand. Any risk to lose the email’s content must be eliminated as far as possible.
>
> Maik
> _______________________________________________
> 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
_______________________________________________
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