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