per user regex/domain issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SPF Engine |
Triaged
|
Medium
|
Unassigned |
Bug Description
The policyd-
"
In addition to specifying individual users, regular expression matching
is also available, but may have performance implications since the
entire user table has to be traversed for each message recipient.
"
However, the code does a simple string comparison.
http://
A simple implementation would be have it check the domain as well so that I could specify something like
example.
So that mails sent to any recipient of the domain example.net is allowed to be forwarded via google.com but any other recipients sent from google.com are subject to the regular SPF checks.
A simple additional test on line 78 would probably solve this.
if user != recipient and user != recipient.
Changed in pypolicyd-spf: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in pypolicyd-spf: | |
milestone: | none → later |
Changed in pypolicyd-spf: | |
status: | Triaged → Invalid |
status: | Invalid → Confirmed |
status: | Confirmed → Opinion |
Changed in pypolicyd-spf: | |
status: | Opinion → Triaged |
Changed in spf-engine: | |
milestone: | none → spf-engine-future |
pypolicyd-spf is in maintenance only mode. Transferring to spf-engine for future consideration.