From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Eric Wong <e@80x24.org>, meta@public-inbox.org
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH] workaround --headers bug with spamc(1)
Date: Fri, 8 Dec 2023 00:05:01 +0000 [thread overview]
Message-ID: <46248a31-5e72-4dff-87ad-1e883131ec81@citrix.com> (raw)
In-Reply-To: <20231207233214.M492093@dcvr>
On 07/12/2023 11:32 pm, Eric Wong wrote:
> As of SpamAssassin 4.0.0, spamc(1) corrupts messages with NUL in
> the body when the `--headers' switch is used. This increases
> transport costs, but most spamc/spamd setups are via local
> sockets, so it's unlikely to be significant.
>
> Link: https://bugs.debian.org/1057749
> Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
For the benefit of posterity, I reported
https://lore.kernel.org/xen-devel/2lyqb2u7tlcaig7nit3rnw5ftfupfemqmffr4ddsnolcrdojme@kmmlzigrzch3/
as a possible corruption in the archive, and within 3h it's been
debugged and worked around. This is very much money-can't-buy levels of
help and support.
Thankyou,
~Andrew
prev parent reply other threads:[~2023-12-08 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 23:32 [PATCH] workaround --headers bug with spamc(1) Eric Wong
2023-12-08 0:05 ` Andrew Cooper [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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46248a31-5e72-4dff-87ad-1e883131ec81@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).