called with 2 bind variables when 0 are needed

[Scott Silva]

on 12/8/2007 1:24 PM Kai Schaetzl spake the following:
> I upgraded a machine which was still holding CentOS 4.2 to the current 4.5 
> via yum. So far so good. Now, after upgrading MailScanner suddenly throws 
> this error to my warn log:
> called with 2 bind variables when 0 are needed
> 
> Google tells me there was one posting about this in April 2006 about this 
> on this list, no reply to it and not much else.
> 
> Anyone knows what this means?
> 
> Apparently, MailScanner is stull running ok. The MailScanner log itself 
> goes like this:
> 
> Dec  8 22:10:38 nx05 MailScanner[16160]: New Batch: Scanning 1 messages, 
> 7338 bytes
> Dec  8 22:10:46 nx05 MailScanner[16160]: Spam Checks: Found 1 spam 
> messages
> Dec  8 22:10:46 nx05 MailScanner[16160]: Virus and Content Scanning: 
> Starting
> Dec  8 22:10:50 nx05 MailScanner[16160]: called with 2 bind variables when 
> 0 are needed
> Dec  8 22:10:50 nx05 MailScanner[16160]: Uninfected: Delivered 1 messages
> Dec  8 22:10:50 nx05 MailScanner[16160]: Batch (1 message) processed in 
> 11.50 seconds
> Dec  8 22:10:50 nx05 MailScanner[16160]: Logging message lB8LAbAk016953 to 
> SQL
> Dec  8 22:10:50 nx05 MailScanner[16160]: "Always Looked Up Last" took 0.00 
> seconds
> Dec  8 22:10:50 nx05 MailScanner[16168]: lB8LAbAk016953: Logged to 
> MailWatch SQL
> 
> So, could this be related to a clamav update as it happens during the 
> clamscan?
> 
> MailScanner 4.54.6
> all Perl modules are from CentOS or rpmforge. Mail-Tools is still 1.77.
> 
> Kai
> 
You state that you just updated MailScanner, but you then list a version from 
mid 2006;
"25/5/2006 - Release of stable 4.54.6. This is to get rid of all the issues 
with 4.53. Next release won't be until July or August. See the Change Log for 
details."

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!