Believe it or not, this question is related to a real, production process. Because the company we are working with is run by cave men, I think, but... Yeah. Anyway.
There is a scheduled task on this machine that connects to an email server (using an IMAP utility we wrote in house) and downloads any attachments that have been sent in the last day. This works just fine when we run it under a user account on the system, but that means we have to keep changing the password (read: it means this process fails once a month when we forget to change the password).
Obviously, the standard procedure would be to run it as a system account so that we don't have to worry about that, and we do have some other jobs that run as
NT AUTHORITY\SYSTEM. This one, however, does not. That's because when we try to run this as SYSTEM, it says that it did its job, but the directory that's supposed to contain all of the attachments it downloaded remains empty while the inbox remains full.
IANASA (I am not a sysadmin!): What can I do to make this run? (Preferably without having to set some kind of a reminder on my calendar that says, "Hey, go change the goofy passwords on your batch jobs.")