I'm attempting to setup pyramid_mailer with a website I'm developing. The
current documentation (
http://docs.pylonsproject.org/projects/pyramid_mailer/en/latest/)
recommends creating a single instance of the Mailer and adding it to the
configuration setup. However, I want to configure numerous jobs that will
run separately from the Pyramid web application using something like the
Python APScheduler that will also send emails out to users. Instead of
having two separate Pyramid Mailer instances in the app, I would like to
abstract the email system into something more like a service . My primary
goal is to use the same Mailer configuration for my scheduled services as
my Pyramid application since this more clearly follows the principal of
Don't Repeat Yourself. Any ideas on how I could accomplish this?

Thanks for your help!

-- 
Vincent Catalano

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to