Skip to content
Webizen Docs
GithubTwitter

Categories

Agent-Labelling-WIP
Documentation Method
DRAFT: Guide For Developers
Old-Work-Archives
Permissive Commons
Social Factors
Webizen Docs Introduction
Webizen Tech Stack
Authentication Fabric
Core Services
Core Technologies
Engineering Considerations
Authentication Logic
Containerisation
Cryptography
Database Requirements
Email Server Logic
InternetStrategy
Prolog
Private DataStore (Vault)
Vocabulary Modelling
Webize
Webizen 2.5 Dev
Webizen 3.0
Webizen 3.5
Webizen 4.0
Webizen Apps
Work in Progress
On this page
On this page

Email Server Logic

The objective is to use the domain name to generate email addresses based upon the user of the address.

ie: MyDomain.tld

Therein - each relationship has different email addresses provided which thereby provides an ability to manage spam.

MailServer OPtions

Maddy:

Maddy Mail Server implements all functionality required to run a e-mail server. It can send messages via SMTP (works as MTA), accept messages via SMTP (works as MX) and store messages while providing access to them via IMAP. In addition to that it implements auxiliary protocols that are mandatory to keep email reasonably secure (DKIM, SPF, DMARC, DANE, MTA-STS).

It replaces Postfix, Dovecot, OpenDKIM, OpenSPF, OpenDMARC and more with one daemon with uniform configuration and minimal maintenance cost. source: https://github.com/foxcpp/maddy

Considerations

Is the email server one of those examples where the use of BadWolf (timestamps, etc) becomes increasingly useful? also the use of BQL becomes less of a problem...

Edit this page
Last updated on 1/29/2023