Developers of Sympa

["K. Clair" <address@concealed>]

Hi,

This is still not working for us (we're now running sympa 6.0.6). Our 
distribute/bad queue has files in it from June 2009. We have not changed 
the default value of clean_delay_queue.

Thomas Berry wrote:
> 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.

I'm confused by this because the code has me believe that $spool is set 
to $Conf{'queue'} unless in message mode, in which case it is set to 
$Conf{'queuedistribute'}:

my $spool = $Conf{'queue'};
if ($main::daemon_usage == DAEMON_MESSAGE) {
    $spool = $Conf{'queuedistribute'};
}

Yet, the Clean queue (bad) process runs only when not in message mode:

unless ($main::daemon_usage == DAEMON_MESSAGE) {
# process expire and bads only in command mode
        ## Clean queue (bad)
        <snip>
        if (-e "$spool/bad") {
          &tools::CleanSpool("$spool/bad", $Conf{'clean_delay_queue'});
        }

This is of course the behavior that is desired, but when this code is 
run, as far as I can tell, $spool is set as $Conf{'queue'} not 
$Conf{'queuedistribute'}.

Am I completely missing something?

One other thing I notice is the in confdef, there is no default 
specified for 'queuedistribute'.  We do not have that explicitly defined 
in sympa.pl, either.  Would this be a problem?  (New messages are 
definitely making it into the distribute/bad directory, though!)

Thanks!
Kristina

> 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