I don't have any magic answers for you yet.
My only suggestion would be to find out what's different in the environment
between running as uwsgi and running under runserver. Perhaps something in
the environment, or perhaps the username under which django runs in either
case.
/var/log/maillog i
ok, after this answer a said I sghoulf test django internal server
I simply started server with runserver
(didn't change email backend)
and the mail sending worked!
so now I think It's a uwsgi related problem
but I couldn't fine anything about that
(there was a page on stackoverflow saying run uw
My best guess is that the mail transport agent on the server is rejecting
the mail because something is different from mail that is send through
other places in your django code. Perhaps the mail "sender" is not correct,
for example?
Unfortunately, looking at the mail log is the best way to see
I don't have access to that file on server.
and log from uwsgi doesn't have any error massage about mail sending
can it be a python3 branch related bug?
در دوشنبه 17 دسامبر 2012، ساعت 1:36:05 (UTC+3:30)، Chris Cogdon نوشته:
>
> Oh... there's your problem... you've set the admin email to ...
Oh... there's your problem... you've set the admin email to ... i'm
sure that doesn't exist! :)
Seriously, though... all that looks correct. Can you check your server's
/var/log/maillog to see if the mail is being accepted?
On Sunday, December 16, 2012 1:33:01 PM UTC-8, Ali Vakilzade wrote:
5 matches
Mail list logo
