Updated 2026-10-08
How to Send Email From Make.com Through Your Own SMTP Server
In Make.com, add the Email app's Send an Email module, create a connection with the Others (SMTP) connection type and Email provider set to Other, then enter SMTP server smtp.bulko.io, port 465 with the secure connection (TLS) option on, and your Bulko SMTP username and password. Port 587 with explicit TLS (STARTTLS) also works.
Make SMTP settings
| Field | Value |
|---|---|
| Connection type | Others (SMTP) |
| Connection name | Any label, for example Bulko SMTP |
| Email provider | Other |
| Host | smtp.bulko.io |
| Port | 465 (implicit TLS) or 587 / 2525 (STARTTLS) |
| Connection security | SSL/TLS with port 465, or TLS (STARTTLS) with port 587 or 2525. The setting must match the port. |
| User name | Your Bulko username, for example smtp_xxxxxxxxxxxxxxxx |
| Password | Your Bulko SMTP password from Dashboard > SMTP Access |
Step-by-step setup
- Buy an SMTP package on the Bulko SMTP Relay page. The username and password are shown in Dashboard > SMTP Access and emailed to you after payment.
- Open your scenario in Make, click the + button, search for the built-in Email app and choose the Send an Email module.
- In the module, click Create a connection (or Add) and set Connection type to Others (SMTP). The other options are Google and Microsoft OAuth connections, which send through those mailboxes instead of your own SMTP server.
- Optionally enter a Connection name. In Email provider, pick Other so Make shows the manual server fields.
- Enter the SMTP server
smtp.bulko.ioand port465, and choose SSL/TLS as the connection security. If you prefer port587(or2525when 587 is blocked), choose TLS (STARTTLS) instead. Exact option names can differ slightly in the Make UI; what matters is that the security type matches the port. Then fill in User name and Password with your Bulko credentials. - Leave the advanced Reject unauthorized certificates setting at Yes and leave Certificate authority empty; those options are only for servers with self-signed certificates. Click Save.
- Fill in the module: recipient address, Subject, the content type (HTML or plain text) and the message content. Map values from earlier modules, for example a form submission or a row from Google Sheets. Set the sender (From) address to one on your own domain.
- Optional: verify the sending domain in Sending Domains and publish the DKIM TXT record (selector
bk1) and thebnc.yourdomain.comCNAME so SPF, DKIM and DMARC align.
Make connects to the SMTP server from its own cloud, and Bulko authenticates the connection by username and password. Save the connection once and select it in every scenario that sends email.
Send a test email
Click Run once with the recipient set to an inbox you can read, or right-click the Send an Email module and choose Run this module only. A green check on the module and a delivered message mean the relay accepted the email. If the run fails, click the error bubble on the module to read the SMTP reply, for example 535 for a login problem or 554 5.7.1 for a filtered message, and compare it with the table below. Open the delivered email, view its original headers and confirm SPF and DKIM pass before turning on scheduling.
Troubleshooting
| Problem | Fix |
|---|---|
| SSL error such as wrong version number when saving the connection | The connection security does not match the port. Use SSL/TLS with 465, or TLS (STARTTLS) with 587 or 2525. |
| Connection timed out | Check the server name smtp.bulko.io and the port. If one port fails, try another of 465, 587 and 2525. Port 25 is not offered for submission. |
| 535 Authentication failed | The User name or Password is wrong. Copy them again from Dashboard > SMTP Access; the user name looks like smtp_xxxxxxxxxxxxxxxx, not an email address. More causes: bulko.io/en/smtp-errors/535/. |
| 554 5.7.1 message rejected | Bulko's content filter flagged the message as phishing, malware, impersonation or a scam. Review the mapped content and links coming from earlier modules. |
| Certificate error or self-signed certificate message | Leave Reject unauthorized certificates at Yes and make sure the server is typed exactly as smtp.bulko.io, without an IP address or a different hostname. |
| Emails arrive in spam | Send from an address on your own domain, verify it in Sending Domains, and check SPF with the Bulko SPF checker. |
FAQ
Which connection type do I pick to use custom SMTP in Make?
Others (SMTP), then Email provider Other. The Google and Microsoft OAuth options send through those mailboxes and do not use your own SMTP server.
Can Make also read incoming mail from Bulko?
No. Bulko is outgoing only, with no IMAP or inbox. For Watch Emails triggers, create a separate Others IMAP connection to your regular mailbox.
Is port 465 or 587 better in Make?
Both are encrypted. Port 465 uses SSL/TLS from the first byte; 587 and 2525 start plain and upgrade with STARTTLS. Pick whichever your network allows and set the matching security type.
How many emails can a Make scenario send through Bulko?
The default is 2,000 emails per day per SMTP account, which [email protected] can raise. Each email also uses Make operations according to your Make plan.
How much does it cost?
Bulko SMTP packages are one-time payments: $5 for 5,000 emails, $15 for 20,000, $30 for 50,000 or $60 for 150,000. There is no subscription and unused emails never expire.
Get SMTP credentials for Make
One-time payment by card or crypto, no subscription. Unused emails never expire. 2,000 emails per day per SMTP account.
What you can send: Acceptable Use Policy.