Re: Blocking disposable or temporary email addresses

['Adam Johnson' via Django developers (Contributions to Django itself)]

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)  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 
> 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 
>>> 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
>> 
>> .
>>
> --
> 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
> 
> .
>

-- 
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.

Re: Blocking disposable or temporary email addresses

['Tobias McNulty' via Django developers (Contributions to Django itself)]

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 
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 
>> 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
> 
> .
>

-- 
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.

Re: Blocking disposable or temporary email addresses

[Yonas]

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  
> 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.

Re: Blocking disposable or temporary email addresses

[James Bennett]

On Wed, May 11, 2022 at 2:21 PM Yonas 
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/CAL13Cg8hgvUkoQyQJ9ryXY%2ByvuabAjonUY4VibXtzmWAYYtt7Q%40mail.gmail.com.

Re: Blocking disposable or temporary email addresses

[Dylan Reinhold]

You will never be able to define a "disposable or temporary" email address
or provider, so it's a non-starter from my perspective.

Dylan

On Wed, May 11, 2022 at 2:21 PM Yonas 
wrote:

> Hi,
>
> Hope everyone is doing well!
>
> What does the community think about adding a feature to Django where
> disposable or temporary emails are not accepted during account registration?
>
> Best,
> Yonas
>
> --
> 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/c6101816-f267-4568-88d8-5b8f17bfd92en%40googlegroups.com
> 
> .
>

-- 
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/CAHtg44Dh8N7h8qsrNXebTs1CFEWpOGNhQU1Mqj-dF-cEzG3Byw%40mail.gmail.com.