MaiScanner --debug hangs

[Steve Freegard]

Robert Lopez wrote:
> I am in the process of testing an install of MailScanner  4.77.6
> installed on a test gateway.
> Email is flowing in and out of the gateway but noting seems to be
> stopped or tagged when it should.
> I just tried the "--debug" option...
> 
> # MailScanner --debug
> In Debugging mode, not forking...
> Trying to setlogsock(unix)
> Building a message batch to scan...
> 
> and the maillog file says:
> Jun  5 10:33:22 mg04 MailScanner[5063]: MailScanner E-Mail Virus
> Scanner version 4.77.6 starting...
> Jun  5 10:33:22 mg04 MailScanner[5063]: Read 854 hostnames from the
> phishing whitelist
> Jun  5 10:33:22 mg04 MailScanner[5063]: Read 10149 hostnames from the
> phishing blacklists
> Jun  5 10:33:22 mg04 MailScanner[5063]: Using SpamAssassin results cache
> Jun  5 10:33:22 mg04 MailScanner[5063]: Connected to SpamAssassin
> cache database
> Jun  5 10:33:22 mg04 MailScanner[5063]: Enabling SpamAssassin
> auto-whitelist functionality...
> Jun  5 10:33:23 mg04 MailScanner[5063]: I have found clamavmodule
> scanners installed, and will use them all by default.
> Jun  5 10:33:23 mg04 MailScanner[5063]: Connected to
> processing-messages database
> Jun  5 10:33:23 mg04 MailScanner[5063]: Found 0 messages in the
> processing-messages database
> Jun  5 10:33:23 mg04 MailScanner[5063]: Using locktype = flock
> 
> Then nothing more happens.
> 
> Is the processing-messages database missing? is it the SpamAssassin
> cache database? or part of clamav?
> 

None of the above; when you run in debug mode a single MailScanner child
starts up and waits for messages; it you've stopped your inbound MTA
then it will just sit there waiting as you have found.

Try (modify to suit your OS):
/etc/init.d/MailScanner stop
/etc/init.d/MailScanner startin
/etc/init.d/MailScanner startout
MailScanner --debug

Regards,
Steve.