Vagrant Cascadian
Dimly Lit Corners
John Goerzen
TiduxI'm working on a UBlue based OS image with Emacs, git-email support, and #nncpnet handling. I'll probably use the new single binary NNCP build and Postfix (I'm not a fan of Debian-Exim's configs) but steal from the original nncpnet-docker's cron+systemd+templating. Keeping it all native to the OS avoids container UID/name sync issues, filesystem mount issues, etc. The old container would probably be ok with "podman run --systemd=always -v /persist:whatever" but eh.
@orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam
==Email==
Maybe I only need to receive email over SMTP.
Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?
Perhaps #FOAF even?
Perhaps as part of NNCPNET?
Maybe (text-only) #USENET also via NNCP?
Edit: bc I just found #NNCP and #NNCPNET and think this could be a solution
==Webdev==
I can use #RubyOnRails as needed ¯\_(ツ)_/¯
@karen With #NNCP, we break the tyranny of online with delay-tolerant networking. https://www.complete.org/nncp/ The new #NNCPNET is an email network running atop it -- with bridges to the public Internet. https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/home
2/
NNCP
What is NNCP? NNCP lets you securely send files, or request remote execution, between systems. It uses asynchronous communication, so the source and destination need never be online simultaneously. NNCP can route requests via intermediate devices – other NNCP nodes, USB sticks, tapes, radios, phones, cloud services, whatever – leading to a network that is highly resilient and flexible. NNCP makes it much easier to communicate with devices that lack Internet connectivity, or have poor Internet.
@tidux This is great! #nncpnet is intentionally a few programs and scripts that work with Unix pipes. The reason for the Docker container was to make it easy for people to play with, but it is my explicit goal that it should be, basically, standard. That is, can plug in anywhere. A couple little programs to verify headers and a little nodelist processing and there you go.
Please tag me when you have something ready to use - I'd love to give it a try!
This is a great article by #LWN @lwn about #NNCPNET, which uses #NNCP to form an email network that lets you run real mail servers (even with an Internet bridge) as easily as it used to be! https://lwn.net/SubscriberLink/1031208/2335d9c8b8eb28c5/
Soliman HindyDoes somebody run an #NNCPNET node?
I'm reading this article: https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/home and I'm wondering if I will try it soon.
I'm reading this article: https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/home and I'm wondering if I will try it soon.
My new blog post, Memoirs of the Early #Internet, unearths a few relics of the early Internet and #UUCP days from some obscure sites.
https://changelog.complete.org/archives/10792-memoirs-of-the-early-internet
Researching cool things a person can do with #asynchronous #email over #NNCP (#NNCPNET) led me down that path. So while you're there, you can also check out the post about the NNCPNET Internet email gateway. https://changelog.complete.org/archives/10783-nncpnet-can-optionally-exchange-internet-email
My blog post on #NNCPNET, the #email network atop #NNCP : https://changelog.complete.org/archives/10768-announcing-the-nncpnet-email-network
@jeremiah_ @elb #NNCPNET, the new #NNCP-based email network, now has a bidirectional, opt-in, Internet #email bridge! https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/bridge/intro
This gates Internet email to/from NNCP. The bridge is off by default. It is a full participant in #SPF, #DKIM, #DMARC, and #TLS in both directions.
Yes, now you can get Internet email straight to your #RaspberryPi ! (And even without this, your Pis can email each other!)