콘텐츠로 바로가기
WordPress.org

한국어

  • 테마
  • 플러그인
  • 소식
    • 문서
    • 포럼
  • About
    • WordPress 6.9
    • 워드프레스 6.8
    • 워드프레스와 40% 웹을 위한 여정
    • 워드프레스 번역 핸드북
  • 워드프레스 한국팀
  • 워드프레스 받기
워드프레스 받기
WordPress.org

Plugin Directory

SwiftTrap for Mailtrap

  • 플러그인 제출하기
  • 내 즐겨찾기
  • 로그인
  • 플러그인 제출하기
  • 내 즐겨찾기
  • 로그인

SwiftTrap for Mailtrap

작성자: SYMONOV
다운로드
  • 세부사항
  • 평가
  • 설치
  • 개발
지원

설명

SwiftTrap is a drop-in replacement for wp_mail() that routes WordPress email through the Mailtrap Email Sending API instead of SMTP. It is purpose-built for Mailtrap — not a generic SMTP plugin with a Mailtrap preset — so it exposes Mailtrap-native features that SMTP cannot: bulk vs transactional stream routing, email categories, custom variables for tracking, suppression lists, and domain verification status.

Why HTTP API instead of SMTP?

  • Lower latency — one HTTPS call per message, no MAIL FROM / RCPT TO / DATA round-trips.
  • Better deliverability — Mailtrap routes API messages through its dedicated transactional and bulk streams; SMTP doesn’t expose stream selection.
  • Native categories — every email is automatically categorized (welcome, password-reset, notification, marketing, etc.) so you can filter and report on them in Mailtrap.
  • No firewall headaches — port 587/465 blocked? API works over standard HTTPS 443.

Why SwiftTrap and not WP Mail SMTP / Post SMTP

  • Generic SMTP plugins use Mailtrap’s SMTP credentials and lose every Mailtrap-only feature.
  • SwiftTrap calls send.api.mailtrap.io for transactional mail and bulk.api.mailtrap.io for bulk mail — automatically, based on category or via filter.
  • No Mailtrap PHP SDK required. Plugin is ~30 KB total and uses only the WordPress HTTP API (wp_remote_post).
  • Stats page shows your sending domain verification status and the live suppression list (bounces, complaints, unsubscribes).

Features

  • Drop-in replacement for wp_mail() — works with WooCommerce, Contact Form 7, Gravity Forms, and any plugin that uses WordPress mail.
  • Automatic email categorization and stream routing overrides via settings grid.
  • Delivery Tracking & Webhooks — Real-time event tracking via custom REST route swifttrap/v1/webhook.
  • Suppression Management — CRUD panel for Mailtrap suppression lists with pre-send recipient suppression checks.
  • Reliability Fallback — Graceful failover back to WordPress native wp_mail() if the Mailtrap API call fails.
  • Site Health integration — Verification test checking Mailtrap token status and sending domain verification.
  • Live Email Log — Browse and filter delivery data pulled directly from the Mailtrap API; search by recipient address, status, or date range with automatic pagination.
  • WP-CLI commands — Command-line management via wp swifttrap (test, stats, prune-logs, send-suppression-sync).
  • Attachment size guard — Configurable limits to prevent oversized files from rejecting at the API gateway.
  • Test email button on the settings page.
  • Mailtrap template support via template_uuid.
  • Falls back to default WordPress mail handler when disabled or token is empty.

Extensible via filters

  • swifttrap_mailtrap_email_category — override the auto-detected email category.
  • swifttrap_mailtrap_use_bulk_stream — force a message into the bulk or transactional stream.
  • swifttrap_mailtrap_template — send via a Mailtrap template by template_uuid.
  • swifttrap_mailtrap_custom_variables — attach tracking metadata to outgoing emails.

Privacy

This plugin sends email payloads (recipients, subject, body, attachments) to the Mailtrap API at send.api.mailtrap.io and bulk.api.mailtrap.io. Account stats and email logs are fetched from mailtrap.io/api/accounts and mailtrap.io/api/email_logs. See the Mailtrap Privacy Policy. No data is sent anywhere else.

스크린샷

Settings page — API token, verified sender, stream routing.
Settings page — API token, verified sender, stream routing.
Stats page — sending domain verification status and suppression list (bounces, complaints, unsubscribes).
Stats page — sending domain verification status and suppression list (bounces, complaints, unsubscribes).
Email log — live Mailtrap API data with filters and pagination.
Email log — live Mailtrap API data with filters and pagination.
Dashboard widget showing integration status, sender, and quick links to Stats and Settings.
Dashboard widget showing integration status, sender, and quick links to Stats and Settings.
Test email confirmation.
Test email confirmation.

설치

  1. Install from Plugins → Add New and search for SwiftTrap for Mailtrap, or upload the swifttrap-for-mailtrap folder to /wp-content/plugins/.
  2. Activate the plugin.
  3. Go to Mailtrap → Settings.
  4. Paste your Mailtrap Send API token (Mailtrap dashboard → Sending Domains → API Tokens).
  5. Set your verified sender email and name.
  6. Click Send test email to verify delivery.

FAQ

Why use SwiftTrap instead of WP Mail SMTP or Post SMTP with Mailtrap credentials?

WP Mail SMTP and Post SMTP route through Mailtrap’s SMTP gateway and treat Mailtrap as just another SMTP host. SwiftTrap uses Mailtrap’s HTTP Send API, which exposes features SMTP cannot: bulk vs transactional stream routing, categories, custom tracking variables, template UUIDs, and live suppression-list visibility. Use SwiftTrap if you want Mailtrap-native behavior; use a generic SMTP plugin if you want a one-config-fits-all-providers setup.

Does it support Mailtrap email templates?

Yes — use the swifttrap_mailtrap_template filter to send via a template_uuid. The template variables can be passed through Mailtrap’s standard template-variables payload.

How does bulk stream routing work?

By default, marketing/promotional categories are routed to bulk.api.mailtrap.io and everything else to send.api.mailtrap.io. Override per-message with the swifttrap_mailtrap_use_bulk_stream filter — useful for batch newsletters from a custom plugin.

Where do I get my API token?

Log in to mailtrap.io, open your sending domain, go to API Tokens, and create a token with sending permissions.

What happens if I disable the plugin or remove the token?

WordPress falls back to its default wp_mail() handler. No emails are silently dropped.

Does the plugin require the Mailtrap PHP SDK?

No. SwiftTrap calls the Mailtrap REST API directly via the WordPress HTTP API. Total plugin size is around 30 KB.

What data is sent externally?

Email data (recipients, subject, body, attachments) goes to send.api.mailtrap.io and bulk.api.mailtrap.io. Account stats are fetched from mailtrap.io/api/accounts. See the Mailtrap Privacy Policy.

Is there an attachment size limit?

Yes — 25 MB per email (matches Mailtrap’s API limit).

후기

이 플러그인에 대한 평가가 없습니다.

기여자 & 개발자

“SwiftTrap for Mailtrap”(은)는 오픈 소스 소프트웨어입니다. 다음의 사람들이 이 플러그인에 기여하였습니다.

기여자
  • SYMONOV

“SwiftTrap for Mailtrap”(이)가 2 개 언어로 번역되었습니다. 기여해 주셔서 번역자님께 감사드립니다.

자국어로 “SwiftTrap for Mailtrap”(을)를 번역하세요.

개발에 관심이 있으십니까?

코드 탐색하기는, SVN 저장소를 확인하시거나, 개발 기록을 RSS로 구독하세요.

변경이력

3.0.1

  • Fixed: Webhook receiver now verifies Mailtrap’s actual Mailtrap-Signature HMAC-SHA256 header instead of a header Mailtrap never sends. Every real delivery-tracking webhook call was being rejected outright since the feature shipped in 2.4.0.
  • Fixed: Webhook payload parsing now unwraps Mailtrap’s {"events": [...]} envelope correctly, so verified events reach do_action('swifttrap_mailtrap_webhook_event', ...).
  • Fixed: Usage card on the Stats page now calls Mailtrap’s current /api/billing/usage endpoint instead of a stale account-scoped path that returned no data.
  • Fixed: Uninstalling the plugin now clears the actual cached transients instead of pre-2.3.0 key names that no longer match.
  • Improved: Email Logs recipient search and account API calls now consistently use bracketed filter syntax and Bearer-token authentication.

3.0.0

  • Breaking: Removed all local file-based email logging. No more log files written to disk — eliminates OOM/disk-full risk on high-volume sites.
  • New: Email Logs panel on the Stats page pulls live data directly from the Mailtrap API (GET /api/email_logs).
  • New: Email Logs support filtering by recipient email address, delivery status, and date range.
  • New: Client-side pagination — buffers up to 1,000 entries from Mailtrap per API call, displays 20 rows at a time with Prev/Next navigation. Automatically fetches the next batch when the buffer is exhausted.
  • New: Webhook handler now fires do_action('swifttrap_mailtrap_webhook_event', $event) for every delivery event, allowing third-party integrations without modifying the plugin.
  • Removed: CSV export, log file clear, log detail modal, log resend, per-page logs setting, and cron-based log cleanup. All replaced by the live API view.
  • Fixed: Stats page no longer creates a redundant nonce attribute on the wrapper element.

2.4.2

  • Fixed: The email log dropped most entries during high-volume or concurrent sends. Each write re-read and rewrote the whole log file, so parallel processes overwrote each other’s lines. Writes now use an atomic, exclusively-locked append, so the Stats dashboard (sends-per-day, categories, totals) reflects the real number of sent emails.
  • Improved: Logging no longer slows down large mailings — appends are O(1) instead of re-reading and rewriting the entire file on every email.

2.4.1

  • Fixed: Suppression list now reads the Mailtrap type field, so the dashboard shows real BOUNCE / COMPLAINT / UNSUBSCRIBE / MANUAL counts instead of marking every record as manual.
  • New: Suppression rows display the message bounce category (when provided) for hard-bounce detail.
  • Fixed: Suppression dates are now formatted server-side using the site’s date format instead of the browser locale.
  • New: “View all in Mailtrap” link on the Suppressions card.
  • New: Per-page selector (10/25/50/100) on the Email Logs screen.
  • Improved: Email Logs header actions aligned to the right; date filter input restyled to match other fields.

2.4.0

  • New: REST Webhook Endpoint (swifttrap/v1/webhook) for tracking delivered, bounced, opened, and clicked statuses.
  • New: Suppression Management CRUD in Admin Stats and pre-send recipient checks to skip suppressed emails.
  • New: Fallback mechanism returning null in pre_wp_mail on API failure so native wp_mail sends the email instead.
  • New: Site Health connection and verified domain status test.
  • New: Upgraded Admin logs UI with search, filtering, CSV export, iframe payload preview modals, and resend actions.
  • New: Category settings grid for category stream mapping rules and sender overrides.
  • New: WP-CLI namespace wp swifttrap (test, stats, prune-logs, send-suppression-sync).
  • New: Attachment size guard setting.
  • Refactored: Extracted CSV row formatter into a helper function for unit tests. Fully covered and verified by the test suite.

2.3.0

  • PHP 8.0 is now the minimum; tested up to WordPress 7.0.
  • Reliability: automatic retry with backoff on transient Mailtrap API errors (429/5xx, honors Retry-After).
  • Deterministic log retention via a daily cron event (replaces the previous probabilistic cleanup).
  • Account/stats/domain/suppression caches are now keyed per API token, so switching tokens no longer serves stale data.
  • Robust JSON handling for all Mailtrap API responses; multisite-safe settings cache.
  • New: “Verify token” button on the settings screen.
  • Code modernized to PHP 8 idioms; first unit-test suite added.

2.2.2

  • Plugin URI: now points to the dedicated landing page at https://plugins.symonov.com/swifttrap-for-mailtrap/
  • No code or behavior changes

2.2.1

  • Readme: USP-first rewrite emphasizing Mailtrap Email API (vs SMTP) and bulk/transactional stream routing
  • Tags: replaced email/mail/smtp with targeted mailtrap, transactional-email, email-api, wp-mail, email-log
  • FAQ: added comparison with WP Mail SMTP / Post SMTP, Mailtrap template support, and bulk stream routing
  • Tested up to WordPress 7.0

2.2.0

  • Replaced all file_get_contents/file_put_contents with WP_Filesystem API
  • Fixed $_GET sanitization with proper wp_unslash() and phpcs annotations
  • Improved PHPDoc headers across all files
  • Better WordPress Coding Standards compliance

2.1.0

  • Added sending domain verification status on Stats page
  • Added suppression list (bounces, complaints, unsubscribes) on Stats page
  • Added swifttrap_mailtrap_template filter for Mailtrap template support
  • Added swifttrap_mailtrap_custom_variables filter for email tracking metadata
  • Extracted reusable swifttrap_mailtrap_get_account_id() with transient caching

2.0.0

  • Removed Mailtrap SDK dependency — uses WordPress HTTP API directly
  • Zero external dependencies, ~30 KB total plugin size
  • Improved WP.org compliance

1.3.0

  • Security: protected log directory from direct web access
  • Added attachment size validation (25 MB limit)
  • Added empty recipient validation
  • Fixed timezone handling in log display
  • Optimized email category computation
  • Improved log file locking

기초

  • 버전 3.0.1
  • 최근 업데이트: 2개월 전
  • 활성화된 설치 10+
  • 워드프레스 버전 6.0 또는 그 이상
  • 다음까지 시험됨: 7.0.4
  • PHP 버전 8.0 또는 그 이상
  • 언어

    English (US), Russian, 그리고 Spanish (Spain).

    자국어로 번역하기

  • 태그:
    Email APIemail logmailtraptransactional emailwp-mail
  • 고급 보기

평점

아직 제출된 리뷰가 없습니다.

Your review

모든 리뷰 보기

기여자

  • SYMONOV

지원

할 말 있으신가요? 도움이 필요하신가요?

지원 포럼 보기

  • 소개
  • 뉴스
  • 호스팅
  • 개인정보
  • 쇼케이스
  • 테마
  • 플러그인
  • 패턴
  • 배우기
  • 지원
  • 개발자 도구
  • WordPress.tv ↗
  • 참여하기
  • 이벤트
  • 기부하기 ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org
WordPress.org

한국어

  • X(이전 트위터) 계정 방문하기
  • 블루스카이 계정 방문하기
  • 마스토돈 계정 방문하기
  • 스레드 계정 방문하기
  • 페이스북 페이지 방문하기
  • 인스타그램 계정 방문하기
  • LinkedIn 계정 방문하기
  • 틱톡 계정 방문하기
  • 유튜브 채널 방문하기
  • 텀블러 계정 방문하기
코드는 詩다
The WordPress® trademark is the intellectual property of the WordPress Foundation.