Service Administration & Onboarding Process

The configuration of our service can be adapted very flexibly to your requirements. It is important to develop a concept which is tailored to the desired integration in advance, so that a smooth implementation can take place later on.

Recommended preliminary considerations.

Is the web service addressed by one or more applications?

If you are using multiple applications, it makes sense to set up multiple separate accounts to ensure security and independence. If a central account is nevertheless desired, we recommend that you design your web service client as a central middleware.

Do the applications send fundimentally different content?

If the content of emails from different applications is fundamentally different in nature (transactional vs. marketing), we recommend using different sender domains, which in turn are routed over different IP addresses. A separate account is not necessary for this.

Do you want to separate the applications with regard to data center (e.g. US vs. EU)?

If your applications are hosted and used on different continents, it makes sense to use one of our local data centers to fulfill local compliance policies, process data completely separately, or avoid high latency. Your account is basically set up for each data center, but you need to control the use of the respective system. The use of an additional data center must be reported to and ordered from Retarus.

Do you want to use more than one sender domain?

The use of multiple domains over a single IP entails operational risks in the event of blocklisting. Therefore, you should check beforehand which volume is likely to be sent via each individual domain and from which country of origin it stems. Depending on these parameters, you should separate domains with a very high volume (> 1,000,000 emails per month) and domains from countries with a higher spam risk (e.g. Eastern European addresses such as *.ru) or mix them with other domains.

Too little traffic also poses a risk of blocklisting. Therefore, it is advisable to merge domains sending very little traffic with others that transmit more. If the overall amount of traffic is very low, we also offer a "shared infrastructure".

Once you have completed these preliminary considerations, we recommend that you create an overview that could look like the one outlined in Service administration hierarchy and Onboarding process.