# Wildduck stack

This application is managed by
[ArgoCD](https://argocd.k-space.ee/applications/argocd/wildduck)

The mail stack consists of several moving parts:

* Haraka with several plugins
  * Wildduck plugin to handle incoming mail on port 25 of mail.k-space.ee
  * Fight spam with Rspamd
  * Fight viruses with ClamAV
* Wildduck
  * Provide API for interfacing with other systems such as
    Wildduck webmail,
    Wildflock e-mail alias generator and
    Wildduck Kubernetes operator which deals with account provisioning
  * Provide IMAP endpoint for accessing mailbox with traditional
    MUA (mail user agents): Android, iPhone, Thunderbird, Evolution etc
* ZoneMTA for handling outbound mail
  * Including mail submission from MUA with the help of Wildduck plugin

Outside Kubernetes there is NAT rule on the Mikrotik router
which rewrites source IP of any TCP port 25 headed traffic to
originate from the IP address of the mail exchange.

## Wildflock forwarding
k6.ee is in use with GSuite - k6.ee is handled by GMail. To keep Wildflock aliases working, any users not found for user@k6.ee on Google side are forwarded to mail.k-space.ee.
```
Settings for Gmail → Routing (https://admin.google.com/ac/apps/gmail/routing): Routing → Rule:
k6.ee aliases
1. Email messages to affect: Inbound
2. For the above types of messages, do the following: Modify message
  Route: Change route, Also reroute spam, Suppress bounces from this recipient: mail.k-space.ee
  Spam: Bypass spam filter for this message.
B. Account types to affect: Unrecognized / Catch-all
```