LH.pl or dhosting.pl for Recovering a Mailbox and Switching a WordPress Site’s Email

Recover the message before changing the route

A small organization hosts its WordPress site and uses a contact mailbox on its domain. A message was deleted before a migration. The team must recover it, retain messages received since its deletion and then change the receiving service. Nameservers stay with the current manager. The first objective is to find the message in a usable restore point. The second is to get everything that may have arrived through the old or new route into the target mailbox.

Record the exact address, folder and reception period of the lost message. Check whether it is still in the trash, an archive folder, webmail or a local copy. An email client using POP without a server copy may have removed the only instance from the server. This situation requires checking the workstation or its archives before relying on a hosting provider’s restore point.

Before any restoration, export the active mailbox to protected storage or make an independent copy. Record folders, the latest messages and a sample attachment. If the provider documents restoration without specifying what happens to the current mailbox, confirm the recovery method and destination. The visible restore-point date does not answer this question.

Separate mailbox contents from DNS delivery

Copying the mailbox concerns historical content and folders. MX records indicate where sending servers deliver new messages. Changing MX records copies no history. The operation therefore requires two forms of evidence. The expected folders must be found on the target, and recent email still reaching the old destination must not be left forgotten there.

The website and email use separate records. Website resolution must remain stable during this work. Nevertheless, check that MX targets do not use an address that the site migration would change. Also record aliases, forwarding rules and addresses used by WordPress. The form may depend on a separate outgoing relay, even when its notifications arrive in the mailbox the team is moving.

For reception, aim to verify the target mailbox before publishing its MX record. If the provider only allows activation after MX changes, agree on a verification method or cutover sequence before opening the new route. Prepare independent access to both services to read messages during the transition. If you lack permissions for the authoritative zone, record the values to apply and identify the person who can publish them. The exercise simulates two DNS views and two mailboxes with demonstration messages.

LH.pl Kiwi and the restore point requested from support

The LH.pl guide to deleted messages requires instructions sent from the account holder’s authorized address. They must specify the mailbox’s full address and the desired restore-point date. LH.pl presents this restoration as free. The guide applies to a mailbox served by LH.pl and used through webmail or IMAP, excluding cases where POP removed messages from the server without keeping a copy. Check which service actually hosted the mailbox on the required date. A future migration to LH.pl does not provide access to the previous operator’s archives.

The deleted-email guide advertises nightly email copies retained for thirty days. Another procedure describes web-file and database copies, also retained for thirty days. Email restoration goes through support. Check that the required point exists for this mailbox. The guide specifies neither response time nor how restoration merges with existing messages. Ask support which points are available, whether a message or folder can be isolated and where restoration will be delivered. Retain the recent copy before asking support to act on the active mailbox.

Kiwi displays 10 GB for the plan, SSH, a WordPress installer and Let’s Encrypt. Check the allocation between site and mailbox, as well as the space needed if two copies coexist. The pricing page advertises hosting in Poland at ATMAN. The restoration guide and channels consulted are in Polish. Webmail allows its interface language to be changed. Separately confirm the language available for technical assistance if the team does not work in Polish.

dhosting.pl Elastyczny and the dPanel command

The dhosting.pl guide opens the Poczta e-mail section in dPanel, then the mailbox backups and the Przywróć button beside the selected point. The official email-plan comparison advertises up to seven days of backups for Elastyczny Web Hosting. The longer Poczta Biznesowa retention applies to a separate plan. Check the point visible for the mailbox and its date before launching the command. The guide describes the panel action without specifying whether it merges the copy with the current mailbox, overwrites certain items or can target a temporary folder.

The pricing page displays an initial 50 GB and expandable space for the site, databases and email. The email table indicates no advertised limit on mailbox count and a sending cap of 24,000 messages per day per mailbox on Elastyczny. A sending cap establishes neither the volume actually available for importing history nor antispam rules. Resource-expansion costs and limits selected in dPanel must be checked if the copy exceeds the starting capacity.

The plan advertises WordPress optimization and Let’s Encrypt. The help pages locate hosting servers in the ATMAN facility in Poland. This does not detail the location of all email copies. The dPanel and restoration documents used are in Polish. Email contact is advertised around the clock, with separate telephone hours. This availability is not a restoration deadline. French or English support is not established by these sources.

Compare annual cost and the data to retain

On November 10, 2026, LH.pl Kiwi displays 60 PLN excluding VAT for the first year and 249 PLN excluding VAT at standard renewal. The legacy PHP compatibility option displays 349 PLN excluding VAT at renewal. dhosting.pl Elastyczny displays 99 PLN excluding VAT for the first year and 399 PLN excluding VAT for the next. Two years at the recorded prices total 309 PLN excluding VAT at LH.pl and 498 PLN excluding VAT at dhosting.pl. These calculations separate hosting from domain, additional storage and any extension costs. An observed introductory price does not guarantee a future invoice amount.

As an example using Poland’s standard 23% VAT, Kiwi costs 73.80 PLN for the first year, then 306.27 PLN at the displayed standard rate. Elastyczny costs 121.77, then 490.77 PLN. Check the VAT actually applied to the quote. The bonus dhosting.pl displays for scaling is not deducted from the renewal price. Size the account for WordPress, the active mailbox, copied folders and the period during which both services coexist.

Also inventory mailbox rules, aliases, contacts, signatures and local archives. IMAP synchronizes message folders and may exclude client-specific items from the transfer. At LH.pl, a contact coordinates the incoming copy of messages present on the source server. The guide provides for the account holder or their contact to prepare pointing afterward. To retain nameservers, agree that the change affects only the necessary email entries. dhosting.pl advertises free assisted migration of up to thirty mailboxes on new accounts and also describes a self-service import. Clarify who copies messages, checks folders and repeats the final synchronization. The authoritative-zone manager retains control of MX records. The service contract and access must remain available while content is extracted. If copy location or access duration after cancellation matters, verify these points before deleting the old account.

Prepare MX and sending without moving nameservers

Prepare the list of mailboxes, aliases and forwarding rules to recreate. If the DNS zone remains with another provider, the dhosting.pl procedure calls for adding the domain in dPanel, setting MX records at the DNS manager, then activating email when the domain points correctly. Before changing production MX records, confirm whether support can prepare reception or offer a test on an acceptance-test domain. If you can neither verify the target nor agree on a cutover sequence with support, postpone the change. dhosting.pl help also asks users to contact support for DKIM with external delegation. For LH.pl, prepare the receiving zone and request the DKIM and DMARC values applicable to your external DNS.

MX specifies the receiving destination. SPF authorizes sending sources and DKIM signs outgoing messages for the domain. DMARC relies on alignment of at least one valid mechanism with the domain visible in the sender address. During coexistence, inventory the senders actually used, including WordPress notifications. Keep a single SPF policy at the relevant name. Check the selectors actually used by the platforms and retain the DMARC policy intended by the domain administrator.

If reducing TTL, do so early enough for old responses to expire. During cutover, keep both mailboxes accessible and check the web record separately. Avoid adding the old server as an improvised backup in the new MX list. This can maintain reception at two destinations beyond the expected cache period. Coexistence of the two services during migration here depends on their availability and the team’s checks.

• In the current DNS zone, record MX entries and their TTL, as well as web records to retain. Query the authoritative zone before cutover, then compare its responses with those of an external resolver.
• Assign the initial copy, MX publication, reception test and final reconciliation to named people.

Copy before cutover and reconcile afterward

When the target mailbox is ready, make an initial copy and retain the archive of active content. At dhosting.pl, self-service import starts from the target mailbox under Poczta e-mail, then Akcje and Import wiadomości. The panel requests the source mail server and mailbox credentials. Separately check who will handle messages arriving after this first copy. Check folders, dates and representative attachments. If local archives contain messages absent from the server, import them separately. Keep a note of renamed folders and configuration items that must be recreated.

Recover the lost message from the identified point. If the operator offers a separate destination, compare the message and its attachment before adding it to the target mailbox. If restoration is only possible on the active mailbox, stop while its effect on recent messages remains unknown and the independent copy has not been verified. A Message-ID helps reconciliation but may be missing or shared. Compare contents, attachments and folders if in doubt. Do not automatically delete a differing copy.

After changing MX records, record arrivals on both accounts. In a real operation, check reception from authorized test accounts and available logs. Also check WordPress SMTP output, test headers and reception in the expected mailbox. Make a final copy of messages still received at the source. Keep it available until routes, traffic and checks allow the transition to be closed.

Replay restoration and both DNS views offline

The exercise loads six fictional EML messages. The backup contains a deleted message and history from the Sent folder. The current mailbox contains the history and a message received since the backup. A full restoration would erase this latter message in the simulated scenario. The script copies the current state, then adds only the missing message. It decodes the MIME attachment and checks its content. A differing file sharing the same identifier triggers a stop without modifying the target mailbox.

The first fictional sender cached the old MX with a TTL of 300 seconds. The second resolves after cutover and receives the new MX. At 90 seconds, a message arrives in each mailbox while the web address remains stable. The script also shows that closing the source at 100 seconds prevents delivery through the still-cached route. It does not model the sending server’s retry delays or a guaranteed public propagation deadline.

After the fictional cache expires, the final synchronization retains five sample messages, including those received through each route. Running it again under the same conditions creates no duplicate. The ZIP file passes fourteen checks on this simulation. EML files are actually read, but delivery and DNS are in-memory states. No email service is used. This exercise checks the decision to keep the source open, then verify both sides before closing it.

• Download the ZIP exercise under “Further reading”, extract it into a separate folder, then run python exercice.py.
• Compare the 14 checks with attendu.json. Identify delivery refused after closing the source, then the two messages that arrived through different MX records and are present in the final mailbox.

Stop or roll back without forgetting the target mailbox

Postpone cutover if the target does not receive email, the recent export cannot be reread, restoration scope remains unknown or the sought message is absent from the selected point. A WordPress error may have a cause other than MX, such as an SMTP relay or credentials. Check the site and mailbox separately. A displayed page and successful webmail login do not prove end-to-end delivery.

If you need to restore the old MX, first check that the old service still accepts recipients and keep the new mailbox accessible. Back up both sides. Messages received only at the target must be recovered before closing it, and cached DNS responses may still direct sending there. Restore the DNS values retained at the outset and check actual responses, logs and folders. A DNS rollback does not put historical content back in place.

Kiwi suits a team willing to use the authorized address and support, with a volume compatible with its initial 10 GB. Elastyczny suits a team that prioritizes acting in dPanel and has a point within the documented period. In both cases, base the choice on the message being present in a usable restore point and on the reconciliation result. Price or retention duration alone is insufficient to decide when to switch.

Further reading

• Read the LH.pl profile
• Read the dhosting.pl profile
• Check the sending of WordPress password reset emails
• Download the email recovery and MX switchover mockup (ZIP)