XstReader Use & Export¶
Use & Export / a practical workflow
Answer one case question at a time. For example: What does this mailbox show about a request to change an invoice's payment details? Your first useful result is a traceable observation, not a whole-mailbox export.
Your outcome: a relevant message, a checked export and a finding another analyst can trace.
Prepare and open a working copy¶
- Obtain an authorised PST or OST, its source details and the case question. Keep the original separate. Record the account, acquisition or export time, scope and any cache limits.
- Make a working copy. Compare its SHA-256 hash with the original and the supplied source hash. Record the viewer version and the examination time zone.
- In XstReader choose File → Open .ost or .pst file. Select the working copy. Wait for the folder tree to load; a large or damaged file may take time.
- Check the source filename and expected folders before searching. Do not assume every folder or every date is present.
SHA-256 means a file fingerprint
Matching hashes show that the copied bytes match the original. They do not prove that the mailbox is complete or that its messages are authentic.
Get to know the window¶
| Area | What to do | Useful habit |
|---|---|---|
| Folders Tree, on the left | Select Inbox, Sent Items or another relevant folder | Record the folder with each observation |
| Message List, at the top | Select a message; compare Subject, From, To, Cc and Date | Check addresses as well as display names |
| Message pane, below the list | Read the body, recipients and attachment list | Note attachment names without launching them |
| Information, on the right | Check the selected item and its source context | Make sure the selected item is the one you intend to record |
| Properties tab | Inspect the properties available for that item; use the save icon to export properties to CSV | Keep a stable identifier such as Internet Message Id, when present |
The final installation screenshot shows the default layout before a file is loaded. Layout can change the panel arrangement; return to the default if a panel is missing.
Find a conversation¶
Filter the selected folder
Type a distinctive term, such as 4821, in the filter above Message List. This filters the current folder's displayed list fields. It is not a search of every folder or the full message body. Use the clear control to remove the filter, select another folder and repeat your search there.
Check the rest of the conversation
Start with an invoice number or a known address. If nothing appears, check the selected folder, clear the filter and try a simpler term. Examine Sent Items as well as Inbox when looking for a response. A similar subject helps you find candidates; compare addresses, message identifiers and available reply properties before linking messages.
Read the item in context¶
Read the whole relevant message. Compare its requested action with the earlier message and any response. Look for changes in payment instructions, urgency or a request to bypass an established process. A suspicious request is a lead to investigate, not proof of compromise.
Open Properties and look for Internet Message Id (PidTagInternetMessageId) where available. Transport headers may also be present, depending on the item. Record a field as unavailable if it is absent. Do not infer authentication results or a route through mail servers from a sender address alone.
Record the displayed date and your examination time zone. Check how your version displays dates before comparing sources. The browser lab explicitly uses UTC; that teaching choice does not establish the real application's time conversion.
What should my first observation say?
Use: source file → folder → item → observation → limit.
Example: “In working copy A, Inbox, the message with subject ‘updated payment details’ asks the recipient to replace the previous account. I recorded its message identifier and displayed date. This message alone does not establish whether the payment was made.”
Choose the right export¶
Open Export Options before exporting. Then select the intended item and choose Message → Export Message. Choose a separate case output folder when prompted. The application can create more than one output if you enable several formats.
| Output | What it is useful for | What to check |
|---|---|---|
| Outlook MSG | A message output for compatible viewers | Reopen it in an approved tool; compare its fields with the source |
| Single HTML | A readable report that can include details and embedded attachments | Check the selected HTML options and inspect the actual output |
| Original format without headers | The original body format, without message headers | This is not a complete message or a substitute for the source mailbox |
| Properties CSV | A property list from the Properties pane's save control | Confirm the selected item, property names and values |
| Attachments as files | Separate attachment outputs, if needed and authorised | Record the parent item, filename and output hash; do not launch unknown content |
For an initial review, choose Single HTML, keep Show Details section enabled and turn off Embed Attachments inside Html file and Export Attachments as files. Verify the result: a checkbox setting is not proof of what was saved. Preserve the mailbox source and note any omitted material. Exporting HTML does not make untrusted message content safe; review outputs in your approved analysis environment.
Scope matters. File and Folder menus also offer bulk exports. Use the Message menu when you need just the selected message. Check the scope, output directory and filenames before and after every export.
Check and hand over¶
Reopen the saved output in an approved viewer. Compare its subject, addresses, date, message identifier and body with the selected source item. Record any missing fields. Hash the saved output and keep its path, format, options and source in the case note. Hash the working copy again and compare it with its pre-examination value.
Give the incident lead a short finding, supporting identifiers, the relevant outputs, a limitation and a next check. For a payment request, independent finance records and a verified supplier contact are more useful next checks than assuming a reply proves payment.
If something does not work¶
| What you see | Try this |
|---|---|
| Empty results | Clear the current folder's filter; check another folder and the source scope |
| Missing property | Record it as unavailable; check another relevant item or approved examination tool |
| File will not open | Check the release, runtime, permissions and verified copy; record the error rather than repairing the original |
| Unexpected export | Check Message versus Folder/File scope, enabled formats, HTML options and the output directory |
| File remains open | Use File → Close file before changing cases |
These instructions follow the iluvadev viewer documentation, application menus and export options. The separate XstExporter command-line application is outside this guide.