Provide setting to disable e-mail sending

(In [8695]) Fixed #8638 -- Show by example that the File.name attribute includes the upload directory as well as the filename. Patch from Ramiro Morales.

Whoops.. typo in commit message. Ignore the above commit.

Having the email get written to stdout might be a nice option for testing emails or seeing what would get sent vs. shutting it off completely.

I was thinking more in what the Testclient does now, having an "outbox" to read from. Printing on stdout can be bad. Imagine you are testing something that sends, ie: 100 mails in a row. You can't check this. But you also *dont want* those mails to go out ;)

+1 for this one

Replying to telenieko:

I was thinking more in what the Testclient does now, having an "outbox" to read from. Printing on stdout can be bad. Imagine you are testing something that sends, ie: 100 mails in a row. You can't check this. But you also *dont want* those mails to go out ;)

Right... I misunderstood this bug and thought it wanted to discard all emails. The outbox idea is much better than stdout, I agree.

Personally, I feel that stdout would be a wonderful option actually. While the email box is awesome, we need to create a bit of code to check that box for the email. While..well, it's not a pain, it'd be nice to just switch to the stdout (server) and see the email pop up there. I just was running into this today, but feel honestly that this sort of feature would be really helpful.

Kinda +1ing this as well, but having an option if we want to suppress stdout in the case of telenieko's feelings makes sense, for the 1-2 emails that I'm working with stdout would be optimal. Having an option for both would be great :)

Why not just use fakemail or something similar? It will dump emails to files in the directory of your choice, so they don't get sent out, but they can be inspected without special tools if necessary. I don't see the need to include something like this in Django when there are perfectly good existing solutions.

BTW, if you want to monitor the directory fastmail dumps into, you could do that with some simple scripting e.g.

watch 'find /path/to/fakemail/dir -type f | xargs cat'

I've started a thread on the Django Developers list: http://groups.google.com/group/django-developers/browse_thread/thread/e7c7228e1f12f174

Python does have it's own built-in version of "fakemail":

python /path/to/python/lib/python2.5/smtpd.py -n -c DebuggingServer localhost:1025

But there may be some ways to make it a little more nicely integrated that the discussion thread brings up.

Following some the mailing list discussion and some conversations with Rob Hudson, it looks like the best option here will be to fix this with documentation. There are some easy tricks you can do with Python's included batteries to fake a debug mail server:

python -m smtpd -n -c DebuggingServer localhost:1025

If you need more than this, you can hunt down fakemail or similar product.

Anyone has done anywork in the documentation? (to start it).

I have it on my list of things to do, but have not yet started anything. Feel free to jump in and I'd be happy to post comments or update a patch if needed.

Remember English is not my native language ;)

Some edits and additions to first patch.

(In [9793]) Fixed #8638 -- Added documentation on how to redirect email to a dummy server for testing purposes. Thanks to Rob Hudson and Marc Fargas for their work on the draft for this change.

(In [9798]) [1.0.X] Fixed #8638 -- Added documentation on how to redirect email to a dummy server for testing purposes. Thanks to Rob Hudson and Marc Fargas for their work on the draft for this change.

Merge of r9793 from trunk.

Milestone post-1.0 deleted