Anti-spam
Every submission passes four checks before a ticket is created.
- CSRF token — enforced by ExpressionEngine itself before the request reaches Wrangler. A bot that posts without first loading the form is stopped here.
- Honeypot — a visually hidden input that must arrive empty.
- Signed render timestamp — the form must have been on screen at least 3 seconds and less than 24 hours. The timestamp is signed, so posting an older value does not work.
- Per-email rate limit —
rate_limit_per_hourtickets per email address per hour.
A rejected visitor goes back to the form with a generic message and their text intact. The message never says which check failed — telling a bot why it was rejected is telling it how to pass.
Why there is no IP limit
ExpressionEngine reports the connecting address, which behind a CDN or load balancer is the proxy's address for every visitor unless a proxy configuration is in place. A per-IP rule on such a site would lock out real customers after a handful of legitimate submissions — and on a support form, the person being turned away is someone with an urgent problem who cannot tell you about it.
Office and mobile networks share addresses too, and an attacker with a modern IPv6 allocation has effectively unlimited ones. So a per-IP limit fails the people you want and does not stop the people you don't.
What actually needs protecting is outbound email volume, and the notification ceiling does that directly without ever refusing a customer.
If you are getting spam anyway
In order of what to try:
- Raise the minimum form time — most junk arrives within a second.
- Lower Rate limit per hour.
- Turn off Allow guest tickets and require an account.
Turning off guest tickets is the strongest control available, and also the biggest ask of your customers. It is worth doing only if the first two have not worked.