SMTP

SMTP is the most widely supported way to send an email. IndiePitcher supports sending custom HTML emails and markdown emails. Sending plaintext emails is not supported.

• Consider the using the SDKs or REST API where possible, the SMTP proxy a limited set of IndiePitcher’s features.
• Same rate limits apply to the SMTP API as the REST API.
• Sent emails through SMTP will show alongside emails sent through the REST API and the SDKs in the IndiePitcher dashboard.

​

SMTP Credentials

• Host: smtp.indiepitcher.com
• Port: 587
• Username: indiepitcher
• Password: YOUR_API_KEY

​

Markdown Support

Send a regular html email containing <indiepitcher-markdown> tag. Any HTML outside of this tag will be ignored.

<indiepitcher-markdown>
Hi there,

You have been invited to create a user on [IndiePitcher](https://indiepitcher.com).

<button ip:no-track href="https://app.indiepitcher.com/register">Accept the invite</button>
<br/>

Thanks,

Your IndiePitcher team
</indiepitcher-markdown>

<!--This tag will be stripped and ignored-->
<div>Some extra html</div>

​

Limitations

The main purpose of the SMTP proxy is to allow integration with services such as Supabase Auth, Firebase Auth, and other services that require SMTP to send emails to your users. In order to avoid abuse by spammers, following limitations are in place:

• Plaintext emails are not supported, only HTML emails.
• Sending email to multiple recepients is not supported.
• Cc/bcc fields are not supported.
• From field is ignored, IndiePitcher will use the sender defined in your project’s settings.

This may change in the future based on feedback and use cases. We recommend using the following credentials to guarantee that the default sender you configured for your project is used.

• Sender name: indiepitcher-ignore-sender-replyto
• Sender email: anything, will be ignored
• Reply to: anything, will be ignored

Please contact us if you have a legit use case for any of the above limitations.

​

Examples

• Integrate with Supabase Auth