Re: How getmail deals with delivery errors and with bounce e-mails

 > [...]
> The common UNIX software practice is to have error messages sent to stderr and
> use a non-zero exit status to alert other programs of issues.

You did say "and" above, but that is not what getmail does. It writes errors to stderr and exits with a zero exit status, indicating no 
trouble, yet it did not process some e-mails because they failed.

You did read what I said about backing up with tools like rsync and tar, if they did that, didn't you?


> When run from cron as is commonly done for getmail, each time getmail writes an error to stderr and/or exits with a non-zero status,

You do know that there are other ways, like systemd, do you? It is not common in the Unix world to infer errors just from the presence of 
text in stderr. I have written here a couple of times that sometimes you get warnings (not errors) on stderr, and sometimes, while 
troubleshooting, you need to enable tracing to stderr. You did read all that detailed reasoning in my previous mail, did you?


 > [...]> Your lack of experience is showing.

Quit discrediting me already. If someone needs to pay attention, or learn at least good manners, it's you.

rdiez