Timeline for procmail returning with exit code 0 even if it can't read its config file: How to prevent?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2022 at 12:01 | vote | accept | Binarus | ||
| Jan 24, 2022 at 7:22 | comment | added | Binarus | Regarding the variable usage: I knew that I better should have removed that assignment :-). Yes, I know that TARGET doesn't mean anything to procmail. The sense of it: I have multiple accounts on the Cyrus IMAP server (i.e. multiple fetchmail snippets like the one I've shown, each of them with a different TARGET variable) and would like to use the same procmail configuration / recipes for all of them. In procmailrc, I then have action lines like the following: | cyrdeliver ... ${TARGET}. This works as expected. | |
| Jan 24, 2022 at 7:19 | comment | added | Binarus | Thank for the great answer, +1! I guess I'll give the answer to you since it answers my question better than the first one which I've already accepted (if it turns out that I can use the -m switch for my purpose). | |
| Jan 24, 2022 at 7:18 | history | edited | tripleee | CC BY-SA 4.0 | Log example |
| Jan 24, 2022 at 7:18 | comment | added | Binarus | Regarding the logs: Before posting the question, I did the following (as root): cd /var/log; grep -r procmail * This didn't yield anything interesting: Some entries from the procmail setup process in dpkg.log (I'm on debian), some entries created by fetchmail ("about to deliver with ... procmail ...), and that was it - not a single trace of procmail's actual activity. Likewise, there was nothing helpful on the screen during my tests. | |
| Jan 24, 2022 at 7:14 | history | answered | tripleee | CC BY-SA 4.0 |