Is it legal to use a fake email address?

Using fake email addresses for privacy protection, testing, or avoiding spam is generally legal. However, using fake emails for fraud, impersonation, identity theft, or other illegal activities is against the law. Always check the terms of service of any platform you're registering for.

How long does a temporary or fake email address last?

The lifespan varies by service: temporary emails typically last 10 minutes to 24 hours, disposable emails can last days to weeks, while burner emails last as long as you maintain them. Always check the specific service's terms for exact durations.

Can I send or reply to emails with a fake email address?

Most temporary and disposable email services only allow you to receive emails, not send them. Some burner email services do allow sending, but functionality is often limited. Check the specific service's capabilities before relying on two-way communication.

Are fake email addresses secure and private?

Security and privacy vary significantly between services. Reputable temporary email providers offer good privacy protection, but some may log data or be accessible to others. Never use fake emails for sensitive accounts like banking or healthcare, and always read the privacy policy of any service you use.

What is a disposable email address?

A temporary inbox created through services like Mailinator or Guerrilla Mail. It requires no identity verification and is automatically destroyed after a set time. Commonly used for privacy, but also heavily associated with fake account creation and spam sign-ups.

How does DMARC help stop fake email attacks?

DMARC tells receiving servers how to handle emails that fail SPF or DKIM checks. With a p=reject policy, spoofed emails impersonating your domain are blocked before they reach anyone's inbox, making it one of the most effective technical controls against fake email abuse.

Exchange Mailbox Recovery: Restore Deleted Mailboxes

Key Takeaways

A deleted Exchange mailbox is not gone immediately – it stays in the database as a disconnected mailbox for the mailbox retention period, 30 days by default.
Inside that window, you can reconnect it in the Exchange Admin Center (EAC) or with Connect-Mailbox, or pull its contents into another mailbox with New-MailboxRestoreRequest.
After retention expires, the mailbox is purged and the only native route back is a backup restored into a Recovery Database (RDB).
If you have no usable backup, an Exchange recovery tool can read the mailbox out of the EDB file directly.
Recovery restores the data. It does not restore the trust signals attached to that address – which is where domain-level authentication matters.

Why Exchange mailboxes get deleted in the first place

Mailboxes disappear for ordinary reasons: employee offboarding, storage cleanup, a botched Active Directory change, a bulk script that matched more accounts than it should have. Sometimes it is a genuine accident – someone removes the wrong user twenty minutes before the finance team needs three years of invoices.

Whatever the cause, your recovery path depends on one thing: how long ago it happened, and which deletion state the mailbox is in. Get that right and the rest is mechanical.

First, identify the deletion state

Before you run anything, work out which of these you are dealing with.

State	What it means	Recovery method
Disconnected (soft-deleted)	Mailbox removed, but the data is still in the mailbox database within retention (30 days by default)	Reconnect via EAC or Connect-Mailbox, or restore into another mailbox with New-MailboxRestoreRequest
Purged (hard-deleted)	Retention period expired, or the mailbox was permanently removed	Restore a backup into a Recovery Database (RDB)
No backup available	Retention gone and no usable backup, but the EDB file still exists	Exchange recovery tool reading the EDB directly
Exchange Online	Mailbox soft-deleted in Microsoft 365	Restore within 30 days from the Microsoft 365 admin center or with Undo-SoftDeletedMailbox

Check which mailboxes are still recoverable in your database:

Get-MailboxDatabase | Get-MailboxStatistics | Where-Object { $_.DisconnectReason -ne $null } | Format-Table DisplayName,MailboxGuid,DisconnectReason,DisconnectDate -AutoSize

If your mailbox appears in that list, you are in the easy case. If it does not, skip ahead to the Recovery Database section.

Option 1: Reconnect a soft-deleted mailbox (within retention)

While the mailbox is still disconnected, you have two choices.

Reconnect it to a user account

In the EAC, go to Recipients → Mailboxes, select More options (…) → Connect a mailbox, then pick the disconnected mailbox and the Active Directory account to attach it to.

The shell equivalent:

Connect-Mailbox -Identity “Aryna Sabalenka” -Database DB01 -User “ArynaS” -Alias ArynaS

Or merge the contents into an existing mailbox

This is usually what you want when the original user has already left and a manager needs access to the history:

New-MailboxRestoreRequest -SourceDatabase DB01 -SourceStoreMailbox “Aryna Sabalenka” -TargetMailbox [email protected] -TargetRootFolder “Recovered-AS” -AllowLegacyDNMismatch

-TargetRootFolder drops everything into a clearly labelled folder instead of mixing it through the manager’s live inbox. It is worth using every time.

Before you do anything else: if you are inside the retention window, extend it. Running Set-MailboxDatabase DB01 -MailboxRetention 45.00:00:00 buys you time while you plan the recovery. It does nothing for mailboxes already purged, so run it early.

Option 2: Recover a permanently deleted mailbox using a Recovery Database (RDB)

Once retention expires, the mailbox is removed from the database and no reconnect command will find it. At this point you need a backup and a Recovery Database.

An RDB is a special mailbox database type that lets you mount a restored copy of a database alongside your production one, browse the mailboxes inside it, and extract what you need – all while the live Exchange Server stays online and users keep working. Nothing about production is touched.

Before you start, confirm:

You hold the required permissions (Organization Management or Recipient Management, depending on the cmdlets you need).
Your backup application can restore Exchange data directly to an RDB. Not all of them can.
Windows Server Backup restores file-level backups to an RDB, not application-level ones.
The restored database file and its transaction logs are copied into the RDB folder structure before you mount anything.

Step 1 – Restore the database and check its state

Copy the recovered database and its log files to a location on the Exchange Server, then check the shutdown state:

Eseutil /mh “E:\Databases\RDB001\DB001.EDB”

Look at the State line. If it reads Clean Shutdown, move on. If it reads Dirty Shutdown, run a soft recovery to replay the logs:

Eseutil /R E01 /l E:\Databases\RDB001 /d E:\Databases\RDB001

E01 – log generation prefix for the recovery database
/l – path to the transaction log files
/d – path to the Exchange database you want to recover

New-MailboxDatabase -Recovery -Name RDB001 -Server EXSV001 -EdbFilePath “E:\Databases\RDB001\DB001.EDB” -LogFolderPath “E:\Databases\RDB001”

-Recovery – flags this as a recovery database, so it cannot be used for live mail
RDB001 – the name of the Recovery Database
EXSV001 – the name of your Exchange Server
-EdbFilePath – full path to the restored EDB, including the filename
-LogFolderPath – folder holding the transaction logs linked to the recovery database

Step 3 – Restart the Information Store and mount the database

Restart-Service MSExchangeIS
Mount-Database RDB001

Step 4 – Confirm the mailbox is actually in there

Get-MailboxStatistics -Database RDB001 | Format-Table DisplayName,MailboxGUID,TotalItemSize -AutoSize

If the mailbox you need is not listed, the backup predates its creation or postdates its deletion. Go back and pick a different restore point rather than working through the remaining steps.

Step 5 – Restore the mailbox data to a live target

New-MailboxRestoreRequest -SourceDatabase RDB001 -SourceStoreMailbox “Aryna Sabalenka” -TargetMailbox [email protected] -TargetRootFolder “Recovered” -AllowLegacyDNMismatch

Use -TargetIsArchive in place of -TargetRootFolder if you would rather land the data in the target user’s archive mailbox – a good choice for large historical restores you do not want inflating the primary quota.

Step 6 – Track the request and clean up

Get-MailboxRestoreRequest | Get-MailboxRestoreRequestStatistics | Format-Table TargetAlias,Status,PercentComplete -AutoSize

Once it is done, clear the completed requests – Exchange keeps them indefinitely and they will clutter future queries:

Get-MailboxRestoreRequest -Status Completed | Remove-MailboxRestoreRequest

Finally, dismount and remove the RDB when you no longer need it:

Dismount-Database RDB001
Remove-MailboxDatabase RDB001

Option 3: Use an Exchange recovery tool

The RDB route works, but it assumes three things: a clean backup, enough disk space to restore a full database copy, and someone comfortable with Eseutil and the Exchange Management Shell. Take away any one of them and the manual process stalls – or worse, a mistyped Eseutil switch damages the file you were trying to save.

Dedicated Exchange recovery software reads the EDB file directly instead. You point the tool at the file, scan it, and it lists everything inside, deleted mailboxes included. From there you export the mailboxes you need straight to a live Exchange Server database, to Microsoft 365, or to PST. Widely used options include Stellar Repair for Exchange, WholeClear Exchange Recovery Software and Kernel for Exchange Server Recovery.

This is usually the faster path when:

Your last good backup is too old, corrupted, or missing entirely.
The database is in a dirty shutdown state that soft recovery cannot repair.
You need a handful of mailboxes, not a whole database, and do not want the RDB overhead.
The recovery has to happen today and nobody on the team lives in the Exchange Management Shell.

Whichever tool you choose, run it against a copy of the EDB file, never the original.

After recovery: the step most teams skip

Getting the mailbox back is only half the job. A mailbox that has been deleted, recreated or reconnected often comes back with loose ends – a recreated user object with a new LegacyExchangeDN, an address that was reassigned to a shared mailbox, forwarding rules nobody remembers setting, or a send-on-behalf permission that quietly survived offboarding.

Those gaps matter beyond mail flow. An address that has been deleted and recreated is an attractive target: attackers spoof exactly these addresses, knowing recipients still recognise the name and rarely question it. If your domain has no enforced authentication policy, a spoofed message from a “recovered” address reaches inboxes looking entirely legitimate.

After any mailbox recovery, confirm the following:

SPF still lists every service that sends on your behalf, including anything added during the recovery. Run the domain through an SPF record lookup and check the record still resolves within the 10-lookup limit.
DKIM signing is intact on every sending source for the domain.
DMARC is at p=quarantine or p=reject, so unauthenticated mail claiming to be from your domain is acted on rather than delivered. If you are not sure where your domain sits, check your DMARC record and read up on what each DMARC policy actually enforces.
Your DMARC aggregate reports show no unexpected sending source that appeared around the time of the incident.

Mailbox recovery and domain authentication solve two halves of the same problem: making sure the mail your organisation depends on is both there and trusted. If one is on your plate this week, the other is worth the same half hour.

Conclusion

Exchange mailbox recovery comes down to timing. Inside the 30-day retention window, a deleted mailbox is simply a disconnected mailbox – reconnect it through the EAC or Connect-Mailbox, or merge its contents into a live mailbox with New-MailboxRestoreRequest, and you are done in minutes. Once retention expires, the mailbox is purged and you need a backup restored into a Recovery Database, with the database confirmed in a clean shutdown state before it will mount. Where no usable backup exists, an Exchange recovery tool reading the EDB file directly is the practical fallback.

Extend mailbox retention before you need it, test that your backups actually restore to an RDB, and keep domain authentication enforced so a recovered address cannot be impersonated while you are busy putting it back.

Frequently asked questions

How long can you recover a deleted mailbox in Exchange Server?

By default, 30 days – the mailbox retention period set on the mailbox database. During that time the mailbox is kept as a disconnected mailbox and can be reconnected or restored. You can change it with Set-MailboxDatabase -MailboxRetention, but only in advance; raising it will not bring back a mailbox that has already been purged.

Can you recover a permanently deleted Exchange mailbox without a backup?

Not through native Exchange tools. Once retention expires, the mailbox is removed from the database and no cmdlet will find it. If the EDB file still exists, an Exchange recovery tool can often extract the mailbox from it directly.

What is a Recovery Database in Exchange?

A special mailbox database type used to mount a restored copy of a database so you can extract mailboxes and items from it. It runs alongside your production database without affecting it, and it cannot be used to send or receive live mail.

Why will my Recovery Database not mount?

Almost always because the database is in a Dirty Shutdown state. Run Eseutil /mh to confirm, then Eseutil /R with the correct log prefix and paths to replay the logs. Re-check with Eseutil /mh – it must report Clean Shutdown before Mount-Database will succeed.

How do you recover a deleted mailbox in Exchange Online?

Soft-deleted Microsoft 365 mailboxes are recoverable for 30 days. Restore the user in the Microsoft 365 admin center under Users → Deleted users, or run Undo-SoftDeletedMailbox in Exchange Online PowerShell. After 30 days the mailbox is permanently removed and cannot be restored by Microsoft.

Does restoring a mailbox restore its permissions and rules?

Not reliably. Mailbox contents restore, but delegate permissions, send-as rights, forwarding rules and the LegacyExchangeDN frequently need to be reapplied by hand – especially when the mailbox is attached to a newly created Active Directory account. Audit them after every recovery.

About
Latest Posts

Ahona Rudra

Domain & Email Security Expert at PowerDMARC

Ahona is the Marketing Manager at PowerDMARC, with 5+ years of experience in writing about cybersecurity topics, specializing in domain and email security. Ahona holds a post-graduation degree in Journalism and Communications, solidifying her career in the security sector since 2019.

Exchange Mailbox Recovery: How to Recover Deleted Mailboxes in Exchange Server