How to Compose Mail From an Alias (and When You Still Can't)

The Short Answer: Compose Needs a Paid Plan, Replies Do Not

To compose mail from an alias in Emcognito, log in to your dashboard, select the alias, and open the compose window. Composing brand-new mail from an alias requires an active paid plan whose first invoice has cleared; it is the only capability the Free tier cannot do at any usage level. On the Emcognito pricing schedule, the annual terms customers actually buy are $20 per year for Plus (or $2 per month) and $36 per year for Pro (or $4 per month). Source: Emcognito source.

Trial accounts cannot compose outbound mail immediately. This restriction protects IP reputation across the shared sending pool. If your immediate goal is composing new mail from an alias to initiate a conversation, plan for that initial invoice settlement before sending your first message.

Replying from your own mail app is paused for security and is refused rather than delivered. Composing a brand-new message from an alias is the Plus and Pro feature. If an incoming message reaches your alias today, you can reply to it on any tier via the web dashboard without paying a cent.

How to Compose Mail From an Alias, Step by Step

Here is the operational workflow for generating outbound mail from an alias from scratch:

1. Select or generate the sending address: In your Emcognito dashboard, open your aliases list. Pick the specific alias you want the recipient to see, or create a new one. The number of aliases an account holds is unlimited on every tier including Free, though creating new aliases is capped at 200 per day from the dashboard across all tiers.
2. Open the compose window: Click the compose button next to that alias. The dashboard sets your selected alias as the authenticated From: address.
3. Draft and verify the headers: Under the IETF RFC 5322 Internet Message Format specification, the From: and Reply-To: headers dictate sender identity and message response routing. Enter your recipient's destination address, add your subject line, and write the body. The recipient's mail server receives the email directly from Emcognito's delivery network. They see your alias as the sender, while your underlying primary inbox address remains completely absent from all message headers.
4. Send the message: Submit the draft. The message leaves the mail server immediately, logs an outbound entry in your delivery dashboard, and decrements your monthly account quota.

There are two critical resource constraints to keep in mind whenever you compose from an alias. First, every compose send counts against the same monthly forward quota that inbound forwarding draws on. Composing and forwarding do not operate on separate tracks; outbound messages consume the exact same quota balance as inbound deliveries. Second, daily send caps apply: 20 messages per day on Plus and 100 messages per day on Pro. For new accounts, these daily send caps ramp up gradually over your first 7 days to establish positive sending telemetry.

If you hit your daily compose cap, inbound forwarding continues uninterrupted. Reaching your daily outbound ceiling simply blocks additional compose actions until the counter resets at midnight UTC.

The Daily Send Cap and the Monthly Quota Are Not the Same Limit

A frequent point of confusion for privacy-conscious users is the distinction between rate-limiting mechanisms and account allowances. In Emcognito, the daily compose cap and the monthly forward quota are separate operational boundaries governing different dimensions of your usage:

• The Daily Compose Cap: Enforces velocity limits on outbound mail creation. Plus accounts are capped at 20 compose sends per 24-hour cycle; Pro accounts are capped at 100 compose sends per 24-hour cycle. This ceiling applies strictly to outbound composition initiated from the dashboard.
• The Monthly Quota: Measures overall transit volume through your account every calendar month. On Free, the limit is 100 forwarded messages per month (which can increase to at most 200 through referral bonuses). On Plus, the limit is 2,500 forwards per month. On Pro, the allowance is 15,000 forwards per month.

Because every compose send draws from your monthly quota, treating compose as an independent budget will quickly exhaust your account limits. For example, if you subscribe to Plus ($20 per year on the pricing table) and send your maximum daily compose allowance across multiple consecutive days, each outbound message decrements your 2,500 monthly forward allowance, reducing the remaining balance available for inbound forwards and delivery-log replies combined.

Replying From an Alias: What Actually Works in 2026

While composing brand-new mail requires a paid plan, replying from an alias is fully functional on the Free plan. However, the exact technical routing differs significantly from conventional mail clients.

To respond to incoming correspondence, locate the message inside your Emcognito delivery log. The delivery log stores received messages for 7 days. Click Reply securely inside the log viewer. An in-dashboard composer opens, pre-addressed to the sender, routing the response through the exact alias the sender originally contacted. Just like compose sends, each delivery-log reply deducts one message from your monthly forward quota.

What does not work is responding directly from your local mail app. Replying from your own mail app is paused for security and is refused rather than delivered. Historically, email alias forwarders used complex reverse-routing schemes—rewriting the envelope Reply-To header into an encoded recipient token on their own domain. If an end user attempted to respond through an external email client, the client sent the message back to the alias server, which unwrapped the token and re-sent it to the actual recipient.

That route is deliberately paused across all Emcognito plans, Free and paid alike. If you try to bypass the delivery log by responding through an external email client, the inbound relay refuses the transmission outright instead of processing it. There is no toggle or configuration option to re-enable local mail app replies. If your day-to-day workflow requires replying to incoming messages, you must keep the Emcognito delivery log open to send your responses.

Understanding this mechanic is critical for identity hygiene. As outlined in the FTC phishing guidance, misconfigured communication channels and spoofed addresses create significant security exposures for consumers. Restricting replies to an authenticated web-based delivery log eliminates the risk of an unauthenticated personal mail client leaking your real IP or primary address in outbound metadata headers.

Which Plan Unlocks Compose, and What Each One Costs

Because outbound compose is metered by billing status, choosing the right tier depends on whether you only need inbound triage or active outbound communication. Emcognito does not gate alias generation: what is metered is forwarded email volume, not aliases. The number of aliases an account holds is unlimited on every tier including Free.

Here is how the tiers break down in detail:

• Emcognito Free: Offers unlimited aliases and 100 forwarded messages per month, which can reach 200 via referral bonuses. Replying through the delivery log is fully enabled. No credit card is required to sign up. Forwarded emails on the Free plan carry a single, clearly-labeled sponsor card at the bottom of the body. Outbound compose is strictly unavailable on this tier.
• Emcognito Plus: Listed on the pricing page at $20 per year (or $2 per month). It includes 2,500 forwarded messages per month, strips the sponsor card from all delivered messages, unlocks the REST API at 50 alias creations per day, and enables outbound compose from any alias once the first invoice clears. The compose cap is 20 messages per day.
• Emcognito Pro: Listed on the pricing page at $36 per year (or $4 per month). Yearly Pro is three months free compared to the monthly cadence and represents the term customers actually buy. It includes 15,000 forwarded messages per month, raises the developer API creation limit to 200 aliases per day, and expands the daily compose cap to 100 messages per day.

You must provide a credit card up front to begin the trial, but you are not billed until the 7 days expire. Remember: compose capabilities activate only after that initial billing cycle successfully processes. Authentication across all tiers is completely passwordless: you log in using an emailed magic link, avoiding master password credential leaks.

Where Compose Fits If You Are Leaving Another Alias Service

Privacy-focused users searching for how to compose mail from alias addresses are frequently migrating from platforms such as SimpleLogin, addy.io, Firefox Relay, DuckDuckGo Email Protection, Proton Pass, or Apple Hide My Email. Many of these users are running one alias per site to trace data brokers, escaping arbitrary alias-creation caps, or seeking a utility independent of an operating system or password manager bundle.

Before standardizing on Emcognito for outbound communication, review the technical boundaries and product design choices to verify it matches your threat model:

• Domain configuration: Emcognito aliases use the shared emcognito.com domain. Custom subdomain support is planned, but custom domains are not available today.
• Source Code and Hosting: Emcognito is closed source and runs only as a hosted service; if open source or self-hosting is a requirement, addy.io is the better fit.
• Service Architecture: Emcognito is an email alias service: it creates durable, reply-capable forwarding addresses that deliver to your real inbox without revealing it. It is not a disposable, burner or temporary inbox. You can suspend any alias with a single click if an address leaks, cutting off the sender instantly, or permanently delete it after a confirmation prompt.
• Outbound Capability Matrix: While services like SimpleLogin and addy.io offer reverse-alias generation or PGP-encrypted mail options, Emcognito isolates outbound compose inside the dashboard and pauses local mail app replies to eliminate header misconfigurations. DuckDuckGo and Apple Hide My Email tie address management to custom browser ecosystems or hardware accounts, whereas Emcognito works through a standard web console and an optional Chrome extension.

Consumer privacy decisions often hinge on minimizing corporate surveillance. As detailed in the FTC guidance on how websites and apps collect and use information, cross-site trackers consistently rely on persistent identifiers like email addresses to link distinct behavioral profiles. Segregating every online subscription behind an isolated alias stops this cross-context aggregation.

Composing From an Alias in Your Own Code

If you are a developer integrating programmatic alias generation into scripts or applications, the Emcognito REST API allows you to automate alias lifecycle tasks. Outbound compose itself is managed through the authenticated dashboard, but address provisioning and tracking are handled entirely over HTTPS.

The developer API is included on paid plans, documented on the pricing page and developer reference: 50 alias creations per day on Plus ($20/year) and 200 per day on Pro ($36/year). The base endpoint is https://api.emcognito.com/v1 (there is no /api/v1 path).

Authentication requires an HTTP header: Authorization: Bearer <key>. API keys begin with the literal prefix emk_ followed by 43 URL-safe characters. There is no live/test environment split.

Endpoint Reference: Creating an Alias

To provision an alias for programmatic outbound tracking, send an HTTP POST request to /v1/aliases:

curl -X POST https://api.emcognito.com/v1/aliases \
  -H "Authorization: Bearer emk_your_key_here_alphanumeric_sequence_43_chars" \
  -H "Content-Type: application/json" \
  -d '{
    "label": "Vendor Inquiries",
    "note": "Created for outbound supplier correspondence",
    "source": "api-script",
    "category": "procurement"
  }'

The response contract has distinct characteristics detailed in the Emcognito developer documentation:

• POST /v1/aliases returns HTTP 200 with the new alias under "alias".
• The object fields are: id, address, status, created_at, forward_count, label, note, source, category, single_use, and expires_at.
• There is no top-level id or email, and no {status, data} envelope.
• The created_at timestamp is an integer epoch, not an ISO string.
• In the developer schema, any unset string field returns as an empty string (""), never null.

Example response body:

{
  "alias": {
    "id": "al_984f1a2e7c3b",
    "address": "k9x2m4q7p@emcognito.com",
    "status": "active",
    "created_at": 1774915200,
    "forward_count": 0,
    "label": "Vendor Inquiries",
    "note": "Created for outbound supplier correspondence",
    "source": "api-script",
    "category": "procurement",
    "single_use": false,
    "expires_at": ""
  }
}

Rate Limits and Error Handling

Under IETF RFC 7231 Section 7.1.3 (Retry-After), servers indicate how long a client ought to wait before making a follow-up request. For Emcognito, the burst limiter returns the full window duration in whole seconds on its 429 status code.

Both types of 429 responses return a bare JSON error body: {"message": "Rate limit exceeded"}. Additionally, v1 of the Emcognito API creates and lists aliases (GET and POST /v1/aliases). Suspending, resuming and deleting an alias are one-click dashboard actions today; there is no PATCH or DELETE endpoint yet. For full parameter definitions and cursor pagination details on GET /v1/aliases, consult the developer documentation.

Pitfalls That Break a Compose Workflow

When operating a multi-alias privacy system, unexpected delivery failures usually stem from operational assumptions rather than network outages. Watch out for these specific implementation traps:

1. Assuming Compose and Forwarding Have Independent Quotas

As noted earlier, outbound mail directly consumes your monthly message allocation. Plus includes 2,500 forwards per month, and Pro includes 15,000 forwards per month. Monitor aggregate usage in your account dashboard to avoid choking inbound forwards late in your billing month.

2. Attempting to Compose During the 7-Day Trial

New signups on Plus or Pro frequently enter the dashboard expecting to dispatch an outbound message immediately. Because trialists have not paid their first invoice, the dashboard locks the compose window. If your operational use case demands immediate compose capability, be aware that the feature activates once the first payment clears.

3. Attempting Direct Mail Client Replies

Replying from your own mail app is paused for security and is refused rather than delivered. Composing a brand-new message from an alias is the Plus and Pro feature.

4. Exceeding the Ramp-Up Cap in Week One

To establish healthy delivery metrics with upstream receiving providers, Emcognito enforces a 7-day ramp-up on the daily compose send cap for all new subscriptions. Scale your outbound correspondence gradually over your first week of operation.

5. Confusing Forwarding Isolation with Cryptographic Encryption

Understanding the exact cryptographic boundary of your alias provider prevents false security assumptions. Emcognito forwards mail over TLS-encrypted transport and does not read message contents or retain them after delivery, apart from a brief hold on mail that arrives over your monthly forward cap, but it is not end-to-end encrypted. For content confidentiality, pair it with an encrypted mailbox such as Proton Mail or Tuta.

Additionally, Emcognito strips tracking pixels (the tiny hidden images that report when you open a message) from forwarded mail on every plan, Free included. It does not remove scripts or rewrite links and does not scan for malware.

Frequently Asked Questions

Can I compose new mail from an alias on the Free plan?

Composing brand-new mail from an alias requires a paid plan (Plus or Pro) whose first invoice has cleared.

Does composing a message count against my monthly forward quota?

Yes. Every compose send decrements your monthly account message quota. On the Plus tier, your 2,500 monthly message allowance covers both inbound forwards and outbound compose sends. On Pro, your 15,000 monthly allowance functions the same way.

Can I reply from Gmail or Outlook instead of the delivery log?

No. Replying from your own mail app is paused for security across all tiers, and any messages sent through that path are refused rather than delivered. To reply to a message received through an alias, open your Emcognito delivery log and select Reply securely on messages delivered within the last 7 days.

How many messages can I send from an alias per day on Plus and Pro?

Plus subscribers can send up to 20 compose messages per day. Pro subscribers can send up to 100 compose messages per day.

Can I suspend or delete an alias through the API?

v1 of the Emcognito API creates and lists aliases (GET and POST /v1/aliases). Suspending, resuming and deleting an alias are one-click dashboard actions today; there is no PATCH or DELETE endpoint yet.

The One Next Step

If composing new mail from any alias is the capability you need, compare the yearly terms on the Emcognito pricing page and pick the tier that matches your expected volume. Plus is $20 per year with 20 compose sends per day, and Pro is $36 per year with 100 compose sends per day. Choose the subscription that fits your outbound requirements, let your initial invoice process, and you can begin dispatching isolated, alias-backed messages directly from your dashboard.