Activate and manage a license
Activate a paid WordPress site, release an old activation, and understand validation.
Activate a paid PressedMail installation on each WordPress site that uses it. The license associates a site URL with the plan's allowance. Free does not require a paid license key.
Activate the site
- Sign in to PressedMail and open Your Plan.
- Copy the license key for the intended plan.
- In WordPress, open PressedMail. An unlicensed paid build shows its activation screen.
- Paste the key into License Key and select Activate License. You can also manage it under Settings > Licensing.
- Confirm the active status and current site details.
- Open Sites in your website account and check the registered domain.
Use the site's actual URL. A migrated domain or staging copy can need its own activation. Do not assume a copied database transfers the old activation to a new hostname.
Move or release an activation
Deactivate the old site through Settings > Licensing or the website's Sites page, then activate the replacement site with the valid key. Check the remaining site allowance before adding another installation.
Regenerating a key is different from freeing one site. The account's key-regeneration action invalidates the old key and requires affected sites to activate again. Use it only when you intend that broader change.
What validation sends
Activation and validation requests can include the license key, site URL and identifiers, product and plugin version, WordPress version, PHP version, and technical compatibility information.
They do not include mailbox bodies, attachments, email passwords, or OAuth tokens. See Where your mail and data live and the Privacy Policy.
The site needs outbound HTTPS to curb.software. A valid purchase cannot activate if the WordPress server cannot reach the licensing service.
Activation or updates fail
Check the key copied from the current account, available site slots, registered domain, and outbound HTTPS. Keep the error text without including the key.
For paid update access and integrity warnings, use Installation, licensing, and updates. Normal file replacement during an update should retain the saved key; deleting plugin data is not a licensing repair.