Need help with MailSpoof? Find answers, report issues, or connect with the community.
Join the MailSpoof community to ask questions, share feedback, and collaborate with other security professionals.
Ask questions, share ideas, and discuss best practices for email security testing with the MailSpoof community.
Open DiscussionsCommon questions and solutions for MailSpoof usage.
Direct MX delivery from residential IPs is blocked by most providers (Gmail, Yahoo, Outlook). Use an external SMTP relay with authentication via --profile or inline --smtp-host, --smtp-user, and --use-tls flags. Port 587 with TLS usually works best.
Run mailspoof profile add gmail --host smtp.gmail.com --port 587 --user you@gmail.com --pass app-password --use-tls. Then use it with --profile gmail on any test command.
All data is stored under ~/.mailspoof/ — templates in templates/custom/, config in config.json, and audit logs in audit.log.
Use mailspoof preview 1 to inspect rendered HTML, mailspoof preview 1 --raw for raw source, and mailspoof edit-template 1 to open in your default editor.
test runs a built-in scenario by ID. custom lets you fully define from-name, subject, and body. start launches the interactive wizard with the built-in SMTP server.
Found a bug or experiencing unexpected behavior? Submit a detailed report so we can investigate and fix it.
Use our structured bug report form to provide all the details we need to reproduce and resolve your issue quickly.
Submit Bug ReportTrack existing issues, contribute fixes, or request new features directly on the GitHub repository.
View IssuesFound a security vulnerability? Please do not open a public issue.
Email security.mailspoof@orildo.sbs directly with a detailed description of the vulnerability, reproduction steps, and your contact information. We will respond within 48 hours and work with you to resolve it before any public disclosure.
Find comprehensive guides covering installation, configuration, usage, and troubleshooting.
Learn how to install, configure, and use MailSpoof effectively. Includes command references and example workflows.
Read DocumentationNeed to reach the MailSpoof team? Here are all available contact channels.
Email security.mailspoof@orildo.sbs for general questions, usage help, and feature requests. Typical response time is 24–48 hours.
Use the structured Bug Report form or open an issue on GitHub Issues.
For vulnerabilities, email security.mailspoof@orildo.sbs directly. Do not open public issues. We respond within 48 hours.
Join GitHub Discussions to ask questions and share feedback with other users.
MailSpoof is open-source and welcomes contributions. Help improve the tool by submitting code, templates, or documentation.