20 | | === Confirmation of vulnerability === |
| 17 | Kind regards, the Django Security Team. |
| 18 | |
| 19 | === DMARC/SPF/Email Spoofing === |
| 20 | |
| 21 | Hello, |
| 22 | |
| 23 | Thank you for your report. The current DMARC and SPF settings are intentional, and we do not consider this a vulnerability. |
| 24 | |
| 25 | For more information on how the Django security team evaluates reports, please see: https://docs.djangoproject.com/en/dev/internals/security/. |
| 26 | |
| 27 | Kind regards, the Django Security Team. |
| 28 | |
| 29 | === Report about djangoproject.com === |
| 30 | |
| 31 | Hello, |
| 32 | |
| 33 | Thank you for your report. This mailing list is intended for reporting security issues related to the Django web framework, rather than its website. I will forward your concern to our Ops team, but you can consider this issue closed. |
| 34 | |
| 35 | For more information on how the Django security team evaluates reports, please see: https://docs.djangoproject.com/en/dev/internals/security/. |
| 36 | |
| 37 | Kind regards, the Django Security Team. |
| 38 | |
| 39 | === Asked for support instead === |
| 40 | |
| 41 | Hello, |
| 42 | |
| 43 | This mailing list is intended for reporting security issues in the Django web framework, not for support related to using or contributing to Django. |
| 44 | |
| 45 | For assistance, please refer to the Getting Help page (https://docs.djangoproject.com/en/dev/faq/help/), where you'll find resources and communities ready to support you. Following these guidelines will also help you structure your question in a way that makes it easier for others to assist. |
| 46 | |
| 47 | Thanks for your understanding! |
| 48 | |
| 49 | == Confirmation of vulnerability == |