At 12:30 AM -0400 5/10/01, Mike Goins is rumored to have typed:
How do you have the accept file set up? Do you have a link from list-l's accept to list-d's accept2 file?
Hmmm. I have a <list>-d in the list-l accept file.
Since accept and dist are linked in the list-l list, and list-d receives the list-l mailing list, that makes a lot of sense. Doesn't have anything to do with the problem, though.
Do I need to put the list-l address in the list-d accept list?
Which (assuming dist and accept are linked in list-d as well, which is the default) would mean list-l would receive the digest issues, which is NOT what you want, now is it? Forget list-l for now...it seems to be working fine, and appears to be sending the mail to list-d, so the problem is in list-d. Stay focused on the DIGEST list, and forget the interactive.
Maybe I'm do not have an understanding of what you mean by accept vs. accept2
That's my bet - they are two seperate files, with two somewhat different functions. I'm also betting that you have foreign_submit UNSET in both lists (that is, people outside the list may NOT submit to the list) - if that assumption is incorrect, everything else I say is completely wrong, and you have some other major problem happening. Look at it this way; if I'm subscribed to list-l, and send an email to list-l, list-l accepts it and then sends a copy to list-d. But since I'm not subscribed to list-d, list-d DOESN'T ACCEPT THE MAIL THAT LIST-L FORWARDED. (It should forward a copy to the maintainer with an X-Diagnostic of "Not on the accept list," or stick it in the maintainer file if you don't have a maintainer address set in rc.custom.) (*sigh*) Much as I prefer explaining the problem, just do this (as whatever user owns your mailing lists): $ cd /path/to/smartlist/list-d $ ln ../list-l/accept accept2 ...and then try it. (Obviously, you _should_ have a set of testing lists to work with, so you can straighten this stuff out without affecting your production lists, but my bet is that you don't.) Charlie