On Thu, 2009-09-17 at 10:51 -0400, Warren Togami wrote:
> Sep 17 10:35:49 localhost spamd[20600]: spamd: setuid to testuser succeeded
> Sep 17 10:35:49 localhost spamd[20600]: spamd: creating default_prefs:
> /home/testuser/.spamassassin/user_prefs
> Sep 17 10:35:49 localhost spamd[20600]: config: cannot create
> /home/testuser/.spamassassin/user_prefs: 2
> Sep 17 10:35:49 localhost spamd[20600]: spamd: failed to create readable
> default_prefs: /home/testuser/.spamassassin/user_prefs
> This command fails to create the ~/.spamassassin directory, but it does
> successfully create .razor and .pyzor directories.
>
> cat /usr/share/doc/spamassassin-3.3.0/sample-spam.txt | spamassassin
>
> This command succeeds in creating ~/.spamassassin.
>
> spamassassin-3.2.5 behaved this way as well, so this is not a
> regression. Should this be considered a bug?
Can definitely positively confirm this does work on Debian/Ubuntu and
Mandriva (custom RPM) with 3.2.
Red Hat specific issue? Possibly SELinux related WRT spamd daemon?
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
