-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Julien,
I suggest a new config variable $IGNORE_RFC1918_A.
If enabled (1) A records with RFC1918 addresses aren't treated as bogus
addresses by policyd-weight
anymore and therefore bogus_mx_score is not added. So the current behavior
persis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> The above says "The sender A and MX records are bogus or empty", it
> doesn't say "The sender A or MX records are bogus or empty"?
It's implemented as "The sender A or MX records are bogus or empty", right.
> And anyway, if the sender domain ha
On Thu, Sep 17, 2015 at 23:31:04 +0200, Werner Detter wrote:
> Hi Julien,
>
> this is the default behaviour of policyd-weight, from the manpage:
>
> -- cut --
> @bogus_mx_score (2.1, 0)
> If the sender domain has neither MX nor A records or these records
> resolve to a bogus IP-Address
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Julien,
this is the default behaviour of policyd-weight, from the manpage:
- -- cut --
@bogus_mx_score (2.1, 0)
If the sender domain has neither MX nor A records or these records resolve
to a bogus IP-Address
(for instance private networ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Julien,
I assume the email delivery attempt was made by the regular mailserver
which is responsible for the domain "valiant.palfrader.org"? If I check
that shortly by telnetting to the policyd-weight port and provide the
following information wi
On Thu, Sep 17, 2015 at 23:02:47 +0200, Werner Detter wrote:
> Hi Julien,
>
> I assume the email delivery attempt was made by the regular mailserver
> which is responsible for the domain "valiant.palfrader.org"? If I check
No, it's being relayed via the debian.org mail servers.
> that shortly
Package: policyd-weight
Version: 0.1.15.2-10
Severity: important
Hi,
mail with an envelope from of wea...@valiant.palfrader.org gets flagged
by policyd-weight. As far as I can see, this is due to the RFC1918
address here:
valiant.palfrader.org. IN A 172.22.118.10
valiant.palfrader.o
7 matches
Mail list logo
