SMTP stands for Simple Mail Transfer Protocol. It’s the set of rules that computers use to send email messages across the internet — kind of like how postal services use standard formats for sending mail between countries.
When someone orders from your store and receives an order confirmation, that email traveled via SMTP. When your app sends a password reset link, that’s SMTP too. Transactional email is any automated message your system sends to one specific person as a result of an action they took.
Marketing emails — newsletters, promotional campaigns, announcements — are different. They’re addressed to many recipients at once and sent on a schedule. Transactional emails are one-to-one, triggered immediately, and often time-sensitive.
If you’re building or running an online business, you need transactional email. Without it, your order confirmations, receipts, reset links, and notifications never reach your customers.
SMTP vs API — which one should you use?
There are two ways to send transactional emails: through an SMTP relay or through an API.
SMTP is simpler. You hand your email to an SMTP server, and it handles delivery. It’s like giving a letter to a postal service — you don’t need to know how the trucks work.
API gives you more control. Your application talks directly to the email provider’s system and tells it exactly what to send, when, and to whom. It’s like having a direct line to the postal service with custom instructions.
Most developers start with SMTP because it takes minutes to configure. APIs are more powerful but require more integration work. KIRIM.EMAIL supports both — SMTP relay and REST API — so you can start simple and scale up.
When Do You Need a Transactional Email Service?
You might think you can just use your web host’s mail server. In theory, you can. In practice, here’s what happens:
- Your emails land in spam more often than not.
- Your IP reputation is shared with thousands of other websites on the same server.
- There’s no tracking — you don’t know if password resets arrived.
- At scale, your host throttles or blocks you without warning.
If any of this sounds familiar, you’ve outgrown basic email sending.
Signs you outgrew your current setup
- Order confirmation emails are going to spam or not arriving at all.
- Your web host limits how many emails you can send per hour.
- You’re using separate tools for marketing email and transactional email.
- Your developer spends time maintaining email server configuration instead of building product.
- You have no visibility into whether emails were delivered or opened.
If one or more of those apply, it’s time to set up a proper transactional email service with SMTP.
How to Set Up SMTP for Transactional Email — Step by Step
Step 1 — Choose your SMTP provider
Your SMTP provider is the service that handles email delivery on your behalf. Rather than self-hosting a mail server (which requires constant maintenance, IP monitoring, and deliverability management), you route your emails through a provider that has the infrastructure, reputation, and deliverability expertise already in place.
KIRIM.EMAIL‘s Kredit plan gives you SMTP relay plus API access starting from $35 for 35,000 email credits. There’s no expiration on credits. You get unlimited contacts, so your transactional sending and your marketing list live in the same place.
Other providers in this space include SendGrid, Mailgun, and Postmark. What distinguishes KIRIM.EMAIL is that you don’t need a separate tool for marketing campaigns — everything runs through one account.
Step 2 — Add your sending domain
Your sending domain is the email address origin your emails come from — for example, if you send from [email protected], your sending domain is yourdomain.com.
Most transactional email services require you to verify ownership of your domain before sending. This is a security measure — it proves you control the identity you’re sending from.
In your KIRIM.EMAIL account, you add your domain in the settings section. The platform walks you through the DNS records you need to create.
Step 3 — Configure DNS records (SPF, DKIM, DMARC)
Three DNS records tell the internet your emails are legitimate:
SPF (Sender Policy Framework) — Tells receivers which mail servers are allowed to send email for your domain. Without it, spam filters assume your emails might be forged.
DKIM (DomainKeys Identified Mail) — Adds a cryptographic signature to your emails so receivers can verify they weren’t tampered with in transit.
DMARC (Domain-based Message Authentication, Reporting, and Conformance) — Tells receivers what to do if an email fails SPF or DKIM checks, and sends you reports on what’s happening.
Most managed SMTP services, including KIRIM.EMAIL, generate these records automatically and tell you exactly what to add to your DNS settings. This typically takes 5–10 minutes.
Step 4 — Get your SMTP credentials
Once your domain is verified, you generate SMTP credentials — usually a username and password or an API key. These are what your application uses to authenticate with the email service.
In KIRIM.EMAIL, you find your SMTP credentials in the Kredit plan settings. They look like a server address (e.g., smtp.kirim.email), a port number (typically 587 or 465), your username, and your password or API key.
Keep these credentials private. Treat them like a password — don’t commit them to public repositories.
Step 5 — Connect to your application
How you connect depends on what you’re building:
WordPress / WooCommerce: Install an SMTP plugin like WP Mail SMTP, then enter your SMTP credentials. The plugin intercepts emails from your site and sends them through the transactional service instead of through your web host.
Custom application: Add the SMTP credentials to your application’s email configuration. Most frameworks (Django, Rails, Node.js) have built-in or plugin-based SMTP support. For example, in Python:
import smtplib
mail_server = smtplib.SMTP('smtp.kirim.email', 587)
mail_server.starttls()
mail_server.login('your_username', 'your_password')
E-commerce platform: Most platforms (Shopify, WooCommerce, Magento) have email settings in their admin panel where you can input SMTP details directly.
If you’re using KIRIM.EMAIL‘s API instead of SMTP, your developer can use the KreditAPI endpoint with your API key. Both SMTP and API are available in the same plan.
How to Test Your SMTP Setup
Before you go live, run a test. Most SMTP providers include a built-in email testing tool. In KIRIM.EMAIL, you can send a test email directly from your account dashboard.
You can also use online SMTP testing tools — search for “SMTP test tool” and you’ll find services that verify your SMTP credentials, check your domain’s SPF/DKIM/DMARC configuration, and measure deliverability readiness.
What to check:
- The test email lands in your inbox, not spam.
- The sender address shows your verified domain, not a generic address.
- SPF, DKIM, and DMARC all show as passing in your DNS check.
If your test email goes to spam, check your DNS records first — an SPF or DKIM misconfiguration is the most common cause.
Common SMTP Setup Mistakes and How to Avoid Them
Using port 25: Port 25 is blocked by most internet service providers to reduce spam. Use port 587 (submission) or 465 (implicit TLS) instead. KIRIM.EMAIL supports both.
Skipping SPF/DKIM setup: Emails without authentication are far more likely to be flagged as spam. Set up both records before you send anything.
Sending from a shared IP: Some low-cost SMTP providers put all customers on shared IPs. If one user sends spam, everyone on that IP suffers. KIRIM.EMAIL uses dedicated infrastructure so your deliverability isn’t affected by someone else’s behavior.
Not monitoring delivery: Set up webhooks or check your email service’s delivery dashboard regularly. You want to know within minutes if a critical email — a password reset, an order confirmation — failed to deliver.
Ignoring bounce rates: If too many of your emails fail to deliver, your sender reputation suffers. Use email validation before every campaign to clean your list and protect your deliverability.
What to Look for in an SMTP Service for Transactional Email
Not all SMTP services are equal. Here’s what to evaluate:
Reliability and uptime — Transactional emails are time-sensitive. A password reset that arrives 20 minutes late frustrates your user. Choose a provider with a track record of high uptime.
Delivery speed — For transactional email, speed matters. Look for providers that guarantee fast delivery, especially for time-sensitive messages like OTP codes and order confirmations.
Scalability without surprises — Some providers throttle you when you scale up. KIRIM.EMAIL‘s Kredit plan is credit-based — you buy what you need, and credits don’t expire. No surprise overages.
Combined marketing and transactional — If you’re running both marketing campaigns and transactional emails, managing them in separate platforms adds complexity. KIRIM.EMAIL lets you handle both from one account, with one set of credentials.
Built-in validation — Bad addresses hurt your sender reputation. KIRIM.EMAIL includes email validation so you’re only ever sending to addresses that actually exist.
FAQ
What is the difference between SMTP and API for transactional email?
SMTP is simpler — your application hands an email to the SMTP server and the server handles delivery. API gives your application direct, programmatic control over every aspect of the email. Both achieve the same result; API is more flexible, SMTP is easier to set up. KIRIM.EMAIL supports both.
How do I find my SMTP credentials?
In your KIRIM.EMAIL account, go to the Kredit plan settings. Your SMTP credentials include a server address (e.g., smtp.kirim.email), a port number (587 or 465), and your username and password or API key. If you don’t have a Kredit plan yet, sign up and you’ll find them in your dashboard.
Can I use SMTP for both marketing emails and transactional emails?
You can, but it’s not ideal. Marketing campaigns go to many recipients at once and are sent on a schedule. Transactional emails are triggered one at a time and need to arrive immediately. KIRIM.EMAIL separates these into one contact-based plan for marketing and a credit-based plan (Kredit) for transactional sending, so each type gets the infrastructure it needs.
How do I know if my SMTP setup is working?
Send a test email to yourself using your SMTP credentials. Check that it arrives in your inbox, not spam, and that the sender address shows your verified domain. You can also use an online SMTP testing tool to verify your DNS configuration (SPF, DKIM, DMARC).
What port should I use for SMTP?
Use port 587 for submission with TLS, or port 465 for implicit TLS. Avoid port 25 — most ISPs block it to reduce spam, and it’s not secure for modern email sending.
Why are my transactional emails going to spam?
The most common causes are: missing SPF/DKIM DNS records, sending from a shared IP with a bad reputation, or a high bounce rate damaging your sender score. Check your DNS configuration first. Use email validation before sending to keep your list clean and protect your deliverability.
