On Sat, Jan 18, 2020 at 02:54:27PM +0100, Alex Woick wrote:
> Henrik K schrieb am 18.01.2020 um 08:15:
> >On Sat, Jan 18, 2020 at 06:56:53AM +0200, Henrik K wrote:
> >>On Tue, Jan 14, 2020 at 02:38:06PM +0100, Alex Woick wrote:
> >>>Link to complete message:
>
Henrik K schrieb am 18.01.2020 um 08:15:
On Sat, Jan 18, 2020 at 06:56:53AM +0200, Henrik K wrote:
On Tue, Jan 14, 2020 at 02:38:06PM +0100, Alex Woick wrote:
Link to complete message:
[2]https://pastebin.com/raw/1DLtnuRX
Spamassassin is running as spamc/spamd, and is embedded in Postfix with
On Sat, Jan 18, 2020 at 06:56:53AM +0200, Henrik K wrote:
> On Tue, Jan 14, 2020 at 02:38:06PM +0100, Alex Woick wrote:
> >
> > Link to complete message:
> > [2]https://pastebin.com/raw/1DLtnuRX
> >
> > Spamassassin is running as spamc/spamd, and is embedded in Postfix with
> > spamass-milter.
On Tue, Jan 14, 2020 at 02:38:06PM +0100, Alex Woick wrote:
>
> Link to complete message:
> [2]https://pastebin.com/raw/1DLtnuRX
>
> Spamassassin is running as spamc/spamd, and is embedded in Postfix with
> spamass-milter. System is running on CentOS 7.
>...
> Any idea how to find out why
On Sat, 2020-01-18 at 01:29 +0200, Jari Fredriksson wrote:
> On 14.1.2020 15.38, Alex Woick wrote:
> > Spamassassin (3.4.3, the same with previous) declares all or almost
> > all the incoming DKIM-signed messages as DKIM_INVALID, and I'm not
> > understanding why.
> > I'm running opendkim on the
On 14.1.2020 15.38, Alex Woick wrote:
Spamassassin (3.4.3, the same with previous) declares all or almost
all the incoming DKIM-signed messages as DKIM_INVALID, and I'm not
understanding why.
I'm running opendkim on the mail server as milter with Postfix, and
the opendkim headers say the same
amassassin always says DKIM_INVALID
Spamassassin (3.4.3, the same with previous) declares all or almost all the
incoming DKIM-signed messages as DKIM_INVALID, and I'm not understanding why.
I'm running opendkim on the mail server as milter with Postfix, and the
opendkim headers say the same dkim
Spamassassin (3.4.3, the same with previous) declares all or almost all
the incoming DKIM-signed messages as DKIM_INVALID, and I'm not
understanding why.
I'm running opendkim on the mail server as milter with Postfix, and the
opendkim headers say the same dkim signatures are all valid.