Django not sending emails to admins
According to the documentation, if DEBUG
is set to False
and something is provided under the ADMINS
setting, Django will send an email whenever the code raises a 500 status code. I have the email settings filled out properly (as I can use send_mail fine) but whenever I intentionally put up erroneous code I get my 500.html template but no error email is sent. What could cause Django to not do this?
python django
add a comment |
According to the documentation, if DEBUG
is set to False
and something is provided under the ADMINS
setting, Django will send an email whenever the code raises a 500 status code. I have the email settings filled out properly (as I can use send_mail fine) but whenever I intentionally put up erroneous code I get my 500.html template but no error email is sent. What could cause Django to not do this?
python django
add a comment |
According to the documentation, if DEBUG
is set to False
and something is provided under the ADMINS
setting, Django will send an email whenever the code raises a 500 status code. I have the email settings filled out properly (as I can use send_mail fine) but whenever I intentionally put up erroneous code I get my 500.html template but no error email is sent. What could cause Django to not do this?
python django
According to the documentation, if DEBUG
is set to False
and something is provided under the ADMINS
setting, Django will send an email whenever the code raises a 500 status code. I have the email settings filled out properly (as I can use send_mail fine) but whenever I intentionally put up erroneous code I get my 500.html template but no error email is sent. What could cause Django to not do this?
python django
python django
asked Sep 12 '09 at 2:57
JoseVega
add a comment |
add a comment |
19 Answers
19
active
oldest
votes
In my case the cause was missing SERVER_EMAIL setting.
The default for SERVER_EMAIL
is root@localhost
. But many of email servers including
my email provider do not accept emails from such suspicious addresses. They silently drop the emails.
Changing the sender email address to django@my-domain.com
solved the problem. In settings.py
:
SERVER_EMAIL = 'django@my-domain.com'
2
Another hint that this is likely the problem is if you check your mail log and see an entry containingsender non-delivery notification
.
– jathanism
Jun 25 '12 at 16:58
add a comment |
Another possibility for error is trouble with your ADMINS setting. The following setting will cause the sending of mail to admins to fail quietly:
ADMINS = (
('your name', 'me@mydomain.com')
)
What's wrong with that? Well ADMINS needs to be a tuple of tuples, so the above needs to be formatted as
ADMINS = (
('your name', 'me@mydomain.com'),
)
Note the trailing comma. Without the failing comma, the 'to' address on the email will be incorrectly formatted (and then probably discarded silently by your SMTP server).
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
add a comment |
I had the same situation. I created a new project and app and it worked, so I knew it was my code. I tracked it down to the LOGGING dictionary in settings.py. I had made some changes a few weeks back for logging with Sentry, but for some reason the error just started today. I changed back to the original and got it working:
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'mail_admins': {
'level': 'ERROR',
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
Then, I made some changes slowly and got it working with Sentry and emailing the ADMINS as well.
Additionally, the LOGGING
configuration gets merged with DEFAULT_LOGGING
by default, so it's useful to have a look at the source code of django.utils.log.DEFAULT_LOGGING
to understand what else may have an effect on your particular situation.
3
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
1
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumeddisable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.
– guidos
Mar 22 '16 at 16:22
Thanks! my problem was on'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
add a comment |
Make sure your EMAIL_HOST and EMAIL_PORT are set up right in settings.py (these refer to your SMTP server). It might be assuming that you have an SMTP server running on localhost.
To test this locally, run Python's built-in test SMTP server:
python -m smtpd -n -c DebuggingServer localhost:1025
Then set these values in your settings.py
EMAIL_HOST='localhost'
EMAIL_PORT=1025
Trigger a 500 error, and you should see the e-mail appear in the python smtpd terminal window.
2
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
add a comment |
My web hosting provider - Webfaction - only allows emails to be sent From an email that has been explicitly created in the administrator panel. Creating one fixed the problem.
1
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
1
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
add a comment |
Another thing worth noting here is that settings handler500
might bypass the mechanism that sends errors on a 500 if the response from the view doesn't have a status code of 500.
If you have a handler500
set, then in that view respond with something like this.
t = loader.get_template('500.html')
response = HttpResponseServerError(
t.render(RequestContext(request, {'custom_context_var':
'IT BROKE OMG FIRE EVERYONE'})))
response.status_code = 500
return response
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
add a comment |
Try this
# ./manage shell
>>> from django.core.mail import send_mail
>>> send_mail('Subject here', 'Here is the message.', 'from@example.com',['to@example.com'], fail_silently=False)
With a to@example.com that you actually get email at.
3
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
add a comment |
Make sure you have DEBUG = False
add a comment |
Sorry if it is too naive, but in my case the emails were sent but were going directly to the SPAM folder. Before trying more complicated things check your SPAM folder first.
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
add a comment |
Although it's been a while, here's my response, so that other people can benefit in the future.
In my case, what was preventing emails to be sent to the ADMINS list, when an error occured, was an application specific setting. I was using django-piston, which provides the setting attributes PISTON_EMAIL_ERRORS and PISTON_DISPLAY_ERRORS. Setting these accordingly, enabled the application server to notify my by mail, whenever piston would crash.
add a comment |
If, for some reason, you set DEBUG_PROPAGATE_EXCEPTIONS to True (it's False by default), email to admin will not work.
add a comment |
... and then there's the facepalm error, when you've used this in development to prevent emails from going out, and then accidentally copy the setting to production:
# Print emails to console
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
(of course you don't see them being printed to console when using a wsgi server). Removing the setting from production fixed this for me.
add a comment |
Just had the same issue after upgraded to Django 2.1 from Django 1.11. Apparently the ADMINS
sections in settings.py
has a change. It takes a list of tuples now, rather than the old tuple of tuples. This fixed for me.
##### old #####
ADMINS = (
("Your Name", "your_email@company.com")
)
##### new #####
ADMINS = [
("Your Name", "your_email@company.com")
]
Re: https://docs.djangoproject.com/en/2.1/ref/settings/#admins
add a comment |
While likely not ideal, I have found using Gmail as the SMTP host works just fine. There is a useful guide at nathanostgard.com.
Feel free to post your relevant settings.py sections (including EMAIL_*, SERVER_EMAIL, ADMINS (just take out your real email), MANAGERS, and DEBUG) if you want an extra set of eyes to check for typos!
add a comment |
For what it's worth I had this issue and none of these suggestions worked for me. It turns out that my problem was that SERVER_EMAIL
was set to an address that the server (Webfaction) didn't recognise. If this site were hosted on Webfaction (as my other sites are), this wouldn't be a problem, but as this was on a different server, the Webfaction servers not only check the authentication of the email being sent, but also the From:
value as well.
add a comment |
In my case, it's the include_html
in mail_admins
.
When I set include_html
to True
,the email server reject to send my email because it think that my emails are spam.
Everything works just fine when I set include_html
to False
.
add a comment |
And yet another thing that can go wrong (I'll just add it to the list, for those people that end up here despite all the great answers above):
Our django setup used SendGrid as the smtp host and had a single admin email-address defined in the django settings. This worked fine for some time, but at some point, mails stopped arriving.
As it turns out, the mail address ended up in the SendGrid 'Bounced' list for some unknown reason, causing emails to that address to be silently dropped forever after. Removing the address from that list, and whitelisting it, fixed the issue.
add a comment |
If you are using or would want to use SendGrid, use the settings below in production.
Install the package
pip install sendgrid-django
Add these settings in settings.py(production)
DEBUG = False
EMAIL_BACKEND = "sendgrid_backend.SendgridBackend"
SENDGRID_API_KEY = "That you generate in sendgrid account"
ADMINS = (
("Your Name", "your_email@company.com")
)
add a comment |
The below info is given in https://docs.djangoproject.com/en/2.1/howto/error-reporting/#email-reports
EMAIL_HOST = "email host"
EMAIL_HOST_USER = "Email username"
EMAIL_HOST_PASSWORD = "Email Password"
DEBUG = False
ADMINS = (
("Your Name", "your_email@company.com")
)
In order to send email, Django requires a few settings telling it how
to connect to your mail server. At the very least, you’ll need to
specify EMAIL_HOST and possibly EMAIL_HOST_USER and
EMAIL_HOST_PASSWORD, though other settings may be also required
depending on your mail server’s configuration. Consult the Django
settings documentation for a full list of email-related settings.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f1414130%2fdjango-not-sending-emails-to-admins%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
19 Answers
19
active
oldest
votes
19 Answers
19
active
oldest
votes
active
oldest
votes
active
oldest
votes
In my case the cause was missing SERVER_EMAIL setting.
The default for SERVER_EMAIL
is root@localhost
. But many of email servers including
my email provider do not accept emails from such suspicious addresses. They silently drop the emails.
Changing the sender email address to django@my-domain.com
solved the problem. In settings.py
:
SERVER_EMAIL = 'django@my-domain.com'
2
Another hint that this is likely the problem is if you check your mail log and see an entry containingsender non-delivery notification
.
– jathanism
Jun 25 '12 at 16:58
add a comment |
In my case the cause was missing SERVER_EMAIL setting.
The default for SERVER_EMAIL
is root@localhost
. But many of email servers including
my email provider do not accept emails from such suspicious addresses. They silently drop the emails.
Changing the sender email address to django@my-domain.com
solved the problem. In settings.py
:
SERVER_EMAIL = 'django@my-domain.com'
2
Another hint that this is likely the problem is if you check your mail log and see an entry containingsender non-delivery notification
.
– jathanism
Jun 25 '12 at 16:58
add a comment |
In my case the cause was missing SERVER_EMAIL setting.
The default for SERVER_EMAIL
is root@localhost
. But many of email servers including
my email provider do not accept emails from such suspicious addresses. They silently drop the emails.
Changing the sender email address to django@my-domain.com
solved the problem. In settings.py
:
SERVER_EMAIL = 'django@my-domain.com'
In my case the cause was missing SERVER_EMAIL setting.
The default for SERVER_EMAIL
is root@localhost
. But many of email servers including
my email provider do not accept emails from such suspicious addresses. They silently drop the emails.
Changing the sender email address to django@my-domain.com
solved the problem. In settings.py
:
SERVER_EMAIL = 'django@my-domain.com'
edited Mar 28 '14 at 17:07
Radek Simko
5,507155697
5,507155697
answered Jul 1 '11 at 17:54
geekQgeekQ
23.5k84748
23.5k84748
2
Another hint that this is likely the problem is if you check your mail log and see an entry containingsender non-delivery notification
.
– jathanism
Jun 25 '12 at 16:58
add a comment |
2
Another hint that this is likely the problem is if you check your mail log and see an entry containingsender non-delivery notification
.
– jathanism
Jun 25 '12 at 16:58
2
2
Another hint that this is likely the problem is if you check your mail log and see an entry containing
sender non-delivery notification
.– jathanism
Jun 25 '12 at 16:58
Another hint that this is likely the problem is if you check your mail log and see an entry containing
sender non-delivery notification
.– jathanism
Jun 25 '12 at 16:58
add a comment |
Another possibility for error is trouble with your ADMINS setting. The following setting will cause the sending of mail to admins to fail quietly:
ADMINS = (
('your name', 'me@mydomain.com')
)
What's wrong with that? Well ADMINS needs to be a tuple of tuples, so the above needs to be formatted as
ADMINS = (
('your name', 'me@mydomain.com'),
)
Note the trailing comma. Without the failing comma, the 'to' address on the email will be incorrectly formatted (and then probably discarded silently by your SMTP server).
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
add a comment |
Another possibility for error is trouble with your ADMINS setting. The following setting will cause the sending of mail to admins to fail quietly:
ADMINS = (
('your name', 'me@mydomain.com')
)
What's wrong with that? Well ADMINS needs to be a tuple of tuples, so the above needs to be formatted as
ADMINS = (
('your name', 'me@mydomain.com'),
)
Note the trailing comma. Without the failing comma, the 'to' address on the email will be incorrectly formatted (and then probably discarded silently by your SMTP server).
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
add a comment |
Another possibility for error is trouble with your ADMINS setting. The following setting will cause the sending of mail to admins to fail quietly:
ADMINS = (
('your name', 'me@mydomain.com')
)
What's wrong with that? Well ADMINS needs to be a tuple of tuples, so the above needs to be formatted as
ADMINS = (
('your name', 'me@mydomain.com'),
)
Note the trailing comma. Without the failing comma, the 'to' address on the email will be incorrectly formatted (and then probably discarded silently by your SMTP server).
Another possibility for error is trouble with your ADMINS setting. The following setting will cause the sending of mail to admins to fail quietly:
ADMINS = (
('your name', 'me@mydomain.com')
)
What's wrong with that? Well ADMINS needs to be a tuple of tuples, so the above needs to be formatted as
ADMINS = (
('your name', 'me@mydomain.com'),
)
Note the trailing comma. Without the failing comma, the 'to' address on the email will be incorrectly formatted (and then probably discarded silently by your SMTP server).
answered Aug 8 '13 at 21:30
wxgeorgewxgeorge
39347
39347
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
add a comment |
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
(It was thanks to @cathal 's answer above running a debugging SMTP server locally that allowed me to locate this as my problem).
– wxgeorge
Aug 8 '13 at 21:31
add a comment |
I had the same situation. I created a new project and app and it worked, so I knew it was my code. I tracked it down to the LOGGING dictionary in settings.py. I had made some changes a few weeks back for logging with Sentry, but for some reason the error just started today. I changed back to the original and got it working:
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'mail_admins': {
'level': 'ERROR',
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
Then, I made some changes slowly and got it working with Sentry and emailing the ADMINS as well.
Additionally, the LOGGING
configuration gets merged with DEFAULT_LOGGING
by default, so it's useful to have a look at the source code of django.utils.log.DEFAULT_LOGGING
to understand what else may have an effect on your particular situation.
3
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
1
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumeddisable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.
– guidos
Mar 22 '16 at 16:22
Thanks! my problem was on'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
add a comment |
I had the same situation. I created a new project and app and it worked, so I knew it was my code. I tracked it down to the LOGGING dictionary in settings.py. I had made some changes a few weeks back for logging with Sentry, but for some reason the error just started today. I changed back to the original and got it working:
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'mail_admins': {
'level': 'ERROR',
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
Then, I made some changes slowly and got it working with Sentry and emailing the ADMINS as well.
Additionally, the LOGGING
configuration gets merged with DEFAULT_LOGGING
by default, so it's useful to have a look at the source code of django.utils.log.DEFAULT_LOGGING
to understand what else may have an effect on your particular situation.
3
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
1
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumeddisable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.
– guidos
Mar 22 '16 at 16:22
Thanks! my problem was on'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
add a comment |
I had the same situation. I created a new project and app and it worked, so I knew it was my code. I tracked it down to the LOGGING dictionary in settings.py. I had made some changes a few weeks back for logging with Sentry, but for some reason the error just started today. I changed back to the original and got it working:
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'mail_admins': {
'level': 'ERROR',
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
Then, I made some changes slowly and got it working with Sentry and emailing the ADMINS as well.
Additionally, the LOGGING
configuration gets merged with DEFAULT_LOGGING
by default, so it's useful to have a look at the source code of django.utils.log.DEFAULT_LOGGING
to understand what else may have an effect on your particular situation.
I had the same situation. I created a new project and app and it worked, so I knew it was my code. I tracked it down to the LOGGING dictionary in settings.py. I had made some changes a few weeks back for logging with Sentry, but for some reason the error just started today. I changed back to the original and got it working:
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'handlers': {
'mail_admins': {
'level': 'ERROR',
'class': 'django.utils.log.AdminEmailHandler'
}
},
'loggers': {
'django.request': {
'handlers': ['mail_admins'],
'level': 'ERROR',
'propagate': True,
},
}
}
Then, I made some changes slowly and got it working with Sentry and emailing the ADMINS as well.
Additionally, the LOGGING
configuration gets merged with DEFAULT_LOGGING
by default, so it's useful to have a look at the source code of django.utils.log.DEFAULT_LOGGING
to understand what else may have an effect on your particular situation.
edited Nov 14 '16 at 17:32
answered Mar 2 '12 at 23:08
FurbeenatorFurbeenator
5,11243146
5,11243146
3
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
1
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumeddisable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.
– guidos
Mar 22 '16 at 16:22
Thanks! my problem was on'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
add a comment |
3
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
1
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumeddisable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.
– guidos
Mar 22 '16 at 16:22
Thanks! my problem was on'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
3
3
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
Under Django 1.4 this fixed it for us.
– boatcoder
Aug 31 '12 at 23:46
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
This fixed it for me (Django 1.7). Thanks
– Paco
Jan 7 '15 at 16:40
1
1
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumed
disable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.– guidos
Mar 22 '16 at 16:22
Adding logging settings killed my admin emails, which worked fine before with default logging. I assumed
disable_existing_loggers': False
would keep existing logging as is, but it didn't. This fixed it.– guidos
Mar 22 '16 at 16:22
Thanks! my problem was on
'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Thanks! my problem was on
'propagate': False
– Manel Clos
Jan 8 '18 at 16:24
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
Great! Worked for me on Django 2.0
– philoj
Feb 7 at 7:00
add a comment |
Make sure your EMAIL_HOST and EMAIL_PORT are set up right in settings.py (these refer to your SMTP server). It might be assuming that you have an SMTP server running on localhost.
To test this locally, run Python's built-in test SMTP server:
python -m smtpd -n -c DebuggingServer localhost:1025
Then set these values in your settings.py
EMAIL_HOST='localhost'
EMAIL_PORT=1025
Trigger a 500 error, and you should see the e-mail appear in the python smtpd terminal window.
2
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
add a comment |
Make sure your EMAIL_HOST and EMAIL_PORT are set up right in settings.py (these refer to your SMTP server). It might be assuming that you have an SMTP server running on localhost.
To test this locally, run Python's built-in test SMTP server:
python -m smtpd -n -c DebuggingServer localhost:1025
Then set these values in your settings.py
EMAIL_HOST='localhost'
EMAIL_PORT=1025
Trigger a 500 error, and you should see the e-mail appear in the python smtpd terminal window.
2
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
add a comment |
Make sure your EMAIL_HOST and EMAIL_PORT are set up right in settings.py (these refer to your SMTP server). It might be assuming that you have an SMTP server running on localhost.
To test this locally, run Python's built-in test SMTP server:
python -m smtpd -n -c DebuggingServer localhost:1025
Then set these values in your settings.py
EMAIL_HOST='localhost'
EMAIL_PORT=1025
Trigger a 500 error, and you should see the e-mail appear in the python smtpd terminal window.
Make sure your EMAIL_HOST and EMAIL_PORT are set up right in settings.py (these refer to your SMTP server). It might be assuming that you have an SMTP server running on localhost.
To test this locally, run Python's built-in test SMTP server:
python -m smtpd -n -c DebuggingServer localhost:1025
Then set these values in your settings.py
EMAIL_HOST='localhost'
EMAIL_PORT=1025
Trigger a 500 error, and you should see the e-mail appear in the python smtpd terminal window.
answered Sep 12 '09 at 3:06
CathalCathal
26614
26614
2
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
add a comment |
2
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
2
2
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
I see the message, but if I set it back to my email settings it doesn't work
– JoseVega
Sep 12 '09 at 5:43
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
also added this, works well, but still nothing changes when set back to normal settings
– Harry
Sep 10 '15 at 13:11
add a comment |
My web hosting provider - Webfaction - only allows emails to be sent From an email that has been explicitly created in the administrator panel. Creating one fixed the problem.
1
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
1
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
add a comment |
My web hosting provider - Webfaction - only allows emails to be sent From an email that has been explicitly created in the administrator panel. Creating one fixed the problem.
1
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
1
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
add a comment |
My web hosting provider - Webfaction - only allows emails to be sent From an email that has been explicitly created in the administrator panel. Creating one fixed the problem.
My web hosting provider - Webfaction - only allows emails to be sent From an email that has been explicitly created in the administrator panel. Creating one fixed the problem.
answered Sep 12 '09 at 5:52
JoseVega
1
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
1
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
add a comment |
1
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
1
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
1
1
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
I use webfaction and send e-mails from googlemail, so I don't think that was really the problem.
– Dominic Rodger
Sep 12 '09 at 6:47
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
That is, Django error e-mails get sent from googlemail.
– Dominic Rodger
Sep 12 '09 at 6:48
1
1
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
it obviously allows you to send emails if you're using google's smtp server, but if you use smtp.webfaction.com as the host then it won't let you unless the email exists. I didn't change anything else and it fixed it so I'm pretty sure that was it.
– JoseVega
Sep 12 '09 at 7:49
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
This fixed the problem for me, too. I am using the telus smpt server and just switched it to authenticated as opposed to not. It worked before the change and to make it work now I had to use an e-mail address that exists to send from.
– jenniwren
May 1 '17 at 23:43
add a comment |
Another thing worth noting here is that settings handler500
might bypass the mechanism that sends errors on a 500 if the response from the view doesn't have a status code of 500.
If you have a handler500
set, then in that view respond with something like this.
t = loader.get_template('500.html')
response = HttpResponseServerError(
t.render(RequestContext(request, {'custom_context_var':
'IT BROKE OMG FIRE EVERYONE'})))
response.status_code = 500
return response
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
add a comment |
Another thing worth noting here is that settings handler500
might bypass the mechanism that sends errors on a 500 if the response from the view doesn't have a status code of 500.
If you have a handler500
set, then in that view respond with something like this.
t = loader.get_template('500.html')
response = HttpResponseServerError(
t.render(RequestContext(request, {'custom_context_var':
'IT BROKE OMG FIRE EVERYONE'})))
response.status_code = 500
return response
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
add a comment |
Another thing worth noting here is that settings handler500
might bypass the mechanism that sends errors on a 500 if the response from the view doesn't have a status code of 500.
If you have a handler500
set, then in that view respond with something like this.
t = loader.get_template('500.html')
response = HttpResponseServerError(
t.render(RequestContext(request, {'custom_context_var':
'IT BROKE OMG FIRE EVERYONE'})))
response.status_code = 500
return response
Another thing worth noting here is that settings handler500
might bypass the mechanism that sends errors on a 500 if the response from the view doesn't have a status code of 500.
If you have a handler500
set, then in that view respond with something like this.
t = loader.get_template('500.html')
response = HttpResponseServerError(
t.render(RequestContext(request, {'custom_context_var':
'IT BROKE OMG FIRE EVERYONE'})))
response.status_code = 500
return response
answered Jan 22 '15 at 23:48
oliversealoliverseal
575614
575614
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
add a comment |
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
I'd added a custom 500 error page and this solved my problem. Thanks.
– alstr
Dec 7 '18 at 8:53
add a comment |
Try this
# ./manage shell
>>> from django.core.mail import send_mail
>>> send_mail('Subject here', 'Here is the message.', 'from@example.com',['to@example.com'], fail_silently=False)
With a to@example.com that you actually get email at.
3
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
add a comment |
Try this
# ./manage shell
>>> from django.core.mail import send_mail
>>> send_mail('Subject here', 'Here is the message.', 'from@example.com',['to@example.com'], fail_silently=False)
With a to@example.com that you actually get email at.
3
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
add a comment |
Try this
# ./manage shell
>>> from django.core.mail import send_mail
>>> send_mail('Subject here', 'Here is the message.', 'from@example.com',['to@example.com'], fail_silently=False)
With a to@example.com that you actually get email at.
Try this
# ./manage shell
>>> from django.core.mail import send_mail
>>> send_mail('Subject here', 'Here is the message.', 'from@example.com',['to@example.com'], fail_silently=False)
With a to@example.com that you actually get email at.
answered Sep 12 '09 at 5:09
Paul TarjanPaul Tarjan
24.1k49149203
24.1k49149203
3
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
add a comment |
3
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
3
3
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
As I said, I already tried that and it works fine.
– JoseVega
Sep 12 '09 at 5:41
add a comment |
Make sure you have DEBUG = False
add a comment |
Make sure you have DEBUG = False
add a comment |
Make sure you have DEBUG = False
Make sure you have DEBUG = False
answered Nov 25 '09 at 2:04
Tim BabychTim Babych
2,76811510
2,76811510
add a comment |
add a comment |
Sorry if it is too naive, but in my case the emails were sent but were going directly to the SPAM folder. Before trying more complicated things check your SPAM folder first.
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
add a comment |
Sorry if it is too naive, but in my case the emails were sent but were going directly to the SPAM folder. Before trying more complicated things check your SPAM folder first.
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
add a comment |
Sorry if it is too naive, but in my case the emails were sent but were going directly to the SPAM folder. Before trying more complicated things check your SPAM folder first.
Sorry if it is too naive, but in my case the emails were sent but were going directly to the SPAM folder. Before trying more complicated things check your SPAM folder first.
answered Dec 2 '13 at 9:08
MiquelMiquel
570716
570716
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
add a comment |
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
Actually.. yea. I had errors from crawlers trying to make an AJAX request without form data. I overestimated the intelligence of spam filters and ended up with all email sent by Django being caught by the spam filter.
– Mike S
May 28 '14 at 17:36
add a comment |
Although it's been a while, here's my response, so that other people can benefit in the future.
In my case, what was preventing emails to be sent to the ADMINS list, when an error occured, was an application specific setting. I was using django-piston, which provides the setting attributes PISTON_EMAIL_ERRORS and PISTON_DISPLAY_ERRORS. Setting these accordingly, enabled the application server to notify my by mail, whenever piston would crash.
add a comment |
Although it's been a while, here's my response, so that other people can benefit in the future.
In my case, what was preventing emails to be sent to the ADMINS list, when an error occured, was an application specific setting. I was using django-piston, which provides the setting attributes PISTON_EMAIL_ERRORS and PISTON_DISPLAY_ERRORS. Setting these accordingly, enabled the application server to notify my by mail, whenever piston would crash.
add a comment |
Although it's been a while, here's my response, so that other people can benefit in the future.
In my case, what was preventing emails to be sent to the ADMINS list, when an error occured, was an application specific setting. I was using django-piston, which provides the setting attributes PISTON_EMAIL_ERRORS and PISTON_DISPLAY_ERRORS. Setting these accordingly, enabled the application server to notify my by mail, whenever piston would crash.
Although it's been a while, here's my response, so that other people can benefit in the future.
In my case, what was preventing emails to be sent to the ADMINS list, when an error occured, was an application specific setting. I was using django-piston, which provides the setting attributes PISTON_EMAIL_ERRORS and PISTON_DISPLAY_ERRORS. Setting these accordingly, enabled the application server to notify my by mail, whenever piston would crash.
answered Dec 9 '11 at 13:29
Charalambos PaschalidesCharalambos Paschalides
3051513
3051513
add a comment |
add a comment |
If, for some reason, you set DEBUG_PROPAGATE_EXCEPTIONS to True (it's False by default), email to admin will not work.
add a comment |
If, for some reason, you set DEBUG_PROPAGATE_EXCEPTIONS to True (it's False by default), email to admin will not work.
add a comment |
If, for some reason, you set DEBUG_PROPAGATE_EXCEPTIONS to True (it's False by default), email to admin will not work.
If, for some reason, you set DEBUG_PROPAGATE_EXCEPTIONS to True (it's False by default), email to admin will not work.
answered Apr 23 '13 at 9:45
Dominique PerettiDominique Peretti
10112
10112
add a comment |
add a comment |
... and then there's the facepalm error, when you've used this in development to prevent emails from going out, and then accidentally copy the setting to production:
# Print emails to console
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
(of course you don't see them being printed to console when using a wsgi server). Removing the setting from production fixed this for me.
add a comment |
... and then there's the facepalm error, when you've used this in development to prevent emails from going out, and then accidentally copy the setting to production:
# Print emails to console
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
(of course you don't see them being printed to console when using a wsgi server). Removing the setting from production fixed this for me.
add a comment |
... and then there's the facepalm error, when you've used this in development to prevent emails from going out, and then accidentally copy the setting to production:
# Print emails to console
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
(of course you don't see them being printed to console when using a wsgi server). Removing the setting from production fixed this for me.
... and then there's the facepalm error, when you've used this in development to prevent emails from going out, and then accidentally copy the setting to production:
# Print emails to console
EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'
(of course you don't see them being printed to console when using a wsgi server). Removing the setting from production fixed this for me.
answered Apr 22 '15 at 18:23
shackershacker
8,34455560
8,34455560
add a comment |
add a comment |
Just had the same issue after upgraded to Django 2.1 from Django 1.11. Apparently the ADMINS
sections in settings.py
has a change. It takes a list of tuples now, rather than the old tuple of tuples. This fixed for me.
##### old #####
ADMINS = (
("Your Name", "your_email@company.com")
)
##### new #####
ADMINS = [
("Your Name", "your_email@company.com")
]
Re: https://docs.djangoproject.com/en/2.1/ref/settings/#admins
add a comment |
Just had the same issue after upgraded to Django 2.1 from Django 1.11. Apparently the ADMINS
sections in settings.py
has a change. It takes a list of tuples now, rather than the old tuple of tuples. This fixed for me.
##### old #####
ADMINS = (
("Your Name", "your_email@company.com")
)
##### new #####
ADMINS = [
("Your Name", "your_email@company.com")
]
Re: https://docs.djangoproject.com/en/2.1/ref/settings/#admins
add a comment |
Just had the same issue after upgraded to Django 2.1 from Django 1.11. Apparently the ADMINS
sections in settings.py
has a change. It takes a list of tuples now, rather than the old tuple of tuples. This fixed for me.
##### old #####
ADMINS = (
("Your Name", "your_email@company.com")
)
##### new #####
ADMINS = [
("Your Name", "your_email@company.com")
]
Re: https://docs.djangoproject.com/en/2.1/ref/settings/#admins
Just had the same issue after upgraded to Django 2.1 from Django 1.11. Apparently the ADMINS
sections in settings.py
has a change. It takes a list of tuples now, rather than the old tuple of tuples. This fixed for me.
##### old #####
ADMINS = (
("Your Name", "your_email@company.com")
)
##### new #####
ADMINS = [
("Your Name", "your_email@company.com")
]
Re: https://docs.djangoproject.com/en/2.1/ref/settings/#admins
answered Nov 20 '18 at 22:31
Click2DeathClick2Death
15819
15819
add a comment |
add a comment |
While likely not ideal, I have found using Gmail as the SMTP host works just fine. There is a useful guide at nathanostgard.com.
Feel free to post your relevant settings.py sections (including EMAIL_*, SERVER_EMAIL, ADMINS (just take out your real email), MANAGERS, and DEBUG) if you want an extra set of eyes to check for typos!
add a comment |
While likely not ideal, I have found using Gmail as the SMTP host works just fine. There is a useful guide at nathanostgard.com.
Feel free to post your relevant settings.py sections (including EMAIL_*, SERVER_EMAIL, ADMINS (just take out your real email), MANAGERS, and DEBUG) if you want an extra set of eyes to check for typos!
add a comment |
While likely not ideal, I have found using Gmail as the SMTP host works just fine. There is a useful guide at nathanostgard.com.
Feel free to post your relevant settings.py sections (including EMAIL_*, SERVER_EMAIL, ADMINS (just take out your real email), MANAGERS, and DEBUG) if you want an extra set of eyes to check for typos!
While likely not ideal, I have found using Gmail as the SMTP host works just fine. There is a useful guide at nathanostgard.com.
Feel free to post your relevant settings.py sections (including EMAIL_*, SERVER_EMAIL, ADMINS (just take out your real email), MANAGERS, and DEBUG) if you want an extra set of eyes to check for typos!
answered Sep 12 '09 at 6:25
John PaulettJohn Paulett
13.4k33936
13.4k33936
add a comment |
add a comment |
For what it's worth I had this issue and none of these suggestions worked for me. It turns out that my problem was that SERVER_EMAIL
was set to an address that the server (Webfaction) didn't recognise. If this site were hosted on Webfaction (as my other sites are), this wouldn't be a problem, but as this was on a different server, the Webfaction servers not only check the authentication of the email being sent, but also the From:
value as well.
add a comment |
For what it's worth I had this issue and none of these suggestions worked for me. It turns out that my problem was that SERVER_EMAIL
was set to an address that the server (Webfaction) didn't recognise. If this site were hosted on Webfaction (as my other sites are), this wouldn't be a problem, but as this was on a different server, the Webfaction servers not only check the authentication of the email being sent, but also the From:
value as well.
add a comment |
For what it's worth I had this issue and none of these suggestions worked for me. It turns out that my problem was that SERVER_EMAIL
was set to an address that the server (Webfaction) didn't recognise. If this site were hosted on Webfaction (as my other sites are), this wouldn't be a problem, but as this was on a different server, the Webfaction servers not only check the authentication of the email being sent, but also the From:
value as well.
For what it's worth I had this issue and none of these suggestions worked for me. It turns out that my problem was that SERVER_EMAIL
was set to an address that the server (Webfaction) didn't recognise. If this site were hosted on Webfaction (as my other sites are), this wouldn't be a problem, but as this was on a different server, the Webfaction servers not only check the authentication of the email being sent, but also the From:
value as well.
answered Aug 16 '14 at 21:44
Daniel QuinnDaniel Quinn
2,02732539
2,02732539
add a comment |
add a comment |
In my case, it's the include_html
in mail_admins
.
When I set include_html
to True
,the email server reject to send my email because it think that my emails are spam.
Everything works just fine when I set include_html
to False
.
add a comment |
In my case, it's the include_html
in mail_admins
.
When I set include_html
to True
,the email server reject to send my email because it think that my emails are spam.
Everything works just fine when I set include_html
to False
.
add a comment |
In my case, it's the include_html
in mail_admins
.
When I set include_html
to True
,the email server reject to send my email because it think that my emails are spam.
Everything works just fine when I set include_html
to False
.
In my case, it's the include_html
in mail_admins
.
When I set include_html
to True
,the email server reject to send my email because it think that my emails are spam.
Everything works just fine when I set include_html
to False
.
answered Apr 8 '15 at 2:22
shellbyeshellbye
2,49522036
2,49522036
add a comment |
add a comment |
And yet another thing that can go wrong (I'll just add it to the list, for those people that end up here despite all the great answers above):
Our django setup used SendGrid as the smtp host and had a single admin email-address defined in the django settings. This worked fine for some time, but at some point, mails stopped arriving.
As it turns out, the mail address ended up in the SendGrid 'Bounced' list for some unknown reason, causing emails to that address to be silently dropped forever after. Removing the address from that list, and whitelisting it, fixed the issue.
add a comment |
And yet another thing that can go wrong (I'll just add it to the list, for those people that end up here despite all the great answers above):
Our django setup used SendGrid as the smtp host and had a single admin email-address defined in the django settings. This worked fine for some time, but at some point, mails stopped arriving.
As it turns out, the mail address ended up in the SendGrid 'Bounced' list for some unknown reason, causing emails to that address to be silently dropped forever after. Removing the address from that list, and whitelisting it, fixed the issue.
add a comment |
And yet another thing that can go wrong (I'll just add it to the list, for those people that end up here despite all the great answers above):
Our django setup used SendGrid as the smtp host and had a single admin email-address defined in the django settings. This worked fine for some time, but at some point, mails stopped arriving.
As it turns out, the mail address ended up in the SendGrid 'Bounced' list for some unknown reason, causing emails to that address to be silently dropped forever after. Removing the address from that list, and whitelisting it, fixed the issue.
And yet another thing that can go wrong (I'll just add it to the list, for those people that end up here despite all the great answers above):
Our django setup used SendGrid as the smtp host and had a single admin email-address defined in the django settings. This worked fine for some time, but at some point, mails stopped arriving.
As it turns out, the mail address ended up in the SendGrid 'Bounced' list for some unknown reason, causing emails to that address to be silently dropped forever after. Removing the address from that list, and whitelisting it, fixed the issue.
answered Oct 2 '17 at 16:42
djvgdjvg
1,1511728
1,1511728
add a comment |
add a comment |
If you are using or would want to use SendGrid, use the settings below in production.
Install the package
pip install sendgrid-django
Add these settings in settings.py(production)
DEBUG = False
EMAIL_BACKEND = "sendgrid_backend.SendgridBackend"
SENDGRID_API_KEY = "That you generate in sendgrid account"
ADMINS = (
("Your Name", "your_email@company.com")
)
add a comment |
If you are using or would want to use SendGrid, use the settings below in production.
Install the package
pip install sendgrid-django
Add these settings in settings.py(production)
DEBUG = False
EMAIL_BACKEND = "sendgrid_backend.SendgridBackend"
SENDGRID_API_KEY = "That you generate in sendgrid account"
ADMINS = (
("Your Name", "your_email@company.com")
)
add a comment |
If you are using or would want to use SendGrid, use the settings below in production.
Install the package
pip install sendgrid-django
Add these settings in settings.py(production)
DEBUG = False
EMAIL_BACKEND = "sendgrid_backend.SendgridBackend"
SENDGRID_API_KEY = "That you generate in sendgrid account"
ADMINS = (
("Your Name", "your_email@company.com")
)
If you are using or would want to use SendGrid, use the settings below in production.
Install the package
pip install sendgrid-django
Add these settings in settings.py(production)
DEBUG = False
EMAIL_BACKEND = "sendgrid_backend.SendgridBackend"
SENDGRID_API_KEY = "That you generate in sendgrid account"
ADMINS = (
("Your Name", "your_email@company.com")
)
answered Aug 10 '18 at 5:20
SuperNovaSuperNova
5,83022921
5,83022921
add a comment |
add a comment |
The below info is given in https://docs.djangoproject.com/en/2.1/howto/error-reporting/#email-reports
EMAIL_HOST = "email host"
EMAIL_HOST_USER = "Email username"
EMAIL_HOST_PASSWORD = "Email Password"
DEBUG = False
ADMINS = (
("Your Name", "your_email@company.com")
)
In order to send email, Django requires a few settings telling it how
to connect to your mail server. At the very least, you’ll need to
specify EMAIL_HOST and possibly EMAIL_HOST_USER and
EMAIL_HOST_PASSWORD, though other settings may be also required
depending on your mail server’s configuration. Consult the Django
settings documentation for a full list of email-related settings.
add a comment |
The below info is given in https://docs.djangoproject.com/en/2.1/howto/error-reporting/#email-reports
EMAIL_HOST = "email host"
EMAIL_HOST_USER = "Email username"
EMAIL_HOST_PASSWORD = "Email Password"
DEBUG = False
ADMINS = (
("Your Name", "your_email@company.com")
)
In order to send email, Django requires a few settings telling it how
to connect to your mail server. At the very least, you’ll need to
specify EMAIL_HOST and possibly EMAIL_HOST_USER and
EMAIL_HOST_PASSWORD, though other settings may be also required
depending on your mail server’s configuration. Consult the Django
settings documentation for a full list of email-related settings.
add a comment |
The below info is given in https://docs.djangoproject.com/en/2.1/howto/error-reporting/#email-reports
EMAIL_HOST = "email host"
EMAIL_HOST_USER = "Email username"
EMAIL_HOST_PASSWORD = "Email Password"
DEBUG = False
ADMINS = (
("Your Name", "your_email@company.com")
)
In order to send email, Django requires a few settings telling it how
to connect to your mail server. At the very least, you’ll need to
specify EMAIL_HOST and possibly EMAIL_HOST_USER and
EMAIL_HOST_PASSWORD, though other settings may be also required
depending on your mail server’s configuration. Consult the Django
settings documentation for a full list of email-related settings.
The below info is given in https://docs.djangoproject.com/en/2.1/howto/error-reporting/#email-reports
EMAIL_HOST = "email host"
EMAIL_HOST_USER = "Email username"
EMAIL_HOST_PASSWORD = "Email Password"
DEBUG = False
ADMINS = (
("Your Name", "your_email@company.com")
)
In order to send email, Django requires a few settings telling it how
to connect to your mail server. At the very least, you’ll need to
specify EMAIL_HOST and possibly EMAIL_HOST_USER and
EMAIL_HOST_PASSWORD, though other settings may be also required
depending on your mail server’s configuration. Consult the Django
settings documentation for a full list of email-related settings.
answered Aug 10 '18 at 5:23
SuperNovaSuperNova
5,83022921
5,83022921
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f1414130%2fdjango-not-sending-emails-to-admins%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown