Hosting agreement

Hosting agreement version 0.1

between Irational.org (server collective) and TITiPI (collective user)

Definition & Limits of Hosting

Irational.org offers TITiPI the possibility to host their email service.

This service is not virtual. The Irational.org server space is shared, in terms of administration, socially and in terms of maintenance.

There will be no automated warnings or predefined storage limits.

The terms of this agreement are adjusted where necessary.

Technical set-up

• Hardware: Raspberry Pi 4 Model B × 1 with WD Blue™ SA510 SATA SSD - 500GB
• Software/Protocols: Debian - Postfix - Dovecot - Alpine - Roundcube - IMAP - SMTP
• Location: Servus datacenter, Linz, Austria

Responsibilities

Irational.org takes responsibility for ensuring that users can contact other email users across networks, including the possibility to contact GAFAM services such as gmail

Users have the responsibility to protect themselves against viruses, and to use strong passwords

Mutual support

There are no end-users. Even if levels of amassed knowledge wildly differ, we try to support each other to make the Irational.org server run as well as it needs to be.

Regular check-ins are scheduled between TITiPI and Irational.org; every three months at a minimum or as needed. This includes server housekeeping, caring for collective documentation, and updating this agreement.

Availability

This service does not want to be perfect. No 99.5% Mail server availability: endless redundancy is a waste

Disasters

Do happen. Both users and Irational.org keep back ups.

Privacy

The directory structure on Irational.org allows users to have general read access to each others' directories, as is the default in Linux. Users may change their own directory permissions for additional privacy. In this way, privacy is not technically enforced, but a matter of practice. The 'root' user is technically able to read other users' files, a capability that they do not exercise. Server users do not have any read access to others' email messages by default. These files have a more restrictive set of permissions than that of ordinary files. By default, mailservers store detailed metadata on every single incoming and outgoing email in the system logs. These logs can only be accessed by users with root access, and are used for debugging. We're in the process of considering the privacy implications of this logging and how to mitigate those.

Data retention

The involved parties plan to open a conversation with Servus concerning mutual responsibilities and procedures, what would happen in case of a police intervention for example, server visits, payments etc.

Optional Services

n/a

Caveat

The relationship between different agents involved in the hosting arrangement do not follow the usual hierarchical architecture of datacenter, serviceprovider and customer. Therefore, this arrangement might break when hitting legal limits, or unforeseen circumstances. We are in the process of figuring out contingency procedures.

Signature

Agreement signed November 2023

For Irational, Kate Rich

For TITiPI, Femke Snelting