Technical requirements - valid from 13.07.2023

Sections on this page:

• Own mail domain
• DNS Configuration
• Customising the spam filter configuration
• Customising the firewall configuration
• Setting smarthosts
• Delivery via 3rd parties
• Sub and alias domains

 

Own mail domain

If outlook.com, hotmail.com, GMX, Bluewin, icloud.com, gmail.com or other major email providers are used, the mailboxes cannot be used in the seppmail.cloud. Only domains owned and controlled by the seppmail.cloud can be routed via the seppmail.cloud.

DNS Configuration

• The customer must have the possibility to change DNS entries:
  • • TXT (SPF, DKIM, DMARC, SwissSign authentication)
    • MX (Mail Exchange -> for Inline configuration)
    • CNAME (seppmail.cloud GINA Webmail Certificate Authentication)
    • CAA (optional, CA-Authorisation)
    • A/AAAA (optional)
• The DNS provider has to allow CNAME entries for destination that start with "_".
• Special case: Hosters who only accept e-mails if the MX record points to their own infrastructure (e.g. Hostpoint).
• Optional: The DNS provider should enable CAA records.
• Optional: The DNS provider should offer DNSSec.

Customising the spam filter configuration

• The customer must be able to change the configuration of an existing spam filter.
• In particular, the SPF check must be deactivated.
• In principle, we advise against connecting several spam filters in series (high risk of false positives).
• An existing on premises antivirus system can still be operated (low risk of false positives).

Customising the firewall configuration

Customers with on premises hosting must adjust the firewall so that the seppmail.cloud has access to the mail server:

• Port 25 (SMTP) for mail delivery.
• optional: Port 2525 (Exchange Backend) for recipient filtering (if not available on port 25).
• optional: Port (to be defined) for directory queries (future feature of the seppmail.cloud).
• recommended: To block port 25 for delivery from hosts other than seppmail.cloud.

Setting smarthosts

For each domain that is to be routed via the seppmail.cloud, it must be possible to route a smarthost with the hosting provider or mail server.

Delivery via 3rd parties

(for example marketing, newsletter or similar)

3rd parties usually have to get SMTP errors, bounces and the like. Therefore, sending via seppmail.cloud is usually not possible or useful. In addition, sending bulk messages (with narrow exceptions for "transactional Bulk") is not allowed.

We recommend sending such messages via a dedicated provider in a subdomain.

Sub and alias domains

If the customer has subdomains ("app.example.com") or alias domains ("example.net") in addition to a main domain ("example.com"), these must each be recorded as separate domains in the seppmail.cloud. Commercially, a concession for the customer is conceivable (for example, a discount on an alias domain if it serves the same users as the main domain). If a sub/alias domain is also to have SigEnc, certificates and SigEnc services must also be ordered.