-
With mox with a NATed IP address behind a router, when a user sends an email to an other user (both users on the same domain, and the domain is managed by mox), the SPF check always fails because the …
-
SPF and DKIM DNS resources are a critical feature of any DNS deployment. Although they can be deployed as already supported TXT records, they have formatting requirements that are currently disallow…
-
Hi,
Here are the data received from SPF, beta docker image.
- ppv1 : 1975.0
- ppv2 : 0.0
- buck1curr : 250.6…
-
When generating a zone with long TXT records (for example DKIM records with 2048 bit keys), the TXT record becomes to long and named-checkzone fails to validate the zone.
It seems that adding the fol…
-
SPF and DKIM both require TXT records set on the relevant domain or subdomain. Assuming evilginx is being used as intended, and any phishlets' domains have their nameservers configured to point to the…
-
When I try to run the hydarte-spf with the default example or my own domain I get "ValueError: too many values to unpack".
```
./.virtualenv/bin/python bin/hydrate-spf 'v=spf1 a mx ~all' ifixit.com…
-
Websites with SPF records show that no SPF record are there.
dexit updated
8 years ago
-
**Current behavior**
Is there a current behavior that the feature relates to? Yes, DNS64
If yes, would you wish the current behavior to change? No, additional configuration.
**Describe the desire…
-
Basically,
```js
[core] Error
at callback (/Haraka/plugins.js:482:34)
at Plugin.exports.return_results (Haraka/plugins/spf.js:295:20)
at ch_cb (Haraka/plugins/spf.js:214:16)
at m…
-
Hi,
In the readme, for some reason `Received-SPF` is listed twice under Headers.
```
$inbound->Headers('Received-SPF');
$inbound->Headers('MIME-Version');
$inbound->Headers('Received-SPF'); /…
kriiv updated
2 years ago