[Mimedefang] umask, mimedefang, clamd and spamassassin

Steve Hanselman steveh at brendata.co.uk
Mon Feb 2 11:23:46 EST 2015


I believe it's 3.4 but I'll check later, I'll go over the strace and identify exactly what is happening.

sent from my nexus 4

On 2 Feb 2015 15:44, "David F. Skoll" <dfs at roaringpenguin.com> wrote:
>
> On Mon, 2 Feb 2015 14:13:31 -0000 
> "Steve Hanselman" <steveh at brendata.co.uk> wrote:On Mon, 2 Feb 2015 14:13:31 -0000
"Steve Hanselman" <steveh at brendata.co.uk> wrote:

> I've just run strace over a session and it would appear that
> spamassassin modifies the umask, which probably explains the issue (it
> also depends which tests you have enabled in spamassassin if you grep
> the tree).

What version of SpamAssassin?  I'm still on 3.3.x and it seems to me that
all the calls to umask are careful to restore the original umask
afterwards.

> I'll check the entire details later but I think that mimedefang needs
> to reset the umask after it has called spamassassin, this is the
> likely cause for a number of the lstat errors with clamd.

OK; I can look at doing that.

Regards,

David.
_______________________________________________
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang at lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


More information about the MIMEDefang mailing list