SMTP email service

Authenticated SMTP email for websites and applications in Bangladesh.

EmailDesk provides organizations in Bangladesh with customer-scoped SMTP submission for transactional and operational email. Each credential works with verified sender identities, gateway DNS requirements, outbound protection, delivery-state evidence, and retry-safe quota recording around provider handoff.

Start your free trial

What EmailDesk provides

A controlled SMTP path with evidence at each stage.

Authenticated SMTP submission

Customer-scoped credentials support secure submission on configured ports and can be limited to a permitted sender domain or exact verified sender identity.

Verified senders and DNS readiness

EmailDesk checks the exact From identity and the active gateway's SPF requirement. DKIM should use the provider-issued selector, and DMARC should align with the authenticated sender domain.

Applications and business software

Use SMTP with compatible applications, CRM systems, website forms, operational tools, and desktop software that can authenticate with a restricted sender.

Security and outbound protection

Before provider handoff, EmailDesk evaluates sender permission, recipients, content, attachments, suppressions, velocity, quota, and outbound policy.

Separate delivery states

Queued or gateway-accepted responses remain separate from local blocks, provider rejections, and later recipient bounces. Acceptance never guarantees inbox delivery.

Retry-safe quota records

A retry of the same EmailDesk relay transaction reuses its receipt and quota key so the same handoff is not charged again. A new send remains a new quota event.

How to begin

Prepare SMTP sending in four stages.

A working SMTP login is only one part of the sending path. The sender identity and its DNS authorization must also match the selected gateway.

01
Verify the sending domain and From address
Confirm control of the exact From email, authorize the active gateway in SPF, publish its DKIM record, and configure aligned DMARC for the sending domain.
02
Create a restricted SMTP credential
Generate the credential for the correct workspace and apply a sender restriction when the application should use only one domain or address.
03
Connect the sending application
Configure the secure SMTP host, port, login, encryption, and verified From address in the application, CRM, website, or compatible desktop software.
04
Test and inspect the evidence
Send a controlled test, then review the delivery state, gateway response, outbound checks, quota use, and any later rejection or bounce evidence.

Operational evidence

Provider handoff is not final inbox delivery.

EmailDesk records the provider-handoff boundary and keeps later outcomes separate. A gateway can accept or queue a message before additional provider processing or recipient filtering, so SMTP acceptance never guarantees inbox placement.

Queued: EmailDesk or the selected gateway accepted the message for further processing.
Accepted: the upstream SMTP handoff succeeded at that stage, not that the recipient received the message.
Blocked: EmailDesk stopped the message before provider handoff because a local requirement or protection check failed.
Rejected: a provider or recipient SMTP system refused the handoff or delivery attempt.
Bounced: later delivery evidence reported that an accepted or queued message could not be delivered.
Troubleshooting evidence includes the sending profile, SMTP response, sender and DNS checks, policy decision, quota receipt, and later provider or bounce events.

Frequently asked questions

Questions about SMTP email service.

Which SMTP ports are supported?

EmailDesk supports secure submission on port 587 with STARTTLS and port 465 with SSL/TLS for configured customer SMTP credentials.

What sender and DNS checks are required?

The exact From address must be verified. The sender domain must authorize the selected gateway in SPF, should publish the provider-issued DKIM record, and should use aligned DMARC. Bulk senders should pass SPF, DKIM, and DMARC. Existing SPF mechanisms must be merged into one record.

Does SMTP acceptance guarantee inbox delivery?

No. A queued or accepted response means the handoff succeeded at that stage. Later provider processing, recipient filtering, rejection, or a bounce can still change the outcome.

When is quota recorded?

Quota is recorded at a genuine provider-handoff attempt. A message blocked locally before handoff does not consume sending quota. Recipient units and applicable attachment units are recorded separately from the message status.

Can an SMTP retry consume quota twice?

A retry of the same EmailDesk relay transaction reuses its receipt and quota key, preventing a duplicate charge for that logical handoff. A separate message or a newly submitted transaction is a new quota event.

What can connect to EmailDesk SMTP?

Compatible applications, CRM systems, website forms, operational tools, and desktop software can submit mail with an active credential and verified sender. Mailbox access through IMAP or POP remains separate from an SMTP sending credential.

Free guided trial

Review EmailDesk against your real email workflow.

Submit a short trial request. No package choice, card, or online payment is required before the request is reviewed.