SPF Engine

IgnoreAuthenticatedClients option missing to make it more usable as milter

Bug #1857234 reported by Elias Ohm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SPF Engine
Triaged
Wishlist
Scott Kitterman
SPF Engine spf-engine-future

Bug Description

Hello,

I now shifted to spf checking with YOur python module because the built-in SPF checking of OpenDMARC is a bit quiet.

I'm missing a "IgnoreAuthenticatedClients" options to be able to run pyspf-milter instead of policyd-spf without having it checking authenticated clients which I authenticate to be permitted as sender in question by different means and I think this is a quite common use-case.

At least for the noin-wanted but permitted submitters over port 25 which is used for reception I do not find a solution to skip checks of these mails by spf-milter (other than sticking to policyd-spf where I can put it behind permit_sasl_authenticated to get that effect - I would like to use milter variant).

Revision history for this message
Scott Kitterman (kitterman) wrote :

I think that makes sense to add. If you add smtpd_milters in master.cf as an override for each service you avoid applying the milter to the submission port, but if you have a mix of authorized and unauthorized on port 25, that's not currently supported. The information to do that is available through the milter interface, so this is something I might add in the future.

Changed in spf-engine:
importance: Undecided → Wishlist
milestone: none → spf-engine-future
status: New → Triaged
Revision history for this message
John Hughes (hughes-john) wrote :

Couldn't this be done by fixing bug #1986753 ?

Revision history for this message
Scott Kitterman (kitterman) wrote :

Might be. I'll take a look into it.

Changed in spf-engine:
assignee: nobody → Scott Kitterman (kitterman)
milestone: spf-engine-future → 3.0.0
Revision history for this message
Scott Kitterman (kitterman) wrote :

Actually no. #1086753 doesn't address this. the milter protocol supports it, so the data is available, but I'm going to hold of on this for now, since there's a number of high priority fixes I need to get into 3.0.0.

Changed in spf-engine:
milestone: 3.0.0 → spf-engine-future
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.