This Message was undeliverable due to the following reason:
A message was not delivered because a loop was found in the Mail
eXchanger (MX) record database. The destination host has an MX
record that points to this host, but there is no account for the
recipient.
Here are a few possible solutions for clearing up this problem:
- return the mail since the address was invalid
- fix the MX records in the DNS for the host in question
and then resubmit the message
- add an account or alias for the recipient on this machine
and then resubmit the message
If this machine should be handling all mail for the destination
host, it should be added to the list of Local-Mail-Domains in
the "System Configuration."
Destination host: allgaeu.net
The following recipients did not receive this message:
<beck@allgaeu.net>
Please reply to Postmaster@ns.allgaeu.net
if you feel this message to be in error.
--===========================_ _= 2146606(3465)
Content-Type: message/delivery-status
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Reporting-MTA: dns; ns.allgaeu.net
Received-From-MTA: dns; [207.53.165.8] [207.53.165.8]
Arrival-Date: Thu, 17 Sep 1998 19:43:47 +0200
--===========================_ _= 2146606(3465)
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Received: from walnut.iea-software.com ([207.53.165.8]) by ns.allgaeu.net
(Netscape Messaging Server 3.5) with ESMTP id AAA4555
for <beck@allgaeu.net> Thu, 17 Sep 1998 19:43:47 +0200
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 za000821 for <radiusnt@iea-software.com> Thu, 17 Sep 1998 10:21:23 +0100
Received: from [204.120.70.18] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id hciaaaaa for <radiusnt@iea-software.com> Thu, 17 Sep 1998 10:21:19 +0100
Received: from jay (jay.office.socket.net [208.19.255.149])
by mail.socket.net (8.8.6/8.8.6) with SMTP id MAA18082
for <radiusnt@iea-software.com> Thu, 17 Sep 1998 12:14:56 -0500
X-Envelope-To: <radiusnt@iea-software.com>
Message-ID: <011401bde260$1cbf9fa0$95ff13d0@jay.socket.net>
From: "Jay Miller" <jaymiller@socket.net>
To: "RadiusNT Mailing List" <radiusnt@iea-software.com>
Subject: Running multiple sessions of RadiusNT on the same server
Date: Thu, 17 Sep 1998 12:25:04 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
I am trying to figure out if it would be possible to run multiple sessions
of RadiusNT on a single server.
The issue is that we want to restrict based on called number (NAS-Port-DNIS)
for some servers. The problem is that not all of our servers provide the
called number attribute, so if we were to place a list of allowed called
numbers in RadATConfigs, no one calling on those servers would be
authenticated. The best solution we can think of is to point the special
servers to a different authenticator. Rather than setting up a second
server to handle two or three servers, we would like to run another session
of RadiusNT, listening on, say, port 1650. This way we could use a whole
separate set of auth properties in the second session.
How does that sound? Any better ideas?
Thanks,
Jay Miller
SOCKET Internet Services
--===========================_ _= 2146606(3465)--