Developers of Sympa

[Thomas Berry <address@concealed>]

Kristina,

when sympa.pl is running as the sympa-message process, it manages the queuedistribute spool.  You can see this under the "Clean queue (bad)" section; sympa-message performs a &CleanSpool on the distribute/bad (queuedistribute) directory based on the clean_delay_queue value in sympa.conf.

As for the queuebounce spool, bounced.pl takes care of that.  The bounce spool doesn't use a bounce/bad directory, instead the files are prepended with "BAD-"; sympa.pl also takes care of the clean-up of the BAD files under "old bad file".

Thomas



Kristina Clair wrote:

Hi Kristina,

The distribute/bad messages are cleaned after some time - one week, if I
remember well.
Actually, paul was right: clean_delay_queue is the parameter you're
looking for.
The parameter setting the bounce/bad retention period is
clean_delay_queuebounce.
Please have a look at
https://www.sympa.org/manual/conf-parameters/part2#clean_delay_queue for
this family of parameter.

Hi,

I'm really confused. I don't see at all how clean_delay_bouncequeue is
effecting *both* distribute/bad and bounce/bad. It only seems to me to be
cleaning out bounce/bad.  We have clean_delay_bouncequeue set at the
default, and we have messages in distribute/bad that are now several years
old.

What am I missing here? :)

Kristina

Regards,

David

Le 27/03/2010 18:56, Kristina Clair a écrit :

Dear Kristina,


Am Samstag, den 27.03.2010, 08:38 -0700 schrieb Kristina Clair:

Is there a reason why there is no configuration option and associated
functionality to remove messages from the distribute/bad spool after a
certain length of time?

Is `clean_delay_queue` the parameter you are looking for?

No, this cleans the messages in the bounce/bad queue. I want to clean
the
messages in distirbute/bad.

-Kristina

--
David Verdin
Comité réseau des universités