Max Mazurov
Max Mazurov
@angelnu idea for a solution * Implement ManageSieve in Maddy so users can use their email clients to upload the filter configs to the server this could be either be...
I implemented a simple interpreter for the base Sieve specification here: https://github.com/foxcpp/go-sieve.
Once we get support for several important extensions into it and find a way to re-use Pigeonhole tests suite - it should be ready for integration into maddy. Though we...
Addressed feedback: added Feature.Contains() and inverted flags (making extensions opt-in rather than opt-out).
Yes, it is directly related. Currently, maddy does but support any deployment setup using active replication. For MX redundancy, your best solution is to configure second MX to buffer incoming...
Well, fine.
Trying to think of a generic-enough solution useful beyond the proposed use case. Something like: ``` check.ip_filter { allow cidr 127.0.0.1/24 deny cidr 0.0.0.0/0 } ``` Multiple allow/deny entries? What...
We are going to omit any advanced functionality for now so lets consider two use cases: 1. Blocking certain subnets/addresses. 2. Allowing messages only from certain subnets/addresses. These could be...
Use-cases to evaluate: ## maddy behind a TLS terminator for all endpoints TLS terminator needs to be protocol aware for server-server SMTP: It needs to proxy SMTP capabilities and inject...
``` smtp tcp://127.0.0.1:2525 { proxy_protocol { assume_tls # should be turned on by default? } # if TLS is configured - it is for TLS between proxy and maddy. Not...