On 12/01/2012 02:12 AM, Nelson A. de Oliveira wrote:
> Package: tumgreyspf
> Version: 1.35-7
> Severity: normal
>
> Hi!
>
> Using greylistByIPOnly = 0 I saw that the expired entries aren't removed
> after GREYLISTEXPIREDAYS.
>
>>From /etc/cron.daily/tumgreyspf it's possible to see, for example:
>
> =====
> + [ -f /etc/tumgreyspf/default.conf ]
> + grep GREYLISTEXPIREDAYS /etc/tumgreyspf/default.conf
> + cut -d= -f2
> + awk {print $1}
> + cut -d. -f1
> + GREYLISTEXPIREDAYS=10
> + [ -z 10 ]
> + greylistDir=/var/lib/tumgreyspf/data
> + [ -d /var/lib/tumgreyspf/data ]
> + ls /var/lib/tumgreyspf/data
> + [ -z client_address ]
> + find /var/lib/tumgreyspf/data/client_address/1/161/ -name check_file -mtime
> +10 -delete
> + rmdir --ignore-fail-on-non-empty
> /var/lib/tumgreyspf/data/client_address/1/161
> + rmdir --ignore-fail-on-non-empty /var/lib/tumgreyspf/data/client_address/1
> + find /var/lib/tumgreyspf/data/client_address/103/10/ -name check_file
> -mtime +10 -delete
> (...)
> =====
>
> But what I have in /var/lib/tumgreyspf/data/client_address/1/161/ is:
>
> =====
> /var/lib/tumgreyspf/data/client_address/1/161/
> /var/lib/tumgreyspf/data/client_address/1/161/0
> /var/lib/tumgreyspf/data/client_address/1/161/0/greylist
> /var/lib/tumgreyspf/data/client_address/1/161/0/greylist/mail@somedomain
> /var/lib/tumgreyspf/data/client_address/1/161/0/greylist/mail@somedomain/receiver1@mydomain
> /var/lib/tumgreyspf/data/client_address/1/161/0/greylist/othermail@otherdomain
> /var/lib/tumgreyspf/data/client_address/1/161/0/greylist/othermail@otherdomain/receiver2@mydomain
> =====
>
> Note that it tries to remove check_file (that is not created with
> greylistByIPOnly = 0) and also remove the dirs that aren't empty.
>
> Problem is that these dirs will grow without limit (and maybe reaching
> some filesystems limit).
>
> It also affects testing/unstable's 1.36-4
>
> Thank you!
>
> Best regards,
> Nelson
Hi Nelson,
I am the one who wrote the cron job, because the python script provided
by upstream was buggy in many ways. I didn't know and never used that
mode, with greylisting by email address, and not by IP address only.
That's interesting.
Could you try to write a version of the script that would work on your
system? We can later check the value of greylistByIPOnly, and have 2
types of clean, depending on that value.
I can try to have a look myself, but it would help a lot of you could
attach to this bug a tarball of an example /var/lib/tumgreyspf folder,
with few entries, so I can do some tests runs.
For the time being, I would recommend any stable or testing users to use
greylistByIPOnly = 1, and then we can try to fix the problem in
experimental first... If it works well, then I think it would be a good
idea to have greylistByIPOnly = 0 by default.
Thoughts?
Thomas
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
