Overview
|
L1 – CuNo |
Retarus Customer No. |
|||||
|
L2 - Technical Account |
Technical Account a |
Technical Account b |
||||
|
Data Center |
DC x |
DC y |
||||
|
L3 - Domain |
Domain a |
Domain b |
Domain c |
Domain d |
Domain e |
Domain f |
|
Approx. Vol. |
A |
B |
C |
D |
E |
F |
|
Client |
Client a |
Client b |
Client c |
Client d |
||
|
IP |
IP 1 |
IP 2 |
IP 3 |
|||
Level 1: Retarus Customer No.
The Retarus customer number is the highest entity. Everything configured under a specific customer number will be billed on a single invoice. If you would like to receive a separate invoice to a different addressee, then you need an additional customer number. Under each customer number you can create an unlimited number of Technical Accounts.
Level 2: Technical Account
An Technical Account is defined as an authentication entity (definition of API username / password etc.) and can be configured to a specific dedicated Retarus data center. Under each Technical Account you can manage several domains. You can also manage the same domain under several Technical Accounts.
Level 3: Domain
The domain configuration is used to define default parameters, and also domain-specific settings such as DKIM, SPF etc. We can route domains via dedicated MTA IP(s).
Client
A client is configured to a specific domain but can be set with the same name for several domains. It will be used to relate several domains or subdomains to a single client. Due to the fact that this is a simple text field, it can alternatively be used to define the content type.
Sample
|
L1 – CuNo |
99999 |
|||||
|
L2 - Technical Account |
Technical Account a |
Technical Account b |
||||
|
Data Center |
DC EU |
DC US |
||||
|
L3 - Domain |
crm.retarus.de |
erp.retarus.de |
news.retarus.de |
news.retarus.ru |
news.retarus.com |
news.retarus.ca |
|
Approx. Vol. |
200.000 |
150.000 |
750.000 |
500.000 |
2.500.000 |
500.000 |
|
Client / Usage |
Transactional |
Newsletter |
Newsletter |
Newsletter |
||
|
IP |
IP 1 |
IP 2 |
IP 3 |
IP 4 |
||