Documentation correction for the separate free GMC catalogue plugin; mail transport is unchanged.<\/p>","1.0.2":"
The test-send limiter now remains effective when several admin requests arrive\nat the same time.<\/p>","1.0.1":"
Important delivery fix: the From address is no longer rewritten when the plugin\nis not actually sending through SMTP.<\/p>","1.0.0":"
First release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.3"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Settings -> SMTP Transport: the account fields, the write-only password\nfield, and the test-send form."}},"plugin_section":[],"plugin_tags":[17561,267,450,6932,6696],"plugin_category":[41],"plugin_contributors":[277384],"plugin_business_model":[],"class_list":["post-363065","plugin","type-plugin","status-publish","hentry","plugin_tags-deliverability","plugin_tags-email","plugin_tags-mail","plugin_tags-phpmailer","plugin_tags-smtp","plugin_category-communication","plugin_contributors-gmcfuerte","plugin_committers-gmcfuerte"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/gmcfuerte-smtp-transport.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
WordPress sends password resets, order confirmations and form notifications with\nwhatever the server hands it. On most hosting that means unauthenticated mail\nfrom an address the domain never authorised, which spam filters quietly discard.<\/p>\n\n
Gmcfuerte SMTP Transport points the standard It is deliberately small: one settings screen, one test button, no dashboard\nwidgets, no onboarding wizard.<\/p>\n\n What makes this one different<\/strong><\/p>\n\n Most SMTP plugins stop at configuring PHPMailer. This one also protects the\nfailure path: if a migration, salt rotation or removed environment secret makes\nthe saved credential unusable, it stops rewriting the From address instead of\nletting fallback mail impersonate the SMTP domain and fail SPF or DKIM. Its test\nsend reports the mail server's real refusal and whether SMTP was actually used;\nthe password is write-only and may stay entirely outside the database. There is\nno telemetry, provider account or remote dashboard.<\/p>\n\n What it does<\/strong><\/p>\n\n External services<\/strong><\/p>\n\n None. This plugin contacts no service of its own: not on activation, not on a\nschedule, not ever. The only outbound connection it makes is to the SMTP host\nyou type into the settings screen, when WordPress sends a message.<\/p>\n\n Separate GMC catalogue edition<\/strong><\/p>\n\n GMC SMTP Mailer, available free from fuerteventuratv.net, includes a mail log (per-recipient delivery\noutcome, the real SMTP error, retention, resend, CSV export, a persistent\nfailure alert), the matching GDPR export\/erase handlers and an admin REST API.\nIt has its own slug and GMC-hosted update channel. This plugin is complete without it, and nothing\nhere is disabled or time-limited.<\/p>\n\n\n From whoever runs the mailbox: your hosting control panel for a mailbox on your\nown domain, or the SMTP credentials page of your transactional mail provider.\nThis plugin does not create accounts and has no provider of its own.<\/p><\/dd>\n It means WordPress accepted the message but your SMTP account was not used,\nbecause the settings are incomplete. The mail went out through the server\ndefault transport, which is exactly the situation this plugin exists to fix.\nFill in host, username and password, save, and test again.<\/p><\/dd>\n No. It is encrypted with AES-256-GCM before it is written, using a key derived\nfrom this site own authentication salt. The field is write-only: it always\nrenders empty, and submitting it blank keeps the stored value. If you would\nrather keep the secret out of the database entirely, define\n GMCFUERTE_SMTP_PASSWORD in Yes. It configures the core No. SMTP Transport keeps no record of your mail. The separate GMC SMTP Mailer\nplugin provides logging and is available free from the GMC catalogue.<\/p><\/dd>\n The password is encrypted with a key derived from this site own salts, so\nchanging them \u2014 a migration, a clone, or Yes, in the sense that two plugins configuring the same mailer will fight over\nit. Use one.<\/p><\/dd>\n\n<\/dl>\n\n\nwp_mail()<\/code> pipeline at an SMTP\naccount you control, so messages leave authenticated and signed by the provider\nyou already pay for.<\/p>\n\n\n
wp_mail()<\/code> through your SMTP host, with STARTTLS, SSL\/TLS, or no\nencryption when a local relay needs it (and \"none\" really means none: the\nautomatic STARTTLS upgrade is switched off, instead of silently overriding\nthe choice you made).<\/li>\nGMCFUERTE_SMTP_PASSWORD<\/code> constant in wp-config.php<\/code> instead, for\nsites that keep credentials out of the database entirely. When it is defined,\nthe settings field says so and is ignored.<\/li>\n\n
gmcfuerte-smtp-transport<\/code>\nfolder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Where do I get the SMTP details?<\/h3><\/dt>\n
The test says the message was sent, but with a warning. What does that mean?<\/h3><\/dt>\n
Is my password stored in plain text?<\/h3><\/dt>\n
wp-config.php<\/code>.<\/p><\/dd>\nDoes it work with the block editor, WooCommerce, contact form plugins?<\/h3><\/dt>\n
wp_mail()<\/code> pipeline, so anything that sends mail\nthe WordPress way is covered without any integration.<\/p><\/dd>\nDoes it log the messages it sends?<\/h3><\/dt>\n
I moved the site and mail stopped arriving. What happened?<\/h3><\/dt>\n
wp config shuffle-salts<\/code> \u2014 leaves a\nstored value this install can no longer read. The settings screen says so, and\nsending falls back to the server default transport with the From address left\nalone. Type the SMTP password again and save.<\/p><\/dd>\nWill it conflict with another SMTP plugin?<\/h3><\/dt>\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
GMCFUERTE_SMTP_PASSWORD<\/code> constant was removed\nfrom wp-config.php<\/code> \u2014 WordPress fell back to the server's default transport\nand still stamped your SMTP domain on the message. SPF and DKIM then fail and\nthe mail is filed as spam. The From address is now left alone unless SMTP is\nreally carrying the message.<\/li>\nload_plugin_textdomain()<\/code> call is now\ndocumented in the source rather than merely absent. WordPress loads the\ntranslations for a directory-hosted plugin itself, and the call has been\ndiscouraged since WordPress 4.6.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n