control: severity -1 wishlist
I think this old bug report is not really valid any more with recent
msmtp I tested.
Now we have -C option for msmtp, user doesn't need to rely on $HOME. So
not even wrapper script is needed. In that sense, this is not even a
bug.
But as a user support pointer, I
I'm aware of this. Perhaps my bug should have been per-user
configuration is incompatible with vixie cron. Personally, I'm
unwilling to put sensitive information in a world-readable file.
Furthermore, people shouldn't be prohibited from using per-user
configuration files simply because
Hi Austin,
vixie-cron runs /usr/sbin/sendmail with the HOME environment variable
set to /. Because msmtp looks for per-user configuration in
$HOME/.msmtp, it will fail to find the configuration file of the user
cron is sending mail on behalf of. On a system that depends on
per-user
Thanks for the quick reply.
Maybe you missed that msmtp is able to use a system wide configuration
file: /etc/msmtprc
I'm aware of this. Perhaps my bug should have been per-user
configuration is incompatible with vixie cron. Personally, I'm
unwilling to put sensitive information in a
Package: msmtp
Version: 1.4.19-1
Severity: normal
vixie-cron runs /usr/sbin/sendmail with the HOME environment variable
set to /. Because msmtp looks for per-user configuration in
$HOME/.msmtp, it will fail to find the configuration file of the user
cron is sending mail on behalf of. On a
5 matches
Mail list logo
