Multiple databases and caches can currently be configured in one's
settings file. It'd be nice if the same could be done with email
connections. For example, Amazon's SES starts out new users with a low
quota that they gradually increase, so splitting emails between SES
and other connections to sta
On Wed, Feb 23, 2011 at 9:02 AM, Niran Babalola wrote:
> Multiple databases and caches can currently be configured in one's
> settings file. It'd be nice if the same could be done with email
> connections. For example, Amazon's SES starts out new users with a low
> quota that they gradually increa
+1
On Tue, Feb 22, 2011 at 8:39 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
> On Wed, Feb 23, 2011 at 9:02 AM, Niran Babalola wrote:
> > Multiple databases and caches can currently be configured in one's
> > settings file. It'd be nice if the same could be done with email
> > conne
On Tue, 2011-02-22 at 19:02 -0600, Niran Babalola wrote:
> Multiple databases and caches can currently be configured in one's
> settings file. It'd be nice if the same could be done with email
> connections. For example, Amazon's SES starts out new users with a low
> quota that they gradually incre
On Wed, Feb 23, 2011 at 11:44 AM, Luke Plant wrote:
> Is it not possible to do this already, by writing your own backend that
> splits up e-mails as you see fit?
Yes, but it'd be nice if the get_connection arguments for each
connection type could be easily referenced by name. Distributing
emails
On Thu, Feb 24, 2011 at 1:44 AM, Luke Plant wrote:
> On Tue, 2011-02-22 at 19:02 -0600, Niran Babalola wrote:
>> Multiple databases and caches can currently be configured in one's
>> settings file. It'd be nice if the same could be done with email
>> connections. For example, Amazon's SES starts o
I agree that this makes a lot of sense for 1.4.
Probably the most common use case is going to be separating classes of
emails (mass-mails (mailchimp or constant contact), transactional
(amazon ses or your provider's mailserver), backend admin
notifications (server sendmail or local mail spool), et
