ietf-nomcom message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [ietf-nomcom Home]


Subject: RE: f***ing filter!


Christian,

You could have replied to the From: address in the message you received
and then you would have been in direct contact with the manager, who
would have answered your question.  However, since it's my system being
used I can explain what happened.

It turns out the issue is somewhat subtle.  The message you forwarded to
this list does not actually show the problem.  The message as received
by the server had the following content:

    > > There were a couple of folks who had attended but not registered and
    w-h-o
    > > volunteered to serve.  I took the decision not to allow
    > > this, broadly interpreting attendance to include registration.
    > > Registration is what is being checked to determine whether the
    > > volunteers are qualified.
    >
    > i agree with your conclusion but not your reasoning.  i just don't
    > think we want cheaters on the nomcom.

Note that I put "w-h-o" above but in your message the "who" appeared on
a line by itself.

The filter that checks for subscription commands and the many variations
of the them also checks for certain other server commands, e.g., "help"
and "who".  Its check for those commands is extremely limited.  In fact,
it only looks for those words appearing on a line by themselves.  Well,
guess what?  In the message you sent that was exactly the case.  See
above.

The problem was exacerbated by the fact that the filter does not pay
attention to excerpted text, i.e., all the lines in your message that
begin with ">" are ignored.  Thus, the "who" looked even more like a
command.

Your message is one of the most extreme examples of an edge condition in
this filter that I've seen in a long time.

Jim



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [ietf-nomcom Home]


Powered by eList eXpress LLC