On 11/1/06, Graham King <[EMAIL PROTECTED]> wrote: > 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: > [...] > Does this sound sane ? If so I will submit a proper patch.
Hi Graham, This does indeed sound sane, and a patch would be great. Usually we're hesitant to add stuff to django.core.mail, as it's intended as a quick convenience library rather than a full replacement for Python's own smtplib library, but if there's a chance spam filters are blocking Django-produced messages, that's a problem that is well worth fixing. Thanks for bringing this up! Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
