SpamAssassin Problems
My SpamAssassin setup on DreamHost has decided to stop working, joy. In my procmail logs:
Can't locate Mail/SpamAssassin/Util/Progress.pm in @INC (@INC contains:
/home/***/usr/share/perl/5.8.4 /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl)
at /mnt/***/vol/boot/***/sales/***/usr/bin/spamassassin line 82.
Of course the file is there because I haven’t changed the setup in months:
find usr -name Progress.pm usr/share/perl/5.8.4/Mail/SpamAssassin/Util/Progress.pm
I guess it might be because when it’s executed it uses the full path (with /mnt) rather than just the /home alias. But @INC includes the path where the file it. I’ll have to wait until I get home to sort this out.
Update: It started working again, no idea why and nothing interesting in the logs. I guess it was some DreamHost home directory mounting issue. It did let me see how much work SpamAssassin does and made me really grateful that it exists.
April 26th, 2006 at 10:35 pm
I found this post via Google, as I’m also a Dreamhost user running into the same problems (which seem to come and go).
The best guess I have right now, based on a couple of other errors I’m seeing in my procmail logs is that /home/[username] isn’t always a valid path on some machines.
For “the other errors”, I’m testing whether referring to $HOME in lieu of /home/[username] works.
I haven’t checked to see if there’s a way to compile spamassassin with $HOME references instead of explicit paths…but a fallback trick seems to work. From my .procmailrc
:0fw
| $HOME/sausr/bin/spamassassin
:0fw
* ! ^X-Spam-Level
| /usr/bin/spamassassin
…which allows at least the DreamHost-installed version of spamassassin to run, when the user-installed version bombs. It’s not perfect, but it beats the spam leakage when /home/[user] goes away.
June 21st, 2006 at 1:22 pm
Michael,
Thanks for the suggestion… that’s a real good idea. I have this problem on occasion, then for ages its all fine again.
I’ve submitted this problem to Dreamhost’s tech support… we’ll see what happens.
Bruce