History and Resume

History and Resume

Languages: English | Français

Since v5.4.0, ngPost records posts in a structured SQLite database instead of relying on the old CSV-only history file.

What is stored

The database tracks each post down to the article level:

• post metadata: name, groups, NZB path, archive name, password state;
• files and articles belonging to the post;
• article status and NNTP attempts;
• enough information to regenerate an NZB or resume missing articles.

The default database is stored next to the config file as ngPost_history.sqlite. You can move it with POST_DB or --post_db.

See Configuration for default paths.

Why SQLite replaced CSV

The legacy POST_HISTORY CSV was useful for a simple log, but it could not track individual articles. SQLite enables:

• reliable resume after network loss or crashes;
• NZB regeneration from history;
• filtering, statistics and actions in the GUI;
• scriptable CLI output with optional JSON;
• explicit import of old CSV history.

GUI workflow

Use the History tab to browse posts, filter results, inspect details, regenerate NZBs, copy or purge stored passwords, and manage resumable posts.

The resume view shows whether a post is fully resumable, partially resumable or not resumable, with article counts so you can decide what to do before sending anything again.

CLI workflow

ngPost --history
ngPost --history_show 42
ngPost --regenerate_nzb 42 -o output.nzb
ngPost --resume_list
ngPost --resume_check 42
ngPost --resume_post 42

Add --json to list/check commands when you need machine-readable output.

Importing legacy CSV history

ngPost --history_import_csv /path/to/POST_HISTORY.csv

The original CSV is preserved. Imported CSV entries are history-only: old CSV files do not contain the article Message-IDs needed for full resume or full NZB regeneration.

For the complete option reference, see Command line usage.