OK, I've noticed differences in the headers, but I still can't figure out what the hell it's problem is sending each message twice... Received: from list by ursine.dyndns.org with local (Exim 3.35 #1 (Debian)) id 16il7Y-0006Hu-00; Wed, 06 Mar 2002 15:46:56 -0800 Date: Wed, 6 Mar 2002 15:46:55 -0800 (PST) From: Paul 'Baloo' Johnson <baloo@ursine.dyndns.org> To: God's Creatures <gc@ursine.dyndns.org> Subject: Echoing Message-ID: <Pine.LNX.4.44.0203061546470.22155-100000@ursine.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <7ft4aC.A.r5F.vpqh8@ursine> Resent-From: gc@ursine.dyndns.org Reply-To: gc@ursine.dyndns.org X-Mailing-List: <gc@ursine.dyndns.org> archive/latest/83 X-Loop: gc@ursine.dyndns.org List-Post: <mailto:gc@ursine.dyndns.org> List-Help: <mailto:gc-request@ursine.dyndns.org?subject=help> List-Subscribe: <mailto:gc-request@ursine.dyndns.org?subject=subscribe> List-Unsubscribe: <mailto:gc-request@ursine.dyndns.org?subject=unsubscribe> Precedence: list Resent-Sender: SmartList <list@ursine.dyndns.org> Resent-Date: Wed, 06 Mar 2002 15:46:56 -0800 And now from the echo.... Received: from list by ursine.dyndns.org with local (Exim 3.35 #1 (Debian)) id 16il7Z-0006IS-00; Wed, 06 Mar 2002 15:46:57 -0800 X-From_:list@ursine.dyndns.org Wed Mar 06 15:46:57 2002 Received: from list by ursine.dyndns.org with local (Exim 3.35 #1 (Debian)) id 16il7Y-0006Hu-00; Wed, 06 Mar 2002 15:46:56 -0800 Old-Date: Wed, 6 Mar 2002 15:46:55 -0800 (PST) From: Paul 'Baloo' Johnson <baloo@ursine.dyndns.org> To: God's Creatures <gc@ursine.dyndns.org> Subject: Echoing Message-ID: <Pine.LNX.4.44.0203061546470.22155-100000@ursine.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <7ft4aC.A.r5F.vpqh8@ursine> Resent-From: gc@ursine.dyndns.org Reply-To: gc@ursine.dyndns.org X-Mailing-List: <gc@ursine.dyndns.org> archive/latest/83 X-Loop: gc@ursine.dyndns.org List-Post: <mailto:gc@ursine.dyndns.org> List-Help: <mailto:gc-request@ursine.dyndns.org?subject=help> List-Subscribe: <mailto:gc-request@ursine.dyndns.org?subject=subscribe> List-Unsubscribe: <mailto:gc-request@ursine.dyndns.org?subject=unsubscribe> Precedence: list Resent-Date: Wed, 06 Mar 2002 15:46:56 -0800 X-Diagnostic: Not on the accept list X-Diagnostic: Mail coming from a daemon, ignored X-Envelope-To: gc-d Resent-Sender: SmartList <list@ursine.dyndns.org> -- Baloo
At 6:48 PM -0500 3/6/02, Paul 'Baloo' Johnson is rumored to have typed:
OK, I've noticed differences in the headers, but I still can't figure out what the hell it's problem is sending each message twice...
It ISN'T sending the mail out to the list twice. One copy is coming to you as the maintainer only, and not to the list. How do I know this?
X-Diagnostic: Not on the accept list X-Diagnostic: Mail coming from a daemon, ignored
Any time you receive mail with X-Diagnostic: header fields, it's mail SmartList is sending to the maintainer ONLY, using the X-Diagnostic: headers to tell the maintainewr what's going on. Charlie
On Wed, 6 Mar 2002, Charlie Summers wrote:
Any time you receive mail with X-Diagnostic: header fields, it's mail SmartList is sending to the maintainer ONLY, using the X-Diagnostic: headers to tell the maintainewr what's going on.
Ah. How do I suppress this? -- Baloo
In article <Pine.LNX.4.44.0203061629350.22155-100000@ursine.dyndns.org>, "Paul 'Baloo' Johnson" <baloo@ursine.dyndns.org> writes:
On Wed, 6 Mar 2002, Charlie Summers wrote:
Any time you receive mail with X-Diagnostic: header fields, it's mail SmartList is sending to the maintainer ONLY, using the X-Diagnostic: headers to tell the maintainewr what's going on.
Ah. How do I suppress this?
You don't want to suppress it. It indicates a condition that may require your attention. In this case, it's telling you that the mail from the `gc' list has been rejected from the `gc-d' list. The solution is probably to link the "accept2" file in the ~list/gc-d directory to the "dist" file in the ~list/gc directory: ln ~list/gc/dist ~list/gc-d/accept2 When a message from the gc list gets forwarded to the gc-d digest list, SmartList will check the "accept" and "accept2" files for gc-d to see whether the poster should be allowed to post to the list. Linking gc's subscriber list to the accept2 list in gc-d makes this work correctly. It's also a good idea to link the digest's "dist" file with the regular list's "accept2" file, for when a digest subscriber posts to the list: ln ~list/gc-d/dist ~list/gc/accept2 I thought that this got handled automatically by the createlist script, actually.
participants (3)
-
Charlie Summers -
Paul 'Baloo' Johnson -
Tim Pierce