dpc22

```systemctl restart sympa``` at 11:38 yesterday morning appears to have shunted a couple of directories from ```/var/spool/sympa/bulk/pct/``` to ```/var/spool/sympa/bulk/bad/pct``` ``` $ ls -l /var/spool/sympa/bulk/bad/pct/ total 8 drwxr-x--- 2 sympa sympa...

The contents of my /var/spool/sympa/bulk/bad directory are currently: ``` 403701785 4 drwxr-x--- 4 sympa sympa 4096 Jun 19 2019 . 403701786 4 drwxr-x--- 2 sympa sympa 4096 Oct 7 11:38...

Stupid question time. Is there a command line tool that would allow me to _remove_ a specific set of subscribers from a list? I have written a Perl script which...

Okay, trial and error revealed that the additional VERP is caused by: ../lib/Sympa/Spindle/ToList.pm ``` $new_message->{shelved}{tracking} ||= 'verp'; ``` Is there any particular reason that I shouldn't just comment that line...

I'm pretty sure that the repeat VERP messages to a single invalid/expired recipient are a consequence of a high priority message interrupting a long running job, which is restarted later...

I have spent some time looking at the code, and I am _pretty sure_ that it is safe to just disable the following in ```./lib/Sympa/Spindle/ToList.pm``` ``` $new_message->{shelved}{tracking} ||= 'verp'; ```...

So, that worked rather nicely. [Long term/15 minute Load average for last 14 days](https://canvas.csi.cam.ac.uk/sympa_graphs/la2.jpg). The two changes from https://github.com/sympa-community/sympa/issues/1238 were deployed on 30th September. That removed the consistent background load...

I spent some time thinking about VERP and tracking at the weekend. I'm pretty sure than "tracking=VERP" is only useful when verp_rate is greater than 0% on a given list....

@ikedas: I seem to have ended up with a number of different issues and suggestions on this thread: 1. Switching off tracking=verp entirely when verp_rate is 0% on a list....

1. Thanks 2. Yes, I think so (one address had 5 emails sent out as a consequence of two actual emails sent to a list). There is quite a lot...