public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Sullivan <msulli1355@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Not getting cron emais that should go to root user
Date: Mon, 27 Jul 2009 12:58:10 -0500	[thread overview]
Message-ID: <1248717490.14851.16.camel@camille.espersunited.com> (raw)

For a long time I haven't gotten cron reports from one particular box on
my network.  I've been seeing these lines in my /var/log/cron.log file:

27-Jul-09 12:00  unable to exec /usr/lib/sendmail -t, user -oem, output
to sink null27-Jul-09 12:09  failed user root parsing pr 2002; Thilo
Bangert <bangert@gentoo.org>

I don't know why it's trying to use sendmail; I use exim.  The server is
actually on the same box that's giving me this problem, but the other
two boxes on the network use ssmtp forwarding to forward their mail to
this box, and I get their cron reports.  

There's nothing in the exim logs about this.




             reply	other threads:[~2009-07-27 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 17:58 Michael Sullivan [this message]
2009-07-27 19:38 ` [gentoo-user] Re: Not getting cron emais that should go to root user walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1248717490.14851.16.camel@camille.espersunited.com \
    --to=msulli1355@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox