[Bug 1840035] Re: account default not found: no configuration file available

2019-08-29 Thread Simon Déziel
Hi Peter, If you don't see the value of applying an Apparmor profile to msmtp please disable it. The package should remember this decision on upgrades and not re-enable it behind your back. I do agree that it kinds of defeat the -C option but the Apparmor profile was designed to accommodate the m

[Bug 1840035] Re: account default not found: no configuration file available

2019-08-28 Thread Peter Selinger
Hi Simon, thanks for the explanation. I guess this is a limitation of Apparmor then, rather than a bug of msmtp. I will work around it using one of the methods you suggested. On the bigger question, I don't konw why it makes sense to armor msmtp. Is it an especially untrusted application? For ex

[Bug 1840035] Re: account default not found: no configuration file available

2019-08-14 Thread Simon Déziel
Hi Peter, The failure to read your msmtp's config is probably because it's a symlink that points to a non-standard location that is not authorized by default in the Apparmor profile. The Apparmor profile allows the following locations: /etc/msmtprcr, owner @{HOME}/.msmtp* r, o