From b844015d22c83fe6fe71263ecb0f0cf49d855853 Mon Sep 17 00:00:00 2001 From: rasmus Date: Wed, 4 Mar 2026 16:20:01 +0200 Subject: [PATCH] doc: wildflock aliases with gsuite Forwarding set up by eaas --- wildduck/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/wildduck/README.md b/wildduck/README.md index 4714e69..87562c5 100644 --- a/wildduck/README.md +++ b/wildduck/README.md @@ -22,3 +22,15 @@ The mail stack consists of several moving parts: 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 +```