Upgraded mod_python to latest version and upgraded python 2.4.x ...
problem gone away.
Go figure.
Thanks all!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send
This gets even more weird.
I copied the send_mass_mail() code from django.core.mail into my
module so I could orchestrate it.
I changed the DNS_NAME lookup to a hardcoded string and then got the
15s delay on the smtplib.SMTP(settings.EMAIL_HOST,
settings.EMAIL_PORT) line?!
So, perhaps the
On Jun 26, 12:55 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2007-06-25 at 19:39 -0700, ZebZiggle wrote:
> > Howdy!
>
> > Emails were taking 15s to send each. Upon investigation it came down
> > to CachedDnsName in django.core.mail. Specifically, the
> > socket.getfqdn() call.
On Jun 25, 11:55 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> (for example, a setting for the fqdn so that we don't even do the lookup
> if the setting exists).
I like that idea. I should be able to just set DNS_NAME myself from
the calling module.
Let me investigate.
Thx guys,
Sandy
On Mon, 2007-06-25 at 19:39 -0700, ZebZiggle wrote:
> Howdy!
>
> Emails were taking 15s to send each. Upon investigation it came down
> to CachedDnsName in django.core.mail. Specifically, the
> socket.getfqdn() call. Also, it *always* happened, not just on
> startup. So it seems the call was
I'm not sure. Each Apache instance may have to populate this, so it
could be noticed several times.
Keep investigating!
Thinking more about it, perhaps CachedDnsName should only lazily
loaded if settings.DEBUG==True. It's not really fair to expect an end
user to have to wait for this timeout
Howdy!
Emails were taking 15s to send each. Upon investigation it came down
to CachedDnsName in django.core.mail. Specifically, the
socket.getfqdn() call. Also, it *always* happened, not just on
startup. So it seems the call was timing out and the cache wasn't
effective.
The strange part is, it
7 matches
Mail list logo
