Have an old Scanner/Printer that requires an open relay to e-mail out scans? Now you can serve up scanned documents on your home network.
A lot of perfectly good scanners and printers end up in a landfill the day their cloud-email feature stops working -- usually because the auth method it depends on (an open relay, a now-revoked app password) quietly breaks somewhere upstream, and the manufacturer has no reason to fix firmware on hardware that old. If your printer can still email a scan to *somewhere*, lambada plus an SMTP open relay it trusts (its own, deliberately -- see Installation) is enough to keep it useful for years past the cloud feature's death, on hardware as small as a Pi Zero.
This repo builds two independent binaries that share the same
attachments/ directory:
lambada-mta-- a minimal SMTP server. The scanner emails scans to the Pi over SMTP;lambada-mtareceives the message, decodes the attachment, and saves it with an epoch-based filename (e.g.1779867473.pdf) toattachments/. Files older than 24 hours are cleaned up on each incoming message.lambada-web-- serves a listing of those files over HTTP: a page with download links, human-readable file sizes, and "time ago" timestamps, plus aGET /files.jsonAPI used by the zouk Mac client. This is a Go port of the scandalous project's Sinatra web server.
The recommended way to get scans onto your Mac is lambada-web's
listing page -- either through the zouk
client, or just a plain web browser pointed at the Pi (browsers flag
the download as unsafe over plain HTTP, so expect an extra "Keep"
click to confirm it anyway).
Make sure you have git and go installed on the Pi, then...
# Pull down the project
mkdir ~/workspace
cd ~/workspace
git clone git@github.com:woodie/lambada.git
cd lambada
# Fetch dependencies, build both binaries, install them to /usr/local/bin,
# and provision /srv/lambada/attachments for the two services to share
# (prompts for sudo only if those locations aren't already writable)
go mod tidy
make install
# Redirect port 25 -> 2525 so lambada-mta can run as a non-root user.
# lambada-web doesn't need this -- it's reachable directly on 0.0.0.0:8080.
sudo iptables -t nat -A PREROUTING -p tcp --dport 25 -j REDIRECT --to-port 2525
# Install and start both services
sudo cp service/lambada-mta.service service/lambada-web.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now lambada-mta lambada-web
sudo systemctl status lambada-mta lambada-web --no-pager
# Scan something and watch the logs
sudo tail -f /var/log/syslogAt this point lambada-web is already reachable on the LAN at
http://<pi>:8080/ -- nginx below is entirely optional.
Skip this unless you specifically want lambada-web reachable on plain
http://<pi>/ (port 80) instead of :8080:
sudo apt-get update
sudo apt-get install -y nginx
sudo cp service/lambada-web.nginx.conf /etc/nginx/sites-available/lambada-web
sudo ln -sf /etc/nginx/sites-available/lambada-web /etc/nginx/sites-enabled/lambada-web
sudo rm -f /etc/nginx/sites-enabled/default
sudo nginx -t && sudo systemctl reload nginx
# Drop lambada-web to loopback-only now that nginx is fronting it
sudo systemctl edit lambada-web
# [Service]
# Environment=LAMBADA_WEB_LISTEN_ADDR=127.0.0.1:8080
sudo systemctl restart lambada-webSee DEVELOPMENT.md for testing, configuration details, and how to roll the nginx step back.