On Sunday, February 6, 2022 7:28:22 AM EST Matus UHLAR - fantomas wrote:
> >The spf.py script seems to take the first nameserver only, and whet it
> >gets no response generates the Tempfail error.
>
> That's bad SW design. If one nameserver returns fail, you should try
> another one.
It's an iss
On 2022-02-06 13:28, Matus UHLAR - fantomas wrote:
On 2022-02-06 05:10, Scott Kitterman wrote:
On Saturday, February 5, 2022 11:36:40 AM EST Fourhundred Thecat
wrote:
> On 2022-02-05 16:00, Scott Kitterman wrote:
Here's how you would do essentially the same query as mentioned in
the log
di
On 2022-02-06 05:10, Scott Kitterman wrote:
On Saturday, February 5, 2022 11:36:40 AM EST Fourhundred Thecat wrote:
> On 2022-02-05 16:00, Scott Kitterman wrote:
Here's how you would do essentially the same query as mentioned in the log
directly with pyspf:
python3 /usr/lib/python3/dist-packa
On 2022-02-05 20:46, post...@ptld.com wrote:
Are you saying OpenDMARC is outdated and policyd-spf is more up to
date?
I read (a year ago) it was the other way around.
What wrong validation would OpenDMARC do because of this?
rfc 7208 is not part of libspf2, that makes opendmarc outdated
i do
> On 2022-02-06 05:10, Scott Kitterman wrote:
On Saturday, February 5, 2022 11:36:40 AM EST Fourhundred Thecat wrote:
> On 2022-02-05 16:00, Scott Kitterman wrote:
Here's how you would do essentially the same query as mentioned in the log
directly with pyspf:
python3 /usr/lib/python3/dist-p
On Saturday, February 5, 2022 11:36:40 AM EST Fourhundred Thecat wrote:
> > On 2022-02-05 16:00, Scott Kitterman wrote:
> > On Saturday, February 5, 2022 8:48:22 AM EST Fourhundred Thecat wrote:
> >> policyd-spf: prepend Received-SPF: Temperror (mailfrom)
> >>
> We are considering (and the latest releases release notes say) deprecating
> the internal SPF libs, and currently recommend using libspf2, which is not
> perfect, but at least spares us having to maintain our own internal
> implementation.
> -Dan
My system (RHEL8 flavor) is using OpenDMARC v1
> On Feb 5, 2022, at 2:08 PM, David Bürgin wrote:
>
> post...@ptld.com:
>> If you are going to use DMARC then you do not need to mess around with or
>> install policyd-spf.
>> OpenDMARC has built in SPF lookup, it adds a header with the SPF results,
>> and uses it in deciding if the email pa
post...@ptld.com:
> If you are going to use DMARC then you do not need to mess around with or
> install policyd-spf.
> OpenDMARC has built in SPF lookup, it adds a header with the SPF results, and
> uses it in deciding if the email passes DMARC or not.
OpenDMARC’s is a defective implementation o
> On 02-05-2022 11:47 am, Benny Pedersen wrote:
> On 2022-02-05 17:15, post...@ptld.com wrote:
>> Just in case you were unaware...
>>
>> If you are going to use DMARC then you do not need to mess around with
>> or install policyd-spf.
>
> you will miss latest rfc on this one
>
> libspf2 is old
> On 02-05-2022 11:47 am, Benny Pedersen wrote:
> On 2022-02-05 17:15, post...@ptld.com wrote:
>> Just in case you were unaware...
>>
>> If you are going to use DMARC then you do not need to mess around with
>> or install policyd-spf.
>
> you will miss latest rfc on this one
>
> libspf2 is old
On 2022-02-05 17:15, post...@ptld.com wrote:
Just in case you were unaware...
If you are going to use DMARC then you do not need to mess around with
or install policyd-spf.
you will miss latest rfc on this one
libspf2 is old
> On 2022-02-05 16:00, Scott Kitterman wrote:
On Saturday, February 5, 2022 8:48:22 AM EST Fourhundred Thecat wrote:
policyd-spf: prepend Received-SPF: Temperror (mailfrom)
identity=mailfrom; client-ip=77.75.76.210; helo=mxd2.seznam.cz;
The policy server itself has the ability
Just in case you were unaware...
If you are going to use DMARC then you do not need to mess around with or
install policyd-spf.
OpenDMARC has built in SPF lookup, it adds a header with the SPF results, and
uses it in deciding if the email passes DMARC or not.
When using DMARC you wouldn't want t
On Saturday, February 5, 2022 8:48:22 AM EST Fourhundred Thecat wrote:
> Hello,
>
> I am using python3-spf and I am getting following error from one host
> trying to deliver email:
>
>policyd-spf: prepend Received-SPF: Temperror (mailfrom)
> identity=mailfrom; client-
On 2022-02-05 14:48, Fourhundred Thecat wrote:
Hello,
I am using python3-spf and I am getting following error from one host
trying to deliver email:
policyd-spf: prepend Received-SPF: Temperror (mailfrom)
identity=mailfrom; client-ip=77.75.76.210; helo=mxd2.seznam.cz;
full log here: https
Hello,
I am using python3-spf and I am getting following error from one host
trying to deliver email:
policyd-spf: prepend Received-SPF: Temperror (mailfrom)
identity=mailfrom; client-ip=77.75.76.210; helo=mxd2.seznam.cz;
full log here: https://ctxt.io/2/AABgmS4AFw
What exactly is happening
17 matches
Mail list logo
