Yeah. That's not working.
BW
Maybe it will magically start working in a few hours time
Code: Select all
sudo opendkim-testkey -d exxoshost.co.uk -s default -vvv
opendkim-testkey: using default configfile /etc/opendkim.conf
opendkim-testkey: checking key 'default._domainkey.exxoshost.co.uk'
opendkim-testkey: key not secure
opendkim-testkey: key OK
If you see Key not secure in the command output, don’t panic. This is because DNSSEC isn’t enabled on your domain name. DNSSEC is a security standard for secure DNS query. Most domain names haven’t enabled DNSSEC.
Code: Select all
host -t any default._domainkey.exxoshost.co.uk
default._domainkey.exxoshost.co.uk descriptive text "v=DKIM1\; k=rsa\; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAklxL/jc94pBcmiBhJjsJG5SEPa0MQUAClcl/pb6/5G1DqSqCb4VB0RdkZIBAkmvEkw1QU........
exxos wrote: ↑Thu May 06, 2021 5:42 pm oh...
Code: Select all
host -t any default._domainkey.exxoshost.co.uk default._domainkey.exxoshost.co.uk descriptive text "v=DKIM1\; k=rsa\; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAklxL/jc94pBcmiBhJjsJG5SEPa0MQUAClcl/pb6/5G1DqSqCb4VB0RdkZIBAkmvEkw1QU........
I think this is sound advice, and also I think a big clue to the real cause of the problem lies in the example they gave of "generic" hostnames:
Code: Select all
postconf -e 'myhostname = mail.exxoshost.co.uk'
ok ill change it.xyzzy76 wrote: ↑Thu May 06, 2021 7:20 pm Something like:
Code: Select all
postconf -e 'myhostname = mail.exxoshost.co.uk'
To be fair, that alert was triggered by 12.101.4.84.rev.sfr.net rather than exxoshost.co.uk, which it became later.derkom wrote: ↑Thu May 06, 2021 6:59 pm I bet what's happening here is they have some kind of pattern matching going on that thinks "exxoshost.co.uk" is generic hosting provider reverse DNS, because of the string "host" existing in the domain name. Depending on how they have their regular expression setup, tacking a hostname on the front as @xyzzy76 suggests may well stop it from tripping their "generic" pattern match.