Department email aliases let sales@, finance@, and ops@ exist without a mailbox per team name. Map each local-part to a person or a shared inbox you already staff. Change destinations when org charts move. Do not buy IMAP for every noun on the website. MailerZ is the map. Exclusive MX. HOLD unknown so guessed department names do not train junk.
Quick answer for department email aliases
List printed department addresses. Create named aliases only for those strings.
Map each to a staffed destination. Empty destinations are how mail goes missing after a 250.
RFC 5321 delivers to MX. One owner. Leftover host MX from old department seats splits mail.
HOLD unknown. Do not FORWARD every guessed dept@ into finance.
Send-as as the department is paid SMTP if needed. Free cannot. Caps exist.
Start free if you only need three departments. Quote pricing when the sheet is longer.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: aliases and catch-all, use cases, and pricing.
User problem and decision criteria
Decision criteria: which department strings are public, who owns each, send-as need, plan alias limits.
Do not create a mailbox per Slack channel.
Agencies should refuse catch-all as a department strategy.
If two departments share one human, one destination is fine. Two seats are not required.
Legal and finance may want separate owners. That is a map choice, not a host.
Org-chart vanity aliases that are not printed can stay uncreated.
Shared passwords for department@ are the sprawl you are leaving.
Suite seats remain for humans who need calendars, not for nouns.
Technical mail flow
MX, local-part, hop to owner, SRS, intact From.
Org change is a destination edit.
Optional SMTP as the department.
History for “we never got that PO.”
HOLD for made-up depts.
Step-by-step setup / decision path
- Inventory printed department strings.
- Create named aliases. HOLD on.
- Exclusive MX. Probe each.
- Enable send-as only where needed.
- Quarterly owner review.
- Add aliases when a new string is printed.
- Never catch-all as a shortcut.
- Quote upgrades before you over-promise.
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
Seat per department: cost sprawl.
Catch-all FORWARD: junk.
Leftover MX: missing POs.
Empty destination: 250 into a void.
Free send-as: refuse.
Unlimited aliases promised on Free: three.
Dual MX: split.
Self-send: lie.
Header rewrite: no.
ESP on department SMTP: caps.
Inboxing SLA: no.
Disabled all depts during reorg: public dead letters.
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
Aliases cost less than seats.
Sprawl is the unused IMAP you still pay.
Solo may replace a pile of department seats.
Junk from FORWARD costs time.
Leftover MX costs POs.
Quote plan limits.
Workspace for nouns is the expensive habit.
No fake inbox KPI.
Operational depth
Build the sheet from the website footer and invoice PDF, not from Slack channel names.
When a department splits, add a new named alias. Do not reuse finance@ for a new team without a redirect plan.
Review destinations quarterly. People leave. Maps rot.
If ops@ and support@ are the same human, say so in the sheet so you do not buy a second seat later.
HOLD review will show guessed names like accounts@ and accounting@. Create one official string and tell vendors.
Exclusive MX before the fiscal close. Leftovers then are expensive.
Send-as hourly caps matter on month-end if many departments send. Stagger or upgrade. Quote pricing.
Do not print ten department addresses on day one of a three-alias Free plan.
Agencies: department maps are a deliverable. Catch-all is not.
Keep ESP campaigns off department SMTP.
Probe after every remapping.
Document who can edit the map. Random edits are sprawl of a different kind.
Departments are aliases, seats are humans
Department addresses are printed local-parts: sales, support, billing, jobs, press, legal, security. Humans are destinations. Three people do not need three Workspace seats to print ten departments. They need ten named aliases and three Gmail or Outlook stores. MailerZ is that hop. Exclusive MX. Leftover aspmx is how half the departments vanish from history.
Size the plan against the printed list. Free is ten aliases. Four departments end Free. Solo is twenty-five and $40/year. Starter is fifty aliases, eight domains, five seats, 5,000 outgoing, 40 per hour. Business is 25/200/25, 12,000 outgoing, 60 per hour. Agency is 100/500/50, 20,000, 60 per hour. Do not enable paid FORWARD to fake the twelfth department on Solo.
Map each department to one store. “Everyone watches sales@” is how nobody watches sales@. Labels in Gmail are destination work. They do not create aliases. Shared destinations still need one probe per name.
Most departments should not send. Inbound is the job. Paid send-as is for the few From identities you approve. Free cannot send. Unauthorized From is 550. Hourly caps are shared. A support loop that sends as support@ all afternoon will 550 on Starter’s 40 per hour.
HOLD on Free makes missing departments visible. That is the sprawl control. FORWARD hides sprawl and feeds spam into the three stores. Validate named aliases first.
When HR changes, change the jobs@ destination. Do not rename jobs@ to jobs-2026@. Printed PDFs do not update. Probe after the swap. Revoke send-as if the old human had it.
Leftover MX plus twenty department names is twenty ways to look flaky. Two resolvers. Delete Google and Microsoft MX if MailerZ is the hop. Paying for Drive does not require aspmx.
Self-send from the sales human to sales@ is invalid. Probe from another mailbox. Header From stays the probe sender. History must exist per department you still print.
Suite sprawl is the other failure. Twenty seats for twenty departments is a class error. Buy seats for humans who need Calendar and Drive. Quote Workspace live if that is real. Otherwise Starter plus three Gmails.
Agencies: departments times clients is alias math. Ten departments on twenty domains is two hundred aliases — Business, not Solo. Do not share one sales@ across clients.
Retention 14/90 is hop evidence, not a department archive. The destination inbox is the store. Export hop rows if a dispute will outlive the window.
Plus tags are not departments. Create billing@ if you print billing@. Do not claim plus-strip.
Monthly: leftover MX, one external probe to the loudest department, send-as counters if any department sends. Five minutes. The outage you avoid is a restored Google MX after an HR ticket.
Start free to prove three departments. Upgrade when the fourth name is still on the letterhead. Do not buy twenty mailboxes to print a directory.
A twelve-department map that stays on Starter
Example map: hello and press to founder A; sales and partners to founder B; billing, invoices, and receipts to finance Gmail; jobs and internships to ops; legal and security to the same ops store with different labels; support to founder B. That is twelve names. Solo cannot hold twelve. Starter can. Free cannot. FORWARD must stay off until these twelve exist and probe green.
Probe list: twelve unique subjects, one other mailbox, twelve hop rows, twelve destination copies. A green hello@ does not prove legal@. Shared destinations do not reduce probes.
Send-as: maybe hello@ and billing@ on Starter’s 5,000/month and 40/hour. The other ten receive only. Phones must not AUTH as support@ unless you mean it.
HR change: internships@ destination swaps to the new recruiter. Name stays. Probe. Revoke the old human’s SMTP if any.
Leftover aspmx: some departments hit a Google Group from 2019. History looks random. Delete leftovers. Groups are not a hop.
Sprawl pressure: marketing wants twenty campaign names. Those are not departments. They are a list. Buy an ESP. Do not burn Agency alias caps on one-off blasts.
Suite pressure: IT quotes twelve seats. Count humans. If three humans need Calendar, quote three seats and a hop for names — or move the store to Workspace and stop publishing MailerZ MX. Dual MX is leftover.
Free proof week: three departments only. Do not print the other nine yet. HOLD will teach you. Then pay Starter and create the rest.
Agencies: twelve departments times ten clients is 120 aliases — Business. Do not put two clients on one sales@ destination “to save an alias.”
Retention: 90 days on Starter. Export if a department dispute lasts longer. Bodies live in the three Gmails.
Plus tags: create the exact string or stop printing it. No plus-strip claim.
Monthly: leftover MX, probe the loudest department, send-as counters. After an offboard, re-probe the names that human watched.
Null MX plus departments is a refuse. Remove it if you receive.
Self-send still lies when you test support@. Use another mailbox.
Start free for three names. Upgrade when the letterhead is longer. Do not buy twelve mailboxes to print a directory. That was the sprawl.
Worked scenarios for department email aliases
A twelve-person company prints sales@, finance@, jobs@, and legal@. They do not need four IMAP boxes. They need four named aliases to the two humans who actually answer. When the sales lead leaves, you remap sales@. You do not migrate a mailbox. You do not leave the leaver's Gmail as the destination.
A university club wants ten department names and has three officers. Map the names that are printed. HOLD the rest. If you FORWARD catch-all, every guessed dean@ becomes a confidentiality incident in a student inbox.
An agency runs departments per client brand: support@ on twenty zones. That is twenty aliases, not twenty mailboxes, and not one shared catch-all across brands. Confirm the live alias and domain caps on /pricing. Agency plan exists. Free is one domain and ten aliases.
Finance wants a mailbox because 'QuickBooks needs one.' QuickBooks needs an address. Map finance@ to the bookkeeper's existing inbox. If a vendor demands IMAP, that vendor is asking for a host. Do not buy a seat for a noun.
HR changes every year. careers@ should be a stable public string. Destinations change. The website does not. That is the whole argument against mailbox sprawl.
Someone creates dept-*@ for every Slack channel. You will hit the plan cap and a mess. Print fewer names. Map those. HOLD unknown. Slack is not a DNS publisher.
Practice and anti-patterns for department maps
Practice: a spreadsheet of printed strings, destinations, and owners. Anti-pattern: creating aliases from memory during a website redesign.
Practice: one destination owner per alias, plus a deputy. Anti-pattern: five people in one Gmail and nobody accountable when it is unread.
Practice: HOLD unknown. Anti-pattern: catch-all FORWARD 'so we never miss a department we forgot to create.' You will receive the internet's typos and a few targeted guesses.
Practice: remap on the last day of employment. Anti-pattern: leaving the leaver as destination because 'they still know the vendors.' That is how invoices leave the company.
Practice: exclusive MX. Anti-pattern: Google MX still on for 'the departments that use Workspace.' Split inbound is not a department strategy.
Practice: paid send-as only for departments that must write as the noun. Anti-pattern: Free users surprised by 550 when sales@ tries SMTP. Quote /pricing. Copy dashboard values. Do not invent ports.
Practice: third-mailbox probes per public department. Anti-pattern: the sales lead emailing sales@ from the destination inbox and declaring the map fine.
Operator closeout for a department map
Closeout is the signed list: local-part, destination, owner, deputy, printed surfaces. If a string is on the site and missing from the list, the cut is incomplete.
Closeout includes probe IDs for each public alias and two-resolver MX listings. Leftover MX is a hard stop even if the map is pretty.
If send-as is in scope for a department, closeout names the paid plan and the client that holds the dashboard secret. Shared SMTP across departments and clients is a later incident.
Offboard dates are in the list. The next leaver should be a remap, not archaeology.
Agencies keep per-brand lists. A blended list is how support@ for brand A lands in brand B's intern.
Schedule a quarterly print crawl. Websites gain footer addresses without tickets. Those become HOLD surprises.
Edge cases in department addressing
Legal wants a separate archive mailbox. That is a host or an archive product. You can still map legal@ to a destination they staff. Do not pretend MailerZ is the archive.
Two departments insist on the same public string. They cannot. Pick one owner or pick two strings. Shared destinations without an owner are unread mail with extra steps.
A department name is a reserved or risky local-part (admin@, postmaster@, abuse@). Understand what you are printing. Some of those have operational meaning. Do not create them as a cute brand.
International offices want local-language local-parts plus English ones. That doubles the map. Write both. Probe both. Do not catch-all the language you forgot.
A union or board requires that mail not land in a personal Gmail. Then they need a shared destination they control, still not necessarily IMAP per department. A single shared inbox plus aliases can be enough. If they require a suite, buy the suite for that job.
Calendar resources are not aliases. Do not create rooms@ and expect MailerZ to become scheduling. Different product.
Field notes from org-chart mail
Org charts change faster than websites. Aliases absorb that if destinations are remapped. Mailboxes absorb that if you enjoy migrations.
The sprawl you prevent is license cost and leftover accounts. The sprawl you still have is naming. Naming is cheaper.
Founders will ask for team@ as a dump. Dump is unread. Prefer sales@ and ops@ with owners. team@ is how things die in a folder named later.
Agencies that standardize sales@, billing@, and support@ across clients can train juniors. Unique random prefixes are for privacy aliases, not for departments customers must remember.
Link /aliases-catch-all and /email-forwarding. Department maps are inbound. Send-as is optional and paid.
RFC 5321 will deliver to whatever MX you published. It will not staff the destination. Staffing is the real department problem. The alias only makes the noun stable.
Handoff memo for HR and ops
Printed nouns, destinations, owners, deputies, HOLD policy, and who remaps. If HR cannot remap, they will ask IT to buy a mailbox for the replacement person. That is the sprawl returning through the side door.
Website and signature owners are in the memo. A footer that still lists an old department is a HOLD ticket.
Exclusive MX and leftover delete are in the memo even though HR does not love DNS. If leftovers return, departments randomly fail. That will look like a people problem.
Free caps are in the memo: one domain, ten aliases. Growing department lists need a paid plan. Confirm /pricing.
SMTP, if any, is per identity and from the dashboard. No shared secret across clients. Free has no send-as.
Acceptance criteria for department aliases
Every printed department string has a named alias and a living destination. Unpublished guesses HOLD.
A leaver drill remapped one alias this quarter without buying a mailbox.
Probes from a third mailbox succeeded. Header From intact. Self-send was not the gate.
Exclusive MX on two resolvers. No department left on leftover Google MX 'because they use Docs.'
No catch-all FORWARD unless a written reason exists. Caps match the plan you bought.
No IMAP promised for each noun. No invented SLA. No inboxing percentage.
Operations review of department sprawl
Count mailboxes bought only to hold a noun. Those are candidates to fold into aliases. Count aliases with no owner. Those are candidates to disable.
Count leftovers: MX, website strings, SMTP From identities. Sprawl is not only seats.
Review shared destinations. If support@ hits a mailbox nobody opens, you have a staffing defect, not an alias defect.
Review plan caps before the next org change. A reorg that adds eight nouns on Free will fail for a boring reason.
Review whether send-as is actually needed per department. Many departments only receive. Do not buy SMTP theater.
Start free on a lab and map three fake departments. The junior should remap one before they touch production.
Quarterly review of the department map
Crawl the website for addresses. Diff against the spreadsheet. Create or HOLD. Do not guess.
Who left? Remap the same week. Who joined? They get a destination, not a noun mailbox, unless a suite job exists.
Did anyone enable catch-all FORWARD to paper over a sloppy print? Revert.
Did leftover MX return after a website save? Morning re-query.
Does /pricing still match the story you told finance? Confirm the card.
Author: MailerZ editorial, Secuno LLC. Review when org charts, pricing, or scope change.
Closing notes on nouns versus seats
Department email aliases are rows on a map. People are destinations. Do not buy a mailbox for every noun on the website. Print what you map. HOLD what you do not. Remap when the org chart moves.
MailerZ is the map: exclusive MX, named aliases, Header From intact, envelope SRS, optional paid SMTP. It is not IMAP and not a campaign ESP.
Start free on one domain if three department names are enough. Upgrade when the list or send-as is the next honest need. Product path: /aliases-catch-all, /email-forwarding, /pricing.
If finance still wants a seat for every noun, show them the last leaver ticket. The cost was never the license. It was the mailbox you forgot to cancel and the invoices that followed that person home. A remap on the last day is cheaper than a migration in the first week of the replacement.
Keep the runbook boring: printed strings, living destinations, HOLD for guesses, exclusive MX, third-mailbox probes. That is department email without mailbox sprawl. Review the map when the org chart moves, not when a customer is already waiting on an unread noun.
Sprawl budget: names versus humans versus sends
Budget names: count letterhead, careers, invoices, legal, security.txt. That number picks Free 3, Solo 15, Starter 50, Business 200, Agency 500.
Budget humans: who needs Calendar and Drive. That number picks suite seats, not aliases. Three humans can watch twelve departments.
Budget sends: who must From as a department. Most should not. Starter 5,000/month and 40/hour is shared. Support loops burn it.
Budget stores: three Gmails is a choice. One grave Gmail is sprawl of attention, not of mailboxes.
Budget leftovers: zero foreign MX. Drive does not need aspmx. Groups are not hops.
Budget FORWARD: off until names exist and probe. Then a written yes or no. Not a debugger.
Budget HOLD: on Free it is the teacher. Missing departments show up. Create or stop printing.
Budget plus tags: create the exact string or delete it from PDFs. No plus-strip.
Budget offboard: destination swap, SMTP revoke, name stays. Do not delete sales@ because Jane left.
Budget campaigns: ESP, not Agency alias caps.
Budget agencies: departments times clients. 12 times 10 is 120 — Business.
Budget proof: one other mailbox, one subject per department, hop plus destination.
Budget self-send: zero as evidence.
Budget SLA: zero inbox percentage. Gmail still files department mail.
Budget archive: destination Gmail. 14/90 is hops. Export if disputes last longer.
Start free for three departments. Print the rest after Starter exists. That is how you avoid mailbox sprawl and alias fiction at the same time.
If IT still quotes one seat per department, send them this budget. Seats are humans. Names are aliases. MX is exclusive. The hop is MailerZ.
Operator Secuno LLC. Not Workspace. Not an ESP. Not a mask app. Exclusive MX or you are not running departments on this hop.
FAQ
- What is the safest way to handle department email aliases?
- List printed department addresses. Create named aliases only for those strings.
- 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
- Departments are aliases.
- Staffed destinations only.
- HOLD unknown.
- Exclusive MX.
- Remap on reorg.
- Free has ten aliases.
- Paid send-as has caps.
- No catch-all department strategy.
Conclusion
Build the nouns as a map. Seat the humans. The website can stay stable while people move.
Start free with the three public departments that actually get mail.