Bug 1521 - spamassin -r fails pyzor report
Summary: spamassin -r fails pyzor report
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.50
Hardware: Other Linux
: P5 normal
Target Milestone: 2.54
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
: 1738 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-02-22 05:25 UTC by Beirne Konarski
Modified: 2003-04-06 16:38 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Beirne Konarski 2003-02-22 05:25:52 UTC 
When reporting spam using spamassassin -r, the pyzor update fails when trying to
create /usr/sbin/.pyzor as a home directory.  It turns out that spamassassin is
clearing out the environment as part of its untainting and the HOME directory
which pyzor needs is gone.  I fixed this as follows:

*** blib/script/spamassassin    Thu Feb 20 21:16:18 2003
--- /usr/bin/spamassassin       Sat Feb 22 08:11:27 2003
***************
*** 161,166 ****
--- 161,167 ----
      PREFIX            => $PREFIX,
      DEF_RULES_DIR     => $DEF_RULES_DIR,
      LOCAL_RULES_DIR   => $LOCAL_RULES_DIR,
+     home_dir_for_helpers      => (getpwuid($>))[7],
    });

  # set debug levels, if any specified (only useful for this command-line
Comment 1 Theo Van Dinter 2003-04-05 14:00:59 UTC 
is this still a problem with 2.53?
Comment 2 Theo Van Dinter 2003-04-05 14:01:28 UTC 
*** Bug 1738 has been marked as a duplicate of this bug. ***
Comment 3 Theo Van Dinter 2003-04-06 12:59:43 UTC 
if this really is a problem, we should fix for 2.54
Comment 4 Beirne Konarski 2003-04-06 18:27:51 UTC 
This isn't happening in 2.52.  I haven't upgraded to 2.53 yet.
Comment 5 Michael Moncur 2003-04-07 00:38:55 UTC 
Pyzor reporting appears to work fine for me after upgrading to 2.54.