I really don't see the point in using an Email model. Just use the email
sending module from the controller (Mail::Builder::Simple or whatever)
and setup a local postfix which accepts outbound emails from local
connections, and you're done. All queuing will be done by postfix, where
it belongs.
You need to install a local mail server so that the Catalyst app does
not get stuck trying to send. We can assume that messages sent from
localhost will be handed over to the local MTA pretty quickly (besides
corner cases like full mailspool and the like). This MTA can be a
full-blown one, or one configured to use use a smart host.
Catalyst offers you some posibilities, but it does not force you to use
them. To me, using a model for sending email is like hammering a nail
with a screw driver. You can surely do it, but it's simpler to use the
hammer. Even if you have a fancy screw driver. :-)
Regards
J.
El 21/03/11 08:51, John M. Dlugosz escribió:
On 3/21/2011 1:48 AM, Octavian Rasnita orasnita-at-gmail.com
|Catalyst/Allow to home| wrote:
You can use any of them or Catalyst::Helper::Model::Email. The plugin
is no longer recommended.
It looks like "helper" just installs a dummy Model that calls
Mail::Builder::Simple. So I thought I'd just call that. But, there
is no documentation as to the return value, and the code appears to
return 1 if it makes it to the end. But what does it return on error,
and where is the error particulars?
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive:
http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
