replyto/readme.txt

=== Reply-To for WP_Mail ===
Contributors: robotstxt, javiercasares
Tags: email, reply-to, mail, smtp
Requires at least: 4.7
Tested up to: 7.1
Stable tag: 2.0.3
Requires PHP: 5.6
Version: 2.0.3
License: GPL-3.0-or-later
License URI: https://www.gnu.org/licenses/gpl-3.0.txt

Configure different "Reply-To" addresses by email context with validation, modern tabbed UI, and automatic migration.

== Description ==

The Reply-To for WP_Mail plugin allows you to easily manage the "Reply-To" header for all emails sent from your WordPress site. With this plugin, you can specify a custom email address that recipients will use when replying to your site's emails, ensuring that responses go to the correct inbox.

Configure a different Reply-To address for each type of email: password resets, comment notifications, user registrations, system updates, and WooCommerce orders.

Two developer filters are available for advanced customization:

* `wp_mail_replyto_context` — override the detected email context.
* `wp_mail_replyto_header` — override or suppress the Reply-To header for a specific email.

== Installation ==

= Automatic download =

Visit the plugin section in your WordPress admin, search for "Reply-To for WP Mail"; download and install the plugin.

= Manual download =

Extract the contents of the ZIP and upload the contents to the `/wp-content/plugins/replyto/` directory. Once uploaded, it will appear in your plugin list.

== Frequently Asked Questions ==

= Will my existing Reply-To setting be preserved after upgrading from v1? =

Yes. The plugin automatically migrates your existing email address and name to the Default context on the first page load after upgrade.

= What happens if I configure a context but leave it disabled? =

Disabled contexts fall back to the Default Reply-To. If no Default is configured, no Reply-To header is added.

= Does this plugin work with WooCommerce? =

Yes. When WooCommerce is active, a dedicated WooCommerce tab appears so you can route order emails to a separate reply address.

= Does this plugin work on WordPress Multisite? =

Yes. Each site in a Multisite network maintains its own configuration. On uninstall, data is removed from all sites.

== Compatibility ==

* WordPress: 4.7 - 7.1
* PHP: 5.6 - 8.5

== Changelog ==

= 2.0.3 =

_Release date: 2026-08-18_

**Highlights**

* Housekeeping release: branding URLs moved to robotstxt.software and declared WordPress support floor set to 4.7.

**Changed**

* Minimum WordPress version raised from 3.6 to 4.7 (real functional floor: register_setting() with array arguments requires WordPress 4.7).
* Developer URL updated to https://www.robotstxt.software/ and plugin home page added (https://www.robotstxt.software/plugins/replyto/).
* Full changelog now hosted at https://www.robotstxt.software/plugins/replyto/changelog/.
* Development tooling updated (PHPCS, WPCS, PHPStan, PHPUnit).

**Added**

* bin/preflight.sh automated pre-deploy verification script.
* WordPress floor verification (wp-compat) integrated into PHPStan analysis.

**Compatibility**

* WordPress: 4.7 - 7.1
* PHP: 5.6 - 8.5

**Tests**

* PHP Coding Standards: 3.13.6
* WordPress Coding Standards: 3.4.1
* PHPStan: 2.2.8 (level 9)
* PHPUnit: 9.6.36

= 2.0.2 =

_Release date: 2026-06-05_

**Highlights**

* Translations added for Spanish (Spain) and Catalan.
* WordPress minimum version corrected to 3.6 based on actual function usage (wp-compat analysis).

**Changed**

* Minimum WordPress version updated from 4.1 to 3.6.
* Tested up to WordPress 7.1.
* POT file regenerated via WP-CLI i18n.

**Added**

* Spanish (Spain) translation (es_ES).
* Catalan translation (ca).

**Compatibility**

* WordPress: 3.6 - 7.1
* PHP: 5.6 - 8.5

**Tests**

* PHP Coding Standards: 3.13.5
* WordPress Coding Standards: 3.3.0
* PHPStan: 2.2.2 (level 9)
* PHPUnit: 9.6.34

= 2.0.1 =

_Release date: 2026-06-05_

**Highlights**

* Major bugfix release addressing three critical issues found during pre-deploy audit.

**Fixed**

* Context cache not resetting between emails in the same PHP process.
* Duplicate Reply-To header injected when an existing Reply-To was present.
* Migration hook only running on admin_init — missed WP-CLI activations.
* RFC 5322 display name quoting now applied only when the name contains special characters.

**Added**

* Developer filters: wp_mail_replyto_context and wp_mail_replyto_header.
* load_plugin_textdomain() for translation support on WordPress < 4.6.

**Security**

* sanitize_callback added to legacy option registrations.

**Compatibility**

* WordPress: 4.1 - 6.9
* PHP: 5.6 - 8.5

**Tests**

* PHP Coding Standards: 3.13.5
* WordPress Coding Standards: 3.3.0
* PHPStan: 2.2.2 (level 9)
* PHPUnit: 9.6.34

= Previous versions =

If you want to see the full changelog, visit the [changelog](https://www.robotstxt.software/plugins/replyto/changelog/) page.

== Upgrade Notice ==

= 2.0.3 =
Housekeeping release: branding URLs moved to robotstxt.software. Minimum WordPress version is now 4.7.

= 2.0.2 =
Translations added for Spanish (Spain) and Catalan. WordPress minimum corrected to 3.6. Upgrade recommended.

= 2.0.1 =
Bugfix release. Fixes context isolation between emails, duplicate Reply-To headers, and migration on WP-CLI. Upgrade recommended.

== Compliance ==

This plugin adheres to the following security measures and review protocols for each version:

* [WordPress Plugin Handbook](https://developer.wordpress.org/plugins/)
* [WordPress Plugin Security](https://developer.wordpress.org/plugins/wordpress-org/plugin-security/)
* [WordPress APIs Security](https://developer.wordpress.org/apis/security/)
* [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards)
* [Plugin Check (PCP)](https://wordpress.org/plugins/plugin-check/)