On 6/25/23 1:31 PM, Ken Alker wrote:
I moved the .psv file from the bad queue into the shunt queue. I then ran "mailman unshunt" (as user 'mailman' while in the virtual environment). I tailed mailman.log during this process and no logs were spit out. The date stamp on the .psv file never changed (maybe it does not when being moved between queues?) and, AFAICT, the file never moved from the shunt queue. I waited maybe five minutes, tops.
I forgot that the extension in the bad queue is .psv (for preserve).
You have to rename it to .pck.
Is there a way to reprocess the bad queue?
You could just move the messages to the 'in' queue.
Changing .psv to .pck in the process. this can be done, e.g., by
for file in `ls var/queue/bad/*.psv;do mv /var/queue/bad/$file
/var/queue/in/${file/psv/pck};done
I just now tried moving the same message into the 'in' queue but, again, nothing happened. I left it in there for five minutes. Do I have to run a program to get it to act on the 'in' queue (I presume that there is a "runner" that is always looking and taking care of this already as I presume this is the queue where all 'normal' traffic is handled).
Again, you need to change the extension to .pck.
Here are the (obfusacted) results of "mailman qfile /opt/mailman/mm/var/queue/shunt/1675389793.6945386+2aeaf0015558c9d8380c96142c3fa9d03a8142bc.psv" (the message I was experimenting with):
[----- start pickle -----] <----- start object 1 -----> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: THE-list subscription notification From: email@obfuscated.com To: the-list-owner@lists.obfuscated.com Message-ID: <167538979369.2390432.521344217673230839@obfuscated.net> Date: Thu, 02 Feb 2023 18:03:13 -0800 Precedence: bulk
user@domain.tld has been successfully subscribed to THE-list.
<----- start object 2 -----> { '_parsemsg': False, 'envsender': 'email@obfuscated.com', 'listid': 'the-list.obfusacted.com', 'nodecorate': True, 'recipients': {'person@domain.tld'}, 'reduced_list_headers': True, 'version': 3} [----- end pickle -----]
I was assuming these were list welcome messages which they aren't. They
are owner notifications, so they were sent to the -owner address and
processed through the owner-pipeline, but unless the Debian package
changed the default-owner-pipeline, it doesn't contain mime-delete so
how they ended up in the bad queue is still a mystery.
However, what would be the point of resending these at this time?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan