XF 2.1 Is there a way to automatically reject emails with more than two periods in the username?

[Sal Collaziano]

An email like name.name@domain.com makes sense. Even firstname.middlename.lastname@domain.com can be fine. But I get a crap ton of emails like a.b.c.d.e.f.g@gmail.com - and I'd love to just automatically reject them all. I run 30 forums so this would save time if possible...

 

[Max Taxable]

OzzModz had an addon for this in the old vbulletin days. Might be a good time to resurrect it.

 

[Lukas W.]

Go to ACP > Users > User discipline > Banned emails and add *.*.*.*@*

 

[Sal Collaziano]

Go to ACP > Users > User discipline > Banned emails and add *.*.*.*@*

Really? Could it be that easy?

 

[whynot]

Yes.

 

[Lukas W.]

Really? Could it be that easy?

Yeah. The * is a wildcard which include dots, so it matches anything with at least three dots at any position before the @.

 

[alternadiv]

Go to ACP > Users > User discipline > Banned emails and add *.*.*.*@*

If you put the extra stars on the other side, does do the same? Some of my spammers are spammer@spam.rj.wdn.u

Do the amount of stars you add need to be exact? So you would need to add a few of these blocks with different star amounts?

 

[Lukas W.]

The star is a wildcard that matches literally any text, from nothing (empty match) to a series of arbitrary characters (including dots). The important part is what you add around it. A pattern of *.* matches anything that includes at least one dot. *.*.* requires at least two dots to match, *@*.* requires at least one dot after the @ to match, etc.

 

[whynot]

If you put the extra stars on the other side, does do the same? Some of my spammers are spammer@spam.rj.wdn.u

*@*.*.*

would do the job provided there are more than one dots after the @ symbol.
Edit: the editor took off some parts, going to edit
Done

 

[djbaxter]

*@*.*.*

would do the job provided there are more than one dots after the @ symbol.
Edit: the editor took off some parts, going to edit
Done

Be careful with this. Sites in a subdomain could be blocked, e.g., subdomain.somesite.com or support.somesite.com