Bugzilla Bug 237932

After updgrading to 2.62-r3, ssmtp failed to be running by cron, apache, etc...
The permissions on /usr/sbin/ssmtp were 755 before upgrade, and after 750.

So, you need to : 
- add all users who send mail to ssmtp group
- or chmod 755 /usr/sbin/ssmtp


Reproducible: Always

Steps to Reproduce:

Perhaps the ebuild should warn users very loudly to check groups for users that
need to be able to use ssmtp.

(In reply to comment #1)
> Perhaps the ebuild should warn users very loudly to check groups for users that
> need to be able to use ssmtp.
> 

Yes, but there are a lot of users who could send mail (cron, apache, ...) and
perhaps you don't even know their existenz...

I concur... I encountered this today, too (out of the blue).  I see no
rationale for chmod'ing /usr/sbin/ssmtp to 750...

also affects /etc/ssmtp/ssmtp.conf.

   chmod 755 /usr/sbin/ssmtp
   chmod 644 /etc/ssmtp/ssmtp.conf

(In reply to comment #3)
> I concur... I encountered this today, too (out of the blue).  I see no
> rationale for chmod'ing /usr/sbin/ssmtp to 750...
> 

bug #187841 is the rationale. I'll add a notice about this behaviour to the
ebuild.

(In reply to comment #5)
> I'll add a notice about this behaviour to the ebuild.

Done. 

This is not working properly.

I have lighttpd running (and php-cgi running as the lighttpd user), with the
lighttpd user being a member of the ssmtp group.

Mail is not sent out. However, if I chmod 755 /usr/sbin/ssmtp, mail works
properly.

This has caused a great deal of breakage for us. I firmly believe this change
should be reverted, ssmtp is meant to be simple. We simply use it to relay
messages to a dedicated box, from a large group of servers, and this has caused
issues, especially when an update comes up, and the chmod is required again(and
possibly forgotten).

Michael

(In reply to comment #7)
> This is not working properly.
> 
> I have lighttpd running (and php-cgi running as the lighttpd user), with the
> lighttpd user being a member of the ssmtp group.
> 
> Mail is not sent out. However, if I chmod 755 /usr/sbin/ssmtp, mail works
> properly.
> 
> This has caused a great deal of breakage for us. I firmly believe this change
> should be reverted, ssmtp is meant to be simple. We simply use it to relay
> messages to a dedicated box, from a large group of servers, and this has caused
> issues, especially when an update comes up, and the chmod is required again(and
> possibly forgotten).
> 
> Michael
> 

get ssmtp-2.62-r4 please

(In reply to comment #8)
> get ssmtp-2.62-r4 please
> 

I am using ssmtp-2.62-r4, and the problem remains.

Michael