A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:
annabel@pop3.zamnet.zm:
Too many "Received" headers for remote delivery
------ This is a copy of the message, including all the headers. ------
Return-path: <radiusnt-return@iea-software.com>
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTh-0003PI-00; Fri, 16 Oct 1998 00:02:37 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTg-0003PG-00; Fri, 16 Oct 1998 00:02:36 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTf-0003PE-00; Fri, 16 Oct 1998 00:02:35 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTd-0003PC-00; Fri, 16 Oct 1998 00:02:33 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTc-0003PA-00; Fri, 16 Oct 1998 00:02:32 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTb-0003P8-00; Fri, 16 Oct 1998 00:02:31 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTZ-0003P6-00; Fri, 16 Oct 1998 00:02:29 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTX-0003P3-00; Fri, 16 Oct 1998 00:02:27 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTV-0003Oy-00; Fri, 16 Oct 1998 00:02:25 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTU-0003Ow-00; Fri, 16 Oct 1998 00:02:24 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTT-0003Ou-00; Fri, 16 Oct 1998 00:02:23 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTS-0003Os-00; Fri, 16 Oct 1998 00:02:22 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTR-0003Oq-00; Fri, 16 Oct 1998 00:02:21 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTP-0003Oo-00; Fri, 16 Oct 1998 00:02:19 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTO-0003Om-00; Fri, 16 Oct 1998 00:02:18 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTM-0003Ok-00; Fri, 16 Oct 1998 00:02:16 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTL-0003Oh-00; Fri, 16 Oct 1998 00:02:15 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTI-0003Od-00; Fri, 16 Oct 1998 00:02:12 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTH-0003Ob-00; Fri, 16 Oct 1998 00:02:11 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTF-0003OQ-00; Fri, 16 Oct 1998 00:02:09 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTD-0003OO-00; Fri, 16 Oct 1998 00:02:07 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvTB-0003OM-00; Fri, 16 Oct 1998 00:02:05 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvT9-0003OI-00; Fri, 16 Oct 1998 00:02:03 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvT6-0003O7-00; Fri, 16 Oct 1998 00:02:00 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvT3-0003O1-00; Fri, 16 Oct 1998 00:01:57 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvSz-0003Nw-00; Fri, 16 Oct 1998 00:01:53 +0200
Received: from puku.zamnet.zm [196.7.240.1]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvSy-0003Ns-00; Fri, 16 Oct 1998 00:01:52 +0200
Received: from relay.zamnet.zm [196.7.240.3]
by puku.zamnet.zm with smtp (Exim 1.61 #1)
id 0zTvSv-0003NZ-00; Fri, 16 Oct 1998 00:01:49 +0200
Received: from walnut.iea-software.com (walnut.iea-software.com [207.53.165.8])
by relay.zamnet.zm (8.9.1a/8.9.1a) with ESMTP id AAA09115
for <amwansa@zamnet.zm> Fri, 16 Oct 1998 00:00:24 +0200 (ZMT)
Received: from walnut.iea-software.com (walnut.iea-software.com [207.53.165.8]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za002410 for <radiusnt@iea-software.com> Thu, 15 Oct 1998 14:11:38 -0700
Received: from [207.53.165.21] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id qplbaaaa for <radiusnt@iea-software.com> Thu, 15 Oct 1998 14:11:35 -0700
Message-ID: <3626681E.5753A256@iea-software.com>
Date: Thu, 15 Oct 1998 14:24:46 -0700
From: "Dale E. Reed Jr." <daler@iea-software.com>
Organization: IEA Software, Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; I)
MIME-Version: 1.0
To: David Moore <dmoore@communitychoice.net>
CC: radiusnt@iea-software.com
Subject: Re: DNIS
References: <3.0.1.32.19981015034239.008e7b7c@communitychoice.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Script: \\FilterScript.mml
X-DomainScript: communitychoice.net\\script.mml
X-UserScript: iea-software.com\radiusnt\script.mml
X-Info: -Reply-To: radiusnt@iea-software.com
X-ListMember: amwansa@zamnet.zm [radiusnt@iea-software.com]
Content-Transfer-Encoding: 7bit
David Moore wrote:
>
> What is the DNIS functionality in the enterprise version supposed to do? I
> cant seem to find any documentation on it.
You might want to re-download the RadiusNT 2.5 docs. The updated docs
on
the FTP site include a full chapter on the Enterprise features,
including
DNIS. Here is an excerpt:
DNIS Access
DNIS Access allows you to limit the telephone numbers an Account Type
can log into. When DNIS Access is enabled, RadiusNT will search for a
matching entry in the DNISNumbers table that matches the NAS-Port-DNIS
attribute in the Authentication request (to the DNISNumber field) and
DNISGroupID matching the DNISGroupID field of the AccountType of the
authenticating user. If a match is found access is granted. If no
match is found the user is not allowed to log via that number.
DNIS Access is not enabled by default. You must enable DNIS Access in
the RadiusNT administrator and restart RadiusNT before it will work.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com