Regulation
General terms and conditions of use of our services
Regulation

Rules for the use of e-mail

Regulation of services

1. Scope of the Service

Email Services are intended for the receipt, consultation and sending of email messages. The General Terms of Service shall apply in addition to the specific provisions set out below.

The service includes:

  • receipt of messages for configured mailboxes;
  • consultation via email clients using POP3 and IMAP4 protocols;
  • consultation and sending via webmail (web interface);
  • sending through an SMTP service subject to the limits of the subscribed plan;
  • the use of authenticated or dedicated SMTP services, where separately contracted.

2. Permitted Use

The Email Service is intended for ordinary use by individuals or businesses within the scope of normal daily activity.

Bulk email sending is not permitted through standard email services. For such purposes, dedicated services must be used (e.g., DEM Mail Server, Dedicated Mail Server, Dedicated SMTP).

The Provider reserves the right to limit or suspend the service in the event of non-compliant use.

3. Conduct Constituting Abuse

The following shall constitute abuse of the service, by way of example and not limitation:

  • sending unsolicited commercial or non-commercial communications (SPAM);
  • distribution of viruses, malware or malicious scripts;
  • sending “mail bombs” or messages with excessively large attachments;
  • repeated sending of messages to non-existent mailboxes;
  • any activity likely to result in IP or domain blacklisting.

4. Message Receipt

The Client is required to regularly download email messages from the server in order to avoid exceeding the mailbox storage limits.

5. Sending of Messages

Email messages may be sent only to recipients who have previously provided their consent to receive such communications, where required by applicable law.

Messages sent:

  • must use an existing and properly configured email address as sender;
  • must be sent in plain text or HTML format compliant with SMTP standards;
  • must not contain executable code or malicious components.

To ensure compatibility with international SMTP standards, individual lines in HTML messages must not exceed 2,048 characters.

Sending messages to more than 10400 recipients simultaneously within the same header is not permitted and, where necessary, messages should be divided into smaller recipient groups.
Messages sent in breach of this limit may be filtered or not delivered without prior notice.

6. Bulk Email and Newsletters

The sending of newsletters or high volumes of email messages is permitted exclusively through dedicated services (DEM Mail Server, Dedicated Mail Server, Dedicated SMTP).

Bulk email sending must comply with the double opt-in mechanism, where required by applicable law.

The Client is responsible for implementing all necessary measures to prevent blacklisting. If bulk sending results in the blacklisting of the IP address associated with the service, the Provider may suspend the service. Reactivation may occur only after delisting procedures have been completed at the Client’s expense.

The following are not permitted:

  • bulk sending from hosting plans via web pages;
  • bulk sending via webmail;
  • bulk sending using domains with an active Private Whois service.

7. Best Practices for Sending Communications and Mailing Lists

The Client using the Services to send newsletters or communications to mailing lists shall adopt the generally recognized best practices for mailing list management and SPAM prevention.

In particular, by way of example and not limitation, the Client shall:

  • use list subscription mechanisms based on double opt-in (explicit confirmation of subscription);
  • provide in each message a simple and immediate unsubscribe mechanism (for example, an unsubscribe link allowing removal with a single click);
  • verify and remove in advance non-existent, incorrect or invalid email addresses;
  • manage and automatically remove addresses generating error messages or non-delivery notices (bounces);
  • properly configure the email authentication records of the domain used for sending (for example SPF and DKIM);
  • adhere, where possible, to complaint reporting and management systems made available by email service providers (for example Feedback Loop systems or registration as a bulk sender);
  • properly configure the sender address and the technical message headers;
  • prepare clear and non-misleading content, avoiding deceptive subject lines and message structures typically associated with SPAM.

Compliance with the above best practices does not guarantee that sent messages will not be classified as SPAM by recipients’ systems.

8. Classification of Messages as SPAM

The classification of an email message as SPAM depends primarily on the content of the message and on the assessment criteria adopted by the recipient or the recipient’s email provider. Such criteria may be subjective and based on automated filtering systems not under the Provider’s control.

The Provider shall not be liable for any classification of messages as SPAM by recipients’ email systems or by their respective providers.

The Provider shall immediately and without prior notice deactivate any service from which the sending of SPAM messages is detected, without prejudice to the right to claim compensation for any damages incurred.

9. IP Address Blacklisting

Improper use of email services may result in the IP addresses used for sending messages being included in blacklists managed by email service providers or third-party organizations that monitor the sending of unsolicited communications.

If the sending activity carried out by the Client causes, or may cause, an IP address associated with the Services to be blacklisted, the Provider reserves the right to temporarily suspend the email sending service in order to prevent further service disruptions or damage to the infrastructure.

If the blacklisting is attributable to the Client’s conduct, the Provider may require the Client to adopt the necessary measures to resolve the issue and may charge the Client for any technical costs incurred for analysis, mitigation, or delisting activities.

The Provider shall not be held liable for any limitations or refusal of message delivery by third-party email systems resulting from the inclusion of IP addresses in blacklists.