We're fairly new with Majordomo and are just starting to put it through its
paces. We have a regular list and a digest list [nytenants and
nytenants-digest], it's moderated and has archives. Sending out several
announcements and getting the bounces we were able to "clean" the list.
Subscribe/Unsubscribe and posting to the regular list seems to work fine.
We have everyone send to the mail list and it all piles up for the digest.
Well our digest went over the trigger mark and whoops! We started getting
tons of returns.
Below is a typical return message. These ranged from user unknown to Remote
Protocol Error. Many were from known good addresses. Notice on the From:,
Sender: and Errors-To: lines the domain indicates AOL and not our server
(cnct.com or list.tenant.net).
>From email@example.com Mon Mar 3 00:25:49 1997
Received: from cnct.com (cnct.com [220.127.116.11]) by emin14.mail.aol.com
(8.6.12/8.6.12) with ESMTP id AAA27644; Mon, 3 Mar 1997 00:25:46 -0500
Received: (from root@localhost) by cnct.com (8.6.12/8.6.12) id XAA19899 for
nytenants-digest-outgoing; Sun, 2 Mar 1997 23:47:22 -0500
Date: Sun, 2 Mar 1997 23:47:22 -0500
From: firstname.lastname@example.org (nytenants-digest)
Subject: nytenants-digest V1 #1
I'm thinking this may be an alias problem, specifically with the usage of
the trailing comma. I'm including the aliase below abd would appreciate any
comments as where we're going wrong. Thanks.
### start of aliases
nytenants: "|/home/d/majordomo-1.94/wrapper resend -l nytenants -h
"|/home/d/majordomo-1.94/wrapper archive2.pl -a -m -f
nytenants-digestify: "|/home/d/majordomo-1.94/wrapper digest -r -C -l
nytenants-request: "|/home/d/majordomo-1.94/wrapper request-answer
nytenants-digest-request: "|/home/d/majordomo-1.94/wrapper request-answer
#### end of aliases