Am Mon, 20 Jul 2015 10:23:30 -0400
schrieb "Walter Dnes" :
> On Mon, Jul 20, 2015 at 01:21:56PM +0200, Marc Joliet wrote
>
> > This choice came about because I switched from fcron to systemd-cron,
> > which runs its mail_on_failure script as user "nobody", which caused
> > my current "passwordeva
On 21/07/2015 00:24, Mick wrote:
> On Monday 20 Jul 2015 22:50:31 Walter Dnes wrote:
>> On Mon, Jul 20, 2015 at 06:49:00PM +0100, Mick wrote
>>
>>> This is all good and dandy, but letting user "nobody" read your
>>> mail accoutn passwd may not be the safest approach to sending email
>>> messages fr
On 20/07/2015 23:50, Walter Dnes wrote:
> On Mon, Jul 20, 2015 at 06:49:00PM +0100, Mick wrote
[snip]
> You can tell it to run a script that contains that command. Having
> passwords floating around on disk in clear text is a *BAD* idea. Some
> "user friendly distros", like Ubuntu, let you r
On Monday 20 Jul 2015 22:50:31 Walter Dnes wrote:
> On Mon, Jul 20, 2015 at 06:49:00PM +0100, Mick wrote
>
> > This is all good and dandy, but letting user "nobody" read your
> > mail accoutn passwd may not be the safest approach to sending email
> > messages from your machine.
>
> I think you
On Mon, Jul 20, 2015 at 06:49:00PM +0100, Mick wrote
> This is all good and dandy, but letting user "nobody" read your
> mail accoutn passwd may not be the safest approach to sending email
> messages from your machine.
I think you missed the point. The "NOPASSWD:" option means that this
one pa
On Monday 20 Jul 2015 15:23:30 Walter Dnes wrote:
> On Mon, Jul 20, 2015 at 01:21:56PM +0200, Marc Joliet wrote
>
> > This choice came about because I switched from fcron to systemd-cron,
> > which runs its mail_on_failure script as user "nobody", which caused
> > my current "passwordeval" command
On Mon, Jul 20, 2015 at 01:21:56PM +0200, Marc Joliet wrote
> This choice came about because I switched from fcron to systemd-cron,
> which runs its mail_on_failure script as user "nobody", which caused
> my current "passwordeval" command ("cat somefile", somefile having
> a mode mask of 0600)
OK, I finally solved this, albeit a bit differently... by switching to
nullmailer.
The TL/DR summary is: use the right tool for the job. Some more details follow
below.
Nullmailer was very easy to set up (the deceptively short HOWTO is pretty much
all that is needed). The only problem is that t
8 matches
Mail list logo
