imapbackup

A Python script for incremental backups of IMAP mailboxes

Runs with mockssource: GitHubhomepagePythonMITcommit fc5d02e39647

Python, MIT licensed. The project labels itself: backup, imap, imap mailbox, mail and python.

imapbackup runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.0 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

imapbackup312.py runs against IMAP servers, downloads messages to mbox files with incremental dedup, and exits 0. Both the 3.12 and 3.8 variants work with the mock server. The 2.x legacy script has a Python 3 syntax error as documented.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
347
forks
69
open issues
0
watchers
14
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing imapbackup, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • imapbackup.py (Python 2.x) has SyntaxError on Python 3 - print statement not parentheses0 minutes
Install time
under a minute
Cold machine to finish
5 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
python3 imapbackup312.py against mock IMAP server: exit 0, 2 messages per folder written to valid mbox files verified via mailbox.mbox; incremental backup showed 0 new messages; quiet mode produced no output; thunderbird mode produced correct filenames; all modes exit 0
Model tokens used
178,586
Exact commit tested
fc5d02e39647
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

22:20:33 I File INBOX.mbox: not found
22:20:33 I INBOX.mbox: 306 bytes total, 155 bytes largest
22:20:33 I Disconnecting
Mbox len: 2
  [email protected], Subj=Hello, MID=<19AF1258-1AAF-44EF-9D9A-731079D6FAD7.ca7185304d246aa8b1b…
  [email protected], Subj=Re: Hello, MID=<19AF1258-1AAF-44EF-9D9A-731079D6FAD7.2c275120f6fa359c1…
VALID MBOOK: messages=2
exec
/bin/sh -lc 'pkill -f mock_imap_server 2>/dev/null; echo done' in /work/repo
 exited 143 in 0ms:
tokens used
178,586

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 0.0 minutes, faster than the median of the 47 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 48 backup projects Argusic has installed and timed, imapbackup was the 2nd fastest to reach a running state, and 32 of 48 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

backupimapimap-mailboxmailpython

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/imapbackup.svg)](https://argusic.com/subject/imapbackup)

Questions

Does imapbackup run?
imapbackup runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test imapbackup?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit fc5d02e39647. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test imapbackup?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does imapbackup take to install?
0.0 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does imapbackup need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing imapbackup?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does imapbackup compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, imapbackup was the 2nd fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for imapbackup?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion