Standalone SMTP relay service that allows inter server communication on I2P ( SMTP federation )
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
fade 38f4b4b04e init 2 months ago
cmd init 2 months ago
docs init 2 months ago
services init 2 months ago
LICENSE init 2 months ago
README.md init 2 months ago
README_smtprelay.md init 2 months ago
auth.go init 2 months ago
auth_test.go init 2 months ago
config.go init 2 months ago
config_test.go init 2 months ago
go.mod init 2 months ago
go.sum init 2 months ago
install.sh init 2 months ago
logger.go init 2 months ago
main.go init 2 months ago
main_test.go init 2 months ago
smtp.go init 2 months ago
smtprelay.ini init 2 months ago

README.md

Author: apophis.

Building & Running

git clone http://git.apophis.i2p/apophis/smtprelay-I2P.git
go get ( to get all required packages)
go build .
  • For debugging or running in terminal (listen port is set in mailserver smarthost config) :
smtprelay -listen '127.0.0.1:7658' -log_level 'debug' -proxy_i2p '127.0.0.1:4447'
  • For production setups you can use openrc/systemd configurations provided - [services]
  • Optionally, you can use automated installation script :
sudo ./install.sh
  • Specific configurations for Exim4/Postifx as well as neomutt are provided as well - [MTA config]

  • To test the validity of your smtprelay-I2P setup, just send an email to apophis@pubsub.i2p

Overview and Features

arch

  • smtprelay-I2P is based on decke/smtprelay project adapted to I2P environment - [decke/smtprelay]
  • Generally, I2P has neither need nor place for DNS like service/records as all address routing is direct. This new paradigm requires some sort of agreement in between MTA operators on mail domain naming scheme.
  • Basically, mailserver domain name and domain served by MTA must be identical.
  • I2P inter server MTA communication is the goal of this project and thus, we ask all I2P MTA operators to use this domain naming scheme to allow for wide I2P MTA federation.

What's next

  • Allow TLS and other AUTH methods over I2P connections ( in case some "genius" needs certificates )
  • Kill All Humans ?