Business Email is an open list (VPE enabled) on a custom domain. Team members use their personal or contractor email addresses but correspond with clients and vendors under a company address. When a team member leaves, they are removed from the list and the contact addresses they used stop routing - outside parties retain no walk-away connection to that individual. When a new member joins, they are added with a pseudonym and existing conversations route to them alongside the rest of the team.
This configuration suits small businesses with contractor or freelance teams, solo practitioners who want to present a full organizational structure, and any team where the outside world should correspond with the company rather than with individuals.
Hybrid teams (employees + contractors). EMail Parrot works equally well when some team members have corporate email accounts and others work as contractors with personal addresses. Employees join with their corporate address; contractors join with their personal address. Everyone appears to outside parties under the same company relay domain. Contractors get a branded presence without needing a corporate email seat. Employees get the added benefit of client contact that does not walk away with them if they leave. The relay does not care what address is behind the pseudonym - the outside world never sees it either way.
1. EMail Parrot Configuration
Set up your custom domain first. Business Email works best with a custom subdomain such as e.yourco.com. Contact support@emparrot.com with your chosen subdomain - they will provide the DNS record to add at your registrar and activate the domain on the EMail Parrot side. This is a one-time setup. Once your domain is active, you can create as many lists as you need at no additional per-list charge.
If you want to test before committing to a custom domain, create a list at emparrot.com first and migrate later.
Create lists to match your team structure. Common starting points: a main team list, a support list, a finance list. Each list is reachable at listname@e.yourco.com. There is no limit on list count at a custom domain.
Add all team members with pseudonyms appropriate for each list context. A contractor named Jane might be “jane” on the dev list and “jane-support” on the support list, or have the same pseudonym everywhere. Use pseudonyms that make sense internally for your team.
Enable VPE on lists that communicate with outside parties. In Group Settings for each relevant list, set “Open Email List with VPE” to True. Leave internal-only lists (HR discussions, internal project coordination) closed.
Create sublists for functional routing. A single-member sublist acts as a personal alias - replies from outside parties route to that person alone. A multi-member sublist routes to everyone on it. Common patterns: a support sublist for whoever is handling support this week, individual aliases for each team member’s one-on-one client relationships.
Use restricted sublists for sensitive internal channels. Prefix the sublist name with ^ to prevent outside parties from sending to it even though the parent list is open.
Recommended settings:
- VPE: enabled on external-facing lists; disabled on internal-only lists
- Direct messaging: on (default)
- Advanced protection: your choice - standard for most businesses, advanced for financial or legal communications
- Strip external content: on (default) - removes tracking pixels and remote images from inbound email; see note below
- AI safe protection: on if team uses AI email assistants
Note on strip external content and outbound HTML. Strip external content removes tracking pixels and externally loaded images from email arriving at your list - protection against surveillance by senders. The same processing applies when relaying outbound: if a team member sends HTML-formatted email with external images (logos, banners, newsletter layouts), recipients may see broken images or plain text. For occasional correspondence this is rarely an issue. If your team regularly sends formatted marketing or promotional email, route that traffic through a dedicated marketing platform rather than the relay.
2. Your Email Client Setup
No required changes to team members’ existing email. They send and receive through EMail Parrot using their personal addresses - nothing about their inbox setup needs to change.
Optional - sorting by list: Team members handling multiple lists may want email filters that route incoming relay mail to list-specific folders. Filter on the sender domain (e.yourco.com) or specific list addresses.
Optional - protecting team inboxes from direct contact: If a team member’s personal address becomes known to outside parties and you want to redirect that contact through the relay, they can set up an auto-responder or filter suggesting correspondents use the company address instead.
3. Addressing Conventions
This is the most important surface for business use. Establish these conventions with your team from the start.
Never give out personal email addresses to clients or vendors. Always use the list address or a sublist/alias address. This is what makes the walk-away protection work - if outside parties never have personal addresses, there is nothing to walk away with.
Save client and vendor contacts in VPE format. When you establish a relationship with an outside party, save their contact record using their VPE-format address: +contact=at=theirdomain.com+listname@e.yourco.com. Use the address conversion tool to generate these. When saved as a contact, all future emails to that party route through the relay automatically.
Use sublist aliases for one-on-one client relationships. If a team member should be the primary contact for a specific client, address that client through a sublist containing only that member: +client=at=co.com+jane.support@e.yourco.com. The client corresponds from the company address; Jane handles it; the rest of the team is not involved unless Jane includes them.
Inbound from clients: Outside parties who email your list address directly (when VPE is enabled) arrive as VPE-encoded senders. Reply using the encoded address in the reply-to field - your email client will handle this automatically when you hit Reply.
Settings to Consider
The recommended settings above cover most business situations. A few additional options worth knowing about:
Advanced protection screens for sophisticated spoofing patterns that standard filtering misses. Turn this on for any list that handles financial correspondence, legal matters, or client communications involving contracts or payments. The stricter screening reduces false-positive delivery of phishing attempts that impersonate known contacts.
AI safe protection blocks prompt-injection attempts embedded in email content - attempts by a sender to manipulate an AI assistant that might process the message on the recipient’s behalf. If anyone on your team uses an AI tool that reads their email, this is worth enabling.
Instant deletion instructs EMail Parrot to purge relayed content from its logs immediately after delivery rather than retaining it through the standard retention window. Enable this if your business operates under a data minimization policy or if team members handle sensitive client information where log retention is a liability.
Restricted sublists (prefix with ^) prevent outside senders from reaching internal channels even when the parent list is open. Use these liberally for internal project discussion, HR topics, or any channel that should never be reachable from outside.
Checklist
- Custom domain configured with support team
- Lists created for each function (support, finance, etc.)
- All team members added with pseudonyms
- VPE enabled on external-facing lists
- Restricted sublists created for internal-only channels
- Individual alias sublists created for team members who handle one-on-one client relationships
- Team trained on VPE addressing conventions
- Team contact books updated to use VPE-format addresses for existing clients and vendors
Back to setup options | Addressing reference | Administrator documentation