On Sun, May 24, 2015 at 03:34:09AM +0200, [email protected] wrote
> 
> What reasons disable fcron to send mail to me or root?

  By convention, it seems that all MTAs have symlinks at
/usr/bin/sendmail /usr/lib/sendmail and /usr/sbin/sendmail.  Programs
that automatically send email, expect to find "sendmail" symlinks.  Do
you have those symlinks from msmtp?

  My most embarressing linux moment was when ssmtp sent output from
verbose cron jobs to root (at me).  My ssmtp was configured to simply
re-route everything to my ISP's MTA.  The net result was that the output
went to root@my_ISP "They were not amused".  That was when I learned
about setting the destination for all userids < 10 to myself.  I also
ran a script designed to break the symlinks and prevent portage from
making sendmail symlinks...

rm -r /usr/bin/sendmail
rm -r /usr/lib/sendmail
rm -r /usr/sbin/sendmail
mkdir /usr/bin/sendmail
touch /usr/bin/sendmail/.keep
mkdir /usr/lib/sendmail
touch /usr/lib/sendmail/.keep
mkdir /usr/sbin/sendmail
touch /usr/sbin/sendmail/.keep

  That worked great for a few years.  Portage output an error message
about being unable to symlink, but continued.  Then portage changed the
failure mode to shut down portage when it was unable to create
symlinks... AAARRRGGGHHH.  Now when that happens, I remove the
"sendmail" directories, run emerge to build ssmtp, and then run the
script to break the symlinks.  I know that it's redundant, after setting
destination for uid < 10, but "once burned, twice shy".

-- 
Walter Dnes <[email protected]>
I don't run "desktop environments"; I run useful applications

Reply via email to