4.50.14 possible bug

Gerry Doris gdoris at rogers.com
Tue Feb 7 14:16:01 GMT 2006

Glenn Steen wrote:
> On 07/02/06, Ugo Bellavance <ugob at camo-route.com> wrote:
>>Even tough I have:
>>Log Speed = no
>>I get these in my logs:
>>Feb  7 07:27:37 mta1 MailScanner[19403]: Batch processed in 36.65 seconds
>>Feb  7 07:27:37 mta1 MailScanner[19403]: Logging message k17COSFG019175
>>to SQL
>>Feb  7 07:27:37 mta1 MailScanner[19403]: Logging message k17CN0FG019106
>>to SQL
>>Feb  7 07:27:37 mta1 MailScanner[19403]: "Always Looked Up Last" took
>>0.05 secon
>>I double-checked the setting and restarted twice...  Is that normal?
>>-> Please don't send a copy of your reply by e-mail.  I read the list.
>>-> Please avoid top-posting, long signatures and HTML, and cut the
>>irrelevant parts in your replies.
> Hi Ugo,
> There is/was an ongoing thread about this, that basically covers the
> why and how etc of this one. Executive summary is: Jeff wanted it,
> Jules liked the idea, and now we all get it. Some others rather
> didin't like it... So ... You are not alone ... (Me, I'm still on the
> fence:-).
> --
> -- Glenn

Glenn is correct.  The Log Speed setting doesn't affect the logging of 
the items you mentioned.  I'm not sure what it does stop???

In any case, if you don't want the speed logging then you'll need to 
comment out the appropriate lines in MessageBatch.pm.

More information about the MailScanner mailing list