-- eredeti üzenet --
Tárgy: Re: Loads of stale zero byte tmp files?
Feladó: Phil Hale <>
Dátum: 2012.05.22. 00:58
I just checked on the github page
(https://github.com/julesfm/MailScanner) and there is 1 pull request
that was posted 2 months ago that has fixes for TNEF regression and a
few other things. So far it has not been pulled into the master
branch. The only other activity is the initial commit of the master
branch 4 months ago. Is the github branch not being used to continue
development?
Phil
On 05/21/2012 05:04 PM, Remco Barendse wrote:
> On Mon, 21 May 2012, Richard Mealing wrote:
>
>> I would check in your mailq.in folder also as you might find tnef
>> files there too.
>>
>> I raised this a couple of weeks ago, but no-one got back to me, so I
>> rolled all my machines back to 4.83.5.
>
> Slowly i am getting the feeling that MailScanner is turning into
> abandonware... The problems with TNEF have been reported ages ago
> and i do remember seeing some fixes posted to the mailing list but
> don't think they ever got incorporated in the latest release of MS.
>
> Pity, MS has always been doing a great job for me
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
)
Julian told us we had to contact him when we wanted a new version released.
He'd approve the pull request and update the information on the website.
@Julian: Isn't it better to let someone else take over those
responsibilities?
On 22 May 2012 01:30, <> wrote:
>
>
> -- eredeti üzenet --
> Tárgy: Re: Loads of stale zero byte tmp files?
> Feladó: Phil Hale <>
> Dátum: 2012.05.22. 00:58
>
>
> I just checked on the github page
> (https://github.com/julesfm/MailScanner) and there is 1 pull request
> that was posted 2 months ago that has fixes for TNEF regression and a
> few other things. So far it has not been pulled into the master
> branch. The only other activity is the initial commit of the master
> branch 4 months ago. Is the github branch not being used to continue
> development?
>
> Phil
>
>
> On 05/21/2012 05:04 PM, Remco Barendse wrote:
> > On Mon, 21 May 2012, Richard Mealing wrote:
> >
> >> I would check in your mailq.in folder also as you might find tnef
> >> files there too.
> >>
> >> I raised this a couple of weeks ago, but no-one got back to me, so I
> >> rolled all my machines back to 4.83.5.
> >
> > Slowly i am getting the feeling that MailScanner is turning into
> > abandonware... The problems with TNEF have been reported ages ago
> > and i do remember seeing some fixes posted to the mailing list but
> > don't think they ever got incorporated in the latest release of MS.
> >
> > Pity, MS has always been doing a great job for me
> --
> MailScanner mailing list
>
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
>
> --
> MailScanner mailing list
>
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>
I don't do that much patching. Could you provide the command I need to
run to get this done, please?
Also, thanks for spending the time in researching and fixing this, Mark.
steve campbell
On 5/22/2012 8:15 PM, Mark Sapiro wrote:
> Remco Barendse wrote:
>
> I have an issue with MailScanner-4.84.5-2 / SpamAss on CentOS 6.2. The
> setup seems to be working ok but i have an issue on 2 boxes that temp
> files do not get deleted. In /tmp stuff like this is piling up quickly:
> -rw-------. 1 root root 94 May 20 22:55 K2M0qbNwv6
> -rw-------. 1 root root 0 May 21 05:08 tmp.1t3DQ6ZFaU
> -rw-------. 1 root root 0 May 21 06:14 tmp.9ZRV7VB41Y
> -rw-------. 1 root root 0 May 21 04:17 tmp.DmqX7lvDJS
> -rw-------. 1 root root 0 May 21 04:17 tmp.HwtJIyJImI
> -rw-------. 1 root root 0 May 21 06:14 tmp.MdrrIsMqGa
> -rw-------. 1 root root 0 May 21 05:08 tmp.ToMnIIFMf1
>
>
> The above files are left behind by the
> /etc/cron.hourly/update_virus_scanners process. This runs
> /usr/sbin/update_virus_scanners every hour which in turn goes through
> all the configured virus scanners checking if the scanner is installed
> and then, if it is, running its update process.
>
> Two of the check processes:
>
> /usr/lib/MailScanner/bitdefender-wrapper
> /usr/lib/MailScanner/clamav-wrapper
>
> when called with -IsItInstalled create these files and don't remove
> them. A third,
>
> /usr/lib/MailScanner/kaspersky-wrapper
>
> only creates the file and fails to remove it when called with the
> -IsItInstalled option and the kaspersky package is installed.
>
> The attached MS.patch file will fix this.
>
>
> and in /var/spool/MailScanner/incoming/SpamAssassin-Temp :
> -rw-------. 1 root root 0 May 21 06:31 MailScanner.UfuR0E
> -rw-------. 1 root root 0 May 21 05:58 MailScanner.vpJ3tf
> -rw-------. 1 root root 0 May 21 03:34 MailScanner.zmZPln
> -rw-------. 1 root root 0 May 21 03:34 MailScanner.zTSxkI
>
>
> One of the above files is created on my system every time MailScanner
> starts a new child process, i.e. every time a child dies of old age and
> is restarted. Also, if I restart MailScanner itself, I get an additional
> one created.
>
> I'm not sure where the actual create and/or failure to remove is.
>
>
> -rw-------. 1 root root 0 May 21 05:42 tmp.1t1IUXAFLV
> -rw-------. 1 root root 0 May 21 05:42 tmp.296NAlpKdS
> -rw-------. 1 root root 0 May 21 03:35 tmp.3cDHk7cwub
> -rw-------. 1 root root 0 May 21 03:20 tmp.3eimiawowx
>
>
> I see these rarely. I don't know what leaves them.
>
>
>
On 5/23/2012 5:21 AM, Steve Campbell wrote:
> I don't do that much patching. Could you provide the command I need to
> run to get this done, please?
Save the MS.patch file somewhere. Then run, either as root or via sudo
patch -p0 < /path/to/MS.patch
That should do it.
> Also, thanks for spending the time in researching and fixing this, Mark.
You're welcome. I only wish I could find where the
/var/spool/MailScanner/incoming/SpamAssassin-Temp/MailScanner* files are
coming from. So far I've been unsuccessful.
--
Mark Sapiro <> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
--
MailScanner mailing list
http://lists.mailscanner.info/mailman/listinfo/mailscanner
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
)