Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Executables/pipes as transports, BSMTP? #297

Open
Mihara opened this issue Feb 21, 2025 · 0 comments
Open

Feature request: Executables/pipes as transports, BSMTP? #297

Mihara opened this issue Feb 21, 2025 · 0 comments

Comments

@Mihara
Copy link

Mihara commented Feb 21, 2025

At least I think this is a feature request, the documentation is not very clear...

Assume I'm using NNCP which is a poorly documented but powerful way to set up highly encrypted friend-to-friend delay tolerant networks, named after UUCP and mimicking it in functionality in several respects. One of its intended uses is serving as an email transport, so one can package email for delivery and pass it through NNCP to where it needs to go.

The way to do that with Postfix and Exim is known. The only kind of transports mox appears to support are SMTP to a specific host ("smarthost"), a SOCKS proxy, and direct connection. At least, nothing else is obviously described and I don't see anything else with a quick skim through the source.

There is no way to imitate the Postfix or Exim setup described above that I can see.

  1. Is this reasonably practical to implement at all, with the way mox's security works? I remember the fairly arcane (for me) systemd settings basically jailing the server process, so I wouldn't be too surprised if it's not feasible.
  2. Perhaps there's a separate "buffer" localhost-smtp solution somewhere, that mox could communicate with that wouldn't be restricted from running arbitrarily chosen executables? E.g. I run something very simple on a separate port that only listens to mox, mox uses it as a transport, it does the back and forth with NNCP?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant