> >>#18 3.6.1, "g=". Is "g=*s*t*e*p*h*e*n" allowed or is one "*" the > >>limit? I don't care, but it should say. > > > >Good catch. Why does the definition for key-g-tag-lpart only allow > >one "*"? > > As already noted, simplicity. There was a comment that it should > only allow "*" at the end, but this would limit the applicability, > e.g., for companies that had a class of addresses that all ended in > "-foo". Is this a large enough use case? I don't know.
I'm going to suggest that this could be a can of worms as the wildcarding is not well define and thus could be interpreted differently. Paul's query about "*s*t*. etc" makes that point. Also, as I understand it, regex is a notoriously ambiguous topic matter. Can I suggest that this is worthy of adding as a tracking item for Eliot to add? We need a clear definition of wildcard evaluation. Can we reference something? Posix perhaps? wildmat() out of INN perhaps? Mark. _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
