Zum Inhalt springen
Zurück zur Startseite

valueFactory.create() – IT-Beratung mit Mehrwert

valueFactory.create() – IT-Beratung mit Mehrwert

  • Startseite
  • Leistungen
  • Angebote
    • j-lawyer.org Kanzleisoftware
    • j-lawyer.BOX virtualisiert
    • Managed Nextcloud
  • Blog
  • Über
  • Fernwartung
  • Impressum
  • Datenschutz

Reducing spam registrations in Trac Issue Tracker

29. April 2015  in Tipps & Tricks  verschlagwortet Account Manager / Regular Expression / Trac von j-dimension.com

When using Trac with the Account Manager plugin as a public instance and with user registrations enabled, it won’t take long until you see a fair amount of spam registrations. While you can use email verification to avoid actual changes to your data (no edit privileges until mail address is verified), you will still have those inactive accounts in your system. Frequent cleanup takes time and is a cumbersome activity.

One potential measure is using the regular expression filter for mail addresses. Users with addresses not matching a specific regular expression will not be created, which means there is no need for later cleanup.

I just want to share an extendable regular expression for use in trac.ini. First, enable regular expression checking by adding „RegExpCheck“ to the following entry:

register_check = BasicCheck, EmailCheck, RegExpCheck, UsernamePermCheck, BotTrapCheck

Now, just disallow specific mail domains. I used to maintain these for the first two weeks or so and then spam registrations were significantly down / unsuccessful:

email_regexp = \S*@(?!((yahoo\.com)|(aol\.com)|(\S*\.org)|(\S*\.bg)|(\S*\.biz)|(\S*\.blog-stuff\.com)|(\S*\.br)|(\S*\.\S*\.com)|(\S*\.dk)|(\S*\.in)|(\S*\.info)|(\S*\.club)|(crossyroadhacks\.com)|(\S*\.eu)|(\S*\.hu)|(\S*\.net)|(\S*\.lv)|(\S*\.pl)|(\S*\.pw)|(\S*\.ru)|(\S*\.su)|(\S*\.top)|(\S*\.\S*\.de)|(\S*\.website)|(\S*mail\.com)|(outlook\.com)|(spamavert\.com)|(spambog\.com)|(mailcatch\.com)|(\S*\.us)|(\S*\.co\.uk)|(mailinator\.com)|(\S*\.xyz)|(yluxuryshomemn\.com)))\S*

Good luck!


Beitragsnavigation

  • Wildfly 9: EJBCLIENT000025: No EJB receiver available for handling →

Neueste Beiträge

  • Ubuntu LXC container not starting after upgrade
  • Self-upgrading Java Enterprise applications
  • Migrating from Jenkins to Travis CI
  • Merging multiple Git repositories into one
  • Automatic database index creation with the Java Persistence API

Archiv

  • Oktober 2023
  • November 2018
  • Juli 2018
  • Juni 2018
  • Mai 2018
  • April 2018
  • November 2015
  • April 2015

Suche

Schlagworte

backup Builds C2 cache constraint Constraint Programming Container CP database do-release-upgrade Docker Dovecot EclipseLink GitHub Hibernate Home Automation IMAP index Java Java Enterprise Jenkins JPA Linux LXC machine mail makespan Manufacturing merge MySQL objectives Odroid openHAB Optaplanner query Raspberry solver SQL synchronization Testing Travis CI Ubuntu Upgrade Wildfly ZWave

Navigation

  • Angebote
    • j-lawyer.BOX virtualisiert
      • Anfrage j-lawyer.BOX virtualisiert
    • j-lawyer.org Kanzleisoftware
      • Anfrage j-lawyer.org Clientinstallation
      • Anfrage j-lawyer.org Komplettinstallation
      • Anfrage j-lawyer.org Online-Datensicherung
      • Anfrage j-lawyer.org Serverinstallation
      • Anfrage j-lawyer.org Updateinstallation
    • Managed Nextcloud
      • Managed Nextcloud – eigene Installation
      • Managed Nextcloud – Nutzer
  • Fernwartung
  • Impressum
    • Datenschutz
    • Datenschutzerklärung j-lawyer.org App iOS / Android
  • Leistungen
  • Über

Letzte Beiträge

  • Ubuntu LXC container not starting after upgrade
  • Self-upgrading Java Enterprise applications
  • Migrating from Jenkins to Travis CI
  • Merging multiple Git repositories into one
  • Automatic database index creation with the Java Persistence API

Beitragskategorien

  • General (16)
    • Tipps & Tricks (8)
    • Troubleshooting (3)
    • Tutorial (10)

Archiv

· © 2026 Jens Kutschke IT Consulting · Präsentiert von · Entworfen mit dem Customizr-Theme ·

Diese Website benutzt Cookies. Wenn du die Website weiter nutzt, gehen wir von deinem Einverständnis aus.