Bug 2652 - Uninitialized value, spamd 2.60 line 660
Summary: Uninitialized value, spamd 2.60 line 660
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.60
Hardware: Other other
: P5 trivial
Target Milestone: 2.63
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-30 18:32 UTC by Sebastian Jaenicke
Modified: 2004-01-19 06:07 UTC (History)
0 users


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 Sebastian Jaenicke 2003-10-30 18:32:23 UTC 
If spamd is configured to run as "spamd -c" and the user does not yet have
a $HOME/.spamassassin directory, spamd creates it, but 

Use of uninitialized value in pattern match (m//) at /usr/local/sbin/spamd line 660

gets logged via syslog. Subsequent use of spamc/spamd does not show this warning
again, it only seems to happen the first time a particular user uses spamc/spamd.
Comment 1 Justin Mason 2003-11-13 19:32:11 UTC 
lowering severity
Comment 2 Theo Van Dinter 2004-01-19 15:07:29 UTC 
This doesn't seem to happen in 2.62.  I picked a random user w/out the prefs dir (rpm in this case):

Jan 19 18:06:09 eclectic spamd[30982]: info: setuid to rpm succeeded
Jan 19 18:06:09 eclectic spamd[30982]: Creating default_prefs [/var/lib/rpm/.spamassassin/
user_prefs]
Jan 19 18:06:09 eclectic spamd[30982]: Created user preferences file: /var/lib/rpm/
.spamassassin/user_prefs

if you can recreate with 2.62 or later, we can reopen the bug.