Do not call mh-next-msg from mh-junk-process-* fns
* mh-junk.el (mh-junk-process-blacklist, mh-junk-process-whitelist): Do not call mh-next-msg. Now that these functions are called from mh-execute-commands, they should not change the current message pointer. The calls to mh-next-msg are probably left over from when blacklist and whitelist message processing was done immediately.
Showing with 2 additions and 4 deletions