Mail: .eml to PDF not creating PDF

[seeharrison]

I just setup my paperless-ngx to pull mail from a dedicated gmail account and it's working great. I have tika and gotenberg installed and I think they are working properly. I am able to drop a .docx file into my consume folder and it processes and shows up in paperless, so I think tika is working. However, when paperless pulls a new message it processes it and places a .eml file into my repository and not a PDF. When I reviewed the logs, it looks like the PDF conversion process is happening... So I'm truly stumpped! My goal is to have Paperless monitor a gmail account and convert anything that comes in to a PDF and put the PDF in my repository.

Any help would be greatly appreciated!

Here are my logs from when the process is occuring:

[2024-04-07 14:40:00,488] [DEBUG] [paperless.tasks] Executing plugin WorkflowTriggerPlugin

[2024-04-07 14:40:00,489] [INFO] [paperless.tasks] WorkflowTriggerPlugin completed with:

[2024-04-07 14:40:00,498] [INFO] [paperless.consumer] Consuming FW Payment Confirmation  UP Centennial Celebration.eml

[2024-04-07 14:40:00,500] [DEBUG] [paperless.consumer] Detected mime type: message/rfc822

[2024-04-07 14:40:00,579] [DEBUG] [paperless.consumer] Parser: MailDocumentParser

[2024-04-07 14:40:00,582] [DEBUG] [paperless.consumer] Parsing FW Payment Confirmation  UP Centennial Celebration.eml...

[2024-04-07 14:40:00,582] [DEBUG] [paperless.parsing.mail] Parsing file FW Payment Confirmation  UP Centennial Celebration.eml into an email

[2024-04-07 14:40:00,584] [DEBUG] [paperless.parsing.mail] Building formatted text from email

[2024-04-07 14:40:00,585] [INFO] [paperless.parsing.mail] Sending content to Tika server

[2024-04-07 14:40:00,716] [DEBUG] [paperless.parsing.mail] Creating a PDF from the email

[2024-04-07 14:40:00,717] [INFO] [paperless.parsing.mail] Converting mail to PDF

[2024-04-07 14:40:04,211] [INFO] [paperless.parsing.mail] Converting message html to PDF

[2024-04-07 14:40:07,424] [DEBUG] [paperless.parsing.mail] Merging email text and HTML content into single PDF

[2024-04-07 14:40:07,941] [DEBUG] [paperless.consumer] Generating thumbnail for FW Payment Confirmation  UP Centennial Celebration.eml...

[2024-04-07 14:40:07,943] [DEBUG] [paperless.parsing] Execute: convert -density 300 -scale 500x5000> -alpha remove -strip -auto-orient -define pdf:use-cropbox=true /tmp/paperless/paperless-aw8itrvm/merged.pdf[0] /tmp/paperless/paperless-aw8itrvm/convert.webp

[2024-04-07 14:40:08,615] [INFO] [paperless.parsing] convert exited 0

[2024-04-07 14:40:08,690] [DEBUG] [paperless.consumer] Saving record to database

[2024-04-07 14:40:08,691] [DEBUG] [paperless.consumer] Creation date from parse_date: 2024-04-07 19:35:15+00:00

[2024-04-07 14:40:08,856] [INFO] [paperless.handlers] Assigning document type Informational to 2024-04-07 FW: Payment Confirmation:  UP Centennial Celebration

[2024-04-07 14:40:08,914] [DEBUG] [paperless.consumer] Deleting file /tmp/paperless/paperless-ngxz56f6t1s/FW Payment Confirmation  UP Centennial Celebration.eml

[2024-04-07 14:40:08,917] [DEBUG] [paperless.parsing.mail] Deleting directory /tmp/paperless/paperless-aw8itrvm

[2024-04-07 14:40:08,918] [INFO] [paperless.consumer] Document 2024-04-07 FW: Payment Confirmation:  UP Centennial Celebration consumption finished_****

[stumpylog]

Why do you think no PDF is created? If there's no errors, that seems highly unlikely. Are you confused about the original vs the archive?

[seeharrison]

And this is why I consult people smarter than me! I found the PDF and the eml file in the appropriate folders. What was throwing me was the fact that it didn't "render" the html. I opened what I thought was going to be a PDF, so a bunch of raw HTML code and assumed something hadn't worked. Thank you for the clarity and sanity check!

Now to figure out why the HTML isn't being rendered. :-)

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. Please see our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.