Sorry, I didn't change the subject line when I posted this.
On 9/29/2023 12:41 PM, Mark London wrote:
Hi - Can anyone tell me why the following email header triggered
DKIM_SIGNED and DKIM_VALID, yet I don't see a DKIM header line?
Strangely, if I run spamassassin from the command line on the
On 9/29/2023 1:47 PM, Reindl Harald (gmail) wrote:
Am 29.09.23 um 19:37 schrieb Bill Cole:
Strangely, if I run spamassassin from the command line on the
message, DKIM_SIGNED is not triggered. SpamAssassin version 3.4.6
Oh. So you've let a piece of security software go most of year after
On 29.09.23 12:41, Mark London wrote:
Hi - Can anyone tell me why the following email header triggered
DKIM_SIGNED and DKIM_VALID, yet I don't see a DKIM header line?
Strangely, if I run spamassassin from the command line on the message,
DKIM_SIGNED is not triggered. SpamAssassin version
On 2023-09-29 at 12:41:42 UTC-0400 (Fri, 29 Sep 2023 12:41:42 -0400)
Mark London
is rumored to have said:
Hi - Can anyone tell me why the following email header triggered
DKIM_SIGNED and DKIM_VALID, yet I don't see a DKIM header line?
Unlikely. That would probably require an unmodified copy
Hi - Can anyone tell me why the following email header triggered
DKIM_SIGNED and DKIM_VALID, yet I don't see a DKIM header line?
Strangely, if I run spamassassin from the command line on the message,
DKIM_SIGNED is not triggered. SpamAssassin version 3.4.6
(Note, I truncated the
Hello,
On Thu, Sep 28, 2023 at 09:08:30PM -0400, Jared Hall wrote:
> 1) Are you using native SA or the spamhaus-dqs plugin?
Just native SA in spamd mode.
> 2) What version of SpamAssassin?
3.4.2. I know, it's ancient. An upgrade is planned but I'd still
like to know what the behaviour is. I
