Prevent cron sending error messages
Clash Royale CLAN TAG#URR8PPP
I have cron set to run a task for user pi (on my Raspberry Pi running Raspbian Stretch) every 15 minutes.
6,21,36,51 * * * * /usr/bin/mosquitto_sub -h Pi3Plus.local -v -C 1 -t weather >> weather.log
I also have ssmtp setup to send email via gmail.
Every so often the cron task fails to connect to the server, and generates an error message.
The problem is that it then attempts to send a message to user pi, which ssmtp changes to pi@gmail and sends to gmail, where it fails.
I have read the man for ssmtp, ssmtp.conf, cron, crontab but cannot find anything to stop these messages.
I could write a script to trap error messages in the cron task to prevent it generating an error.
cron ssmtp
add a comment |
I have cron set to run a task for user pi (on my Raspberry Pi running Raspbian Stretch) every 15 minutes.
6,21,36,51 * * * * /usr/bin/mosquitto_sub -h Pi3Plus.local -v -C 1 -t weather >> weather.log
I also have ssmtp setup to send email via gmail.
Every so often the cron task fails to connect to the server, and generates an error message.
The problem is that it then attempts to send a message to user pi, which ssmtp changes to pi@gmail and sends to gmail, where it fails.
I have read the man for ssmtp, ssmtp.conf, cron, crontab but cannot find anything to stop these messages.
I could write a script to trap error messages in the cron task to prevent it generating an error.
cron ssmtp
add a comment |
I have cron set to run a task for user pi (on my Raspberry Pi running Raspbian Stretch) every 15 minutes.
6,21,36,51 * * * * /usr/bin/mosquitto_sub -h Pi3Plus.local -v -C 1 -t weather >> weather.log
I also have ssmtp setup to send email via gmail.
Every so often the cron task fails to connect to the server, and generates an error message.
The problem is that it then attempts to send a message to user pi, which ssmtp changes to pi@gmail and sends to gmail, where it fails.
I have read the man for ssmtp, ssmtp.conf, cron, crontab but cannot find anything to stop these messages.
I could write a script to trap error messages in the cron task to prevent it generating an error.
cron ssmtp
I have cron set to run a task for user pi (on my Raspberry Pi running Raspbian Stretch) every 15 minutes.
6,21,36,51 * * * * /usr/bin/mosquitto_sub -h Pi3Plus.local -v -C 1 -t weather >> weather.log
I also have ssmtp setup to send email via gmail.
Every so often the cron task fails to connect to the server, and generates an error message.
The problem is that it then attempts to send a message to user pi, which ssmtp changes to pi@gmail and sends to gmail, where it fails.
I have read the man for ssmtp, ssmtp.conf, cron, crontab but cannot find anything to stop these messages.
I could write a script to trap error messages in the cron task to prevent it generating an error.
cron ssmtp
cron ssmtp
edited Feb 8 at 4:19
Milliways
asked Feb 8 at 4:00
MilliwaysMilliways
556823
556823
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
From the crontab manual:
In addition to LOGNAME, HOME, and SHELL, cron(8) will look at MAILTO
if it has any reason to send mail as a result of running commands in
"this" crontab. If MAILTO is defined (and non-empty), mail is sent to
the user so named. If MAILTO is defined but empty (MAILTO=""), no
mail will be sent. Otherwise mail is sent to the owner of the
crontab.
Simply add the variable to the top of the crontab file, as shown in this example (taken from the same man page, slightly edited for clarity):
# mail any output to 'paul', no matter whose crontab this is
MAILTO=paul
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499397%2fprevent-cron-sending-error-messages%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the crontab manual:
In addition to LOGNAME, HOME, and SHELL, cron(8) will look at MAILTO
if it has any reason to send mail as a result of running commands in
"this" crontab. If MAILTO is defined (and non-empty), mail is sent to
the user so named. If MAILTO is defined but empty (MAILTO=""), no
mail will be sent. Otherwise mail is sent to the owner of the
crontab.
Simply add the variable to the top of the crontab file, as shown in this example (taken from the same man page, slightly edited for clarity):
# mail any output to 'paul', no matter whose crontab this is
MAILTO=paul
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
add a comment |
From the crontab manual:
In addition to LOGNAME, HOME, and SHELL, cron(8) will look at MAILTO
if it has any reason to send mail as a result of running commands in
"this" crontab. If MAILTO is defined (and non-empty), mail is sent to
the user so named. If MAILTO is defined but empty (MAILTO=""), no
mail will be sent. Otherwise mail is sent to the owner of the
crontab.
Simply add the variable to the top of the crontab file, as shown in this example (taken from the same man page, slightly edited for clarity):
# mail any output to 'paul', no matter whose crontab this is
MAILTO=paul
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
add a comment |
From the crontab manual:
In addition to LOGNAME, HOME, and SHELL, cron(8) will look at MAILTO
if it has any reason to send mail as a result of running commands in
"this" crontab. If MAILTO is defined (and non-empty), mail is sent to
the user so named. If MAILTO is defined but empty (MAILTO=""), no
mail will be sent. Otherwise mail is sent to the owner of the
crontab.
Simply add the variable to the top of the crontab file, as shown in this example (taken from the same man page, slightly edited for clarity):
# mail any output to 'paul', no matter whose crontab this is
MAILTO=paul
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
From the crontab manual:
In addition to LOGNAME, HOME, and SHELL, cron(8) will look at MAILTO
if it has any reason to send mail as a result of running commands in
"this" crontab. If MAILTO is defined (and non-empty), mail is sent to
the user so named. If MAILTO is defined but empty (MAILTO=""), no
mail will be sent. Otherwise mail is sent to the owner of the
crontab.
Simply add the variable to the top of the crontab file, as shown in this example (taken from the same man page, slightly edited for clarity):
# mail any output to 'paul', no matter whose crontab this is
MAILTO=paul
# run five minutes after midnight, every day
5 0 * * * $HOME/bin/daily.job >> $HOME/tmp/out 2>&1
edited Feb 8 at 6:22
answered Feb 8 at 4:57
HaxielHaxiel
3,0701918
3,0701918
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499397%2fprevent-cron-sending-error-messages%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown