On Mon, 7 Jun 2004, Daniel Quinlan wrote:
Let me run an idea past you all. How about an SPF parameter to indicate
that only permitted senders may relay messages? That is, nobody else
would be allowed to relay messages from the sender, period. (This is
not the same as "-all".)
Already handled via exists.
SPF is already completely general with exists. The only way to make
it more powerful is to define more macros so that more variables are
available to the exists code.
We don't want to add any more shortcut mechanisms for receivers to
execute - because unless *every* receiver executes them the same way,
we have problems. Now that SPF1 is being deployed, we can't afford
to introduce new receiver side mechanisms. As the sender, you can
create whatever algorithms your heart desires - including the very
useful one you mentioned. Remember, receiver side mechanisms are
redundant. They can all be replaced by exists, including the ones
we haven't thought of yet.
I need to find time to setup a Python custom DNS server...
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.