https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5894
--- Comment #17 from grubs <[email protected]> 2010-06-22 20:06:46 EDT --- For our systems 99.9% of the time we call spamassassin via vdelivermail also as this gets around simscan's poor handling of multiple recipient adresses. However... when we have dedicated scanning boxes that receive email, scan with spamassassin, and then forward the email on to another server we still use simscan to employ spamasassin during the smtp session. It is for these situations where there is no relevant mailbox on the server where spamassassin is running that I'm seeing the behaviour I reported. With further thought on this - perhaps the log entry "info: handle_user unable to find user: 'simscan'" is simply an info message that can be ignored in this configuration?? We *are* getting the mail scanned so spamd *is* working. ie - when the user is not on the box I assume we fall into this block of code. # we *still* die if this can't be found 2158 if (!defined $userdir) { 2159 my $errmsg = "spamd: handle_user unable to find user: '$prefsfrom'\n"; 2160 die $errmsg if $spamtest->{'paranoid'}; 2161 # if we are given a username, but can't look it up, maybe name 2162 # services are down? let's break out here to allow them to get 2163 # 'defaults' when we are not running paranoid 2164 info($errmsg); 2165 return 0; 2166 } It just seems untidy... -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
