Nextpertise a journal of interesting technical ideas . . .

Save to Kindle with a DIY CI

by Brent Stewart on Tuesday, May 9, 2023

My previous post dealt with building an easy way to convert Word files to Markdown and automatically incorporate them in Obsidian. That was accomplished by copying the DOCX file into a directory and having automation to perform the actions to get the file into the right place with the right format. I was pleased with the way that worked out and thought about other places where I’d like to use a similar approach.

Print to Tablet

I’ve always wanted a way to “print to tablet”. I’ve had IPads and Galaxy Tabs and enjoy the form factor - tablets are an easy way to read. But there’s never been a great way to move something I create on my desktop over to the tablet. I’ve resorted to saving it to PDF, emailing it to myself, and then opening it on the tablet. But wait! Because of the way tabllet break up storage, it’s usually confusing to understand where the file is stored and which programs should be used. Bah!

This really galls me because sometimes I’ll print out a document and think, “This would save a lot of paper if I could just print it to my tablet”. The thought of saving printing costs, saving a fraction of a tree, and having the file in a convenient form would really be nice.


How did I get this to work? In my mind, the basic building blocks would be inotifywait (discussed in the previous post), kindle’s email import function and ssmtp (discussed in Command Line Email). Expiriments with ssmtp determined that it’s hard to use with attachments, but researching that led me to mpack.

This project will use inotifywait to monitor a directory. When a file is put in that directory it will be copied out to the kindle app on my tablet. There’s a little longer discussion of inotifywait in the previous post.

Amazon Devices

Amazon provides an email associated with every Kindle, physical or app, that can be used to import files. Sending an email to that address will copy the attached file into the Kindle’s local library (and convert it if needed). You can find this email address two ways - either login to Amazon and navigate to “Accounts & List” and choose “Devices”. From here you can select either a Fire Tablet or a Kindle app and see it’s assigned email address. It will look like You can also go into the kindle app and find it under “More”, then “Settings” and it will be shown as Send to Kindle Email Address.

Amazon calls this function the “Kindle Personal Document Service” and claim that it can convert several types of files. I tested PDF, DOCX, and EPUB and didn’t have any issues.

Table of supported import formats

The last piece is mpack. I used ssmtp in my previous project and found some ideas on how to attach a file using ssmtp, but never got that to work. In the process of researching that issue I found mpack, which uses ssmtp (at least the settings and a library) to send an email with attachment. Install mpack on Ubuntu using sudo apt install mpack. Once it’s installed, here’s a usage example to help you test. The part being echo’d in is the body of the email - unnecessary when sending to kindle. Email subject is set with “-s”. Attachment is defined with “-a”, and then followed by the email address this should go to.

echo "Sent from your linux desktop" | mpack -s "Subject Line" -a "File.TXT" destination_email@ddress

If there are issues, I suggest going back to the ssmtp setup and making sure that part is working.

Mixing it all together.

I defined a directory send2kindle. Anything copied in will be sent to my kindle email address and imported into that kindle library. I created a batch file ( and made it executable. That script is shown below.


inotifywait -m -e create -e moved_to --format "%f" $TARGET | while read FILENAME
  echo Detected $FILENAME
  echo "Sent from your linux desktop" \
  | mpack -s "$FILENAME" -a "send2kindle/$FILENAME"

This follows the logic used in the previous post. Note that the backslash (" \ “) shows line continuation, so the echo and pipe are one line. I did it that way to make it easier to read here. I’ve setup innotify to trigger on something being copied in. The previous discussion has a few more details on that command if you are interested. Note that I leave the files in the directory, so you may need to occassionally clean up and delete them. I could have added a rm command, but I decided that it might be useful to have a copy. Once they’re copied in, they won’t trigger the workflow again.


With everything in place, all that’s left is testing. Run the script and then copy a file into that directory. It should pop into the Kindle library of your choice in less than a minute.

Just like I did in the previous discussion, I recommend settting up the watcher script to start itself after reboot.

crontab -e  # gets us into edit mode
# add below entry
@reboot /home/brent/

In closing

This really extends some of the recent things I’ve been doing in a very useful way. For instance, I can Print from any file and choose “PDF” as the printer. When prompted for a filename, directing that to ~/send2kindle/newfile.pdf will send it to my tablet. It’s not very complex to get setup and working and it “scratches an itch” I had. Hope it is useful to you as well!

Recent articles related to these tags: linux CI shell
Share this article: