Hello Exim users,
We recently received many of our end users complains that they are having
problem sending email to *.gov.hk with this exim error:
DANE ERROR: TLSA LOOKUP DEFER
However we have contacted our government and their responds is:
“Our DNSSEC setup is fine, and it is not nesserary to
te:
> On Wed, Mar 25, 2020 at 01:10:53PM -0400, Phil Pennock via Exim-users
wrote:
>
> > On 2020-03-23 at 20:54 +0800, daniel via Exim-users wrote:
> > > We recently received many of our end users complains that they
are having problem sending email to *.gov.hk with this e
wrote:
On 2020-03-23 at 20:54 +0800, daniel via Exim-users wrote:
We recently received many of our end users complains that they are having
problem sending email to *.gov.hk with this exim error:
DANE ERROR: TLSA LOOKUP DEFER
Their DNS is broken.
However we have contacted our government
, it INSTANTLY
works again.
Thank you.
On 2020/3/30 下午 07:34, Phil Pennock wrote:
On 2020-03-25 at 13:10 -0400, Phil Pennock via Exim-users wrote:
On 2020-03-23 at 20:54 +0800, daniel via Exim-users wrote:
We recently received many of our end users complains that they are having
problem
The only thing I replaced is database name, database user and password.
so it is "127.0.0.1/mail/mailro/mysupersecretpassword"
(password obviously changed), it doesn't say anything else...
Pasting the full line here again:
message: failed to expand "${lookup pgsql {servers=127.0.0.1/xx/xx/xx;
Thanks, changing the syntax for the pgsql server/credentials did the trick!
2. Juni 2020 16:37, "Jeremy Harris via Exim-users"
schrieb:
> On 02/06/2020 15:29, dan...@k8n.de wrote:
>
>> The only thing I replaced is database name, database user and password.
>>
>> so it is
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
PDKIM >> Signed DKIM-Signature header, canonicalized >>>>>>>>>>>>>>>>>
dkim-signature:v=1;{SP}a=rsa-sha256;{SP}q=dns/txt;{SP}c=relaxed/relaxed;{SP}d=btlancashire.co.uk;{SP}s=x;{SP}h=Date:Su
Message classification: OFFICIAL
Hi all
We need to add disclaimers to out email and also use DKIM to sign our messages.
Each of these things work individually but if they are both configured on a
transport then the DKIM check fails because the disclaimer is added after the
signature has been
