I was reading the concern about package maintainers regarding adding SPF
capability in MTA packages (where the original source does not do so).
Thinking about this, I can see where many people would not want to have
this enabled "by surprise" (and least not until it is universally in use).
What I was think that could be done is to have a centrally administered
flag that would apply to SPF libraries running under MTAs to enable SPF
or leave it disabled (so as to function as if SPF were not deployed).
That might be the existance of a file "/etc/spf-enabled-in-mta" that the
library could stat() to see if it should proceed. If the file exists,
do the SPF thing. If it does not exist, behave as if there is no SPF,
which I guess would be like "?all". SPF command line tools would not be
affected, other than to mention:
File "/etc/spf-enabled-in-mta" not found, so SPF is not active in your MTA.
Compile-time options could rename the file or disable this feature.
Being more of a system administrator than a programmer (despite 31 years
experience programming, of which 21 is in C and 17 on Unix), I tend to
think in terms of sysadmin flexibility, and like to have "control knobs"
like this. My still-being-written DNS server will have stuff like this
in it.
--
-----------------------------------------------------------------------------
| Phil Howard KA9WGN | http://linuxhomepage.com/ http://ham.org/ |
| (first name) at ipal.net | http://phil.ipal.org/ http://ka9wgn.ham.org/ |
-----------------------------------------------------------------------------
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname@Ë`Ì{5¤¨wâÇSÓ°)h
capability in MTA packages (where the original source does not do so).
Thinking about this, I can see where many people would not want to have
this enabled "by surprise" (and least not until it is universally in use).
What I was think that could be done is to have a centrally administered
flag that would apply to SPF libraries running under MTAs to enable SPF
or leave it disabled (so as to function as if SPF were not deployed).
That might be the existance of a file "/etc/spf-enabled-in-mta" that the
library could stat() to see if it should proceed. If the file exists,
do the SPF thing. If it does not exist, behave as if there is no SPF,
which I guess would be like "?all". SPF command line tools would not be
affected, other than to mention:
File "/etc/spf-enabled-in-mta" not found, so SPF is not active in your MTA.
Compile-time options could rename the file or disable this feature.
Being more of a system administrator than a programmer (despite 31 years
experience programming, of which 21 is in C and 17 on Unix), I tend to
think in terms of sysadmin flexibility, and like to have "control knobs"
like this. My still-being-written DNS server will have stuff like this
in it.
--
-----------------------------------------------------------------------------
| Phil Howard KA9WGN | http://linuxhomepage.com/ http://ham.org/ |
| (first name) at ipal.net | http://phil.ipal.org/ http://ka9wgn.ham.org/ |
-----------------------------------------------------------------------------
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname@Ë`Ì{5¤¨wâÇSÓ°)h