sending-emails
Send Mailtrap Emails Correctly
Mailtrap send paths can be confusing when transactional, bulk, batch, and campaigns overlap. This skill maps the right path and gives implementation references.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "sending-emails" from https://skillstore.io/skills/mailtrap-sending-emails.md and its manifest at https://skillstore.io/api/skills/mailtrap-sending-emails/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "sending-emails". I need password reset emails from a Rails app.
Expected outcome:
Use transactional sending. Prefer the official SDK if it supports your needed options, then verify the domain, token scope, sender, and recipient handling.
Using "sending-emails". We send weekly promotions to contacts stored in our own database.
Expected outcome:
Use the bulk stream rather than the transactional host. Confirm consent, unsubscribe handling, token scope, and sending-domain setup before production sends.
Using "sending-emails". I need to hand off many different notification messages at once.
Expected outcome:
Use batch on the correct stream. Batch reduces request overhead, but it does not change whether messages are transactional or promotional.
Security Audit
SafeMost static findings are false positives caused by Markdown inline code, fenced curl examples, and official Mailtrap URLs. The live email sending capability is confirmed because the skill documents API and SMTP paths that can send external email when used with valid credentials. No prompt injection, credential exfiltration, or hidden execution intent was found in SKILL.md.
Capability review items (8)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (28)
🌐 Network access (25)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/mailtrap-sending-emails/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/mailtrap-sending-emails?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/mailtrap-sending-emails?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mailtrap-sending-emails/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/mailtrap-sending-emails.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
mailtrap. (2026). sending-emails security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mailtrap-sending-emails/audits/6BibTeX citation
@techreport{mailtrap-mailtrap-sending-emails-2026,
author = {mailtrap},
title = {sending-emails security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/mailtrap-sending-emails/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "sending-emails security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "mailtrap"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/mailtrap-sending-emails/audits/6"
identifiers:
- type: other
value: "skillstore:mailtrap-sending-emails:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Choose an integration path
Compare Mailtrap platform integrations, SDKs, HTTP API, and SMTP for a new application.
Configure operational email
Set up password resets, receipts, alerts, and notifications on the correct transactional stream.
Plan marketing volume
Distinguish bulk, batch, and campaigns before sending promotional messages through Mailtrap.
Try These Prompts
Help me choose the right Mailtrap send method for my app. My platform is [platform], message type is [type], and volume is [volume].
Guide me through Mailtrap transactional email setup for [language or framework]. Include token handling, sender domain checks, and the preferred SDK or API path.
Review my planned Mailtrap workflow for [message goal]. Decide whether I need bulk, batch, campaigns, or transactional sending, and explain the tradeoffs.
Help troubleshoot my Mailtrap live send issue. I use [API or SMTP], stream [transactional or bulk], error [error], and environment [environment].
Best Practices
- Confirm the stream, recipient authorization, and sender domain before any live send.
- Store Mailtrap tokens in environment variables and rotate them when access changes.
- Test with sandbox or controlled recipients before bulk, batch, or production traffic.
Avoid
- Sending promotional messages through the transactional host.
- Running live curl examples with production tokens without user confirmation.
- Guessing SDK constructors or method names instead of checking the current README.