Problem: a person on the distribution list whose email accountname is the same as the beginning of the listname CANNOT submit to the list. Even if "person@xx.yy.zz" is in the file accept(dist) or accept2, when they attempt to submit to "personlist@xx.yy.zz" they are seen as "Not on the accept list". I have the lastest software bits for Smartlist, in particular, for multigram.c I can see that the problem results from multigram returning an error (when it should not). For example, with "person@xx.yy.zz" in the accept file (linked to dist), and given this in file "msg":

Subject: got this? Date: Mon, 1 Dec 2014 14:07:25 -0800 To: personlist <personlist@xx.yy.zz> From: person@xx.yy.zz

That is really great. el persono

this formail|multigram pipe from rc.submit returns "worked": if cat msg|formail -X"From " -xFrom: -xReply-To: -xSender: -xResent-From: -xResent-Reply-To: -xResent-Sender: -xReturn-Path: |../.bin/multigram -b1 -m -l28672 -Lzoology.ubc.ca -xbpersonlist@zoology.ubc.ca -xbpersonlist-request@zoology.ubc.ca accept accept2; then echo worked; else echo failed; fi While this, with bpersonlist => personlist, fails: if cat msg|formail -X"From " -xFrom: -xReply-To: -xSender: -xResent-From: -xResent-Reply-To: -xResent-Sender: -xReturn-Path: |../.bin/multigram -b1 -m -l28672 -Lzoology.ubc.ca -xpersonlist@zoology.ubc.ca -xpersonlist-request@zoology.ubc.ca accept accept2; then echo worked; else echo failed; fi If someone could point to the unanchored match in the impressively dense code of multigram.c, I would be grateful. This problem happens often for me where we have a guy einstein@xx.yy.zz wanting to submit to his own lab's mailing list "einsteinlab@xx.yy.zz" Thanks, Alistair