Dear django-developers,
At the moment django.core.mail does not set a Message-ID header in the
mails it sends. SpamAssassin spots this and says INVALID_MSGID and /or
MSGID_NO_HOST. I think the Message-ID is also used for message
threading, and matters when you have clustered mail servers.
I suggest changing django.core.mail.send_mass_mail to include this
section after it sets the 'Date' header:
msg['Message-ID'] = "<[EMAIL PROTECTED]>" % ( time.time(),
random.getrandbits(64), socket.getfqdn() )
(along with 'import socket, time, random' at the top).
This adds a message id according to the format recommended here:
http://www.jwz.org/doc/mid.html
http://rfc.sunsite.dk/rfc/rfc822.html
Does this sound sane ? If so I will submit a proper patch.
Thanks,
Graham.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
