2015-03-09 17:44 GMT+01:00 Gavin Wahl :
> I expect this command to work with any email backend and to actually do a
> complete, end-to-end test of the configuration.
>
> I agree.
Another example: my SMTP provider will accept emails but put them on hold
until you've validated the sender's address.
> Thus, the test sending email is quite unnecessary, I would like a check
that connects to the SMTP server (if the emails settings are
setup else do nothing) when the application starts.
This wouldn't be useful to me at all. For one, it only is defined for an
SMTP backend. Also, I wouldn't trust
On Fri, Feb 27, 2015 at 9:01 AM, aRkadeFR wrote:
> Hello,
>
> I've written couple of time similar command for my project too.
>
> But if I take a step back, these commands (for my projects) are
> only here to test that my SMTP settings are well setup. Thus,
> the test sending email is quite unnece
Hello,
I've written couple of time similar command for my project too.
But if I take a step back, these commands (for my projects) are
only here to test that my SMTP settings are well setup. Thus,
the test sending email is quite unnecessary, I would like a check
that connects to the SMTP server
Hi Gavin,
I've lost track of how many times I've written that exact code when setting
up a new box - I just didn't wrap it up as a management command. There's a
similar testing cycle with new cache settings.
My only concern would be the one that Tim expressed - that it's ultimately
a one line she
I opened a ticket for this but was asked to discuss it on the mailing list.
When configuring django to send emails through an SMTP server, there are
usually many different settings to try to get it to work. I've written a
management command that just sends an email to make testing the settings
