On Thu, Nov 26, 2015 at 4:32 PM, Andrew wrote:
> I just want to know why the whole FastCGI Plack loaded Catalyst app came
> down half way through,
> and how I can have a Perl script process sending 3000 emails without that
> happening every time, =S.
>
As
I would pick up at least an email alias, that can be easibly
auto-generated and updated each time a new user joins.
---> While I understand the principles you are recommending, I'm not sure
exactly what is being suggested, as regards to implementation. Are we
talking exim, vexim, a custom perl
- Original Message -
From: Len Jaffe
To: The elegant MVC web framework
Sent: Friday, December 04, 2015 10:14 PM
Subject: Re: [Catalyst] Sending 3000 emails.
On Fri, Dec 4, 2015 at 4:03 PM, Andrew <catalystgr...@unitedgames.co.uk>
wrote:
Exim itself
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 -
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 <catalys
...or so I
gather from an initial skim read...
- Original Message -
From: Andrew
To: The elegant MVC web framework
Sent: Friday, December 04, 2015 9:03 PM
Subject: Re: [Catalyst] Sending 3000 emails.
Exim itself should be the queue and processor shouldn't
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
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!
>
>
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
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
: Andrew
To: The elegant MVC web framework
Sent: Friday, December 04, 2015 4:35 PM
Subject: Re: [Catalyst] Sending 3000 emails.
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
quot; <dar...@darrenduncan.net>
To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk>
Sent: Monday, November 30, 2015 11:41 PM
Subject: Re: [Catalyst] Sending 3000 emails.
On 2015-11-30 9:29 AM, Andrew wrote:
> ...given that my attempt to send 3000 emails
On 12/2/2015 10:10 AM, Andrew wrote:
> As noted, it all works until about 1020 emails in, at which point the
> Catalyst app crashes (although this has only happened once - I do not wish
> to try again and risk another crash). I am using Email::Stuffer in a for
> loop, iterating over an array of
Original Message -
> From: "Darren Duncan" <dar...@darrenduncan.net>
> To: "The elegant MVC web framework" <catalyst@lists.scsys.co.uk>
> Sent: Monday, November 30, 2015 11:41 PM
> Subject: Re: [Catalyst] Sending 3000 emails.
>
>
> On 2015-11-30
On Wed, Dec 2, 2015 at 10:59 AM, Lance A. Brown
wrote:
> On 12/2/2015 10:10 AM, Andrew wrote:
> > As noted, it all works until about 1020 emails in, at which point the
> > Catalyst app crashes (although this has only happened once - I do not
> wish
> > to try again and risk
y, November 29, 2015 1:31 AM
Subject: Re: [Catalyst] Sending 3000 emails.
I'll add that you should look into a transactional email partner like
sendgrid, mailgun, etc. They'll help you stay out of the black lists by
showing you what not to do, ans how to set up DKIM, etc. for authentic
e hands them to local SMTP, and the local SMPT delivers them
upstream (called smarthosting) to sendgrid for delivery to the far corners
to the net.
> - Original Message -
> *From:* Len Jaffe <lenja...@jaffesystems.com>
> *To:* The elegant MVC web framework <catalyst@lists.sc
I'll add that you should look into a transactional email partner like
sendgrid, mailgun, etc. They'll help you stay out of the black lists by
showing you what not to do, ans how to set up DKIM, etc. for authentication
of your email.
I use sendgrid professionally, with one of my cusotmers that
Hi Andrew,
You lot are all experts at Catalyst and Perl,
I am no expert in Catalyst or Perl, but I have learned a thing or two
about email in my career.
I have found the best way for people to send butt-loads of emails to
members is to use mailing list software. This generally involves
A queue in Perl is better when there is a need of sending thousand messages.
Without a queue, if the Catalyst-based code just sends the messages directly
and a browser is waiting for a page to load after the web app sent them, it may
time-out. But otherwise it should work and not crash the web
Maybe not the answer you're looking for but I'd go with an email service
such as sendgrid which takes most if not all of the pain out of sending
emails. They have a simple REST API you can POST your email to and provides
callbacks for delivery notifications etc as well...
I'm not advocating
21 matches
Mail list logo