Keep your sender reputation when you move

What carries over

Mailbox providers such as Gmail and Outlook judge most of your mail by the domain that signs it with DKIM, not by the service that sent it. If you move the same sending domain to opensend.cc, the reputation that domain has built moves with it. SES gives you new DKIM keys, but they sign for the same domain.

Three things decide what you keep:

If you already send through your own SES account

Connect opensend.cc to the same AWS account. Its production access, sending quotas and reputation history stay with the account.

When you add a domain that already exists as an SES identity in that account, opensend.cc stops and asks the installation administrator to review it. Approving lets opensend.cc take the identity over and keeps its existing DKIM records. See existing SES identities.

If you're moving off another provider

Your old provider's account history stays with them. A new AWS account starts in the SES sandbox in every region: you can only send to verified addresses, at most 200 messages a day and one a second. Request production access for each sending region before you move real traffic. AWS sets your sending quota and raises it as your account builds a clean record.

By default, SES sends from IP addresses shared with other SES customers, which AWS manages closely. If you want IP addresses no other customer uses, SES offers dedicated IPs. Its managed option warms them up for you, based on how you send. opensend.cc doesn't set dedicated IPs up for you.

Inside one installation, each team sends through its own SES tenant, with its own suppression list. A team that sends to a bad list can be paused without stopping other teams. AWS quotas, billing and sandbox state are still shared across the account. See SES tenancy.

Move without starting over

You don't have to switch everything at once. Run both providers side by side and move volume over gradually.

1. Add the domain and publish its records. Add your domain and publish the DKIM records opensend.cc shows next to your current ones. DKIM records use different selectors, so both providers can sign at the same time. The return path defaults to send.<your domain>. If your current provider already uses that subdomain with different values, choose another Custom Return-Path when you add the domain. It can't be changed later.
2. Move your suppressions first. Import addresses that bounced or complained at your old provider with batch-add suppressions before you send anything. Sending to them again is the quickest way to raise your bounce and complaint rates.
3. Start small. Send a small share of your volume through opensend.cc: your transactional mail, or your most engaged recipients. Keep the rest on your current provider.
4. Grow over one to two weeks. Increase the share each day while your rates stay healthy, and stay within your SES quota. opensend.cc has no warm-up command; split the traffic in your application.
5. Switch the rest. Once all your volume is on opensend.cc and rates are steady, remove the old provider's records.

If you're in the middle of a campaign, finish the current send on your old provider and start the next one on opensend.cc. Moving one campaign between providers halfway makes problems harder to trace.

Watch your rates

AWS reviews accounts by their bounce and complaint rates:

opensend.cc suppresses an address after a hard bounce or a complaint, so you don't send to it twice. See suppressions.

The installation administrator can see each team's volume, bounce rate and complaint rate under Team sending. These are calculated from opensend.cc's events over the last 24 hours; AWS uses its own window. See AWS SES setup.