Tip of the day: The beauty of the paperless office is that you can automate workflows. But maybe you are not familiar with all the capabilities of automation in #DEVONthink or don’t know when which one makes sense? Here are the main options and when it’s best to use each. #automation #paperless #pkm #productivity #tipoftheday #workflow https://www.devontechnologies.com/blog/20230620-automation-options

Tip of the day: #DEVONthink is a good place to build a digital book collection. Users of the Pro or Server edition of #DEVONthink can add custom metadata to their books from the millions of books available in Google Books with a script. Here is, how to do that. #academics #automation #paperless #pkm #productivity #research #tipoftheday #workflow https://www.devontechnologies.com/blog/20230328-google-books-metadata

Digitalisierung von Dokumenten könnte kaum einfacher sein.
Brief auf Scanner legen. 1 Knopf drücken. #Paperless macht den Rest

natürlich #selfhosting

Paperless-ngx:

Mal ein deutlich besser gemachtes Video zu Paperless-ngx. Die Installation finde ich zwar zu umständlich, aber es werden recht praxisnah und ausführlich die Grundlagen erklärt. Ein bisschen Storytelling mit kleinen Videos ist auch dabei. (Hat sogar über 50.000 Aufrufe.)

#paperless #paperlessngx #selfhosted

https://www.youtube.com/watch?v=WRyBPMH9zf0&list=WL&index=2

In theory, I have almost everything I wanted to have self-hosted on my small server:
- #nextcloud for files, calendar, storing notes from #joplin
- #immich for photos
- #vikunja for my ToDo
- #pihole
- #paperless for digital copies of important documents
And these are my must-have.

I have few more things that are nice (like Jellyfin and few more) but it's for future.

However, I'm too scared to ditch cloud solutions, that I will lose my data because of my stupidity

Fixing PaperlessNGX Email Processing Issues After Restart

When running PaperlessNGX in Docker, I encountered an issue where certain emails were not processed after restarting the Paperless container in the middle of a batch processing operation. Paperless saw the emails in the inbox but incorrect

ly marked them as already processed.

Identifying the Issue

The first step to diagnose the issue was to check the mail.log file within Paperless. The log provided information on which emails were skipped from processing, including their unique IDs. For example:

[2025-02-17 09:50:03,084] [DEBUG] [paperless_mail] Skipping mail '321' subject 'Email from Epson WF-4830 Series' from 'scanner@example.com', already processed.

Logging into the Database

To access the Paperless database running inside a Docker container, I used the following command:

docker compose exec db /bin/bash

This command opens a bash shell inside the db service container, allowing further interaction with PostgreSQL.

Resolving the Issue

To resolve the issue, I connected to the Paperless database, which was running on PostgreSQL. Using the provided email UID from the mail.log, I deleted the corresponding entries from the paperless_mail_processedmail table to allow Paperless to process the email again.

psql -U paperless_db_user

Here’s the SQL command I used:

DELETE FROM paperless_mail_processedmail WHERE uid = '322';

After running this command for every of the reported mails that are skipped, Paperless successfully reprocessed the emails during the next processing cycle.

Conclusion

If you encounter similar issues with PaperlessNGX not processing certain emails after a restart, checking the mail.log and manually deleting the processed mail entries from the database can be an effective solution.