On Fri, Dec 4, 2015 at 4:03 PM, Andrew
wrote:
> Exim itself should be the queue and processor shouldn't it?
>
> exim is not the job processor and queue. It is the Mail Transfer Agent
(MTA). The job
processor generates my email, and hands it off to exim for delivery.
--
Len Jaffe - Informatio
Am reading some interesting stuff now.
There's an odq argument you can pass to sendmail, which adds stuff to the mail
queue without waiting to send,
and there's a tutorial on Perl Maven for sending to multiple addresses using
Email::Stuffer without wasting memory creating multiple objects...or s
Exim itself should be the queue and processor shouldn't it?
- Original Message -
From: Len Jaffe
To: The elegant MVC web framework
Sent: Friday, December 04, 2015 8:48 PM
Subject: Re: [Catalyst] Sending 3000 emails.
On Fri, Dec 4, 2015 at 2:04 PM, Andrew
wrote:
On Fri, Dec 4, 2015 at 2:04 PM, Andrew
wrote:
>
>
> If you're handing off the mail to exim, you're fine. Your implementation
> is correct for your use case
>
> ---> Of course, I'm guessing I'm handing off to exim - I should probably
> do something to check!
>
> Look for Email::Sender configurati
If you're handing off the mail to exim, you're fine. Your implementation is
correct for your use case
---> Of course, I'm guessing I'm handing off to exim - I should probably do
something to check!
if the sign up for your service,
queue a "send them a welcome email" job,
and let th
Or in simpler terms
my web app could just set a flag.
And I could have another perl script going as a cron job, that just checks the
flag every hour, to see if it needs to send out the emails or not.
I'm curious in that case, how such a separate script gets bundled in with your
Cataylst
On Fri, Dec 4, 2015 at 11:35 AM, Andrew
wrote:
>
>
> one does not send any email directly as the result of a browser
> interaction,
> but rather one notes that an email needs to be sent (queues a job request),
> and a demon or cron job (a queue processor) creates ands sends the mail.
>
> > So
one does not send any email directly as the result of a browser interaction,
but rather one notes that an email needs to be sent (queues a job request),
and a demon or cron job (a queue processor) creates ands sends the mail.
> So let's do this. How do we go about it?
Scenario - use
