Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.1.X] Fixed #13048: Corrected typo in email documentation. Backport of [12694] from trunk.

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12695 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
James Bennett 2010-03-07 00:52:11 +00:00
parent 55bcc8ac30
commit 8a8366d2fa
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/email.txt
View File

@ -354,11 +354,11 @@ send out, you could send this with::
Testing e-mail sending Testing e-mail sending
---------------------- ----------------------
The are times when you do not want Django to send e-mails at all. For example, There are times when you do not want Django to send e-mails at
while developing a website, you probably don't want to send out thousands of all. For example, while developing a website, you probably don't want
e-mails -- but you may want to validate that e-mails will be sent to the right to send out thousands of e-mails -- but you may want to validate that
people under the right conditions, and that those e-mails will contain the e-mails will be sent to the right people under the right conditions,
correct content. and that those e-mails will contain the correct content.
The easiest way to test your project's use of e-mail is to use a "dumb" e-mail The easiest way to test your project's use of e-mail is to use a "dumb" e-mail
server that receives the e-mails locally and displays them to the terminal, server that receives the e-mails locally and displays them to the terminal,