A careers email alias is a public contract. Print careers@yourdomain once, map it to whoever owns hiring this quarter, and change only the destination when HR changes. Do not issue a new address every time a recruiter leaves. Do not give that person a mailbox seat for a string. MailerZ keeps the local-part stable. Header From on inbound stays the applicant. Exclusive MX so leftover hosts do not steal resumes.
Quick answer for careers email alias
Create careers@ as a named alias before you print it on a job post. Map it to a human inbox, not a shared password.
When HR changes, edit the destination. Do not reprint the website. Applicants should never notice the staff change.
RFC 5321 will deliver to MX. If leftover Google MX still exists, some resumes never reach the new owner.
HOLD unknown so guessed HR local-parts do not flood the recruiter. careers@ is enough.
If the recruiter must send as careers@, that is paid send-as. Copy dashboard SMTP. Free cannot. Solo allows 20 send-as per hour.
Soft CTA: start free, create careers@, probe, then print it.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: aliases and catch-all, use cases, and send and reply.
User problem and decision criteria
Decision criteria: is the address already printed, who owns hiring, do they need send-as, is MX exclusive, is HOLD on.
Criteria that do not belong: a new mailbox per recruiter, catch-all FORWARD, inboxing promises.
If two agencies both want the alias, pick one destination or a shared inbox you can actually staff.
If legal wants a store of applications, MailerZ’s fourteen or ninety days is not an ATS. Use an applicant tracker.
If the old recruiter’s personal Gmail was the destination, change it the day they leave. That is an offboarding control.
Agencies should put destination change in the SOW as a five-minute task, not a migration.
Do not use plus-addressing on Gmail as the public careers address. You cannot revoke it at your domain.
Do not put careers@ on a privacy-mask domain you do not own.
Technical mail flow
Inbound MX to MailerZ, local-part careers, hop to the current owner, SRS envelope, intact Header From.
Destination change is a map edit. No DNS change.
Outbound as careers@ is paid SMTP if needed.
History shows the hop if a candidate swears they mailed you.
ATS links can still be the apply button. Email is the overflow.
Step-by-step setup / decision path
- Create careers@ mapped to the current owner.
- HOLD unknown.
- Exclusive MX. Probe.
- Print the address.
- On HR change, edit destination only.
- Revoke old send-as.
- Re-probe.
- Update the owner sheet.
Write the class of the next failure before you change a second record.
HOLD unknown unless you have a written FORWARD reason.
Quote live pricing before you promise alias counts.
Failure modes and proof
Printed before alias existed: held or 550. Proof: history.
Leftover MX: missing resumes. Proof: public MX.
Old recruiter still destination: privacy incident. Proof: the map.
Catch-all FORWARD: junk in the hiring inbox.
Free send-as: refuse.
Shared password mailbox: offboarding fails.
Self-send test: lie.
ATS promised in MailerZ: no.
Dual MX: split applications.
Inboxing SLA on applications: fiction.
Header rewrite: MailerZ will not.
Disabled alias instead of remapping: public dead letter.
MailerZ workflow and product boundary
MailerZ is custom-domain aliasing and forwarding with optional paid send-as. Secuno LLC operates mailerz.net. The app is mail.mailerz.net. Not Workspace, not IMAP, not an open relay, not a campaign ESP.
Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. Exclusive MX. Hold unknown on Free. Copy SMTP host, port, and TLS or STARTTLS from the dashboard when you send.
Free: one domain, ten aliases, one seat, fourteen-day store, send-as disabled, SMTP and API disabled. Solo forty dollars a year, twenty-five aliases, ninety-day store, 2,500 outgoing, 20 send-as per hour. Starter eight or eighty. Business nineteen or one hundred ninety. Agency thirty-nine or three hundred ninety. Quote pricing. No SOC 2, ISO, HIPAA, SLA, or inboxing percentage.
Cost, alternatives, and trade-offs
A stable alias is cheaper than reprinting ads.
A mailbox seat per recruiter is the expensive habit.
ATS is the right spend for pipeline. MailerZ is the overflow pipe.
Agencies should bill destination changes as operations, not migrations.
Leftover MX during hiring season costs candidates, not just dollars.
Free is enough for one careers plus two other roles. Solo if you need send-as.
Do not buy Workspace for one alias.
No inboxing percentage as a hiring KPI.
Operational depth
Put careers@ in the same change ticket as the job-board URL. They launch together.
When HR changes, the checklist is: destination edit, probe from a third mailbox, confirm the old human no longer receives, revoke send-as if they had it.
If an agency recruiter needs a copy, add a second destination only if the product supports it; otherwise use a shared inbox you control. Do not invent a feature.
Review held mail for close typos like carrier@ or career@. Create a named alias only if you will staff it.
Do not forward all unknown mail to the recruiter. Recruiters already live in noise.
Keep the public string forever. Companies that change jobs@ to hiring@ every reorg train the internet to guess.
If you send rejection mail as careers@, stay on operational volume. A blast is an ESP job.
Document the owner in a sheet. The next reorg should not require archaeology.
Exclusive MX before a campus hiring fair. Leftovers during a fair are a visible incident.
If candidates mail from portals that cannot follow forwards, offer the ATS link as primary and keep the alias as backup.
Store windows matter if you missed a resume. Act inside fourteen or ninety days.
Quote plan alias limits before you create a dozen department variants.
Field notes when HR changes
The public string is the contract
careers@ on a jobs page, a LinkedIn post, and a campus flyer is a contract with applicants. Changing the printed string every time a recruiter leaves trains the internet to guess. Keep careers@. Change the destination map. Applicants should never learn the staff name from the address.
Plus-addressing on Gmail is not a public careers address. You cannot revoke you+jobs@gmail.com at your domain. A privacy-mask domain you do not own is also the wrong print. Own the zone. Name the local-part. Map a human.
Offboarding is a map edit, not a mailbox wipe
The day a recruiter leaves, the destination must not be their personal Gmail. That is a privacy incident waiting for a resume with a social security number. Edit the map first. Probe from a third mailbox. Confirm the old human no longer receives. Revoke paid send-as if they had a dashboard pair for careers@. Then collect the laptop.
Do not disable the alias instead of remapping. A disabled public careers@ is a dead letter on every live job post. Remap. Re-probe. Update the owner sheet. Agencies should write destination change as a five-minute operations task in the SOW, not a migration.
HOLD unknowns or the recruiter drowns
Free holds unknown recipients. Paid plans may forward unknowns. Everyday production should hold. Catch-all forward into the hiring inbox is how career@ typos, spam, and harvested guesses become the recruiter’s full-time job. Review the hold store. Promote a leftover only when a real applicant used it — career@ or jobs@ if you will staff it as a named alias.
Two agencies both wanting the alias is a staffing problem. Pick one destination or a shared inbox you control. Do not invent a fan-out feature. Do not share a mailbox password. MailerZ is not IMAP.
Send-as as careers@ is optional and paid
Most teams only receive applications. If someone must reject or schedule as careers@, that is paid send-as, one secret, From equal to the named alias. Free 550 is honest. Solo allows 20 send-as per hour. Confirm pricing. A blast of rejections is an ESP job, not this hop. Operational volume only.
Copy dashboard host, port, and TLS together. Do not paste a Gmail password into an ATS plugin and call it native send-as.
Exclusive MX during hiring season
Leftover Google or registrar MX means some resumes never appear in history. Public lookup. Delete leftovers. Dual MX is leftover, not a courtesy backup during a campus fair. Save the old exclusive set as text if you ever need rollback. Rollback is republish that set, not both MX live.
Self-send from the recruiter Gmail to careers@ is not a probe. Use an unrelated provider and a unique subject. Confirm Header From is the applicant, not a rewritten hop. MailerZ does not rewrite Header From. Envelope SRS only.
ATS versus the overflow pipe
An applicant tracker is the pipeline. MailerZ fourteen-day Free store and ninety-day paid store are hops this layer saw. They are not an ATS, not Vault, not legal hold, not HIPAA, not SOC 2. If counsel wants a store of applications, buy the tracker or a hold product. Act inside the hop window if you missed a resume and history still has the row.
Portals that cannot follow forwards should use the ATS apply button as primary. Keep careers@ as overflow. Print both only if you will staff both.
Plan math for extra department names
Free is ten aliases. careers@ plus hello@ plus billing@ fills Free. A dozen department variants need Starter at fifty aliases or higher. Confirm the live pricing page. Limits are not an inbox-placement promise. Quote alias counts before you print intern@, faculty@, and campus@ on the same week.
Seats operate the dashboard. They are not mailbox seats. Do not buy Workspace for one printed string.
Worked story: a shop printed careers@ before the alias existed. Leftover Google MX 250’d. History was empty. They created the alias, cut leftovers, probed with a unique subject, then updated the jobs page. The first week of applications never had a hop. The second week did.
Second story: HR changed firms and left the old recruiter Gmail as destination for six weeks. Applications with attachments sat in a personal account. They remapped the same day they noticed, probed, revoked send-as, and wrote destination change into the offboarding checklist. The public string never changed.
Operator brief: create careers@ before you print it. HOLD unknowns. Exclusive MX. Probe from another mailbox. When HR changes, edit the destination only, re-probe, revoke old SMTP. MailerZ is inbound MX plus optional paid SMTP. Not IMAP. Not an ATS. Start free, prove inbound, upgrade when From must travel as careers@.
Related: aliases and catch-all, use cases, send and reply, how to reassign a role address when an employee leaves, and pricing. Keep the owner sheet next to the MX screenshot. The next reorg should not require archaeology.
Operator packet when hiring email must survive reorgs
Print after probe, never before
Job boards, campus flyers, and footer links outlive recruiters. The only safe print is a named careers@ that already has exclusive MX and a unique-subject probe in history. Printing first is how you create a week of applications with no hop. Leftover Google MX 250s into a store nobody opens. MailerZ history stays empty. Cut leftovers first, then create the alias, then probe, then print.
If you already printed, treat it as an incident: create the alias, exclusive MX, probe, search HOLD for close typos, and write the missed week as unrecoverable if hop one never ran. The fourteen-day or ninety-day store cannot invent a leftover miss.
Owner sheet columns that prevent archaeology
Local-part, current dest mailbox, backup dest if the product maps two, send-as yes or no, date of last probe, unique subject of last probe, date the human last changed, and who can edit the map. The next reorg should take five minutes. If the sheet is a Slack thread, you will remap the wrong dest.
Agencies put this sheet in the client folder next to the old MX screenshot. Destination change is operations. It is not a migration and not a new printed string.
What to revoke on exit day
Destination map. Dashboard send-as pair if they had one. Gmail Send mail as on their laptop if they copied SMTP. Shared inbox membership if the dest was a group. The alias itself stays. The public jobs URL stays. The ATS stay. Only the human path changes.
If they used a personal Gmail as dest, that is the incident. Remap immediately. Ask them to delete copies they should not keep. MailerZ cannot wipe their Gmail. We can stop new hops.
Campus fairs and burst weeks
Exclusive MX before the fair, not during. Dual MX during a fair is a visible split. HOLD review daily during the fair if you expect typos. Do not enable catch-all forward for the week. You will spend the next month in junk.
If two agencies staff the fair, one dest you control. Copies can be a human process in the ATS. Do not invent fan-out. Do not share SMTP. Free has ten aliases — do not mint intern@, campus@, and faculty@ on Free without a plan card.
Evidence when a candidate swears they mailed you
Unique subject if you asked them to resend. Public MX. History row or empty. Destination including spam. Header From intact. Empty history is leftover MX or a missing alias. Destination 250 plus missing Primary is a folder. Do not start at DKIM. Do not promise an inbox SLA on applications.
Related: how to reassign a role address when an employee leaves, how to set up legal@, aliases and catch-all, send and reply, pricing. Start free, prove careers@, upgrade when rejection mail must leave as the domain.
More operational notes
Who may edit the careers map
Limit dashboard seats that can change destinations. A contractor who can remap careers@ to their own Gmail is a data incident. Seats operate the dashboard. They are not mailbox seats. Revoke the contractor seat at the same time you remap dest after a project ends.
Job-board vendors and their own MX fantasies
Some boards offer to “host careers email.” That is another inbound owner. If they publish MX, they are leftover MX. Keep MailerZ exclusive. Give the board the address as a string, not DNS control. If they require a mailbox they can IMAP, that is a store request. Keep one seat or decline.
Attachments and dest quotas
Resumes are large. Destination Gmail quotas are a dest problem. MailerZ hop history will show 250 or a dest 552. Do not cut MX because a dest mailbox is full. Empty the dest or change dest. HOLD is not a resume archive. Act inside fourteen or ninety days if you missed a hop you still hold.
Intern programs and seasonal names
intern@ for a summer is a named alias you will disable in September. Do not catch-all forward all summer. Disable the name when the program ends. Keep careers@. Reprinting intern@ every year is fine if you recreate and probe. Reusing a burned intern@ after a leak is not.
Legal copies
If counsel wants a copy of applications, that is an ATS or hold product, or a second dest you can name. MailerZ is not legal hold. Do not fan-out to five founders. See the legal@ article for hop evidence versus archive. Probe after every dest add.
MailerZ remains inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA. Free is one domain, ten aliases, one seat, a fourteen-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is forty dollars per year. Starter is eight monthly or eighty yearly. Business is nineteen or one hundred ninety. Agency is thirty-nine or three hundred ninety. Confirm numbers on the pricing page. Limits are not an inbox-placement promise. Start free at the MailerZ register URL when inbound must be proven first.
Worked closeout
A full week-of-change story
Monday: the recruiter resigns. Tuesday: remap careers@ to the founder Gmail, revoke the old send-as pair, probe from a personal Outlook with subject careers-remap-tuesday. History 250. Founder searches all mail. Old recruiter mailbox stays quiet for new hops. Wednesday: campus flyer still says careers@ — good, the string did not change. Thursday: HOLD shows career@ without the s. Create career@ as a named alias only if you will staff it; otherwise leave it held. Friday: print nothing new. Update the owner sheet. That is a week of operations, not a migration.
If Monday had been “disable careers@ so the recruiter cannot read it,” every flyer would have become a dead letter. Disable is for leaked prefixes, not for staff changes. Remap is for staff changes. See disable a compromised alias for the kill-switch. This page is the stable public string.
What applicants experience
They send a resume to the printed address. SMTP follows public MX. If leftovers own inbound, they get a 250 from Google and you get silence. If MailerZ owns inbound and the alias exists, you get a hop and the dest store gets a copy. Header From is the applicant. Envelope SRS is the hop. They never need to know HR changed. If you reprint hiring@ every reorg, they mail the dead string and you blame Gmail.
Plan math again because hiring always adds names
Free fills at ten aliases. careers@ plus hello@ plus billing@ is the whole Free card. intern@, faculty@, campus@, and press@ need Starter or higher. Confirm pricing. Do not promise a dozen department variants on a sales call without a card. Seats that edit the map are not extra mailboxes. HOLD review during a fair is staff time. Fourteen-day Free store is not an ATS. Ninety-day paid store is still not an ATS.
Close this hiring ticket
Named careers@ exists. Exclusive MX. Leftovers gone. Unique-subject probe after the last dest change. Old human revoked. Send-as rotated if it existed. Owner sheet updated. HOLD on. ATS still the pipeline. Start free, prove inbound, upgrade when rejection mail must leave as careers@. Sign in if the domain is already there.
Last operational reminders
Why this is not a new mailbox project
Recruiters ask for a mailbox because hosts sold mailboxes. Hiring needed a stable public string and a dest that can change. MailerZ is that map. Gmail or Outlook stays the store. IMAP on careers@ would make offboarding a password problem again. Keep the hop. Remap people. Exclusive MX so leftover hosts do not steal resumes during the week you thought you were done.
If two dests must see every application and the product maps two destinations, name both on the owner sheet. If it does not, use a shared inbox you control. Do not invent fan-out. Do not share SMTP. Free has no send-as. Solo allows 20 send-as per hour if rejection mail must leave as careers@. Confirm pricing. Probe after every dest change. Search dest including spam. Header From is the applicant. Envelope SRS only. Not an ATS. Not HIPAA. Not SOC 2. Start free, then print the address.
FAQ
- What is the safest way to handle careers email alias?
- Create careers@ as a named alias before you print it on a job post. Map it to a human inbox, not a shared password.
- Does this require a new mailbox?
- No. MailerZ is not IMAP. Keep Gmail or Outlook as the store unless you need a suite for other reasons.
- Will it work with Gmail or Outlook?
- Yes as destinations. Self-send is not the test. Open original on a third mailbox.
- What DNS records are involved?
- Exclusive MX, verification TXT, one SPF if you send-as. Leftover MX is a hard stop. Copy sending values from the dashboard.
- What should I test before production?
- A uniquely titled probe from an unrelated provider to each public alias. Confirm Header From and hop history.
Key takeaways
- Public string stays. Destination changes.
- Named alias, not a seat.
- HOLD unknown.
- Exclusive MX.
- Paid send-as only if they send.
- Offboard the old human from the map.
- ATS is not MailerZ.
- Probe after every owner change.
Conclusion
Stand up careers@ once. Remap people. That is how hiring email survives reorgs.
Start free, probe, then print the address on the jobs page.