forcemerge 919323 919326
thanks
Hi,
On Mon, Jan 14, 2019 at 04:40:36PM -0600, Sergio Mendoza wrote:
[...]
> A few days ago, msmtp fails to work. It all seems to be related to the
> inability to read ~/.msmtprc file. In other words it seems that
Merging and closing this bug as it is fixed
On 2019-01-14 6:03 p.m., Sergio Mendoza wrote:
> Yes. I have now checked and I have .msmtprc as a symlink. If it is not
> a symlink then I have no problems and everything runs smooth.
Great, thanks Sergio.
> In any case
> this is the output you asked for:
>
> root@quetzalli:~# dmesg | grep
Hi Sergio,
On 2019-01-14 5:40 p.m., Sergio Mendoza wrote:
> A few days ago, msmtp fails to work. It all seems to be related to the
> inability to read ~/.msmtprc file. In other words it seems that
> ~/.msmtprc needs to have mode 644. This is not at all desired since
> sensible (private)
Dear Simon,
Yes. I have now checked and I have .msmtprc as a symlink. If it is not
a symlink then I have no problems and everything runs smooth. In any case
this is the output you asked for:
root@quetzalli:~# dmesg | grep apparmor | tail -n 20
[1064093.935900] audit: type=1400
Package: msmtp
Version: 1.8.1-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
A few days ago, msmtp fails to work. It all seems to be related to the
inability to read ~/.msmtprc file. In other words it seems that
~/.msmtprc needs to have mode 644. This is not at
5 matches
Mail list logo
