Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readpst -e output filenames aren't deterministic #15

Closed
martinvonwittich opened this issue Aug 23, 2024 · 2 comments
Closed

readpst -e output filenames aren't deterministic #15

martinvonwittich opened this issue Aug 23, 2024 · 2 comments

Comments

@martinvonwittich
Copy link

When I run readpst -e twice with the same input file:

mkdir readpst.output
mkdir readpst.output2
readpst -e -o readpst.output /root/mail_exchange/Some.User.pst
readpst -e -o readpst.output2 /root/mail_exchange/Some.User.pst

the resulting $ID.eml aren't necessarily in deterministic order. They're still identical e.g. for Inbox/1.eml:

host ~ # grep -i '^Message-ID' readpst.output{,.2}/Some.User/Posteingang/1.eml   
readpst.output/Some.User/Inbox/1.eml:Message-ID: <e26d970c5bd345e1b2818d514fa96624@host>
readpst.output.2/Some.User/Inbox/1.eml:Message-ID: <e26d970c5bd345e1b2818d514fa96624@host>

but not any longer e.g. for Inbox/1000.eml:

host ~ # grep -i '^Message-ID' readpst.output{,.2}/Some.User/Posteingang/1000.eml
readpst.output/Some.User/Inbox/1000.eml:Message-ID: <AM0PR08MB427305D64481B39AE42B116DFB472@AM0PR08MB4273.eurprd08.prod.outlook.com>
readpst.output.2/Some.User/Inbox/1000.eml:Message-ID: <95bb64dd32324624a2dd1a104c4a5452@host>
@martinvonwittich
Copy link
Author

This seems related to #9, but probably a separate issue.

The readpst version I'm using is:

host ~ # apt-cache policy pst-utils
pst-utils:
  Installiert:           0.6.75-1
  Installationskandidat: 0.6.75-1
  Versionstabelle:
 *** 0.6.75-1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
host ~ # readpst -V                
ReadPST / LibPST v0.6.75
Little Endian implementation being used.

@martinvonwittich
Copy link
Author

martinvonwittich commented Aug 23, 2024

OK, this is very likely just a duplicate of #7. I noticed that for the different runs, I was getting a different amount of skipped files. While trying to debug that, I found the report #7. After using -j 0 for two runs, I no longer get different Message-IDs:

host ~ # grep -i '^Message-ID' readpst.output{.1,.2}/Some.User/Posteingang/1.eml            
readpst.output.1/Some.User/Posteingang/1.eml:Message-ID: <e26d970c5bd345e1b2818d514fa96624@host>
readpst.output.2/Some.User/Posteingang/1.eml:Message-ID: <e26d970c5bd345e1b2818d514fa96624@host>
host ~ # grep -i '^Message-ID' readpst.output{.1,.2}/Some.User/Posteingang/1000.eml
readpst.output.1/Some.User/Posteingang/1000.eml:Message-ID: <FA075301-28D2-4520-9CC2-C25879EEF41E@host>
readpst.output.2/Some.User/Posteingang/1000.eml:Message-ID: <FA075301-28D2-4520-9CC2-C25879EEF41E@host>
host ~ # grep -i '^Message-ID' readpst.output{.1,.2}/Some.User/Posteingang/8000.eml
readpst.output.1/Some.User/Posteingang/8000.eml:Message-ID: <06f7280727364b7a9740b6ad228dd51a@host>
readpst.output.2/Some.User/Posteingang/8000.eml:Message-ID: <06f7280727364b7a9740b6ad228dd51a@host>

The emails are still different due to randomly generated boundaries, but that is tracked as #9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant