Oui, y compris celles des crews (surtout celles des crews en fait, car je pense qu'il y en a très peu d'actives). Quand je parle des mailing lists, ce sont toutes les adresses mails @ppbe qui ne sont ni des alias, ni des adresses personnelles.

Je suis ok avec ta proposition HgO.

Still the same team behind the project thou
(not only the founders, the whole team).

English

Knowing that our IT costs where reduced by 50% (explained here),

Recieving this morning from Infomaniak, the information about the auto-upgrade on the 4th of April

Meaning that the new admin panel will probably be more confortable to use and manage, but the new costs may raise from 120€/year to ±350€ regarding the number of mailboxes we keep.

Having a small active it-squad.

The upgrade will be done automatically.

Français

Sachant que les frais informatiques viennent d'être réduits de moitier (expliqué ici),

Ayant reçu de Infomaniak l'information que la Console Évoluera le 4 avril

Ce qui veut dire que la migration vers leur nouveaux outils (plus confortable?), et leurs nouveaux tarifs (probablement passant de 120€ / ans à ±350€ en fonction du nombre de boîtes mails qu'on gardera).

N'ayant qu'une petite it-squad active.

La mise à jour se fera automatiquement.

Nederlands

(bijgestaan vertaalmachine)

Wetende dat IT-uitgaven worden 50% verminderd (hier uitgelegd),

Een Infomaniak bericht vanochtend aangekomen uit te leggen dat de console zal worden bijgewerkt, op 4 april

Dit betekent dat de nieuwe admin panel waarschijnlijk meer comfortabel te gebruiken en te beheren zal zijn, maar de nieuwe kosten kunnen verhogen van 120 € / jaar tot ±350 € met betrekking tot het aantal mailboxen we houden.

We hebben een kleine actieve it-squad.

De upgrade zal automatisch worden gedaan.

If we (it-squad / Belgian Pirates) want, have time, ressources (more human than anyting else :sweat_smile: ) ... we can also set-up our own mail server.

Knowing that :

Setting up our own mail server is doable, but from personal experience is a real PITA:
* Microsoft mail services blacklist whole netblocks (Hetzner, OVH)
* Google is very picky and inconsistent (sometimes silently end up in the spam folder)

In addition to just installing the SMTP server, the following MUST be met to hope reaching the mailbox:

• Proper forward DNS records (A, AAAA) and reverse (PTR)
• Proper SPF records in the DNS
• Working DKIM setup (both on mail server and in DNS records)
• Bonus: DMARC records for reporting
• Bonus: TLS on mail server
• Proper MX record (mail reception only)

And we can use this bundle of FOSS tools : https://hub.docker.com/r/tvial/docker-mailserver/

Because the IPs of Hetzner are blacklisted «by default» by Microsoft (as a anti-spam solution), once we have a new mail server hosted at Hetzner, and if we want to be able to send emails to live.be, outlook.com, hotmail.com and maybe everyone hosted on office365 ...

We also have to consider to have a Microsoft Live Account

• Do we create one for the IT-Squad?

Subscribing to Microsoft JMRP and SNDS to «register the IP address of our future mail server from Hetzner as a workaround for the Hetzner blocking by Microsoft.

Thanks to @gilbertotorres for the share.

In addition of what we wrote before

Setting up our own mail server is doable, but a real PITA (Pain In The Ass):

• Microsoft mail services blacklist whole netblocks (Hetzner, OVH)
• Google is very picky and inconsistent (sometimes silently end up in the spam folder)

In addition to just installing the SMTP server, the following MUST be met to hope reaching the mailbox:

• Proper forward DNS records (A, AAAA) and reverse (PTR)
• Proper SPF records in the DNS
• Working DKIM setup (both on mail server and in DNS records)
• Bonus: DMARC records for reporting
• Bonus: TLS on mail server
• Proper MX record (mail reception only)

As a reminder and for our Mastodon

We have had to register a Mailgun account to have a «clean smtp» to send mail (notifications, password recovery, ...).

The account was registered using those required informations:

• An email: we used the personnal mail of @damiensrobert
• A visa card: we used mine.
• A billing address: Mermaid vsw/asbl

Just a quick note that is important, https://hub.docker.com/r/tvial/docker-mailserver/ seems very complete, well made and very easy to install but the tools installed are command line tools. Meaning that to manage them we'll have to use SSH and the linux terminal.

I am sure there are web applications that allow you to configure the services installed by this project but integrating the web applications with this project will require work and testing.

Finally, we will have to configure our own webmail client (probably roundcube) to use the services installed by the project.

On other words, it seems very professional but it will require quite some work. I think it would be a good solution to avoid to depend on providers who can stop or change the condition of their services and really controlling our infrastructure.

Note that as it is a open source project and that it seems very popular with over 500K downloads in the docker hub (1). It means we can probably have some traction to have other open source project to integrate nicely with it. At least, we can try to open issues on the web applications bugtrackers that we will need to use to administer the mail not using the command line in order to ask them to support the docker mail server. They might answer positively and I would not bury the idea before trying.

(1) https://hub.docker.com/search/?isAutomated=0&isOfficial=0&page=1&pullCount=0&q=tvial%2Fdocker-mailserver&starCount=0

This docker image seems to have everything described in the 4 articles posted by @tierce

Thanks to @zefredz : a serie of articles about running your own mail server :

• How to run your own e-mail server with your own domain, part 1
• Taking e-mail back, part 2: Arming your server with Postfix and Dovecot
• Taking e-mail back, part 3: Fortifying your box against spammers
• Taking e-mail back, part 4: The finale, with webmail & everything after

... Ya plus qu'a lire / faire / etc....

We (@tierce, @damiensrobert, @iljabaert and I) decided to install a test mail server under the domain parley.be (a domain we already have) using docker and the docker-mailserver fullstack.

At the end of the day, we have a partly working mail server (imap, smtp, tls) :)

What's left to do for next time : understand why ssl does not work properly (certificate error) and why clamav is failing to scan emails.