Proper Email Format: Formal Structure, Examples & Address Rules

Email format means two different things, and most guides only answer one of them. It is the structure of a professional email (subject, greeting, body, closing, signature), and it is the pattern a company uses to build its addresses (first.last@company.com, flast@company.com, and so on). This guide covers both: how to structure an email that gets read, the RFC 5321 rules that make an address valid, the most common company email formats by size, and how to find the exact format a company uses before you hit send.

The proper email format has five parts in order: a specific subject line, a greeting matched to the relationship, an opening line that states the purpose, a body with only the details the reader needs, and a closing with a sign-off and signature. A valid email address follows a separate format defined by RFC 5321: local-part@domain, with the local part capped at 64 characters and the full address capped at 254 characters in practice.

Two different questions hide behind the same search term. Someone asking "email format" might want the structure of a professional email: what goes where, how long it should be, how to open and close it. Someone else is trying to guess how a company builds its addresses, because they have a name and a domain but no way to reach the person. Most guides answer one and ignore the other.

This guide answers both. Use the proper format section to structure any professional email, the valid address format section for the technical rules behind local-part@domain, and the company address formats and how to find one sections if you are trying to reach someone at a specific company.

What Is the Proper Format for a Professional Email?

The proper format for a professional email has five parts, always in the same order: a subject line, a greeting, an opening line that states the purpose, a body with supporting details, and a closing with a sign-off and signature. Drop one of the five and the reader has to work to figure out what you want. Keep all five short and the email reads in seconds instead of minutes.

Here is the structure, part by part:

1. Subject line. 4 to 8 words that name the action or topic. "Confirm Q3 pricing by Friday" gets opened; "Quick question" gets skimmed and archived.
2. Greeting. "Hi [Name]," works for most professional email. Match the formality to the relationship and the reader's own last message if you have one.
3. Opening line. One sentence, first thing in the body, that states why you are writing. "I'm reaching out to confirm next week's onboarding call."
4. Body. 2 to 5 lines with only the facts the reader needs to respond: one line of context, the essential details, and options if a decision is required.
5. Closing. One line that names the next step, a sign-off phrase ("Best," "Thanks," "Best regards,"), and a signature with your name, role, and one way to reach you.

Assembled into a real email, the five parts look like this:

Subject: Confirm Q3 pricing by Friday

Hi Elena,

I'm reaching out to confirm the updated Q3 pricing before we send the contract to Legal.

The only change is Section 4: seat price drops to $79/user for 50+ seats, matching what we discussed on the call. Everything else in the March proposal stays the same.

Can you confirm you're good with the new number by Friday so we can get the contract out Monday?

Best,
Marc Dubois
Head of Sales, Sortlist
marc@sortlist.com

Notice the ask sits in the first line of the body, not buried at the bottom. That habit, more than any wording choice, is the difference between an email that gets a same-day reply and one that sits unread for a week.

What Is a Valid Email Address Format?

A valid email address follows the format local-part@domain, as defined by RFC 5321, the internet standard that governs how mail servers transmit email. The local part identifies the mailbox, for example "jane.doe"; the "@" symbol separates it from the domain; and the domain identifies the mail server responsible for delivery, for example "company.com".

The technical rules that make an address valid:

• Exactly one "@" symbol. "jane@doe@company.com" is not valid; there can only be one separator between the local part and the domain.
• Local part capped at 64 characters. RFC 5321 limits the section before the "@" to 64 octets.
• Domain capped at 255 characters. The domain, including any subdomains, has its own 255-octet ceiling.
• Restricted characters in the local part. Letters, digits, and a limited set of symbols (dot, underscore, percent, plus, hyphen) are safe unquoted. A dot cannot open, close, or repeat consecutively.
• The domain must resolve. A syntactically valid address can still bounce if the domain has no mail exchange (MX) record, which is why passing a format check does not guarantee deliverability.

A few examples make the rules concrete:

What Are the Most Common Company Email Address Formats?

Most companies pick one address pattern for the whole domain and build every employee's address from their name using that pattern. Learn the pattern once, and you can build almost anyone's address at that company from a name and a domain alone.

The pattern that dominates changes predictably with company size (choosing a pattern for your own team instead? The professional email generator builds the candidates in one click):

The practical takeaway: if you only know one confirmed address at a company, you can usually infer the pattern for the whole domain, unless the company is large enough to run a first.last convention with occasional exceptions for name collisions (two "Jane Doe" entries, for instance, which often get a middle initial or number appended).

How Do You Find a Company's Email Address Format?

Once you know the pattern, you can build most addresses at that company without ever seeing them published. Four ways to confirm it before you rely on a guess:

1. Check a published address. The "Contact," "About," or "Press" page often shows one real address ("press@acme.com" or "jane.doe@acme.com"), which reveals the pattern instantly.
2. Read the source of an email you already have. A signature, a forwarded thread, or a quote in a press release frequently contains a real, working address.
3. Search LinkedIn and company bios. Some profiles list a direct email; job postings and conference bios occasionally include one too.
4. Use pattern-matching plus verification. Given one confirmed address at a domain, apply the same pattern to any other name at that company, then verify each guess against the mail server before you send.

That last step is what an email finder automates: it applies every known pattern to the name you give it, ranks the candidates by how common each pattern is at that company size, and checks the domain's mail servers before you rely on any of them. It is free and needs no account. For list-scale work, Overloop's B2B contact database covers 450M profiles with formats already mapped, so you search by name and company instead of testing permutations one at a time.

If you build addresses manually, verify before you send at any volume. A syntactically valid, correctly patterned guess can still hit a closed mailbox, and sending a batch of unverified guesses damages your domain's sending reputation. Running a list through an email verification API before a campaign catches invalid and high-risk addresses before they turn into bounces.

A worked example, from a name to a verified address

Say you need to reach Maria Ferrer at a 2,000-person software company on the domain northwind.com, and you have no confirmed address at that domain yet.

1. Start from headcount. Between 1,001 and 5,000 employees, first.last is the most likely convention, so maria.ferrer@northwind.com is the leading candidate.
2. Generate the alternates. The realistic runners-up are mferrer@, mariaferrer@, maria_ferrer@ and ferrerm@. Five candidates covers the large majority of B2B domains.
3. Check the domain can receive mail at all. A domain that publishes no MX records cannot accept mail, and no permutation will work. That is one DNS lookup, and it invalidates the entire candidate list in a single step. The domain health checker reads the MX, SPF, DKIM and DMARC records for a domain.
4. Confirm the convention with one named address. A role address like press@northwind.com or info@ tells you nothing about the personal pattern, because role mailboxes are created by hand. A named address quoted in a press release, a conference bio or an email signature does.
5. Verify, then send to one address only. Never load five permutations of the same person into a campaign. Four of them are wrong by construction, and each one is a bounce recorded against your sending domain.

Why a correct pattern can still bounce

Pattern matching gets you the shape of an address. Four things break it even when the shape is right, and each one is a different failure to plan for.

The catch-all case is the one that costs money, because it looks like success. On a catch-all domain a verification pass returns a clean result for every guess you feed it, which is exactly the signal that tempts people to load all five permutations into a sequence. The correct read of an accept-all response is that the domain declined to answer the question.

Formal Email Format vs Casual: Which Should You Use?

Once the five-part structure is right, tone is the only variable left. Get it wrong and you either sound stiff to a friendly contact or sloppy to someone who expects polish. Here is the quick chooser.

• Formal: "Dear [Title] [Last name]," and "Sincerely," or "Best regards," for first contact with executives, legal or financial matters, and job applications.
• Professional (the default): "Hi [First name]," and "Best," or "Thanks," for most day-to-day work email.
• Casual: "Hi [Name]," or just "[Name]," and "Cheers," or "Talk soon," for people you know well.
• Cold outreach: "Hi [First name]," followed by a question-based call to action instead of a generic sign-off.

For the openers and greetings that fit each context, see our guide to how to start an email. For the full list of sign-offs grouped by formality, see 45+ email sign-offs by context. The format stays the same across all four; only the greeting, sign-off, and word choice shift.

Email Format Examples by Situation

Here is the five-part format applied across common situations. Copy the structure, replace the specifics.

Formal request to a senior stakeholder

Subject: Approval needed: updated MSA by Thursday

Hello Ms. Patel,

I'm writing to request your approval on the updated Master Service Agreement before our legal team can countersign.

Section 4 (payment terms) now matches the terms from our last call: net 30 instead of net 45. Everything else is unchanged from the version you reviewed in March.

Could you confirm approval by Thursday so we can keep the July 15 onboarding date?

Best regards,
Jordan Lee
Head of Partnerships, Acme Co
jordan@acme.co

Cold outreach to a new prospect

Subject: Question about outbound at Nordvale

Hi Alex,

Saw Nordvale is hiring two SDRs this quarter, which usually means outbound volume is about to jump.

We help B2B teams personalize cold email and LinkedIn outreach at scale without losing the "a human wrote this" feel.

Worth a quick 15-minute call next week to compare notes?

Appreciate your time either way,
Priya Nair
Sales Lead, Overloop

To apply this structure across a sequence, cold email software can keep templates, follow-ups, and replies in one workflow.

Internal quick update

Subject: Update: contract redlines resolved

Hi team,

Legal signed off on the redlines this morning. No changes to pricing or scope.

Next step: I'll send the final PDF for countersignature by end of day.

Thanks,
Sam

Meeting or scheduling request

Subject: 15 min on SOC 2 timeline?

Hi Marcus,

I'd like to align on the SOC 2 audit timeline before we brief the board next month.

Are you free Tuesday or Wednesday afternoon, 30 minutes, your call on the time?

Thanks,
Dana

Following up on a quiet proposal

Subject: Re: Q3 proposal (bumping this)

Hi Elena,

Circling back on the proposal from last week in case it got buried.

Two options if it's still relevant: (A) start with the pilot scope, or (B) go straight to the full rollout.

Should I follow up next month instead, or is this still a priority?

Best,
Marc

Job application email

Subject: Application: Senior RevOps Manager (Jane Doe)

Dear Hiring Team,

I'm applying for the Senior RevOps Manager role posted this week. I've attached my resume and a short case study relevant to your onboarding funnel.

I'm available for a call any afternoon this week if that's useful.

Sincerely,
Jane Doe
jane.doe@email.com

Common Email Format Mistakes to Avoid

Most format mistakes cost you a reply before the reader even considers the content. Here is what to drop and what to do instead.

For the subject lines that get these opened in the first place, see our guide to the best subject lines for sales emails, and for length benchmarks, what's the best email length for sales outreach.