SMTP2GO is a fast and scalable email service provider, for sending transactional and marketing emails and viewing reports on email delivery.

SMTP2GO looks forward to working with the security community to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

SMTP2GO will make a best effort to meet the following response targets for hackers participating in our program:

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
• Follow HackerOne's disclosure guidelines.

Program Rules

• Please provide detailed reports with reproducible steps.
• Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
• Social engineering (e.g. phishing, vishing, smishing) is prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Test Plan

Free trial: You may register up to two test accounts on the SMTP2GO website (https://www.smtp2go.com/pricing/). However, please make sure to use your Hacker Email Alias - [username]@wearehackerone.com and [username+test]@wearehackerone.com when creating accounts for our tracking purposes.

Paid accounts: There are additional permissions that are not accessible to free accounts like Email Archiving, Email Testing and the addition of Dedicated IP Addresses.

#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Clickjacking on pages with no sensitive actions.
• Unauthenticated/logout/login CSRF.
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our service (DoS).
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• The ability to send an email from any domain name (not just one of your account's verified Sender Domains). This is only considered a vulnerability if the email becomes DKIM-signed with a DKIM signature at that same domain name. For example, you manage to send an email from [email protected] and it becomes signed with a DKIM signature with d=anotherdomain.com.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep SMTP2GO and our users safe!