Recognyze.AI vs WP SMTP Mailer – SMTP7

Recognyze.AI is a WordPress plugin for publishers who want to protect content, monetize AI usage, and control how agents access their site. Use the dashboard to sign posts in bulk, connect securely to the Recognyze Publisher API, and monitor signed and unsigned access-including Bot Wall blocks and optional Markdown for AI agents. Key Features Content Protection: Cryptographic signatures that verify authenticity and register content with Recognyze Post Management Dashboard: Overview of recognized, pending, and bulk sign/sync actions AutoRecognyze: Optionally recognize new Posts and Pages automatically on publish (Essentials settings) API Integration: Connect with your Recognyze account; API keys are encrypted at rest (AES-256-GCM when OpenSSL is available) API Key Rotation: Automatic rotation before expiry (14-day buffer), manual “Rotate now”, and visible key ID/expiration in Essentials Bot Wall (Agents & Bot Access): Rules-driven blocking for AI crawlers with per-bot and per-category controls (HTML/Markdown), powered by portal Bot Rules AI Bot Detection: Track signed and unsigned visits, including blocked Bot Wall requests and bot attribution metadata Access Logs: Logging for signed content access with event-based export and retention cleanup Unsigned Access Logs: Track unsigned content access and bot-like traffic separately Bulk Operations: Sign or synchronize many posts at once Encrypted Storage: API keys stored encrypted; Basic Auth credentials used only once to obtain a key and are never saved Export Functionality: Export access logs to Recognyze when batch size or time-based conditions are met Markdown for Agents: Serve content as Markdown via .md URLs or Accept: text/markdown, with Recognyze frontmatter, verify URLs, usage fees in points, and token estimates Use Cases Content creators who want to protect their intellectual property Publishers who want to monetize AI usage of their content Bloggers who want to track which AI systems access their content News organizations managing content licensing for AI training Any WordPress site owner concerned about AI crawler access Technical Features Supports multiple post types (posts, pages, and configurable types) RESTful Publisher API integration with optional dev-mode custom endpoint URL API key lifecycle (includes/api-key-rotation.php): metadata sync via GET /account/publisher/api-keys/current/, scheduled and manual PUT rotate Bot Rules cache with daily refresh from the Recognyze portal Optional softmax IP + User-Agent attribution for Bot Wall when portal ipVerification data is available Comprehensive access logging with event-based export and cleanup Scheduled tasks for log cleanup, export, API key metadata sync, and Bot Rules refresh Developer-friendly with hooks and filters (e.g. wprc_api_key_rotation_buffer_days) WordPress Coding Standards compliant Markdown for Agents (includes/markdown-for-agents.php): Content negotiation for text/markdown, YAML frontmatter with Recognyze id, verify_url, usage_fee (points), content_length, markdown_tokens; optional signed-only mode; Link header for alternate type Token estimator (includes/token-estimator.php): In-plugin token count for Markdown body (word/char heuristic), exposed as X-Markdown-Tokens header and in frontmatter Privacy & Data This plugin collects access logs that may include IP addresses, user agents, and timestamps. These logs are stored in your WordPress database and automatically exported and cleaned up based on export conditions (batch size or time interval). See the Privacy Policy section in Settings for more details. Support & Documentation For detailed documentation, API information, and support, visit Recognyze.AI Privacy Policy Recognyze.AI collects and stores the following data: Access Logs: When visitors access your signed content, the plugin may log: * IP address * User agent * Timestamp * Referrer URL * Post ID accessed Unsigned / Bot Wall logs: When enabled, the plugin may also log unsigned visits and Bot Wall blocks (including bot identity metadata where configured). API key metadata: Key ID, name, status, and expiration date (not the secret) are stored locally to support rotation scheduling. Storage: All data is stored in your WordPress database on your server. Retention: Logs are automatically exported and cleaned up from the database based on export conditions (batch size reached or 120-minute fallback interval). Exported logs are removed immediately after successful export. Export: If configured, access logs may be exported to external systems via API. User Rights: Site administrators can manually delete logs at any time from the Access Logs pages. Third Party Services: When you sign content, metadata is sent to the Recognyze.AI API. See the Recognyze.AI Privacy Policy for details on how this data is handled. Support For support, documentation, and feature requests: Website: https://recognyze.ai Documentation: https://www.recognyze.ai/publishers/wordpress/ Support: https://www.recognyze.ai/contact-us/

WP SMTP Mailer – SMTP7 allows you to configure and send all outgoing emails via a SMTP server (It works like the postman). This will prevent your emails from going into the junk/spam folder of the recipients. Go to Settings > SMTP7 and configure SMTP then post SMTP credentials. You can set the following options: Specify the from name and email address for outgoing email. Choose to send mail by SMTP or PHP’s mail() function. Specify an SMTP host (defaults to localhost). Specify an SMTP port (defaults to 25). Choose SSL / TLS encryption (not the same as STARTTLS). Choose to use SMTP authentication or not (defaults to not). Specify an SMTP username and password. SMTP Testing server : MailMug.net SMTP Testing : https://youtu.be/fAXevTJ0r8I Support : http://www.ciphercoin.com/contact/ Contact Form 7 Not Sending Emails WordPress SMTP Mailer Features Send email using a SMTP sever. You can use Gmail, Yahoo, Hotmail’s SMTP server if you have an account with them. Securely deliver emails to your recipients. Username and password encryption List of SMTP Servers (Outgoing) Gmail :- Host: smtp.gmail.com – Secure(SSL) – Port(465) Gmail :- Host: smtp.gmail.com – Secure(TLS) – Port(587) Outlook.com :- Host: smtp-mail.outlook.com – Secure(TLS) – Port(587) Office365.com :- Host: smtp.office365.com – Secure(TLS) – Port(587) Hotmail.com :- Host: smtp.live.com – Secure(TLS) – Port(587) Yahoo Mail :- Host: smtp.mail.yahoo.com – Secure(TLS) – Port(587) Yahoo Mail :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Yahoo Mail Deutschland :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Yahoo Mail Plus :- Host: plus.smtp.mail.yahoo.com – Secure(SSL) – Port(465) AOL.com :- Host: smtp.aol.com – Secure(TLS) – Port(587) AT&T :- Host: smtp.att.yahoo.com – Secure(SSL) – Port(465) NTL @ntlworld.com :- Host: smtp.ntlworld.com – Secure(SSL) – Port(465) BT Connect :- Host: smtp.btconnect.com – No-Encryption – Port(25) BT Openworld :- Host: mail.btopenworld.com – No-Encryption – Port(25) BT Internet :- Host: mail.btinternet.com – No-Encryption – Port(25) Orange :- Host: smtp.orange.net – No-Encryption – Port(25) Orange UK :- Host: smtp.orange.co.uk – No-Encryption – Port(25) Wanadoo UK :- Host: smtp.wanadoo.co.uk – No-Encryption – Port(25) Comcast :- Host: smtp.comcast.net – No-Encryption – Port(587) Yahoo Mail AU/NZ :- Host: smtp.mail.yahoo.com.au – Secure(SSL) – Port(465) O2 Deutschland :- Host: mail.o2online.de – No-Encryption – Port(25) zoho Mail :- Host: smtp.zoho.com – Secure(SSL) – Port(465) T-Online Deutschland :- Host: securesmtp.t-online.de – Secure(TLS) – Port(587) 1&1 (1and1) :- Host: smtp.1and1.com – Secure(TLS) – Port(587) 1&1 Deutschland :- Host: smtp.1und1.de – Secure(TLS) – Port(587) Verizon :- Host: outgoing.verizon.net – Secure (SSL) – Port(465) Verizon (Yahoo hosted) :- Host: outgoing.yahoo.verizon.net – No-Encryption – Port(587) Mail.com :- Host: smtp.mail.com – Secure(SSL) – Port(465) GMX.com :- Host: smtp.gmx.com – Secure(SSL) – Port(465) Yahoo Mail UK :- Host: smtp.mail.yahoo.co.uk – Secure(SSL) – Port(465) Airmail :- Host: smtp.airmail.net – Secure(SSL) – Port(465) Bluewin.ch :- Host: smtpauth.bluewin.ch – Secure(SSL) – Port(465) Eartlink.net :- Host: smtpauth.earthlink.net – Secure(SSL) – Port(587) iCloud Mail :- Host: smtp.mail.me.com – Secure(SSL) – Port(587) Rocketmail :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Rogers :- Host: smtp.broadband.rogers.com – Secure(SSL) – Port(465) Ameritech.net :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Pacbell :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Swbell :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Bellsouth :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Flash :- Host:- smtp.mail.att.net – Secure(SSL) – Port(465) Note: These SMTP Ports and Settings may be different depending upon your Host Provider. Please contact your Web Server Host for correct details.