public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] applied: [PATCH pmg-api] report: adapt to changes in SpamAssassin dns api
Date: Fri, 7 Jul 2023 18:57:51 +0200	[thread overview]
Message-ID: <20230707185751.55d5e8e9@rosa.proxmox.com> (raw)
In-Reply-To: <9a03919d-2084-18fb-8689-750c62c962ee@proxmox.com>

On Tue, 27 Jun 2023 11:23:58 +0200
Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:

> Am 27/06/2023 um 11:00 schrieb Stoiko Ivanov:
> > SpamAssassin 4.0 changed the way it does DNS-lookups a bit (switched
> > to asynchronous lookups) - this broke pmg-system-report, since
> > we use the SpamAssassin API to check that DNS-resolution works.
> > The reason for this is that SA used to take only the first entry from
> > /etc/resolv.conf - and SA being able to do correct resolution is
> > critical for it to work.
> > 
> > This patch fixes the incompatible use of the DNS-API, but does not
> > change to the asynchronous model.
> > 
> > Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> > ---
> > tested on my pmg installation - a quick verification that it works
> > indeed would be appreciated
> > 
> >  src/PMG/Report.pm | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> >  
> 
> applied, with Friedrich's T-b, thanks!
> 
> should this get also backported to stable-7 branch? as SA 4.0 is available
> there too.

Sorry for overlooking the question (and underlying issue) - yes it should.
I pushed the changes to stable-7 - thanks!




      reply	other threads:[~2023-07-07 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  9:00 [pmg-devel] " Stoiko Ivanov
2023-06-27  9:15 ` Friedrich Weber
2023-06-27  9:23 ` [pmg-devel] applied: " Thomas Lamprecht
2023-07-07 16:57   ` Stoiko Ivanov [this message]

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=20230707185751.55d5e8e9@rosa.proxmox.com \
    --to=s.ivanov@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal