I would say this feature is a bit more questionable these days, since even big companies like Apple provide "disposable" email addresses for privacy protection.
And I also agree this would be better in a separate package, where updating the list of domains would be easier and not tied to Django's eight-monthly release cycle. On Thu, May 12, 2022 at 1:09 AM 'Tobias McNulty' via Django developers (Contributions to Django itself) <django-developers@googlegroups.com> wrote: > Hi Yonas, > > Thanks for sharing this list. Even so, in my opinion, this feature lives > best outside of Django where it can be appropriately customized as needed > for a given project. > > I hope this helps. > > Best, > Tobias > > > On Wed, May 11, 2022, 6:46 PM Yonas <ytilahu...@alumni.alueducation.com> > wrote: > >> >> Would syncing the block list from repos like >> https://github.com/disposable-email-domains/disposable-email-domains >> (actively maintained since 2014) ease the burden of updating the list? >> On Thursday, May 12, 2022 at 12:44:28 AM UTC+3 James Bennett wrote: >> >>> On Wed, May 11, 2022 at 2:21 PM Yonas <ytila...@alumni.alueducation.com> >>> wrote: >>> >>>> What does the community think about adding a feature to Django where >>>> disposable or temporary emails are not accepted during account >>>> registration? >>> >>> >>> I used to try to do this in my django-registration package, but >>> eventually gave up on it because maintaining an up-to-date list of all >>> possible domains and other patterns was not feasible. I expect the same >>> would be true with Django — it would require frequent updates to the list >>> of domains/patterns to block, and people would complain that the updates >>> weren’t fast enough, because Django only releases once a month (and that’s >>> assuming updates to the blocked email list would be considered for >>> inclusion in the monthly bugfix releases, rather than only at feature >>> release updates). >>> >>> So I expect this isn’t something Django could or should do. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/b669801b-f695-49c2-9d04-2ff7db74dc58n%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/b669801b-f695-49c2-9d04-2ff7db74dc58n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMGFDKRONKrsAw35VBN8%3DYiNWkEzQWd5kUcYH1G8CjqG2eo%3DbQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMGFDKRONKrsAw35VBN8%3DYiNWkEzQWd5kUcYH1G8CjqG2eo%3DbQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3w6RGHhtj3%3DU7irivW4dbfUmbmZjOT0VdYKSWM9s-Bpw%40mail.gmail.com.
