Not rated yet
Email after a submission — notifications and autoresponders (DNN)
A submission can send two different emails, and they are configured separately: one tells
your team that something arrived, the other tells the visitor you received it. Neither is on by
default, and each stays silent rather than failing loudly when it is not fully configured — which is
why "MegaForm is not sending email" is almost always one of the two switches below.
1. Telling your team
The form carries a list of recipients. Leave it empty and no team email is sent at all — this is
the single most common reason nothing arrives.
- Recipients — one or more addresses, separated by a comma or a semicolon.
- Template — optional. Leave it empty and MegaForm builds a default email containing a
table of every submitted field.
The subject, when you do not supply your own template, is:
[MegaForm] New submission: <form title> (#<submission id>)
Each address is sent to individually. If one address fails — a typo, a mailbox that is full —
the failure is written to the log and the remaining recipients still get their copy. You do not lose
the whole notification because of one bad address.
2. Telling the visitor (autoresponder)
The autoresponder needs two things set, not one:
- The autoresponder must be enabled.
- You must name which field holds the visitor address. MegaForm does not guess: it reads the
value of the field key you name, so a form with several email fields still sends to the right one.
If that field is empty on a particular submission — an optional email box the visitor skipped — no
autoresponder is sent for that submission, and the submission itself is unaffected.
Subject and body are both optional. With no subject of your own the visitor receives:
Thank you — <form title>
3. Tokens you can put in a template
Both templates accept the same tokens. Anything that is not a known token is left alone.
| Token | Becomes |
|---|
{{submission_id}} | The submission number |
{{form_title}} | The form title |
{{submitted_date}} | Submission time, yyyy-MM-dd HH:mm:ss, UTC |
{{ip_address}} | The submitter IP address |
{{all_fields}} | A table of every submitted field and its value |
{{your_field_key}} | The value of any single field, by its key |
Use the field key, not the label. A field labelled "Work email" with the key work_email is
{{work_email}}.
4. What happens when mail fails
Sending is deliberately unable to break a submission. Every send is wrapped: a failure is written to
the log under MegaForm.Notify or MegaForm.Autoresponder and the visitor still sees the success
screen, because a mail server outage must not cost you the data someone just typed.
The consequence worth knowing: a silent inbox is not proof of a broken form. Check the log
before you change anything — the submission is already stored either way, and you can confirm that
in the submissions list.
5. When nothing arrives
- Is the recipient list empty? Empty means "send nothing", not "send to the admin".
- For the autoresponder: is it enabled and is the email field named?
- Did the visitor actually fill that email field on this submission?
- Can DNN send mail at all? MegaForm hands the message to the host SMTP settings; if those are
wrong, every module on the site is equally silent.
- Check the log for
MegaForm.Notify / MegaForm.Autoresponder entries.