Emails not getting scanned

Martin Hepworth maxsec at gmail.com
Tue Dec 20 06:31:15 GMT 2011


FYI in centos 6 the default mta could be postfix if it's like red hat ! So
you may need to disable postfix if u want to get this going..

Martin


On Tuesday, 20 December 2011, Tony Arcus <tony at ai.net.nz> wrote:
>
> Quoting Chris Stone <axisml at gmail.com>:
>
>> Tony,
>>
>> On Mon, Dec 19, 2011 at 3:05 PM, Tony Arcus <tony at ai.net.nz> wrote:
>>>
>>> Sendmail is:
>>> service sendmail stop
>>> chkconfig sendmail off
>>>
>>> Mailscanner is on
>>>
>>> When I do a
>>> /etc/init.d/MailScanner status
>>> Checking MailScanner daemons:
>>>         MailScanner:                                      [  OK  ]
>>>         incoming sendmail:                                [  OK  ]
>>>         outgoing sendmail:                                [  OK  ]
>>>
>>> All looks good and as I would expect,
>>> but when I do a
>>> /etc/init.d/sendmail status
>>> sendmail is stopped
>>> sm-client (pid  19322) is running...
>>
>> You turned off the sendmail init scripts with your chkconfig - as you
>> should have. That sendmail init script is going to be looking at
>> /var/spool/mqueue not /var/spool/mqueue.in. The sendmail daemon you
>> are seeing with the /etc/init.d/MailScanner status (or service
>> MailScanner status) is the one that is using /var/spool/mqueue.in as
>> the incoming queue and /var/spool/mqueue as the outbound queue. You
>> should only use the MailScanner init script to see the status of the
>> daemons rather than the sendmail init script.
>>
>> The sm-client indicates that your local sendmail client is running,
>> which you do not need. Do a 'service sendmail stop' and then a
>> 'service MailScanner restart' to clean up and make sure only the
>> sendmail daemons you need are running. The 'chkconfig sendmail off'
>> will keep that init script from running on boot.
>>
>>> Still nothing here that causes me to think things are wrong.
>>> What I can confirm is that emails are entering the queue
>>> /var/spool/mqueue.in/, but immediately get processed (by something)
directly
>>> to the user. MailScanner never gets to process them.
>>
>> Take a look at the 'Incoming Queue Dir' setting in your
>> /etc/MailScanner/MailScanner.conf file. You should have:
>>
>> Incoming Queue Dir = /var/spool/mqueue.in
>>
>> but, I am guessing, you probably have:
>>
>> Incoming Queue Dir = /var/spool/mqueue
>>
>>
>>
>> Chris
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website!
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>>
>
> Thanks Chris for your suggestions.
>
> What you have suggested is what I have so far been trying to trouble
shoot.
> No sendmail process is running as a result of running
> /etc/init.d/sendmail start
>
> The sendmail processes I currently have running are as a result of
starting MailScanner.
> ps aux|grep send
> root      1328  0.0  0.1  10028  2008 ?        Ss   12:10   0:00
sendmail: accepting connections
> smmsp     1332  0.0  0.1   9792  1532 ?        Ss   12:10   0:00
sendmail: Queue runner at 00:15:00 for
> /var/spool/clientmqueue
> root      1336  0.0  0.1   9784  1620 ?        Ss   12:10   0:00
sendmail: Queue runner at 00:15:00 for /var/spool/mqueue
>
> Even on systems that are running correctly there is a running sm-client.
> I looked in /var/run/sm-client.pid on my good systems where everything is
operational and:
>
> cat /var/run/sm-client.pid
> 1332
> /usr/sbin/sendmail -L sm-msp-queue -Ac -q15m
-OPidFile=/var/run/sm-client.pid
> [root at mail strider]# ps aux|grep 1332
> smmsp     1332  0.0  0.1   9792  1532 ?        Ss   12:10   0:00
sendmail: Queue runner at 00:15:00 for
> /var/spool/clientmqueue
>
> So unless I am mistaken (always possible) this is okay.
>
> As for /etc/MailScanner/MailScanner.conf
> cat /etc/MailScanner/MailScanner.conf|grep "Queue Dir"
> Incoming Queue Dir = /var/spool/mqueue.in
> Outgoing Queue Dir = /var/spool/mqueue
>
> So everything would seem to be set up correctly, the incoming emails are
going in to /var/spool/mqueue.in (not some where else) and instantly on to
the user, so MailScanner never gets them to process.
>
> So what is getting the messages out of /var/spool/mqueue.in, and how to
stop this so MailScanner does them 5 seconds later.
>
> PS
> Centos 6
> Mailscanner 4.84.3
> sendmail-cf-8.14.4-8.el6.noarch
> sendmail-8.14.4-8.el6.i686
>
> 1 gig ram
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!

-- 
-- 
Martin Hepworth
Oxford, UK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20111220/88fc5ced/attachment.html


More information about the MailScanner mailing list