After an urgent inquiry re my health from a friend, I discovered
that e-mails had not been getting out of my machine for 7 days .
I tracked the problem down to a change in /etc/group
when I updated Ssmtp 2.61-r2 -> 2.62-r3 :
there's a new entry 'ssmtp', which needs to be enabled for '<user>'.
There was 1 line in the file in /var/log/emerge-logs/ ,
which didn't explicitly warn that sysadmin action was required,
but nothing anywhere else AFAICS, incl in the 'man' file.
Has anyone else got caught by this ?
--
========================,,======================== ====================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
09-22-2008, 07:40 AM
Etaoin Shrdlu
Ssmtp gotcha
On Monday 22 September 2008, 06:26, Philip Webb wrote:
> After an urgent inquiry re my health from a friend, I discovered
> that e-mails had not been getting out of my machine for 7 days .
> I tracked the problem down to a change in /etc/group
> when I updated Ssmtp 2.61-r2 -> 2.62-r3 :
> there's a new entry 'ssmtp', which needs to be enabled for '<user>'.
> There was 1 line in the file in /var/log/emerge-logs/ ,
> which didn't explicitly warn that sysadmin action was required,
> but nothing anywhere else AFAICS, incl in the 'man' file.
>
> Has anyone else got caught by this ?
Yes, I saw that. I had to add the users who use ssmtp to the ssmtp group
(or, alternatively, chmod 755 the binary). There is a bug on b.g.o.:
http://bugs.gentoo.org/show_bug.cgi?id=237932
which links to the interesting one:
http://bugs.gentoo.org/show_bug.cgi?id=187841
09-24-2008, 01:58 AM
"Mark Shields"
Ssmtp gotcha
On Mon, Sep 22, 2008 at 3:40 AM, Etaoin Shrdlu <shrdlu@unlimitedmail.org> wrote:
On Monday 22 September 2008, 06:26, Philip Webb wrote:
> After an urgent inquiry re my health from a friend, I discovered
> that e-mails had not been getting out of my machine for *7 days .
> I tracked the problem down to a change in */etc/group
> when I updated Ssmtp *2.61-r2 *-> *2.62-r3 :
> there's a new entry 'ssmtp', which needs to be enabled for '<user>'.
> There was *1 line *in the file in */var/log/emerge-logs/ ,
> which didn't explicitly warn that sysadmin action was required,
> but nothing anywhere else AFAICS, incl in the 'man' file.
>
> Has anyone else got caught by this ?
Yes, I saw that. I had to add the users who use ssmtp to the ssmtp group
(or, alternatively, chmod 755 the binary). There is a bug on b.g.o.:
http://bugs.gentoo.org/show_bug.cgi?id=237932
which links to the interesting one:
http://bugs.gentoo.org/show_bug.cgi?id=187841
I was wondering about this.* I ended up making it world executable like you mentioned.* The day before I went on vacation the Gentoo box at work stopped regularly e-mailing.* What a pain.
--
- Mark Shields
09-26-2008, 05:46 AM
"Walter Dnes"
Ssmtp gotcha
On Mon, Sep 22, 2008 at 12:26:13AM -0400, Philip Webb wrote
> After an urgent inquiry re my health from a friend, I discovered
> that e-mails had not been getting out of my machine for 7 days .
> I tracked the problem down to a change in /etc/group
> when I updated Ssmtp 2.61-r2 -> 2.62-r3 :
> there's a new entry 'ssmtp', which needs to be enabled for '<user>'.
<ELVIS>Thank you, thank you, thank you verrry, verrry much</ELVIS>
I got a totally useless error message using ssmtp after the same
upgrade. I reverted to 2.61-r2, and was about to send a query to the
list, but I checked first.