Email workflow integrations and SDKs

Download shared WordPress and WooCommerce ZIP

1. Install

Run these commands from the WordPress directory with WP-CLI available, or upload the downloaded ZIP through Plugins > Add New > Upload Plugin and activate it. Open Settings > SendRepute. Configure and activate each site separately on multisite. Keep a supported WordPress/PHP combination; a minimum version is not a recommendation to run end-of-life software.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-wp.zip
wp plugin install ./sendrepute-wp.zip --activate

Alternative: install from public source

Use this source route instead of the website download instructions above. The repository README explains the remaining activation and configuration steps; building a ZIP alone does not install a plugin. For Python, the second command adds optional Django support. Keep credentials in server secrets and review the security notes before enabling paid features. Only Node is on npm; a public GitHub repository does not imply WordPress.org, n8n Cloud, Packagist or PyPI publication.

git clone https://github.com/sendrepute/sendrepute-wordpress.git
cd sendrepute-wordpress
python3 package.py

2. Configure securely

Create a server-side customer token with classify, account:read and catalog:read scopes, expiry and spend caps. Enter it in settings or load SENDREPUTE_API_TOKEN from your server secret store as shown. Stored tokens use authenticated encryption with WordPress salts and OpenSSL; re-enter them after salt rotation. Run the non-paid connection check, review classification pricing, then explicitly enable automatic analysis. Set advisory/blocking mode, threshold and independent fail-open/fail-closed policy.

// wp-config.php — optional server-secret alternative to settings storage.
$sendreputeToken = getenv('SENDREPUTE_API_TOKEN');
if (is_string($sendreputeToken) && $sendreputeToken !== '') {
    define('SENDREPUTE_API_TOKEN', $sendreputeToken);
}

3. Use it deliberately

The function below uses normal wp_mail and sends only when your application calls it. With paid analysis enabled, the plugin analyzes at pre_wp_mail and then permits or blocks the existing transport. Supply your own authorized recipient; test against a non-relaying local mail sink first. A false result means the caller must handle the rejected send—it is not queued.

// Call deliberately: this sends through your existing WordPress transport.
function sendrepute_reviewed_message($recipient) {
    return wp_mail(
        $recipient,
        'Your requested account summary',
        'Here is the account summary you requested.'
    );
}

What else can it do?

Settings also provides manual AI rewrite and template-generation actions with separate paid confirmation. Price display needs vip:read; rewrite needs rewrite; generation needs ai:generate, and VIP generation requires active VIP membership. Results are escaped, copy-only text: never automatically applied or sent. Existing tokens do not gain scopes automatically.

Results, failures and limits

Advisory allows delivery; blocking compares the finite spam probability to your threshold. API timeouts and failures follow the separate failure policy, not a spam label. Opaque local locks suppress repeated analysis for 24 hours; unknown network outcomes are not retried automatically. Sends themselves are not deduplicated. Installed update checks covered a tracked 0.1.0 ZIP upgraded to 0.2.0, administrator nonce rejection/save and the selected WooCommerce path. A separate 40-scenario matrix covered both plugin load orders with WP Mail SMTP and FluentSMTP, including To/Cc/Bcc, Reply-To, headers, attachments, SMTP rejection and policy outcomes. These exact tuples do not certify other CMS, SMTP plugin or provider versions. Hooks that bypass wp_mail and later transport changes remain outside coverage. Deactivation preserves settings; uninstall removes credentials even when retaining disabled settings. Remove a wp-config token yourself.

WooCommerce email adapter

0.2.0

Included in the same SendRepute 0.2.0 ZIP as the WordPress plugin; there is no separate WooCommerce add-on or download. It requires the plugin's WordPress 5.7+, PHP 7.4+ and OpenSSL baseline. The adapter was source-reviewed against WooCommerce 10.4.3, not certified across every WooCommerce or mail-extension version.

WooCommerce analysis has its own administrator switch and exact built-in email-type selections, all off by default. The global analysis and paid-consent controls must also be on. Unselected and extension-defined types bypass analysis. Every selected built-in customer_* type is protected and advisory-only: it may be analyzed but is never blocked. Selected multipart mail fails classification before any paid request; advisory or fail-open preserves delivery, while fail-closed blocks only non-protected mail.

1. Install

This is the same installable ZIP used by the WordPress guide. Install it once; do not install a second WooCommerce add-on. Activate SendRepute, then open Settings > SendRepute. Keep WordPress, WooCommerce, PHP and the real mail transport supported and updated.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-wp.zip
wp plugin install ./sendrepute-wp.zip --activate

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-wordpress.git
cd sendrepute-wordpress
python3 package.py

2. Configure securely

Use a scoped customer token from server secrets or the encrypted WordPress setting. First configure the shared non-paid connection check, current-price review, global paid consent, risk mode, threshold and failure policy. Then separately enable WooCommerce analysis and select only the built-in email types you have reviewed. Extension-defined types are never selected automatically.

// wp-config.php — keep the shared WordPress/WooCommerce token server-side.
$sendreputeToken = getenv('SENDREPUTE_API_TOKEN');
if (is_string($sendreputeToken) && $sendreputeToken !== '') {
    define('SENDREPUTE_API_TOKEN', $sendreputeToken);
}

3. Use it deliberately

Continue sending through WooCommerce normally. The adapter wraps the callback already chosen by WooCommerce and preserves its original arguments and transport; it does not provide a new send method. If another filter mutates callback arguments, ordinary mail is nested during that callback, or a custom callback never calls wp_mail, analysis is conservatively bypassed rather than falling into the general paid path. Test selected non-critical types with a non-relaying mail sink.

Results, failures and limits

Selected single-part mail follows the shared WordPress advisory, threshold and failure policies, except every customer_* type is protected and advisory-only. Protected customer mail always continues after a high-risk result, API failure or unsupported content. WooCommerce constructs multipart alternatives after pre_wp_mail, so selected multipart mail fails before any paid request instead of being partially classified; only selected non-protected mail can be refused by fail-closed. Callback context is removed after success, failure and nested sends.

Drupal mail backend

0.1.0

Requires Drupal 10.3+ or 11.x and PHP 8.1+. Install the ZIP as a module, grant administer sendrepute only to trusted administrators, configure a bounded non-address sender display name, and select exact module/key mail routes. Version 0.1.0 supports Drupal core php_mail only; it is a Mail backend, not a provider or replacement transport. Installed-site evidence covers exact Drupal 10.6.17 and 11.4.7 releases with PHP 8.4.10.

Paid consent and every route are off by default. Each exact route uses the fixed core php_mail delegate, advisory or block mode, an independent preserve or block failure policy, threshold, and deliberate critical-mail selection. Account and security mail remains deliverable unless that exact route explicitly allows critical blocking. The same php_mail instance formats and sends one scalar final body; multipart and attachment-bearing output are unsupported.

Download Drupal ZIP

1. Install

Run from the Drupal project root, or upload the ZIP with Drupal's module installer. The archive contains a sendrepute module root suitable for modules/contrib. Enable it, grant administer sendrepute only to trusted administrators, and open Configuration > System > SendRepute.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-drupal.zip
unzip sendrepute-drupal.zip -d modules/contrib
drush en sendrepute -y

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-drupal.git
cd sendrepute-drupal

2. Configure securely

Store a classify-scoped SENDREPUTE_API_TOKEN only in the web/PHP process environment. It is never accepted by the form or exported in Drupal configuration. In the form, enter a required sender display name of at most 320 bytes with no address, angle brackets or controls. Add one seven-field line per exact route as shown; delegate must be php_mail. Choose advisory/block mode, preserve/block failure policy, threshold, and critical yes/no. Begin with advisory, preserve and no.

export SENDREPUTE_API_TOKEN="replace-with-a-scoped-server-token"
# Enter a non-address sender display name in Configuration > System > SendRepute.
# One exact route in Configuration > System > SendRepute:
# contact|page_mail|php_mail|advisory|preserve|0.90|no

3. Use it deliberately

Keep calling Drupal's normal mail manager. For an opted-in route, sendrepute_mail calls core php_mail's format(), analyzes that final scalar body, applies policy, and then calls the same cached php_mail instance's mail(). Other delegate IDs are rejected. It does not use hook_mail_alter and does not rewrite the message.

Results, failures and limits

A validated success blocks only at or above the configured threshold in block mode. The complete nested classification result and billing response are validated before spamProbability can affect delivery. API, authentication, balance, rate-limit, malformed, multipart, attachment-indicator and size failures follow the independent route failure policy, except protected critical mail continues. The installed 10.6.17/11.4.7 matrix covered installation and in-place ZIP replacement while enabled, real administrator login, Form API CSRF rejection/save, plugin discovery, route opt-in, synthetic classification, critical-mail preservation and core php_mail through a local sink. Baseline source checks also cover immutable 10.3.0 and 11.0.0 archives; neither result certifies every later patch or contributed mailer. The configured display name, non-empty subject and length-framed body are sent; addresses, recipients, headers, parameters and attachments are excluded. Subject is limited to 998 bytes and body to 256 KiB. There is one verified-HTTPS attempt, no redirects, retry or queue.

PrestaShop mail module

0.1.1

Version 0.1.1 supports exactly PrestaShop 9.0.0, 9.0.1, 9.0.2 and 9.0.3 with PHP 8.1–8.4. Upload the ZIP in Modules > Module Manager, then configure SendRepute mail classification. All four official prebuilt classic releases passed isolated installation, authenticated administrator configuration and ZIP-update checks; their unchanged Mail::send() implementations also passed the offline real-mail matrix. PrestaShop 8, 9.1+ and later unlisted 9.0 patches are not supported.

The module, paid/content consent, and exact template selection are all off by default. It analyzes the final rendered subject and every supported displayed body without rebuilding the Symfony message. A message containing both text/plain and text/html is sent in one bounded classification request: the plain alternative is made inert, the original HTML is preserved, and the service analyzes each typed alternative independently without concatenation. The result uses the highest risk with the complete content audits, produces one paid classification, and never returns a partial safety score. Advisory never interrupts sending. Threshold blocking and fail-closed throw one exception implementing both Symfony Mailer's ExceptionInterface and PrestaShop's ModuleErrorInterface; on every supported release the installed test observed Mail::send() return false with no SMTP delivery. Failure policy is independent of the risk threshold.

Download PrestaShop ZIP

Download Symfony source ZIP

1. Install

Download the 0.1.1 ZIP, then use Modules > Module Manager > Upload a module and choose it. Open Configure for SendRepute mail classification. Do not force installation outside exact PrestaShop 9.0.0–9.0.3: cancellation and signing behavior depend on the audited Mail::send() paths.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-prestashop.zip

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-prestashop.git
cd sendrepute-prestashop

2. Configure securely

Set SENDREPUTE_API_BASE to the canonical production SendRepute HTTPS origin supplied for this module and SENDREPUTE_API_TOKEN to a scoped server token in the PHP-FPM/server environment. The base must be a path-free public DNS HTTPS origin; literals, credentials, redirects and private DNS answers are refused. Run the non-paid account/pricing connection check, then explicitly enable the module, paid/content consent and exact template names. Choose advisory/block, threshold and open/closed failure policy independently.

export SENDREPUTE_API_BASE="replace-with-the-canonical-sendrepute-https-origin"
export SENDREPUTE_API_TOKEN="replace-with-a-scoped-server-token"

3. Use it deliberately

Continue using PrestaShop's normal Mail::send flow. The early hook only remembers an opted-in exact template. The final hook reads the already-rendered Symfony Email subject, text body and HTML body without changing recipients, headers, attachments or transport. For dual bodies, it submits inert plain text and the original HTML as typed alternatives in one request; independent service normalization prevents one fragment from consuming another while retaining visible HTML link and image destinations for audit. A single plain body stays on the narrow inert-text path, and a single HTML body stays on the narrow DOM-extraction path. Classification completes before PrestaShop creates a separate DKIM-signed message. The supported-release matrix verified the emitted multipart structure plus DKIM body hash and RSA signature after classification. PrestaShop's pinned signing path omits Bcc from the prepared signed headers and loses that blind SMTP recipient; valid signature evidence therefore does not establish Bcc delivery compatibility. Do not combine DKIM and Bcc on this supported path. Unsupported display sources, active semantics, ambiguous quoted-printable or base64 HTML, and oversized aggregate content follow the configured failure policy before payment. Leave critical templates unselected unless deliberately approved.

Results, failures and limits

The classifier accepts one text/plain body, one text/html body or both as independently analyzed displayed alternatives. Literal text, entity, hidden and style content in an accepted alternative cannot consume or hide a later alternative; ambiguous quoted-printable or base64 HTML is rejected before payment instead. Any accepted alternative can determine the highest-risk result, while content audits cover every alternative; classification is charged once only after the complete bounded input is accepted. The required legacy body exactly duplicates the inert plain alternative for a dual message, and that duplicate plus both typed alternatives share the exact 524288-byte request budget. Recipients, attachments and embedded resources are excluded, and the original pre-signing transport message is preserved. The real-mail fixture separately checks MIME/signature integrity and actual SMTP recipients: DKIM signatures remain valid after classification, but the audited upstream signed path does not preserve Bcc recipients. A validated classification stores a limited latest advisory summary. Block mode throws only at or above the threshold; the dual-interface exception survives hook dispatch and produces false before transport on all four installed releases. Unsupported content, API and validation errors follow open/closed independently. One HTTPS attempt uses pinned public DNS, verified TLS, finite timeouts, a 256 KiB response cap, no redirects and no retry. Blocking relies on the audited PrestaShop Mail::send() exception catch, not the final hook return value.

Symfony Mailer adapter

0.1.1

Requires PHP 8.1+ and targets Symfony Mailer 6.4 or 7.4 only; the exact verified releases are 6.4.46 and 7.4.19. No Symfony 8.1 or untested-line compatibility is claimed. Install the local source ZIP through a Composer path repository; this package is not published to Packagist.

The bundle and paid consent are off by default, and only a message with the exact configured opt-in header is eligible. Advisory or blocking score policy is independent from allow or block failure policy. Classification runs on the official pre-send MessageEvent; rejection uses MessageEvent::reject(). Queued clone events are skipped so the worker transport event is the one paid classification point.

Download Rails source ZIP

1. Install

Extract the downloaded ZIP into a retained packages directory, register that directory as a Composer path repository, require the exact 0.1.1 package, and register SendRepute\Symfony\SendReputeBundle if Flex does not. The source archive is local and unpublished.

mkdir -p packages
curl -fL https://www.sendrepute.com/downloads/sendrepute-symfony.zip -o packages/sendrepute-symfony.zip
unzip packages/sendrepute-symfony.zip -d packages
composer config repositories.sendrepute path ./packages/sendrepute-symfony
composer require sendrepute/symfony:0.1.1

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-symfony.git
cd sendrepute-symfony

2. Configure securely

Resolve SENDREPUTE_API_TOKEN from server secrets. Keep enabled and paid_analysis_consent false while reviewing current pricing. Mode, threshold and failure policy are independent. The endpoint is fixed to verified HTTPS with bounded deadlines, no redirects or retries, and a 1 MiB response cap.

send_repute:
  enabled: false
  paid_analysis_consent: false
  api_token: '%env(SENDREPUTE_API_TOKEN)%'
  mode: advisory
  failure_policy: allow
  spam_probability_threshold: 0.8

3. Use it deliberately

Add the exact opt-in header only to reviewed non-critical Email objects, then continue through the normal Mailer. The message, envelope, transport and header are not rewritten. For Messenger delivery, configure the bundle in workers: producer clone events are intentionally not classified.

$email->getHeaders()->addTextHeader('X-SendRepute-Classify', 'yes');
$mailer->send($email);

Results, failures and limits

Exactly one in-memory text or HTML body is supported. Mixed alternatives, textual DataParts, streams or paths, CSS braces, markup, quoted-printable syntax, base64 headers or whole-body base64 fail before payment and follow failure policy; ordinary braces-free content is unchanged. Every required nested response field and optional audit branch is validated and unknown properties are rejected. Advisory never score-blocks; blocking rejects at the threshold through the real transport event.

Rails Action Mailer adapter

0.1.0

Requires Ruby 3.2+ and is narrowly verified with real Action Mailer 7.1.6 and Mail 2.9.1; the callback path was also observed on Action Mailer 7.2.3.2. This is not certification of every allowed Rails 7.x release. Install the local source ZIP through Bundler; no RubyGems publication is claimed.

Both global paid gates default off, and each mailer action must call sendrepute_paid_preflight! explicitly. Advisory/block score behavior and preserve/block failure behavior are independent. Password resets, MFA, login, verification, billing and security routes should remain unselected. Every multipart message and ambiguous CSS, quoted-printable or base64-looking content is rejected before payment; one accepted decoded text or HTML body is analyzed without changing the original message or transport.

Download Spring Java source ZIP

1. Install

Extract the ZIP exactly into vendor/sendrepute-rails, add the local path entry to the Gemfile, run Bundler in your controlled environment, and include SendRepute::Rails::Mailer in ApplicationMailer. This is not a RubyGems installation.

# Download sendrepute-rails.zip, then extract it into vendor/sendrepute-rails.
gem "sendrepute-rails", path: "vendor/sendrepute-rails"

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-rails.git
cd sendrepute-rails

2. Configure securely

Keep enabled and paid_consent false until current pricing and routes are reviewed. Read the token from Rails credentials or another server secret. Configure advisory/block, preserve/block and threshold independently; on_result and on_error callbacks must not log message content, authorization data or complete responses.

SendRepute::Rails.configure do |config|
  config.enabled = false
  config.paid_consent = false
  config.token = Rails.application.credentials.dig(:sendrepute, :api_token)
  config.mode = :advisory
  config.failure_policy = :preserve
  config.score_threshold = 0.8
end

3. Use it deliberately

Call sendrepute_paid_preflight! only inside each deliberately selected non-critical mailer action. Normal actions bypass classification. The paid hook uses Action Mailer's before_deliver route; no global auto-opt-in is provided and the adapter does not rewrite the Mail::Message.

class ApplicationMailer < ActionMailer::Base
  include SendRepute::Rails::Mailer
end

def newsletter
  sendrepute_paid_preflight!
  mail(to: params[:to], subject: "News")
end

Results, failures and limits

One decoded text/plain or text/html displayed body is supported. Every multipart or ambiguous normalizer input fails before payment and follows failure policy. A complete typed nested response can block only in block mode at or above threshold; advisory preserves every score. Result and error callbacks receive immutable safe data, and callback exceptions or throw(:abort) are caught locally so they cannot terminate advisory or preserve delivery. The fixed endpoint refuses redirects and retries and uses a bounded total deadline. Real Action Mailer 7.1.6 tests passed: 19 runs and 59 assertions; no paid request or real delivery occurred.

Spring JavaMailSender adapter

0.1.1

Requires Java 17+ and targets Spring Framework 6.2.x JavaMailSender; exact dependency verification used Spring Framework 6.2.19. There is no Spring Boot 4 or broad framework-version claim. Build the local source ZIP with Maven; it is not published to Maven Central or another registry.

The decorator, paid consent, advisory mode and allow-on-failure defaults are explicit. Only sendWithSendRepute(...) performs paid pre-send analysis; every ordinary send(...) overload bypasses classification and delegates unchanged. Use ordinary send for critical mail unless that individual send is deliberately selected. Supported displayed MIME alternatives are inertly framed together; unsupported, nested, signed, encrypted or ambiguous content fails before payment.

Download Magento source ZIP

1. Install

Extract the 0.1.1 source ZIP, run mvn verify, and install it only into your controlled local Maven repository. The consuming application supplies its existing JavaMailSender and runtime mail implementation. Exact dependency verification used Java 17 bytecode, Spring Framework 6.2.19 and the versions documented in the included README.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-spring-mail.zip
unzip sendrepute-spring-mail.zip
cd sendrepute-spring-mail-0.1.1
mvn verify
mvn install

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-java.git
cd sendrepute-java

2. Configure securely

Construct SendReputeConfiguration from a server-side token and explicit switches. Keep enabled and paidAnalysisConsent false until pricing and selected calls are reviewed. Advisory/blocking, threshold, and allow/block failure policy are independent. The endpoint is fixed to verified HTTPS with no redirect or retry.

var settings = new SendReputeConfiguration(
    token, false, false,
    SendReputeConfiguration.Mode.ADVISORY,
    SendReputeConfiguration.FailurePolicy.ALLOW,
    0.80, Duration.ofSeconds(3), Duration.ofSeconds(10));
var reviewedSender = new SendReputeJavaMailSender(existingSender, settings);

3. Use it deliberately

Call sendWithSendRepute(...) only for an individual SimpleMailMessage, MimeMessage or MimeMessagePreparator that should incur analysis. Single and varargs overloads are supported. Every normal send(...) overload bypasses classification. Preparators render once and the original prepared MIME is delegated after policy permits.

// Paid classification is possible only on this explicit method.
reviewedSender.sendWithSendRepute(reviewedMessage);

// Every ordinary JavaMailSender send overload bypasses classification.
reviewedSender.send(criticalMessage);

Results, failures and limits

All supported displayed plain and HTML parts are analyzed; recipients and attachments are excluded. Traversal is capped at 16 levels, 256 parts and 524,288 displayed UTF-8 bytes. Ignored inline binary is never materialized; unknown or unbounded lazy displayed sources fail before a stream is opened or a paid request is made, and supported source reads are bounded. Numeric-entity framing keeps fragments inert through the checked server normalizer order. Entire varargs batches prepare and normalize before the first paid request, and inspection does not generate Jakarta Mail headers. A recursively exact nested response is required.

Magento Open Source mail adapter

0.1.1

Supports only Magento Open Source 2.4.7-p5 and 2.4.7-p6 with the exact immutable mail-interface sources reviewed. Offline typed fixtures passed, but no full Magento installation was performed; no other Magento or Adobe Commerce release is certified. Install the local ZIP through a Composer path repository; it is not an Adobe Marketplace package.

The module, paid consent and route lists all default off. Every template identifier requires two independent exact approvals; criticality is never inferred from its name. The aroundSendMessage plugin analyzes at the final transport boundary without rebuilding the message. Advisory/block threshold policy and preserve/block failure policy are independent; blocking raises a visible Magento MailException. Multiple displayed MIME parts and ambiguous content fail before payment.

Download .NET MailKit source ZIP

1. Install

Extract the ZIP to a retained package directory, register its SendRepute_MailAdapter root as a Composer path repository, require version 0.1.1, then use Magento's normal module enable and setup upgrade process. Do not represent this local archive as an Adobe Marketplace package.

mkdir -p packages/sendrepute-magento
curl -fLO https://www.sendrepute.com/downloads/sendrepute-magento.zip
unzip sendrepute-magento.zip -d packages/sendrepute-magento
composer config repositories.sendrepute path ./packages/sendrepute-magento/SendRepute_MailAdapter
composer require sendrepute/magento-mail-adapter:0.1.1
bin/magento module:enable SendRepute_MailAdapter
bin/magento setup:upgrade

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-magento.git
cd sendrepute-magento

2. Configure securely

Set SENDREPUTE_API_TOKEN only in the PHP-FPM and CLI server environment. In Stores > Configuration > Services > SendRepute, keep the module and paid consent off initially. Add every exact template identifier to both independent route-approval lists; names, including numeric names, never infer criticality. Configure advisory/block, threshold and preserve/block failure behavior separately.

export SENDREPUTE_API_TOKEN="replace-with-a-scoped-server-token"
# Then configure Stores > Configuration > Services > SendRepute.

3. Use it deliberately

Continue using Magento's normal template and transport flow. Route correlation records the exact identifier and store selected through TransportBuilder, while the final aroundSendMessage plugin reads the official typed email and MIME interfaces before calling the same transport. Builder state clears in finally, and builder/message correlations use object-keyed WeakMap entries so an abandoned built transport cannot leave reusable numeric object-ID authorization. The adapter does not provide a new send method or mutate the message.

Results, failures and limits

Only one supported displayed MIME part is accepted; attachments are preserved but excluded from analysis. Multiple displayed parts, unsupported transfer encodings or charsets, streams, nested MIME and ambiguous normalizer text fail before payment. One verified-HTTPS request has bounded deadlines and response size with no retry or redirect. A valid nested result may block at threshold; configured fail-block raises Magento MailException.

.NET MailKit adapter

0.1.0

Requires .NET 8 and exact dependency evidence for MailKit/MimeKit 4.18.0. It is an explicit wrapper around an application-owned IMailTransport, not a global hook, SMTP client or replacement transport. Build or reference the local source ZIP; no NuGet publication is claimed.

The adapter and paid consent default off; advisory and preserve-send are independent defaults. Calls to AnalyzeAsync, AnalyzeThenSend or AnalyzeThenSendAsync are explicit. Critical security/account mail needs a separate per-call category and consent. Every supported displayed plain/HTML alternative is inertly framed into one bounded request; unsupported, nested, signed or encrypted content fails before payment. The original MimeMessage and cancellation token reach the existing transport only after policy permits.

Download Zapier and Make recipe ZIP

1. Install

Extract the source ZIP and reference src/SendRepute.MailKit/SendRepute.MailKit.csproj from the consuming .NET 8 project. Restore obtains MailKit/MimeKit 4.18.0. This source package is local and unpublished; it is not a NuGet installation.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-mailkit.zip
unzip sendrepute-mailkit.zip
dotnet add reference ./sendrepute-mailkit-0.1.0/src/SendRepute.MailKit/SendRepute.MailKit.csproj

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-dotnet.git
cd sendrepute-dotnet

2. Configure securely

Wrap the existing application-owned IMailTransport with SendReputeMailAdapter. Read the API token from server configuration and keep Enabled and PaidAnalysisConsent false until reviewed. Advisory/block threshold and preserve/block failure settings are independent. The endpoint, TLS floor, one-attempt behavior, deadlines and 1 MiB bounds are fixed.

var options = new SendReputeOptions {
    Enabled = false,
    PaidAnalysisConsent = false,
    ApiToken = configuration["SENDREPUTE_API_KEY"]!,
    Enforcement = EnforcementPolicy.Advisory,
    OnFailure = FailurePolicy.PreserveSend,
    SpamProbabilityThreshold = 0.80
};
var adapter = new SendReputeMailAdapter(existingTransport, new SendReputeClient(options), options);

3. Use it deliberately

Invoke AnalyzeAsync for analysis only, or AnalyzeThenSend and AnalyzeThenSendAsync for explicit pre-send behavior. No ordinary or global mail path is intercepted. Pass paid consent and the message category on each selected operation; critical security/account mail requires the separate critical-consent setting.

await adapter.AnalyzeThenSendAsync(message, new AnalysisConsent {
    PaidAnalysisConsent = true,
    Category = MessageCategory.Ordinary
}, cancellationToken);

Results, failures and limits

Actual MimeKit decoding collects every supported displayed plain and HTML alternative into inert framing while excluding recipients and attachments. Non-base64 outer framing and late-decoded entities neutralize CSS braces, quoted-printable text, base64 headers, whole-body base64 and markup before service normalization. Unsupported, nested, signed or encrypted displayed content fails before payment. Every required response field is typed; optional flaggedTermCount must be a non-negative integer and optional contentAudit is fully and recursively validated against the public contract. The exact original MimeMessage and cancellation token reach the supplied transport only when independent score and failure policies permit.

Zapier manual draft analysis

0.2.0

Manual Zapier recipe for displaying paid analysis of exactly three owner-selected draft strings. It is not a SendRepute Zapier app, marketplace listing, import artifact, pre-send adapter, sender, allow/block route or whole-message classifier. Zapier Webhooks uses an owner-operated bounded HTTPS proxy because the SendRepute token must not enter the Zap.

Two compile-time constants default false before HTTP. The Zap maps sender display name, subject and body only, posts JSON to the included owner-proxy design, completely validates the nested response, then displays advisory and billing fields in a private review step. It must not add a sender, Paths enforcement, Autoreplay or failure-preserve route; failed Code or Webhook steps stop.

Download Zapier and Make recipe ZIP

1. Install

Download and extract the shared 0.2.0 recipe source. Read the included Zapier guide and deploy the included loopback Node proxy only behind an owner-managed HTTPS reverse proxy. This package does not deploy it. There is no SendRepute Zapier app or importable Zap artifact.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-automation-recipes.zip
unzip sendrepute-automation-recipes.zip
cd sendrepute-automation-recipes

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-automation.git
cd sendrepute-automation

2. Configure securely

Keep the Zap off. In the exact preflight Code source, ENABLED and PAID_CONSENT both remain false until paid use is reviewed. The owner proxy stores SENDREPUTE_API_TOKEN; the Zap receives only one separately revocable credential from SENDREPUTE_PROXY_CREDENTIALS. Editors and task history may expose it, so restrict, rotate and revoke it. Configure per-credential token-bucket and concurrency limits, global connection/concurrency caps, a persistent owner-set daily paid-call budget, restrictive upstream spend limits, and matching TLS-terminator size/rate/deadline controls. Do not enable Autoreplay.

// In zapier/preflight.js; review charges before changing either literal.
const ENABLED = false;
const PAID_CONSENT = false;

3. Use it deliberately

Build the steps manually: draft trigger; preflight Code mapping only sender, subject and body; Webhooks POST with JSON rows to the owner proxy; response-validation Code; private review display. Never manually interpolate raw JSON. Display requestId, model, label, spamProbability and billing only; do not add a mail action or Paths decision.

{
  "sender": "Mapped draft sender display name",
  "subject": "Mapped draft subject",
  "body": "Mapped draft body"
}

Results, failures and limits

The recipe analyzes only the three mapped strings; unmapped MIME, HTML alternatives, attachments and eventual outbound content remain unanalyzed. Conservative preflight rejects known normalizer triggers but does not prove whole-message coverage. Proxy rate, concurrency and daily-budget limits reject before upstream, and budget reservation persists before the paid attempt; run one proxy process per budget file. The proxy makes one bounded fixed-HTTPS attempt. Any non-200 or incomplete exact response throws and stops; there is no preserve, Resume or substitute result.

Make manual draft analysis

0.2.0

Manual Make scenario instructions for displaying paid analysis of exactly three selected draft strings. It is not a blueprint, approved SendRepute app, mail sender, enforcement route or claim about unmapped MIME, HTML, attachments or eventual outbound content. The bearer token belongs only in Make HTTP's secure keychain.

Persisted enabled and paidConsent booleans default false and an AND filter stops before HTTP. JSON is produced by Make's JSON module and sent once by the HTTP module with redirects and retries disabled. A response filter is only a display guard, not full validation or permission to send. HTTP failures use Break, never Resume or substitute output.

1. Install

Download and extract the shared 0.2.0 recipe source, then follow the included Make guide to construct current native modules manually. No blueprint, marketplace app or import format is claimed. Keep scenario scheduling off while testing against a mock endpoint.

curl -fLO https://www.sendrepute.com/downloads/sendrepute-automation-recipes.zip
unzip sendrepute-automation-recipes.zip
cat sendrepute-automation-recipes/make/README.md

Alternative: install from public source

git clone https://github.com/sendrepute/sendrepute-automation.git
cd sendrepute-automation

2. Configure securely

Create persisted boolean Tools variables enabled=false and paidConsent=false, followed by an AND filter requiring both true. Use JSON > Create JSON for exactly sender, subject and body. Store the SendRepute bearer token only in the HTTP app secure keychain; exported scenarios must contain no credential.

Tools variables: enabled = false; paidConsent = false
Filter: enabled = true AND paidConsent = true
HTTP credential: secure keychain; Authorization header
Body type: Raw; Content type: application/json; map serialized JSON
Follow redirect: No; Timeout: 10 seconds; no retry
Response filter: Minimal display guard

3. Use it deliberately

Configure one HTTP POST to the fixed classify URL. Select Body type Raw and the application/json content-type control without adding a conflicting free-text header, then map the serialized output from JSON > Create JSON. Enable parsed response, disable redirects, set a 10-second timeout, and add no repeater or automatic retry. Require the module's 1 MiB response limit; if unavailable, use an owner-controlled bounded proxy instead. Add only a private review display after the Minimal display guard—never a sender or allow/block router.

{
  "sender": "Mapped draft sender display name",
  "subject": "Mapped draft subject",
  "body": "Mapped draft body"
}

Results, failures and limits

Only the mapped strings are analyzed; normalization is not identity with an original or outbound email. The response filter checks status and core result/billing presence only and is explicitly not full schema validation or enforcement. HTTP errors use Break so later actions do not run; never use Resume, fabricated output or a failure-preserve route.

Node.js SDK

0.1.1

Server-only SDK for Node.js 18.17+. Install @sendrepute/node from npm or use the downloadable tarball. The optional Nodemailer adapter preserves your existing transport. Set a scoped API key and an explicit API base URL in your server environment, never browser code.

Register createSendReputePlugin at the stream stage only after reviewing pricing and deliberately enabling paid analysis consent. Advisory mode reports findings without blocking delivery. Blocking mode enforces spamProbabilityThreshold; onApiFailure chooses allow or block, while a changed-price refusal always blocks delivery. Classification is a paid API operation.

Download Node.js tarball