public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Test of mail list
Date: Thu, 11 Jan 2024 14:38:53 +0100	[thread overview]
Message-ID: <9ebb3a04-07a1-405a-a38c-bf663f346ebc@ipfire.org> (raw)
In-Reply-To: <27CB86A5-CB76-4051-AE54-E1E9D0DD4C5A@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi Michael,

On 11/01/2024 14:01, Michael Tremer wrote:
> Hello Adolf,
> 
> It looks like we have some issues with Mailman 3 again.
> 
> It just seems to lock up for no apparent reason. I had to restart several services several times to get some emails that were stuck in the queue delivered.
> 
> So, I will have to go and investigate… Please let me know if there are further emails getting stuck or even go missing.

So the two patch set for the wsdd implementation is now in patchwork but 
is still not showing in the dev list archive.

Also in patchwork there are two patches from a four patch set related to 
the logging or not of DROPHOSTILE.
So two patches from that set are missing, 1/4 and 2/4 and due to that 
patchwork has called the 3/4 and 4/4 patches as belonging to an untitled 
series. I suspect that if 1/4 and 2/4 get through they will not end up 
being in the same patch set.

Regards,
Adolf.

> 
> -Michael
> 
>> On 11 Jan 2024, at 07:43, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> This is a test mail to see if individual named mails are delivered because my dev mailing list mails are not getting into the mail archive when I look online.
>>
>> Regards,
>> Adolf.
>>
>> -- 
>> Sent from my laptop
>>
> 

-- 
Sent from my laptop

  reply	other threads:[~2024-01-11 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  7:43 Adolf Belka
2024-01-11 13:01 ` Michael Tremer
2024-01-11 13:38   ` Adolf Belka [this message]
2024-01-11 13:42     ` Adolf Belka
2024-01-11 13:50       ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ebb3a04-07a1-405a-a38c-bf663f346ebc@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox