This project aims to provide mail forwarding service. It does use a simple rules to describe the fowardings to operate.
The service contains a few simple protection mechanisms:
TODO:
- allow enforcing signed message over tls
- evaluate if checking SPF on helo hostname makes sense
OVER CONTAINERS AND SPF:
Sender Policy Framework does provide a series of mechanisms to validate if a sender is authorized to send a mail.
Most often this will rely on the source ip of the connection. This source IP cannot be easily identified in containers that are often natted.
To the recieving end of the mail the source ip may also be randomised by your container platform. Especially when hosting containers in a cloud, the source IP may be difficult to identify.
In these situation to avoid being flagged as spam it is always best to use DKIM to sign message. That is why a warning is provided when relaying unsigned messages.
The service supports starttls and will warn while relaying unsigned email or in clear text
Rules are defined per block separated by ";". All blocks are evaluated to define the set of destinations addresses.
Each block is defined by multiple statements separated by ":".
The first statement defines the source address:
* wildcard that will match zero or more characters? wildcard that will match exactly one character# wildcard that will match exactly on digit! that will negate the match doneThe following statements are destination addresses:
Samples
Forward all mails for "test.it" to one user "[email protected]" :
@test.it:[email protected]
Forward all users ending with fw in the "test.it" domain to the same user (fw included) in the "hello.com" domain:
*[email protected]:@hello.com
Forward all except "admin" in the "test.it" domain to one user "[email protected]":
Content type
Image
Digest
Size
1.8 MB
Last updated
over 4 years ago
docker pull cblomart/go-naive-mail-forward