Engineering Glossary · Mailbox Ops
Autoresponders: The Interval Is the Only Thing Stopping a Loop
Two vacation notices pointed at each other will exchange several thousand messages overnight, and the only thing standing between you and that is one number.
The short answer
An autoresponder answers everything arriving at a mailbox with a canned message, without anybody at the keyboard — a subject, a body, a start date, an end date and a per-sender interval.
That interval is not a nicety, it is the loop breaker. A responder with no interval will answer every message from the same address every time, and if the address at the other end is also automated the pair will trade messages until a queue fills or a rate limit intervenes. Set it in hours or days, not minutes, and check that your responder honours the headers that mark bulk and machine-generated mail before you point it at anything public.
By the HostingFast team · Reviewed 12 August 2026
100+
Terms in the glossary
2 min
Average read time
Plain
English throughout
24/7
Humans if you get stuck
You configure it per mailbox with a subject and a message, and crucially with start and end dates plus a per-sender interval. That interval is the throttle stopping a mailing list or a chatty correspondent from collecting the same notice hourly.
Holidays are only half the use. A standing acknowledgement on a sales or support address — received, we answer within one working day — is quiet customer service that costs nothing to operate and nothing to maintain.
The loop, and the three things that prevent it
First, the per-sender interval: once a day per address is generous and still useful. Second, header awareness. A well-behaved responder skips anything carrying Auto-Submitted with a value other than no, Precedence set to bulk or list, or a List-Id header, because all three mark mail that nothing should reply to. Third, a null envelope sender: bounces arrive with an empty return path and must never be answered.
If your responder honours all three, pointing it at a public address is safe. If it honours none of them — and some minimal implementations do not — then the interval is your only defence, and it should be set accordingly.
Both dates are the feature, not the fine print
Set the start and the stop at the moment you create it. A responder with a start date raises itself while you are already on a plane; one with an end date retires itself without anyone remembering to go back in. The failure everybody has seen is the out-of-office still answering in March, and it is entirely a consequence of leaving the second field blank.
Book the leave and enter both dates inside the same five minutes. It is the cheapest reliability improvement available in a mail system, and it takes less time than writing the message does.
Using it as instrumentation rather than an apology
A standing acknowledgement on support@ or sales@ sets an expectation, and an expectation is measurable. If the notice promises a reply within one working day, the number of chasing emails arriving inside that day tells you whether people believe it. That figure moves when the promise changes, which makes the responder a lever rather than a formality.
Keep the message specific: when you will reply, who to contact if it cannot wait, and nothing else. Long automated replies get skimmed and then ignored, and an ignored acknowledgement provides none of the reassurance it was set up to provide.
Where this lands on HostingFast
Autoresponders are configured per mailbox from the panel, alongside forwarders and filters, and mailboxes on your own domain are included with the plan. NVMe storage and LiteSpeed caching power every tier, from the smallest plan up — speed is the baseline here, not an upsell.
Follow-on entries: Email Forwarder, Spam Filter, Webmail and SMTP.
Definitions written for people who deploy
Every entry here started life as a support ticket. Rather than explain the same term for the two hundredth time, we wrote it down properly — with the header names, the settings and the failure modes still in them.
NVMe storage and LiteSpeed caching power every tier, from the smallest plan up — speed is the baseline here, not an upsell.
- 100+ entries, each with the mechanism spelled out
- Commands you can paste, numbers you can compare against
- Neighbouring terms wired together at the foot of every page
- Written by the engineers who answer the tickets
Why HostingFast
Standard on every plan
Loop conditions named
Where two automated systems can talk to each other, the entry says exactly which setting prevents it.
Headers as evidence
Auto-Submitted, Precedence and List-Id are named, because that is what a responder should be checking.
Mechanism, not vocabulary
How the feature behaves under load and at the edges, not a description of the settings screen.
A number to aim at
Intervals in hours rather than 'a sensible value', so a configuration decision has an actual default.
Wired to its neighbours
Autoresponder runs into Email Forwarder, Spam Filter and SMTP — the terms that share its failure modes.
This term, landed
Autoresponder defined, its loop risk bounded and its dates set — enough to point one at a public address safely.
Quick Start
From order to online
- 1
Set the interval before the message
Once per sender per day is a safe default. This is the setting that decides whether the responder is safe on a public address.
- 2
Fill in both dates in the same sitting
A start date raises it without you; an end date retires it without you. Leaving the second blank is how one ends up answering in March.
- 3
Test it against a list address
Send from an address carrying List-Id or Precedence: bulk and confirm nothing comes back. If it replies, the interval is now your only protection.
Built In
Loaded onto every plan
- Mailboxes on your own domain, included with the plan
- Browser webmail plus IMAP, POP and SMTP for any mail client
- cPanel, so responders, forwarders and filters sit on one screen
- Real SSH, plus Git and Composer, on the developer-focused plans
- Upgrades applied in place — changing plan is not a migration
- 99.9% uptime as the target, monitored around the clock
- Human support on duty every hour of every day
- WordPress and 400+ other applications installed in one click
- Softaculous on board for one-click application installs
- Daily backups with self-service restores you run yourself from the panel
Frequently Asked
What people ask us most often
Will it reply to mailing lists and automated mail?
It should not, and a well-implemented responder does not. Mail carrying Auto-Submitted, Precedence: bulk or a List-Id header is marked as machine-generated precisely so nothing answers it, and bounces arrive with an empty envelope sender for the same reason. Where a responder ignores those markers, the per-sender interval becomes the only thing preventing a flood.
How do I stop two autoresponders answering each other?
The per-sender interval is the hard stop, so set it in hours or days rather than minutes. Beyond that, rely on header awareness and never point a responder at a mailbox that is itself automated. If you have already seen the symptom, the Received chain on any of the messages shows the two hostnames alternating, which identifies both ends immediately.
Does it turn itself off?
Only if you fill in the end date, which is why it belongs in the same five minutes as the message itself. With both dates set the notice raises and lowers itself while you are elsewhere. With the end date blank it runs until somebody notices, and somebody usually notices when a customer mentions it.
What happens to my registration time if I transfer a domain in?
It carries over. Unlock the name with your current registrar, take the auth code, and start the transfer from your client area — any remaining registration term comes with it rather than being lost, and DNS keeps resolving the whole way through. It is a routine operation, not a cutover.
Keep reading
Webmail
The mailbox in a browser — where you confirm what the responder actually sent, and to whom.
SMTP
The dispatch protocol underneath, and the limits that apply to anything sending in volume.
How to Set Up an Email Autoresponder
Setting one up with both dates filled in, and the interval that keeps it safe on a public address.
VPS Hosting
KVM virtual servers — root access, DDoS filtering and one flat monthly price.
Business Hosting
Shared hosting with the full developer toolbelt: SSH, Node.js, Python and PostgreSQL.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Mail that behaves while you are away.
Mailboxes included with every plan, responders and filters on one screen, and NVMe under all of it.
View VPS Hosting plans