Skip to main content

Account issues

”An account with that email address already exists” or “This email address is already in use”

This typically happens when an account was created for another product, for example, Inbound Filtering. If you have an account with another product contact sales@mailchannels.com to add the Email API to your account. If you do not have an account contact support@mailchannels.com and the team will help resolve the issue. If you are not sure contact support@mailchannels.com and the team will help you resolve the issue.

API actions are returning a successful response, but seem to have no effect

This typically happens when the API key in the X-Api-Key header is not associated with the account you think it is. For example, if you have an account examplecorp, and a sub-account examplecorp-marketing, API keys created in the examplecorp account will make API calls that affect the examplecorp account, not the examplecorp-marketing account. Make sure you are using an API key that is associated with the account you want to affect.
The only header that is required for the Email API is the X-Api-Key header. Other headers are ignored.

Sending errors

550 5.7.1 This sender is not authorized to send from domain

This error indicates that the Domain Lockdown record is not properly configured for the sending domain. Make sure that the Domain Lockdown record is configured and that the DNS record has propagated. For each domain you send from, create a TXT record at the _mailchannels subdomain. For example, if you send from example.com, create a TXT record at _mailchannels.example.com. The TXT record should contain the following value:
v=mc1 auth=examplecorp
where examplecorp is your MailChannels account name. To check that your record has propagated, you can use the check-domain tool or the API. Below are examples of how to use the API to check that the record has propagated.
#!/usr/bin/env bash
# Check that a domain's DKIM, SPF, and Domain Lockdown records are configured
# correctly and have propagated.
set -u
: "${MAILCHANNELS_API_KEY:?Set MAILCHANNELS_API_KEY before running}"
: "${DOMAIN:?Set DOMAIN (the sending domain, e.g. example.com)}"

curl -X POST "https://api.mailchannels.net/tx/v1/check-domain" \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: $MAILCHANNELS_API_KEY" \
  -d @- <<JSON
{
  "domain": "$DOMAIN"
}
JSON

550 5.1.2 [SDNF] Sender Domain Not Found.

This error indicates that the sending domain does not have a valid DNS record. Make sure that the sending domain has a valid A or MX record. Use the check-domain tool to verify that the sending domain has a valid DNS record.

What to include when contacting support

Include the failed request, the error response, timestamp with time zone, sending domain, sender address, recipient domain, request_id if available, and your account name. The more information you can provide, the faster the team can investigate and resolve the issue.