Ryan Smith <ryan@rhinointernet.com> wrote:
> I created that directory, and upon sending the mkdigest command to
> majordomo, it replied saying that the digesting had been successful. The
> 001 002 003 004 files were removed from the
> $majordomo_home/digests/blah-list-digest directory, and created 1 file in
> $majordomo_home/lists/blah-list-digest.archive called v01.n001.
Good, that's what's supposed to happen.
> Now just so I'm clear, is it the contents of the v01.n001 file that was to
> be sent to the subscribers of the digested list ?
Yup.
> There were two addresses in blah-list-digest, and neither one of them
> received a digested email.
> Any ideas why the members of blah-list-digest didn't receive the email ?
Perhaps because there's a typo in your blah-list-digest-outgoing
alias? It says:
blah-list-digest-outgoing::include:/usr/local/majordomo/digests/blah-list-digest
Is the member list really in digests/blah-list-digest, or is it
actually in lists/blah-list-digest where member lists usually live?
If that's not the problem then examining your mailer log should give
you some clues.
BTW, using "predictable" outbound alias names like list-outgoing is a
bit of a security risk; people who send directly to that alias will
bypass any checks you've configured through 'resend'. No biggy if
these lists are hosted on an internal machine unreachable from the
outside world, but a possible spam facilitator if that alias is
reachable from the outside world.
Mike.
--
mike.oliver@eng
Follow-Ups:
|
|