Form submissions not arriving? Eight causes and one check for each

You added a contact form to a static site, pressed send, and no email came. Before you change anything else, go through these in order.

  1. The activation email was never clicked. Some form services hold every submission until you confirm your address once, using a link they email to you. Check: search your inbox and spam folder for a confirmation message from the service and click its link.
  1. Your mail provider filtered the message. Test messages often look like spam, and some services may run their own spam filter too. Check: look in the spam folder, then in any label or filter rules you have set up, and send a test with a normal-looking sentence rather than "test test".
  1. You reached the free limit. Some free plans stop at a fixed number of submissions a month, and over-limit submissions may be blocked, held or dropped depending on the service. Check: open the service's dashboard and compare this month's count with the limit on its pricing page, then read the service's own documentation for what happens to submissions over the limit.
  1. The form has a file upload field. Some free plans reject uploads, so the whole submission may fail. Check: remove the file field, send a test, and see whether the email arrives.
  1. The form is being sent from a server, not a browser. Some services refuse requests that arrive without the origin information a browser adds, and slow responses can time out. Check: send the same test from a plain HTML page in a browser, opened from a local web server or the live site, not straight from a file (a page opened from disk sends no Referer). If that works, the server-side call may be the cause, so compare the response status and headers of the two requests.
  1. The address behind your form key is dead. If the key is tied to a mailbox that no longer exists, nothing arrives. Worse, a page that shows "thank you" whenever any one step succeeds hides the failure. Check: confirm the address in the service's settings, then send a test and read the real response, not just the message on your page.
  1. The form still posts to the placeholder address. Until you claim an endpoint, the generator's HTML posts to a placeholder address ending in CLAIM_YOUR_ENDPOINT, which stores nothing, sends nothing and answers with a 404 status. An endpoint ID that matches no live form gets a 404 too. Check: look at the form tag in your live page's source. If the action still ends in CLAIM_YOUR_ENDPOINT, paste the HTML from your claim result in its place, deploy, and send a test.
  1. The hidden spam trap was filled in. The form has a hidden field named _gotcha. Any value in it marks the message as spam: Lamofel never emails it and lists it in your dashboard as held as spam, while the visitor still sees a thank-you, so nothing looks wrong. Check: in your dashboard, find the message by its time; if it is listed as held as spam, open the form source and confirm the _gotcha input is hidden, has no value attribute and keeps autocomplete="off", as generated.

If you would rather try a different service: Lamofel is a form-to-email service that is free, needs no credit card, and allows 100 messages a month. It is built and run with the help of AI systems. You enter your email, then confirm it with a link we send.

Generate a free form ยท See plans · Claim a free endpoint