This Message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.
The queue containing messages destined for gl.i-server.net
was expired by the Postmaster of mail.i-server.net.
The following recipients did not receive your message:
Please reply to Postmaster@mail.i-server.net
if you feel this message to be in error.
--===========================_ _= 3681945(144)
Received: from walnut.iea-software.com ([22.214.171.124])
by mail.i-server.net (Post.Office MTA v3.1 release PO205e
ID# 127-49346U1000L100S0) with ESMTP id AAA153
for <email@example.com> Sat, 12 Sep 1998 00:52:39 +0200
Received: from walnut.iea-software.com (walnut.iea-software.com [126.96.36.199]) by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id za000498 for <firstname.lastname@example.org> Fri, 11 Sep 1998 15:40:43 +0100
Received: from [188.8.131.52] by walnut.iea-software.com (NTMail 4.00.0020/NT6651.00.c89adb95) with ESMTP id ldfaaaaa for <email@example.com> Fri, 11 Sep 1998 15:40:39 +0100
Received: from [184.108.40.206] by corona.terraworld.net (NTMail 3.03.0017/12.aabg) with ESMTP id aa622674 for <firstname.lastname@example.org> Fri, 11 Sep 1998 17:54:11 -0500
From: Duane Schaub <email@example.com>
Date: Fri, 11 Sep 1998 22:54:10 "GMT"
X-mailer: AspMail 2.62 (SMTPD334A4)
Subject: RE:Online Provisioning and Bay Networks
Content-Type: text/plain; charset="us-ascii"
We are successfully using the 5399 and 8000 series boxes. We
had a lot of problems until the V.90 was released. They are
very difficult to configure initially... If you are not familiar
with the product, don't expect to open the box and make it work
on the same day like a PM3!
We are still unable to assign Static IP's to a few users. We have
an open ticket on this issue and are having a hard time getting
Bay support to understand the issue.
The boxes are VERY robust but make Cisco look like cake! There are
so many features and the docs are 1800+ pages, that it's difficult
to get all of the options right without leaving security holes or
not being able to authenticate all users. (PAP, CHAP, Clear, etc.)
Also, you will want to disable the built-in HTTP and FTP servers until
a latter release of the Bay OS that supports IP restrictions. The
HTTP server is really cool though.
From: Mike McCarn<firstname.lastname@example.org>
Subject: Online Provisioning and Bay Networks
Is anyone out there using Emerald & RadiusNT with a Baynetworks 5399 access
Also, is there a way to setup online provisioning using Emerald? We would
like to allow people to sign up through our website. If necessary, I could
write the Cold Fusion to do this but I am not sure if this is the best way.
This EMail was sent using QwikMail Online EMail.
Try QwikMail Online EMail at http://www.qwikmail.com.
--===========================_ _= 3681945(144)--