For now, I will add this functionality to mftp-doctor.

In the long term though, I feel like it would be better if we could move the entire error management part to mftp itself, like @harshkhandeparkar mentioned below.

ig ideally, mftp doesn't need a separate doctor. it should just handle errors itself.
at the highest level, it is just a loop right? Maybe the loop itself can have a try catch that emails.
and in case it does crash, docker compose healthcheck can be used to revive it
this way, doctor also doesn't have to connect to naarad. mftp itself will send the warning.