This Message was undeliverable due to the following reason:
A message was not delivered because a loop was found in the Mail
eXchanger record database (the MX loop condition). The destination
host has an MX record that points to this host, but there is no
account for the designated recipient.
Here are a few possible solutions for clearing up this problem:
- add the domain name to your list of Local Mail Domains
if this mail server has complete authority over all
mail accounts within that domain
- 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: geekpowered.com
The following recipients did not receive this message:
<david@geekpowered.com>
Please reply to Postmaster@mail.mcsweb1.com
if you feel this message to be in error.
--===========================_ _= 3888409(3220)
Content-Type: message/rfc822
Received: from walnut.iea-software.com ([207.53.165.8]) by mail.mcsweb1.com
(Post.Office MTA v3.1.2 release (PO203-101c)
ID# 0-44404U2500L250S0) with ESMTP id AAA11331
for <david@geekpowered.com> Thu, 15 Oct 1998 14:43:33 -0700
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 za002428 for <emerald@iea-software.com> Thu, 15 Oct 1998 15:17:23 -0700
Received: from [206.85.21.2] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id ctlbaaaa for <emerald@iea-software.com> Thu, 15 Oct 1998 15:17:20 -0700
Date: Thu, 15 Oct 1998 17:24:34 CDT
Message-Id: <199810151724.AA1973223974@rwts.qcom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: "MailingList Receiver" <list_rx@qcom.net>
Reply-To: <list_rx@qcom.net>
X-Sender: <list_rx@rwts.qcom.net>
To: emerald@iea-software.com
Subject: callback/emerald/radius attributes
X-Mailer: <IMail v4.06>
X-DomainScript: iea-software.com\\script.mml
X-Script: \\FilterScript.mml
X-UserScript: iea-software.com\emerald\script.mml
>> RadiusNT 2.5, Emerald, PM-3 -
>> I have a user that we will be setting up with ISDN >>service that we will need to dialback to avoid toll >>charges.
>> The customer will be running a 3com router with NAT.
>
>The last I heard, 3Com Office Connect routers do NOT >support
>call back. I almost bought one until I found that out. :(
>
> They will need to dial-up, authenticate into our system >then have the PM-3 drop them, dial them back and make the >permanent connection.
>
> Is this possible and what lines in the SA record need to >be set? I am also assuming there will need to be a >location set into the PM-3..
>
> Reply to the list please as I didn't find anything in the >archive for this -
>
>You might be able to use the RADIUS call back attributes, >but this isn't
>an
>easy task to accomplish.
Just off the phone with customer and 3Com told them they were sent the wrong model router to do it on their end. I just wish to be able to at least attempt to perform accounting on this circuit.
I assume there is a way to specify the RADIUS call back attributes thru the client's SA record. Particularly, if I am going to send a command to initiate a call from the PM-3's location table, which RADIUS attribute(s) are used for that? This isn't very clear to me looking thru the RadiusNT documentation and comparing notes with the PM-3 command line/radius guide. I suppose this is an idea that is implemented rarely - if ever - from Emerald.
You all are `da Experts.
Thanks
--===========================_ _= 3888409(3220)--