accumulation of files in /var/spool/mqueue.in

S Mohan smohan at vsnl.com
Wed Mar 12 02:27:06 GMT 2003


I chose 6 days as beyond that, as per standard setting, sendmail would
not deliver anyway. Thus residual files have to be broken. This is
assuming MailScanner would probably not have as big a backlog as 5 days.

Julian:
Is it reasonable to assume that MailScanner picks up the oldest files
for processing first?

Is there any way of extracting average wait time in mqueue.in so that we
can increase number of children if need be and see if it makes a
difference else increase Ram/ CPU Power?

Mohan
-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
Behalf Of Craig Pratt
Sent: Tuesday, March 11, 2003 8:17 AM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: accumulation of files in /var/spool/mqueue.in


Thanks for the tip. I've been seeing these queue files occasionally as
well.

Most recently, when I updated the sendmail access.db without restarting
sendmail/MailScanner. This seemed to cause sendmail to die during SMTP
connections - presumably due to the fact that sendmail's cached file
state didn't match the actual file.

What I'm wondering, though, is it safe to delete the files in mqueue.in
with sendmail/MailScanner running? [sounds like a potential FAQ, as
well]

Craig

On Monday, March 10, 2003, at 05:39  PM, S Mohan wrote:
> I had the same stuff. I looked up a few files and associated mail log.

> These were remnants of broken SMTP conversations. In order to clear
> these automatically, I created a daily cron job as under.
>
> Find /var/spool/mqueue.in -mtime +6|xargs rm -f
>
> I gave 6 days as sendmail will anyway abort after 5 days delivery.
> Thus files older than that anyway would be broken files.
>
> Mohan
>
> -----Original Message-----
> From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
> Behalf Of David Closson
> Sent: Tuesday, March 11, 2003 1:27 AM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Re: accumulation of files in /var/spool/mqueue.in
>
>
> OK, I figured as much.  Thank you for the rapid response.
>
> We are processing about 350,000 emails a day (heavier day) with
> MailScanner and Spamassassin.  This figure is combined in and out for
> all of our users.
>
>
> _________
> Sincerely,
> David Closson
> 209-736-0111
>
>
>
>
>
>> From: Julian Field <mailscanner at ECS.SOTON.AC.UK>
>> Reply-To: MailScanner mailing list <MAILSCANNER at JISCMAIL.AC.UK>
>> To: MAILSCANNER at JISCMAIL.AC.UK
>> Subject: Re: accumulation of files in /var/spool/mqueue.in
>> Date: Mon, 10 Mar 2003 19:27:44 +0000
>> MIME-Version: 1.0
>> Received: from cpimssmtpa03.msn.com ([207.46.181.90]) by
>> mc5-f17.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Mon,
>> 10
>
>> Mar 2003 11:30:21 -0800
>> Received: from smtp.jiscmail.ac.uk ([130.246.192.48]) by
>> cpimssmtpa03.msn.com with Microsoft SMTPSVC(5.0.2195.4453); Mon, 10
>> Mar
>
>> 2003 11:25:18 -0800
>> Received: from LISTSERV.JISCMAIL.AC.UK (jiscmail.ac.uk) by
>> smtp.jiscmail.ac.uk (LSMTP for Windows NT v1.1b) with SMTP id
>> <3.0000634F at smtp.jiscmail.ac.uk>; Mon, 10 Mar 2003 19:28:14 +0000
>> Received: from JISCMAIL.AC.UK by JISCMAIL.AC.UK (LISTSERV-TCP/IP
> release
>> 1.8e)          with spool id 19357891 for MAILSCANNER at JISCMAIL.AC.UK;
> Mon,
>> 10 Mar          2003 19:28:14 +0000
>> Received: from 130.246.192.52 by JISCMAIL.AC.UK (SMTPL release 1.0h)
> with
>> TCP;          Mon, 10 Mar 2003 19:28:14 GMT
>> Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk
> [152.78.70.1])
>> by          ori.rl.ac.uk (8.11.1/8.11.1) with ESMTP id h2AJSCe29811
>> for
>>      <MAILSCANNER at JISCMAIL.AC.UK>; Mon, 10 Mar 2003 19:28:12 GMT
>> Received: from pigeon.ecs.soton.ac.uk (ns1 [152.78.68.1]) by
>> raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id TAA23530 for
>> <MAILSCANNER at JISCMAIL.AC.UK>; Mon, 10 Mar 2003 19:28:11 GMT
>> Received: from thief.ecs.soton.ac.uk (staff-vpn132 [152.78.236.132])
>> by
>>      pigeon.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id TAA19506 for
>>    <MAILSCANNER at JISCMAIL.AC.UK>; Mon, 10 Mar 2003 19:28:10 GMT
>> X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
>> X-MSN-Trace: {838B357B-4735-4DB1-A653-A9E73A906214}
>> X-RAL-MFrom: <mailscanner at ecs.soton.ac.uk>
>> X-RAL-Connect: <raven.ecs.soton.ac.uk [152.78.70.1]>
>> X-Sender:  (Unverified)
>> X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
>> Message-ID:  <5.2.0.9.2.20030310192506.027bbf80 at imap.ecs.soton.ac.uk>
>> Sender:       MailScanner mailing list <MAILSCANNER at JISCMAIL.AC.UK>
>> In-Reply-To:  <BAY3-F34EbjkyqU7a0x00023ce6 at hotmail.com>
>> Precedence: list
>> Return-Path: owner-mailscanner at JISCMAIL.AC.UK
>> X-OriginalArrivalTime: 10 Mar 2003 19:25:19.0093 (UTC)
>> FILETIME=[C9492A50:01C2E73A]
>>
>> At 19:12 10/03/2003, you wrote:
>>> Greetings,
>>>
>>> Using RH 7.3
>>> Using Sendmail 8.11-6
>>> MailScanner 4.13-3
>>> Using McAfee AV
>>>
>>> I have been happily using MailScanner for almost a year now and have

>>> had to remove the accumulation of files in /var/spool/mqueue.in
>>> after a month or so.
>>>
>>> I am not sure if these are messages already delivered and were not
>>> removed or ?
>>>
>>> I have had no reports of missing email.
>>
>> If they are stray files that aren't part of a matching qf / df pair,
>> then you can safely delete them. If an SMTP session into your server
>> gets interrupted for some reason, a stray file will be left behind.
>> The
>
>> server at the far end of the session knows that its message
>> transmission got interrupted and will retry anyway. SMTP is designed
>> pretty carefully to ensure things don't get lost in transit.
>> --
>> Julian Field
>> www.MailScanner.info
>> Professional Support Services at www.MailScanner.biz MailScanner
>> thanks
>
>> transtec Computers for their support
>
>
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
> --
> This message checked for dangerous content by MailScanner on
> StrongBox.
>


--
This message checked for dangerous content by MailScanner on StrongBox.



More information about the MailScanner mailing list