customize versus supercite

I've been trying to get supercite to understand addresses produced by our *wonderful* exchange server. Addresses look like "Raymond Toy (EUS)" <EUSRTOY(a)am1.ericsson.se&gt; The solution I came up with is to use sc-attrib-selection-list with sc-consult to get what I want. What I did was to use this for sc-attrib-selection-list: (("from" (("\"\\([^ ]+\\) \\([^ ]+\\) (EUS)" (let ((field (sc-mail-field "from"))) (string-match "\"\\([^ ]+\\) \\([^ ]+\\) (EUS)" field) (match-string 1 field)))))) If I set this directly, this almost works. The problem is in sc-select-attribution when it tries to eval the list. sc-scan-info-alist returns that as '((let ((field ...)))) which can't be eval'ed. I had to use (eval (first attrib)) instead of just (eval attrib). I guess I could have made sc-scan-info-alist return the right thing too. Now, when I tried to use customize to set this, customize puts an extra set of parens around the list, so sc-select-attribution now sees '(((let ((field ...))))), which is even worse. I can supply a patch for supercite, if someone can tell me if sc-select-attribution or sc-scan-info-alist should be changed. I don't know what to do about customize in this case. Ray