pffexport Use & Export¶
One source / one recorded export
Start with a question, such as what does this mailbox show about a changed payment request? Your result should connect the source file, the command, the exported item and the finding. Exporting files alone does not answer the case question.
Prepare the source and paths¶
Open Ubuntu on WSL. Work on an authorised copy, keep the original separate and compare their SHA-256 hashes. Record the account, acquisition or export time, folder/date scope and any known cache limits. Do not open a live mailbox or use personal mail as a substitute for training evidence.
| Windows path | WSL path for the same mounted file |
|---|---|
C:\Cases\Email 01\working\mailbox.pst |
/mnt/c/Cases/Email 01/working/mailbox.pst |
Quote paths containing spaces. WSL Linux paths are case-sensitive in normal Linux storage. For large exports, use approved storage with enough room; Linux tools usually perform better on WSL's Linux filesystem. See Microsoft's WSL filesystem guidance.
Check the installed tools¶
Save the version and help with the case record. Use pffinfo to record basic file information before an export. It does not prove that the source is complete or authentic. The pffinfo manual explains its options.
Read an export command¶
This is a path example, not a supplied dataset. Use the real path of your verified working copy and a new case output name. Create the parent outputs and logs directories first.
pffexport -m items -f text \
-l "/home/analyst/email-case/logs/export.log" \
-t "/home/analyst/email-case/outputs/mailbox" \
"/home/analyst/email-case/working/mailbox.pst"
What goes in¶
The final argument is the source file. -m items selects allocated items, which are items still referenced by the file's structure. It is a useful starting scope for this lesson, not a promise that the file contains every message ever sent.
What comes out¶
-t gives a basename. With this mode, look for mailbox.export, not just mailbox. -l names an item log; keep console output and the exit status too. Use a fresh basename for each attempt.
Choose scope and format deliberately¶
| Choice | Meaning | Beginner starting point |
|---|---|---|
-m items |
Export allocated items | Use for the core lab |
-m recovered |
Export orphan and recovered items | Separate recovery exercise with independent checks |
-m all |
Include allocated, orphan and recovered items | Broader scope; keep categories distinct |
-f text |
Prefer a text body representation | Start here and inspect the actual files |
-f html, rtf or all |
Other preferred body representations | Use when needed; verify what the source makes available |
-d |
Write item values to ItemValues.txt |
Optional property inspection after the core task |
-f chooses body representation; it is not a switch to exclude attachments. Keep extracted attachments separate from execution and do not launch recovered content. The source or installed version may affect available fields and formats. More output does not necessarily mean better evidence.
These options and suffixes follow the upstream manual and command implementation. Recovery is not guaranteed; absence from any export is not proof that an item never existed.
Inspect the output before drawing a conclusion¶
- Read the item log and captured console output. Note warnings, failures, the exit status and whether any useful files were written. A zero exit status is only one check.
- List the output tree. Follow a relevant folder and item, rather than treating every exported file as a separate email.
- Inspect a message's body and available transport headers as text. The exporter can create
InternetHeaders.txtwhen those headers exist. Keep its relationship to the same item's other files. An attachment directory may be namedAttachments; names and layout depend on the item and release. - Record the actual exported path, source mailbox, source folder, subject, addresses, date/time context and available message identifier. Compare selected fields with an independent source view or instructor check.
The export implementation shows that body, headers, recipients and attachments can be separate outputs. Do not assume that a body file is a complete EML or MSG. Preserve the mailbox and the complete relevant item directory, including available contextual files.
What should I look for in an email investigation?
Compare the requested action with an earlier related item and any response. Check addresses as well as display names. An available Message-ID can help identify the item; it does not establish authenticity. Record a field as unavailable if it is missing. A message Date, local file timestamp or export time does not automatically establish delivery or reading.
Check, preserve and explain¶
Hash saved outputs and record their paths. Keep the hash list outside the files it describes. Recheck the working-copy hash after the export. Record the exact command, mode, format, tool version and any errors with the result.
A useful handover has three parts: what the records show, what they cannot establish, and what evidence to check next. A payment request and reply do not prove money moved. Finance records or verification through a known supplier contact may answer the next question.
If something does not work¶
| Problem | First check |
|---|---|
command not found |
Are you in Ubuntu, and was pff-tools installed there? |
| Source not found | Check the quoted WSL path, drive mount and filename case |
| Output already exists | Choose a new basename; retain the earlier attempt and its logs |
| Few or no files | Check source scope, console/item logs and file compatibility; do not claim a complete result |
| No headers or readable body | Record the gap and compare with another approved view of the source |
| Unexpected attachment files | Text preference does not exclude attachments; keep them as evidence without launching them |
The Hands-on Labs practise this workflow with plain-language steps and a blank case worksheet.