Ok, after mungling through the archives. I already have had the digest list as a member of the main list and it is getting the emails, but apparently is rejecting them and I am assuming it is due to the `From`. Log of the digest list:
From akai-request@midicase.com Tue May 8 13:43:13 2001 Subject: Re: [Akai] More a musical question! Folder: formail -R"From X-From_:" -iDate: -iReturn-Receipt-To: -iRea 2010 From akai-request@midicase.com Tue May 8 15:03:00 2001 Subject: Re: [Akai] S5000 Amp mod problem Folder: formail -R"From X-From_:" -iDate: -iReturn-Receipt-To: -iRea 1826
Looking at the Digest archive directory, I see the digest.xx files are not getting populated. I am also assuming that an alternate method is to have the main list send to the digest by way of the rc.local.s20. I'm having trouble finding an example of this. Would someone point me to an example? Also, since I have a few hundred messages that have not been making it to the digest is there a way to send them from the main list archive to the digest list?
At 10:30 PM -0400 5/9/01, Mike Goins is rumored to have typed:
Looking at the Digest archive directory, I see the digest.xx files are not getting populated.
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? Do you realize that you _need_ to have this _if_ you have postings limited to subscribers? (Yes, there _are_ other ways around this, but this is the easiest.)
I am also assuming that an alternate method is to have the main list send to the digest by way of the rc.local.s20. I'm having trouble finding an example of this. Would someone point me to an example?
This is the one I use, and I have never had a lick of trouble with it, but some people suggest there can be lockfile problems. It's really pretty simple; assuming list-l and list-d, in your list-l rc.local.s20 file, add: # # Send this to the digest (which will send it back...) # :0c | flist list-d Note that if you don't have your accept/accept2 files straightened out, this won't work for you, either. (The advantage here is that you can set your list-d alias to pipe to "flist list-l" to avoid having to do a lot of filtering in both lists.)
Also, since I have a few hundred messages that have not been making it to the digest is there a way to send them from the main list archive to the digest list?
You could manually pipe them to flist, manually email them to the digest list, or just forget about it and start from where you get your accept links straightened out. (I actually wondered if there was a "blessed" method for this; I'd be happy to write up a checklist if I were sure what way is considered the "correct" method.) Charlie
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. Do I need to put the list-l address in the list-d accept list? Or more specifically <list>-request@domain address, since this is the address that the -d list is getting the messages from. I though about this but was not sure of the confusing consequences (if any). Maybe I'm do not have an understanding of what you mean by accept vs. accept2
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
(*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
Thanks Charlie! I was up late last night going through the issue. I was even corresponding with my hosting service (who apparently supports it). The issues seemed to be resolved by placing the list-request@domain address in the accept file for the digest. The hosting service was aware of this 'fix' and stated that this did not deliver consistent results. I'm wondering how the next digest will behave as the -request address is in the dist list for the digest. I would imagine that it just get sent back to the maintainer address as a rejection. We'll see.
At 9:15 AM -0400 5/10/01, Mike Goins is rumored to have typed:
I was even corresponding with my hosting service (who apparently supports it).
Wow, that's impressive. Most hosting companies give their users the software for which they pay no licensing fees, and then send their users here for _all_ support. (Great way to shift their support costs, but it doesn't exactly enamour us with those companies...)
The issues seemed to be resolved by placing the list-request@domain address in the accept file for the digest.
(*sigh*) Best case, you get consistant errors...worst case, you get the digest distributed to all of the interactive subscribers. Wouldn't have beeen my choice for a "fix" to a problem that yields to understanding _why_ it's happening.
The hosting service was aware of this 'fix' and stated that this did not deliver consistent results.
Depends on the header fields the machine's mailer is supplying. I have had zero problems cross-linking accept to accept2 files in my interactive/digest pairs. But then, I point my aliases differently than suggested by the Manual and FAQ, too. Charlie
I found some more help in the smartlist FAQ section 2.16. Apparently you can use accept and accept2 files in the list directory. I'm assuming it would be helpful to put the digest members in a mail list accept2 file? Then in the digest, I could put the id of the mail that gets sent to the digest in an accept2 file, and take it out of the accept file. Since there is not a corresponding dist2, the messages are accepted, but not distributed to. No just to find a way to keep the accept2 files up to date in the main list with the digest members?
participants (2)
-
Charlie Summers -
Mike Goins