> 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 they're running msmtp from cron.
Thanks for clarification.
> That being said, the more I look into this, the more I feel this is
> really a cron bug. msmtp's logic is to use the value of HOME, if set,
> and to fall back on the password database otherwise. This seems
> utterly reasonable. On the other hand, cron's setting of HOME
> violates convention and expectation, suggesting that cron is the poor
> player here.
I agree that it's not a msmtp bug and you should submit this feature
request to the multiple vixie-cron's compatible programs developers.
> It would be nice if this incompatibility, its cause, and the potential
> workaround you mentioned were at least documented. There's abundant
> evidence that I'm not the only one who has sunk hours of their life
> into figuring out why cron and msmtp don't play nicely.
As a workaround it could be possible to use a wrapper in your own
crontabs.
exemple:
--8<---------
* * * * * mywrapper.sh my_command --option1 --option2
--------->8--
This wrapper will run 'my_command --option1 --option2' and catch
stderr/stdout and the return code to pipe them (if necessary) to msmtp.
Hence it will be possible to use your own msmtp configuration.
Regards,
--
Emmanuel Bouthenot
mail: kol...@{openics,debian}.org gpg: 1024D/0x414EC36E
xmpp: [email protected] irc: kol...@{freenode,oftc}
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
