Damn I really wanted this but I have no idea how to execute a SQL query tho, too bad it's only for expert users.
That one already exists, the rule doesn't match any possible subdomains though.Thanks for this.
May i suggest adding YOPmail.com to the list.
If you navigate:can this added manualy inside XF2?
list of disposable email?
That one already exists, the rule doesn't match any possible subdomains though.
View attachment 178735
If you navigate:
Admin Control Panel → Users → User discipline → Banned emails
You can add the full list either automatically or selectively add any specific domains manually. This functionality is a XenForo core feature.
This is not really required, all you currently need is a single google account to confirm multiple users:with the exception of having your own domain
(it's very easy to create functionality to mitigate this for the very popular Gmail addresses -facebook has been doing it for a while- either in the core or with an add-on)the-kenny@HN [1] said:In Gmail, you can add arbitrary dots (.) to your email address and add filters based on it: f.o.o@gmail.com You can also append a plus-sign with arbitrary text on it: foo+asdfsdfaiugo@gmail.com Both will route mails to foo@gmail.com.
As said, you can add a filter to add a label to all mails to this address and skip inbox for them. That's what I do.
From my experience, disposable email hosts allow the easy creation of email addresses for people who want to register on websites without having to input their main email address (which might include their real name or other identifiable text - e.g. nicknames used publicly in the past).What is not considered a disposable email?
That's probably because of a server timeout.I imported it but it only imported 983 items, any other way to import this?
The following free domains are blanket banned: .tk .ml .ga .cf .gq
The list was reduced from 7,350 hosts to 5,318 in the October update.
All the hosts, that are of 5 characters or less, have the @ symbol prepended before the wildcard. Lengthier domains are evaluated without the @ symbol.
*@test.test
to that field and Save. Then, try re-importing the xml.*@test2.test
..cf i don't think you should ban itCan you try to manually add a dummy email into that ban list? Enter for example:*@test.test
to that field and Save. Then, try re-importing the xml.
If the problem persists, try to import the version attached in this post and let me know if it creates a new record:*@test2.test
.
Are you able to upload other files to your server, such as post attachments?
Have any new server errors been logged?
Can you fire up the browser developer tools (press F12) and observe the output while you do the same actions like in your screencap above?
Ah adding a dummy email first then allowed me to import, not sure why that was. Thank you.Can you try to manually add a dummy email into that ban list? Enter for example:*@test.test
to that field and Save. Then, try re-importing the xml.
If the problem persists, try to import the version attached in this post and let me know if it creates a new record:*@test2.test
.
Are you able to upload other files to your server, such as post attachments?
Have any new server errors been logged?
Can you fire up the browser developer tools (press F12) and observe the output while you do the same actions like in your screencap above?
I hesitated adding the free TLDs at first, but the list had become huge because of them and harder to import (due to timeouts)..cf i don't think you should ban it
You can manually delete any records that match the oldxf_ban_email.reason
value and then re-apply the new update.
SQL:DELETE FROM `xf_ban_email` WHERE reason = 'https://xenforo.com/community/resources/ban-disposable-email-hosts.5939/'
Even though that is just a cosmetic change, it will result to a more homogeneous result.
I was able to reproduce that, that's a cache issue, try pruning the cache by either executing the following SQL command:
Or alternatively, by manually banning a new host, e.g.SQL:UPDATE xf_data_registry SET data_value = 'a:0:{}' WHERE data_key = 'bannedEmails'
*@000.test
, which you then can delete. That should update the cache.
Afterwards, re-import the updated list.
We use essential cookies to make this site work, and optional cookies to enhance your experience.