Sender Health Signals
Sendzovo can consider signals such as complaints, hard bounces, unknown-user signals, deferrals, authentication problems, verification failures, sending velocity and other reputation-related indicators.
Sendzovo combines transactional email delivery with recipient verification, suppressions and sender-health protection. Mandrill, now Mailchimp Transactional, focuses on transactional messaging, delivery infrastructure and reputation management.
Last updated: September 14, 2026
The badges below describe the availability or documentation status of each capability.
The capability is currently available and supported by the provider.
The capability exists but depends on eligibility, network conditions, account requirements or other specific conditions.
The capability is planned for Sendzovo but is not generally available yet.
The provider's current documentation confirms that the capability is not offered.
We could not reliably confirm the capability from the provider's current public information.
Different Approach does not necessarily mean unavailable. It means we could not reliably confirm the capability from current public documentation.
Compare the core sending infrastructure offered by Sendzovo and Mandrill.
| Feature | Sendzovo | Mandrill |
|---|---|---|
| Transactional emails | Available | Available |
| Bulk / broadcast sending | Available | Available |
| SMTP | Available | Available |
| REST API | Available | Available |
| Pre-built email templates | Available | Available |
| Dynamic template engine | Available | Available |
| Custom Email Templates | Available | Available |
| Scheduled delivery | Available | Available |
| Message attachments | Available | Available |
| Dedicated IP options | Available | Available |
Sendzovo treats recipient verification as a core part of the email workflow.
| Feature | Sendzovo | Mandrill |
|---|---|---|
| Email address validation | Available | Not Available |
| Syntax / domain / MX checks | Available | Not Available |
| Disposable address detection | Available | Not Available |
| Role address detection | Available | Not Available |
| Live SMTP mailbox probing | Available | Not Available |
| Catch-all domain detection | Available | Not Available |
| Verification scoring | Available | Not Available |
| Bulk verification | Available | Not Available |
| Verify-before-send workflow | Available | Not Available |
Verify large recipient lists before using them in applications or sending workflows.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Bulk email verification | Available | Not Available |
| Verification job API | Available | Not Available |
| Verification scoring | Available | Not Available |
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Verify-before-send workflow | Available | Not Available |
| Verification + sending platform | Same platform | Not Available |
Sendzovo is designed around a workflow where verification results can feed into suppression and sending decisions. This helps applications avoid sending to recipients that have already been identified as invalid or risky.
Compare the mechanisms used to protect delivery quality and sender reputation.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Hard bounce handling | Available | Available |
| Soft bounce / deferral handling | Available | Not Available |
| Recipient suppression after hard bounce | Available | Available |
| Delivery failure visibility | Available | Available |
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Complaint processing | Available | Available |
| Feedback loop processing | Available | Available |
| Complaint-based suppression | Available | Available |
Complaint signals can influence sender reputation. Processing these signals quickly allows a sending platform to suppress affected recipients and incorporate the signal into broader sender-health decisions.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Automatic suppression | Available | Available |
| Hard bounce suppression | Available | Available |
| Complaint suppression | Available | Available |
| Invalid-recipient suppression | Available | Available |
| Repeated soft-bounce suppression | Available | Available |
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Numeric sender-health score | Available | Not Available |
| Sending velocity / risk monitoring | Available | Available |
| Risk-based throttling | Available | Available |
| Automatic pause / review state | Available | Conditional |
Sendzovo can consider signals such as complaints, hard bounces, unknown-user signals, deferrals, authentication problems, verification failures, sending velocity and other reputation-related indicators.
A message being accepted by a recipient mail server does not automatically mean the sender is healthy. Sender-health monitoring combines multiple signals to identify increasing risk.
Compare domain verification, email authentication, API credentials and rate controls.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Domain ownership verification | Available | Available |
| DNS-based verification | Available | Available |
| Domain sending-readiness state | Available | Conditional |
| Capability | Sendzovo | Mandrill |
|---|---|---|
| DKIM guidance | Available | Conditional |
| SPF guidance | Available | Conditional |
| DMARC guidance | Available | Conditional |
DKIM adds a cryptographic signature to outgoing messages so receiving systems can verify that the message was authorized by the sending domain and was not modified after signing.
SPF identifies the servers authorized to send mail for a domain. Sendzovo provides SPF configuration guidance and avoids recommending destructive replacement of an existing SPF policy.
DMARC builds on domain authentication by defining how receiving systems should evaluate messages that fail authentication alignment.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| API keys | Available | Available |
| Scoped API permissions | Available | Available |
Sendzovo API keys support scopes so applications can be granted the permissions they actually need. This allows different application credentials to have different access levels.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| API rate limiting | Available | Available |
| Per-key limits | Available | Not Available |
| Per-organization limits | Available | Available |
| Risk-based sending controls | Available | Available |
Rate limiting and sender-health controls serve different purposes. Rate limits protect infrastructure and access, while sender-health controls respond to reputation risk.
Compare the tools available for monitoring message activity and integrating email events with your applications.
| Event / Capability | Sendzovo | Mandrill |
|---|---|---|
| Queued event | Available | Available |
| Sent event | Available | Available |
| Delivered event | Available | Available |
| Deferred event | Available | Available |
| Bounced / failed event | Available | Available |
A delivered event means the recipient mail system accepted the message. It does not mean that the recipient opened or read the email.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Open tracking | Available | Available |
| Click tracking | Available | Available |
| Customer tracking controls | Available | Conditional |
Open tracking can use a tracking pixel to estimate when an email was opened. Because mail clients can preload or block images, open tracking should be treated as an approximate signal.
Click tracking records interactions with tracked links. Customers can control tracking behavior, while certain security-sensitive or unsubscribe links may be excluded.
| Capability | Sendzovo | Mandrill |
|---|---|---|
| Webhook support | Available | Available |
| Signed webhook requests | Available | Available |
| Webhook retries | Available | Available |
| Exponential backoff | Available | Not Available |
| Dashboard webhook replay | Available | Not Available |
Sendzovo signs webhook requests using timestamp and signature headers so receiving applications can verify webhook authenticity.
Providers change their products frequently. If something here looks incorrect or outdated, let us know.
Sendzovo can be a strong fit for teams that need transactional email together with recipient verification, suppression and sender-health protection in the same platform.
Mandrill was rebranded as Mailchimp Transactional in 2025. The transactional email infrastructure and API are now positioned under the Mailchimp Transactional name.
Yes. Sendzovo supports syntax, domain and MX validation, disposable and role-address detection, verification scoring, bulk verification, and conditional SMTP probing and catch-all detection.
Mandrill, now Mailchimp Transactional, is primarily a transactional email delivery platform. Its documented functionality focuses on sending, delivery, reputation, bounces, complaints, suppressions and related transactional email capabilities rather than dedicated recipient verification.
Yes. Sendzovo supports Verify-Before-Send workflows that combine recipient verification with transactional email delivery.
Yes. Mailchimp Transactional provides SMTP integration as well as a transactional REST API.
Yes. Mailchimp Transactional supports webhooks for events including sent, delivered, deferred, hard bounce, soft bounce, open, click, spam, unsubscribe and rejected messages.
Yes. Sendzovo provides a 0–100 Sender Health score and evaluates signals such as complaints, bounces, deferrals, authentication problems, verification signals and sending-risk patterns.
Applications using API or SMTP-based delivery can migrate incrementally by configuring a Sendzovo domain, updating API or SMTP credentials, testing workflows and gradually moving production traffic.
Send transactional email, verify recipients before they reach your pipeline, and protect your sending reputation from invalid recipients, bounces and complaints.