How to Pause Email Aliases: A Quick Guide to Stopping Spam Instantly

To learn how to pause email aliases, open your dashboard, locate the address receiving unwanted mail, and select Pause alias. Inbound messages to that address stop forwarding instantly, cutting off the sender without exposing your primary inbox.

Pausing is reversible. It keeps the forwarding address intact on your account, so account recovery links and purchase receipts tied to that identity remain accessible whenever you decide to unpause. Deleting an alias, by contrast, requires a confirmation prompt and cannot be undone with one click. When you run a dedicated forwarding address for each site, the alias that fills with junk also identifies the company that suffered a breach or sold your record. In Emcognito, pausing is strictly an interactive dashboard action; the v1 developer API handles creation and listing, but has no suspension or deletion endpoints.

The one-click answer: pause the alias, not the inbox

When an inbox fills with spam, filtering rules by sender address or subject line fail quickly because bulk senders rotate sending domains and headers. Knowing how to pause email aliases gives you a clean control plane: cut the pipe at the edge instead of writing complex filter rules in your email client. A single click on the Pause alias button halts all inbound routing for that specific address at the mail server level.

The primary advantage of pausing over discarding an address is identity preservation. If you delete an address connected to an online merchant, you lose the ability to receive delivery tracking updates, billing notices, or one-time login passcodes. Pausing preserves the address record in your dashboard. If you need to trigger a password reset next month, you can unpause the alias for two minutes, receive the verification link, complete your login, and pause it again.

Deleting an alias is permanent. Emcognito protects against accidental removal by requiring a confirmation prompt before an alias is purged. Once deleted, the inbound routing rule is erased. Delete an alias only when an account is closed and you no longer need transactional records or account recovery through that handle.

Assigning a distinct address to every service provides attribution. If you generate a distinct address for an online retailer and that address begins receiving mortgage refinance solicitations, you know that merchant disclosed your data. According to FTC consumer guidance on how websites and apps collect and use information, third parties track online browsing activity to show targeted ads, and mobile apps may request access to device contacts. When you trace the breach directly to a specific merchant handle, you can cut off the incoming traffic without affecting any of your other communication channels.

For programmatic users, note that Emcognito's developer API surface does not manage address state. The v1 REST API exposes GET /v1/aliases to retrieve lists and POST /v1/aliases to generate addresses. There is no PATCH, PUT, or DELETE route. Managing state, pausing forwarding, and permanently deleting records take place within the web dashboard interface.

What pausing does and does not stop

Pausing an alias changes how inbound mail gateways process incoming envelopes. To use temporary alias suspension effectively, you must understand the operational boundary between your forwarding server and your personal mailbox.

Pausing stops any new message addressed to that specific alias from being relayed to your delivery mailbox. The inbound server rejects or drops the incoming message based on system rules, keeping your primary inbox clear. It stops automated newsletter drips, bulk promotional blasts, and unsolicited inbound cold emails sent to that identity.

Pausing does not stop several things:

• It does not pull back mail that reached your destination mailbox prior to pausing.
• It does not prevent senders from contacting your other active aliases or your primary email address if they obtained it elsewhere.
• It does not delete your customer account or personal data from the database of the merchant that held the alias.
• It does not stop you from composing brand-new outbound messages or initiating replies on plans that include outbound delivery.

Suspension governs inbound message routing, not merchant data retention. Halting email delivery does not invoke privacy regulations like GDPR or CCPA. If a company suffered a data spill containing your name, billing address, and phone number, pausing the associated email address blocks incoming messages but leaves your broader profile in their records.

The most common operational failure with a paused alias involves transactional dependencies. If your bank or primary cloud host is mapped to an alias that you suspended because of promotional noise, critical notices will fail to deliver. The FTC phishing guidance advises consumers to check sender details and verify communications directly through official accounts. If you have paused an alias, security notices and legitimate password verification messages cannot reach you. Always separate transactional credentials from marketing subscriptions. Keep a dedicated administrative alias for vital logins and pause only secondary or non-critical marketing handles.

Pause vs delete vs block: pick the right control

Effective inbox hygiene requires matching the right administrative action to the type of inbound mail problem you face.

A pause is an operational pause on inbound routing. It is completely reversible, preserves the address record, and stops forwarding immediately. Use this control when a service sends excessive promotional volume or when an account is dormant, but you still want the option to log in or inspect transactional history later.

Deletion is a permanent revocation of an address. It requires confirming a prompt and wipes the routing target permanently. Reserve deletion for dead platforms, spam traps that have outlived their diagnostic purpose, or one-off web interactions you intend to abandon permanently. You can read more about evaluating long-term addresses against temporary solutions in this guide to temporary email alternatives.

Blocking a sender is a targeted filter applied to an individual address while keeping the alias open. On Emcognito Plus and Pro tiers, incoming messages include new-sender alerts equipped with a one-tap block. If a merchant's marketing partner begins emailing you, you can block that individual sending domain without disrupting account recovery messages from the main merchant platform.

Temporary alias suspension is an investigative step when you notice an influx of spam. Suspending the address halts the noise while you verify whether the leak came from a single rogue marketing partner or a full database breach. Use this simple decision framework:

1. Pause the alias if you need future access to the merchant account.
2. Delete the alias if you have permanently deleted the merchant account.
3. Keep the alias live and block the specific third-party sender if the merchant handle receives critical receipts alongside unsolicited third-party pitches.

Where the pause control lives on each service

Different forwarding services arrange alias suspension differently. Some tools maintain lightweight web consoles, while others bundle alias management inside operating systems or browser suites.

On Emcognito, the pause action is located directly on each address row in the main management dashboard. Clicking Pause alias updates the routing status immediately. If you choose to remove the identity entirely, clicking delete opens a confirmation prompt to prevent accidental loss.

Third-party forwarding platforms handle suspension based on their own system architecture:

• SimpleLogin provides an on/off toggle within the main dashboard list, where switching the toggle off deactivates the alias and causes incoming mail to be blocked or discarded according to account settings. If you are comparing platforms, you can review this analysis of SimpleLogin options.
• As detailed in the addy.io FAQ, addy.io allows users to deactivate aliases directly from the web interface, which causes the service to bounce or discard incoming messages. 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. You can read a direct comparison in this review of addy.io for power users.
• Firefox Relay offers an active/inactive toggle switch next to each address card in its management dashboard, and turning the toggle off stops mail forwarding to your underlying primary email.
• DuckDuckGo Email Protection manages address state via the DuckDuckGo browser extension settings or mobile browser menu, where individual private duck addresses can be deactivated.
• Proton Pass controls aliases through an integrated password manager interface, where users open the specific login item in the desktop or mobile extension to toggle the alias status off.
• Apple Hide My Email is embedded directly into macOS and iOS settings under iCloud account profiles, requiring users to navigate to iCloud settings, locate Hide My Email, select the specific address, and turn off forwarding.

The following table compares the operational design of these forwarding models:

Operating system and password manager integrations link your address controls to a specific proprietary runtime. Standalone tools let you manage forwarding settings without switching browser vendors, migrating vault databases, or changing operating systems.

Managing leaked email addresses: a pause-first workflow

When an address is published in a credential leak or sold to lead brokers, the volume of inbound spam increases rapidly. Using a structured protocol for managing leaked email addresses lets you isolate the compromised identity systematically.

Research published by the Pew Research Center research on email use demonstrates that email remains a central communication tool for professional and personal tasks. A noisy inbox disrupts daily workflows. Here is the operational sequence to contain a compromised address:

1. Inspect the headers or delivery metadata of the incoming spam message to identify the recipient alias. If you maintain unique addresses per platform, the recipient handle immediately names the compromised platform.
2. Log into your dashboard and click Pause alias on that record. This immediately stops incoming mail from reaching your real inbox without deleting the address or breaking active user sessions on the underlying website.
3. Watch your inbox over the next 24 hours. If spam volume drops to baseline, you have confirmed that this alias was the only compromised address. If spam continues arriving, inspect the remaining messages to see if secondary aliases or your primary email were also compromised.
4. If you still need the merchant account, keep the alias paused while you update your account credentials. You can also generate a new alias, swap the address in your merchant profile, unpause the old alias briefly to confirm the migration email, and then permanently pause or delete the old one.
5. If the primary service sends legitimate receipts through the alias, but an affiliate is sending spam, unpause the handle and use the one-tap block feature on paid plans to block the affiliate address directly.

Adopting an organizer methodology—generating one alias per service—makes diagnosing leaks straightforward. When every site has its own isolated identity, addressing a compromise takes seconds.

Edge cases that trip people up

While the mechanics of pausing an address are simple, several subtle technical behaviors can disrupt everyday operations if overlooked.

The primary issue is transactional delivery failure. If you attempt an account recovery or password reset on an external service while its associated alias is paused, the message will fail to deliver. If a site locks your profile for suspicious activity, you cannot receive the unlocking code until you manually access your dashboard and unpause the alias. Check the routing state of your alias before initiating security changes on external services.

Another operational boundary involves historical message threading. On Emcognito Plus and Pro plans, you can reply directly from your mail app (Gmail, Outlook, Apple Mail) to a forwarded message, and the reply routes out from the alias. The message must originate from your sign-in mailbox with passing SPF and an aligned DKIM signature. However, mail forwarded before October 5, 2026 carries no reply address, so replying to old threads is not supported. For older communications, you must initiate a new outbound message from the dashboard.

Outbound message permissions also vary by plan tier. On the legacy Free tier, attempting to reply directly from your mail app is refused with an upgrade message. Free accounts created before October 29, 2026 can use the Reply securely feature within the web delivery log until November 3, 2026, after which replying becomes exclusive to Plus and Pro tiers. Pausing an alias halts inbound routing, but outbound compose capabilities on Plus and Pro accounts remain functional.

Quota accounting is another detail to monitor. In Emcognito, metered units apply to message deliveries, not the number of aliases you hold. Aliases are unlimited across all plans, including legacy Free accounts. A paused alias consumes none of your monthly forwarding allowance while it remains idle, because dropped or rejected inbound envelopes do not count toward your delivery tally. You can maintain hundreds of dormant or paused aliases without paying quota penalties.

Finally, keep legacy account boundaries in mind. New Emcognito accounts choose between Plus and Pro at checkout. The Free tier was closed to new registrations on October 29, 2026. Accounts opened before that date retain unlimited aliases and their allotted monthly forwards (35 forwards per month for accounts created between October 19 and October 28, 2026; 100 forwards per month for older accounts). If you operate a legacy Free account, alias pausing remains fully available in your dashboard.

When pausing is the wrong tool

Pausing is an effective tool for managing alias routing, but certain security and architectural challenges require different approaches.

If your real destination email address is leaked directly, pausing aliases will accomplish nothing. When a sender bypasses your aliases entirely because your personal address was exposed in a direct breach, you cannot filter that traffic at the forwarding layer. You must use mail client filters or migrate your core mailbox to a new address.

Pausing an existing address does not help you bypass daily creation caps. In Emcognito, address generation is subject to rate controls across all tiers: users can create up to 200 aliases per day through the web dashboard. API creations are limited to 50 aliases per day on Plus and 200 per day on Pro. Pausing or deleting an old address does not restore your daily creation allotment, which resets automatically at 00:00 UTC.

Programmatic workflows that require automated suspension cannot use Emcognito's API today. The developer API exposes only two endpoints: GET /v1/aliases and POST /v1/aliases. Pausing, unpausing, and deleting addresses are strictly web dashboard functions. If your infrastructure relies on programmatic lifecycle controls to suspend addresses via scripts, you will need to manage those events manually in the web console.

Frequently asked questions

Does pausing an alias delete the address?

No. Pausing stops incoming mail from forwarding to your primary inbox while preserving the alias record, configuration settings, and activity history in your dashboard. You can resume forwarding at any time by selecting the unpause option. Deleting an alias is a separate, permanent action that requires confirming a prompt.

Will I still receive password reset emails to a paused alias?

No. When an alias is paused, incoming messages are blocked at the mail server and will not reach your destination inbox. To receive a password reset link, verification code, or login token, open your dashboard and unpause the alias before requesting the email from the service provider.

Can I pause an alias through the Emcognito developer API?

No. The Emcognito v1 developer API supports listing aliases with GET /v1/aliases and generating new aliases with POST /v1/aliases. It does not provide endpoints for pausing, resuming, or deleting addresses. All alias status adjustments must be performed interactively through the web dashboard.

What is the difference between pausing an alias and blocking a sender?

Pausing an alias rejects all incoming traffic sent to that specific alias, regardless of who sends it. Blocking a sender filters out a specific originating email address while keeping the alias active, allowing legitimate transactional receipts and notices from other senders to reach your inbox.

Do paused aliases count against my monthly forward limit?

No. Emcognito meters delivered forwarding messages, not the total number of aliases stored on your account. Paused aliases that do not forward mail consume none of your monthly volume, and all plans include an unlimited number of total aliases.

If you need to compose new mail from any alias after pausing incoming traffic, Emcognito Plus is $20 per year and Pro is $36 per year. Find plan details on Emcognito's pricing page.