You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
strings /usr/sbin/cron | grep sendmail. That's usually a symbolic link to the actual mta.loggeror whatever. There probably already are ready-made debian packages which do just that.config.h(cron sources) you have#define MAILARG _PATH_SENDMAIL. Inpathnames.h(cron sources), you have a#definewhich sets_PATH_SENDMAIL, but this is not relevant because_PATH_SENDMAILalready is defined here by the inclusion of<paths.h>(glibc sources), and there you finally have#define _PATH_SENDMAIL "/usr/sbin/sendmail". To change the script's location, you could write#define MAILARG "/your/own/path/to/script"inconfig.hand recompile cron./usr/sbin/sendmaila symbolic link pointing to the custom script? Then you'll have the same problem as my solution: What if the "real" program expected there is needed? I fear that there is no other way than recompiling to solve this problem .../usr/sbin/sendmail, and make it figure out who has called it when it is executed. If cron has called it, make it behave as described in my solution; if not, let it just call the "real" sendmail binary (wherever you have moved it to) with the same arguments and stdin (that is, just let the script "relay" the arguments and stdin to sendmail).