I think it would be good for us to do some testAccount.expect_runOp('downloadBodyReps', {}) calls here.  Since there is a potential race (not terribly likely, but potential), I think it might make sense to just have 2 downloadBodyReps: true calls followed by a withBodyReps call and not have any chaining in place to rule out the potential for the job to never be issued.

```
// only the first job will actually download the bodies, the other jobs will still happen but will turn into no-ops
testAccount.expect_runOp('downloadBodyReps', { save: 'server' }); // this might need conn: true/etc.
testAccount.expect_runOp('downloadBodyReps', { save: false });
testAccount.expect_runOp('downloadBodyReps', { save: false });
```

Ideally we could also put an expectation on the sync too to make sure that we're only trying to talk to the server once.  It doesn't look like POP3 currently has a good logging event to hang off of this and in general it seems like the gymnastics aren't yet justified since we haven't actually regressed on this.  So, I think the save event may be a sufficient proxy for now.

This may also let you remove the set matching mode.