1. 8
    1. 3

      I have a similar scanner and went a different route. The scanner can talk SFTP and so I wrote a custom sftp-server replacement that runs sandboxed, reads files into shared memory objects, and then hands them off to another process. Mine then does OCR and files them according to patterns defined in Lua, but you could easily make it send email instead.

      1. 3

        Go is really well-suited for this kind of thing :)

        My solution for scanning in Go, directly pushing PDFs to Google Drive (meaning you get full-text search): https://github.com/stapelberg/scan2drive

        1. 2

          I thought it’d be in reference to https://en.wikipedia.org/wiki/Internet_fax

          Fax machine → Phone line → Fax gateway → email message (over Internet) → computer email account
          Computer → Internet → fax gateway → phone line → fax machine
          
          1. 2

            Sadly no mention on that page of tpc.int which was the 1990s version of email to fax

            https://www.rfc-editor.org/rfc/rfc1528

            https://www.rfc-editor.org/rfc/rfc1529

            https://www.rfc-editor.org/rfc/rfc1530

            (tpc = the phone company; the domain was allocated in that period of confusion about what .int was for that also caused ip6.int)

            tpc.int relied on volunteers to run the email-to-fax gateways, and it had a bespoke DNS server that could translate big endian phone numbers into little endian domain names that were delegated hierarchially to the volunteers.

            So if you wanted to fax a former employer of mine you could send email to remote-printer@441223334400.tpc.int which was equivalent to remote-printer@334400.1223.44.tpc.int or remote-printer@0.0.4.4.3.3.3.2.2.1.4.4.tpc.int etc usw. The domain 44.tpc.int aka 4.4.tpc.int was delegated to Demon Internet (another former employer of mine) who provided an email to fax service for the whole of the UK.