HDTenEightyP/NetNews huggingface dataset:
From: SYSTEM@TEX.AC.UK (UK TeX Archive Manager <system@uk.ac.tex>)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: What is the PC way of testing mail/network connectivity?
Date: Fri, 22 Jan 93 12:42 GMT
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

In message <9301211703.AA07595@hqpyr1.us.oracle.com> dated Thu, 21 Jan 93
09:03:51 PST COMET@com.oracle.us (Comet) said:

>In-Reply-To: HQPYR1:info-multinet-relay@TGV.COM's message of 01-21-93 06:32
>
>On USEnet, there are test newsgroups (e.g. ba.test, misc.test) which are used
>to test if a person's posts will make it out into the greater computropolis.
>
>But where is a test mail address?  Is there some kind of mail-reflector or a
>gateway to/from the test newsgroups or anything?  After all, not every site HAS
>USEnet newsgroups.

Seems like a ``good idea'' to have such a reflector, but I've never heard of
one {\latin per se}.

However, anyone who is interested is welcome to use a facility which was set up
on this machine back in the drear dark days in which callers to TeXserver were
required to provide a return address.  Since many people didn't know what this
would be (given that non-Janet callers were furthermore required to specify the
approriate gateway too), I set up a facility such that anyone could mail to
<RMCS_TeX@TeX.ac.uk> specifying a subject line in the mail that read WHERE AM I,
with or without whitespace, and with or without a trailing `?'.  The text could
appear in UPPER, lower or mIxEd case.

What was mailed back was a message giving the address of the calling site in a
format that could be used (in fact was used, to post the notification) to send
TO that calling site FROM uk.ac.TeX.  The only restriction that I would warn
you of these days is that the command procedure which does the parsing is still
only cognizant of Grey-Book Mail address ordering, for mail arriving through
DEC's CBS product.  IT WILL NOT understand incoming SMTP mail, which has the
addresses in the reverse of the standard UK ordering, although such mail is
receivable here.  So if your mailer bypasses the MX records which specify that
mail for TeX.ac.uk shall be routed through nsfnet-relay.ac.uk, it won't work.

Brian {Hamilton Kelly}
System Manager for the
UK TeX Archive at Aston Universtiy
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: TCP-IP Cards for HP IIIsi's
From: Plain@ACAD.FANDM.EDU (Jack Plain - Networks and Systems)
Date: 26 Jan 1993 14:55:48 -0500
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

What TCP-IP cards are some of you using for your HP IIIsi printer(s) and
where do you purchase them?
Thanks 
Jack Plain
Plain@fandm.edu
From: NED@SIGURD.INNOSOFT.COM (Ned Freed)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: mail problem
Date: 27 Jan 93 04:21:44 GMT
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> There are very few computer/network applications in our environment that 
> don't provide an immediate indication when an error occurs.  Unfortunately
> one of our most critical computer/network applications (e-mail) is an
> application that doesn't provide immediate notification.  Do any Multinet 
> sites have an automated alarm system to determine when e-mail is not being 
> delivered?  Waiting for user complaints is not appropriate in our business.

This sort of system-level monitoring of the overall health of the email system
is quite a different problem than per-user-per-message reporting. Although
probe messages are a useful tool, it is usually more important to monitor
aggregrate statistics like message queue sizes, mean time to delivery, and so
on.

The problem with monitoring and reporting on email is that email itself often
as not is the tool of choice for providing notification about application
errors. (For example, the print symbiont we use locally reports PostScript
errors via email.) But if there's a problem in the email system the last thing
you want to use to report it is email! I've seen email-reports-on-email setups
go into catastrophic overload and meltdown on more than one occasion; one such
mess took several days of staff time to clean up.

The obvious tool to use for this sort of monitoring would be SNMP, of course.
(I won't bother to explain SNMP's characteristics that make it a good choice
here.) However, application monitoring with SNMP has received almost total
neglect in IETF circles -- I don't know why this is so, but it sure is!

There is a very rudimentary Applications MIB that provides facilities for
monitoring mail systems and directory services. However, in my opinion
it is not suitable at present for serious production use.

But there is some hope -- there's a new IETF working group called MADMAN (Mail
And Directory Management) whose task is to put together a pair of MIBs for
monitoring mail and directory systems. The group is off to a slow start but I
am hopeful that things will begin to move in the near future.

> >The only thing that's unreliable about nondelivery notices is the inconsistency
> >of their generation. However, users adapt amazingly quickly to the nature of
> >the systems they use, so they usually take these differences in stride.

> And the amount of time that must pass before they are generated.  The default
> value on systems here ranges from 7 days to a few hours.  The user community
> prefers a standard delay (preferably single digit hours), but that is hard
> to implement when some vendors hardcode this value.

Not only must this be settable to a wide range of values, it also must
vary from one service to the next. User expectations of email, FAX, and pagers,
for example, are quite different. PMDF, for example, provides per-hour
or per-day units that can be set on a per-channel basis.

				Ned
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Mail Problem
From: SEF@GROUCH.JPL.NASA.GOV (Better is the enemy of good... Voltaire)
Date: Mon, 25 Jan 1993 11:16:01 -0800 (PST)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List


A question about Internet mail and Multinet: Is there any way to set the return
time on old undeliverable mail messages? A user (and a manager) of mine
recently complained about learning 4 days later that his message didn't get
through. He would prefer wait no longer than 24 hours. Is this a user settable
variable? 

Thank You, 
Scott Fullner, JPL Navigation
From: SHEAFFER_DM@DIR.TEXAS.GOV (Danny Sheaffer)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: MultiNet SMTP agent config vs. sendmail
Date: Mon, 25 Jan 1993 14:10:28 -0600 (CST)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

Howdy

I'm having a problem sending mail from MultiNet to a UNIX host.  The problem
seems to be with the sendmail configuration on the UNIX system.  It doesn't
seem to know the equivalent of it's "SMTP Host Name" and returns the following
error in the bounced mail message:

	   ----- Transcript of session follows -----
	>>> HELO delta1.tsl.texas.gov
	<<< 553 Local configuration error, hostname not recognized as local
	554 <root@tsl.texas.gov>... Service unavailable

Is this indeed the problem and does anybody know how to fix it?

Danny Sheaffer
danny@dir.texas.gov
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: (None)
From: SB_WDK@GEN.GETRONICS.NL
Date: Thu, 21 Jan 1993 14:53:11 +0200 (CET)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List


Hello,

I don't really have a problem, but consider this as a test.
We've just finished the installation of Multinet 3.1D on a VAX-3100
model 90, running VMS 5.5-2.
Thusfar without any problems, and now we're testing the functionality
of email and our Domain Name System.
So please send a reply on this mail.

Greetings in behave of the Systems and Network Management Group of
Geveke electronics b.v. - The Netherlands.

Wilfried Dudink


*******************************************************************************
* Geveke electronics b.v.             * Internet: dudinkw@gen.getronics.nl    *
* I&A Department                      * Phone   : +31-20-5879497              *
*                                     * Fax     : +31-20-5879400              *
* Donauweg 10                         *                                       *
* 1043 AJ AMSTERDAM                   *                                       *
* THE NETHERLANDS                     *                                       *
*******************************************************************************
From: mcmahon@TGV.COM (Midnight at U Street Metro Station)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: FWD: RE: Mail Problem
Date: Mon, 25 Jan 93 11:38:42 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

(went to info-multinet-relay by mistake)

>A question about Internet mail and Multinet: Is there any way to set the 
return
>time on old undeliverable mail messages? A user (and a manager) of mine
>recently complained about learning 4 days later that his message didn't 
get
>through. He would prefer wait no longer than 24 hours. Is this a user 
settable
>variable? 

No, it's a system-wide setting.  The logical name that controls it is
MULTINET_SMTP_RETURN_INTERVAL; it's equivalence string should be a VMS
delta time value.   If you wanted to set the value to be one day, for
example, you would define it as follows:

    $ DEFINE/SYSTEM/EXEC MULTINET_SMTP_RETURN_INTERVAL "1 00:00:00.00"

-Matt


--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
From: RABINOWITZ@vax4.bear.com (Ari Rabinowitz, WorkStations, x6518)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Problem with X11 TCP/IP transport not finding host names
Date: Thu, 21 Jan 1993 13:38:23 -0500 (EST)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

Hi,

I am having a problem with the TCPIP transport finding hosts.  I have seen
this before, when some old UCX files existed in the SYS$SYSTEM directory.
I have renamed all of the UCX$*.DAT files to other names, but the problems
persist.

Here is a sample:

VAX2::[] >> sh disp/symb

    Device:    WSA112:  [super]
    Node:      XBOSTON
    Transport: TCPIP
    Server:    0
    Screen:    0

VAX2::[] >> mu trac 'DECW$DISPLAY_NODE'
traceroute to xboston (147.107.244.120), 30 hops max, 38 byte packets
 1  cn_whip1-e4 (147.107.3.200)  0 ms  0 ms  10 ms
 2  wpvaxbup (147.107.7.203)  10 ms  10 ms  10 ms
 3  pwvaxbup-wan (147.107.9.201)  10 ms  10 ms  10 ms
 4  147.107.1.211 (147.107.1.211)  20 ms  20 ms  10 ms
 5  boston_site (147.107.245.201)  320 ms  60 ms  110 ms
 6  xboston (147.107.244.120)  50 ms  80 ms  50 ms
VAX2::[] >> mu x11
%X11DEBUG-I-STARTING, MultiNet X11 transport diagnostics starting...
%X11DEBUG-F-UNKNOWNHOST, unknown host XBOSTON
-X11DEBUG-I-USERACTION, reissue the SET DISPLAY command with a valid /NODE= 
qualifier
VAX2::[] >>

As you can see, the node xboston exists and is responding, and MultiNet knows
about it for the Traceroute, but the TCPIP transport doesn't see it.

I've tried the obvious of putting the host name in quotes so that is is
"xboston" not XBOSTON but it makes no difference.  I've even restarted the
MultiNet server after renaming the UCX$*.DAT file.

What else can I do?  Any suggestions would be gratefully accepted.

Thanks,
Ari
--
Ari Rabinowitz                  rabinowitz@bear.com for VMS and personal mail
WorkStation Administrator	ari@bear.com for sun/HP Un*x mail
Bear Stearns
From: JFISHER@ISDRES.ER.USGS.GOV (James R. Fisher 703-648-7026)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: multinet_smtp_return_interval
Date: Mon, 25 Jan 1993 16:54:29 -0500 (EST)
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

In a previous article, madison@TGV.COM wrote:
> 
>No, it's a system-wide setting.  The logical name that controls it is
>MULTINET_SMTP_RETURN_INTERVAL; it's equivalence string should be a VMS
>delta time value.   If you wanted to set the value to be one day, for
>example, you would define it as follows:
> 
>    $ DEFINE/SYSTEM/EXEC MULTINET_SMTP_RETURN_INTERVAL "1 00:00:00

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
IMHO, it would be nice to have more than one such logical, each tied to
a specific queue, so that i could have a say, 'local mail' queue with
return interval of 12-24 hours for mail going to reliable sites in 
usually accessible places, and another queue, say, 'overseas mail'
with a return interval of 5-7 days for mail going to places where the
availability of nameservers and connectivity to distant hosts is
problematical.
-jrf

 
jfisher@isdres.er.usgs.gov        James R. Fisher
jfisher@usgsresv  (Bitnet)        US Geological Survey, Reston, VA 22092
isdres::jfisher   (Span)          703-648-7026
From: adelman@TGV.COM (Kenneth Adelman)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: mail problem
Date: Mon, 25 Jan 93 18:18:16 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> Some SMTP mailers issue nondelivery messages on a periodic basis.  Thus after
> the mail has been in queue for an hour, the sender would receive a message
> similar to:

>      From: Mailer_Daemon
>      To:   originating_user
>      Subject:  RE:  subject_line_of_original_message

>      This message has not been delivered after 1 hour.

>      The system will keep trying to deliver this message for 48 hours.
>      At that time, the message will be returned to you.

>      Thank you for your patience.

> Using nondelivery times of 1/2, 1, 2, 4, 8, 12, 16, 24, 36, and 48 hours
> (actually 1/2, 1, and 24 are probably sufficient) would ensure that the
> originator was well aware of the delay in delivery yet allow sufficient
> time for the message to get through a slow link.

> Does anyone think a feature of this sort should be included in Multinet?

    I've always lobbied very strongly AGAINST this sort of thing. It
can turn simple mail loops into something that explodes exponentially. I
feel that unless specificically requested (eg, mailing list explosion)
a mailer should never generate more than one message out for each message
that arrives inbound.

							Ken
From: adelman@TGV.COM (Kenneth Adelman)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: Enhancement request.
Date: Thu, 21 Jan 93 11:25:46 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> I have a suggestion for the NFS Configuration interface:

> We've got several file systems exported with Multinet NFS.  I've just
> removed a host from the allowed to mount list and find the user interface
> in MU CONFIG/NFS somewhat lacking.  I can't SHOW anything except everything
> or a selected mount point.  The problem is that I don't remember all the
> mount points I have exported.  And they go by so fast when I do a SHOW who
> can catch them?  Anyway, a variation on the following themes would be nice.

> Remove a particular host from all the exported disks:

>    NFS-CONFIG> DELETE MOUNT-RESTRICTION <host> *

> Add a particular host to all the exported disks:

>    NFS-CONFIG> ADD MOUNT-RESTRICTION <host> *

> And for variation, how 'bout adding a /CONFIRM qualifier so it prompts me
> yes or no for the deletion or addition on each mount point before it does
> it?

> Show just the exported file systems:

>    NFS-CONFIG> SHOW/EXPORT

> Show the UID mapping for a single username:

>    NFS-CONFIG> SHOW/UID <username>

> The method I use now, is to EDIT/TPU/READ MULTINET:NFS.CONFIGURATION in one
> window and then run MU CONFIG/NFS in another workstation window.  Without a
> workstation, the procedure would be even more cumbersome.

    The SHOW command enhancement is already planned.

								Ken
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re: Change directory in FTP Server.
From: adelman@TGV.COM (Kenneth Adelman)
Date: Tue, 26 Jan 93 08:22:58 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> I've got a problem with our FTP Server. I want to use "cd .." to go back
> one directory, but it doesn't work.
> I've seen sites where it does work (also with MultiNet), so I want to know
> how I can change this.
> The point is, I've got some disappointed "dos" and "unix" users, who don't
> even know what VMS is. (We are running MultiNet 3.1D)

    Well, unfortunately, a little while back I was tied up and against
my will forced to allow "cd .."  act like "cd [-]".  The reason it
shouldn't is that ".."  is a UNIX filespec and FTP is supposed to
implement the file specifications of the operating system it is
running on.  I agree with the previous poster that "CDUP" is the
correct operating system independent way of going up one level in a
directory tree.

							    Ken
From: VANCE@TGV.COM (L. Stuart Vance)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re:  TCP-IP Cards for HP IIIsi's
Date: 27 Jan 93 01:37:48 GMT
Organization: TGV, Incorporated
X-Gateway-Source-Info: Mailing List

>What TCP-IP cards are some of you using for your HP IIIsi printer(s) and
>where do you purchase them?

We use the HP JetDirect cards (part number 2059T).  They work just great with
our stream symbiont (plus, we have a dandy setup text library that one of our
customers put together for the IIIsi).  Use anonymous FTP to PUBLIC.TGV.COM and
get the stuff out of the [.HPLJ3SI] directory.

Regards!
-----Stuart
From: VANCE@TGV.COM (L. Stuart Vance)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Re:  TCP/IP via PSI **REAL** slow?
Date: Sun, 24 Jan 1993 22:34:55 -0800 (PST)
Organization: TGV, Incorporated
X-Gateway-Source-Info: Mailing List

>We may (in the next two months) try to use Multinet's TCP/IP encapsulated
>within X.25 to gateway traffic from our Holland office to our local Colorado
>office.  The reason we want to try something sooo boneheaded is because the
>X.25 bridges are DNA traffic relays only (I may not be explaining this very
>well).  What we have is a VAX with PSI sending/receiving data to/from a DEC
>DEMSB (I hope that's the right letters) on both sides of the world.  What's
>better is this existing link is only 9600 baud!  Could you laugh any harder?
>:-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-( :-(
>
>Anyway, is this doomed?  *OR*, with huge performance delays assumed, will
>it work?  Is anyone out there trying something similar (God help you)?
>With any luck, upper management will spring for extra $$ for a faster X.25
>link at the very least.

Your delays/performance problems will be twofold: the low bandwidth, and the
high latency (round trip time).  TELNET will be rather painful because of the
latter, FTP painful because of the former.  It's certainly not hopeless. 
Things will function, but you'll need to set your expectations rather low from
the start.  The main thing is to bring up the link in "test" mode first to see
how good or bad it will be before turning it over to your users.

Regards!
-----Stuart
From: mcmahon@TGV.COM (Midnight at U Street Metro Station)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: FTP "welcome" message
Date: Wed, 27 Jan 93 19:10:06 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

> Some time ago, I FTPed into a VMS/MultiNet system that had a nice little
> (10 lines or so) "welcome" explaining that it was a VMS machine and here's
> how directories are specified, and what file names look like, etc.
> 
> I'd like to use the /MESSAGE facility of the FTP server to do this.  I want
> to "borrow" the verbage but can't remember where I saw it.  Anybody care to
> point me at a system with what they consider a "good" FTP welcome?
 
 I like the ones on TGV.COM and PUBLIC.TGV.COM :-)
 
Cheers!
John 'Fast-Eddie' McMahon    ()
TGV, Incorporated            () "Any networking problem can be solved by
603 Mission Street           ()  the application of 33 miles of Unshielded 
Santa Cruz, California 95060 ()  Twisted Pair (UTP)"   
408-427-4366 or 800-TGV-3440 ()                      [InterOp Spring 1992]
E-Mail: MCMAHON@TGV.COM      ()
From: mahan@TGV.COM (Patrick L. Mahan)
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: Not really related but...
Date: Thu, 21 Jan 93 09:38:55 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

#
#This question is not related to Multinet, but since I know expertise
#lives on this list, here goes:
#
#	On VMS AXP V1.0, how does one go about linking against the 
#	the system symbol table?  SYS.STB does not exist and many (most)
#	of the other .STB files in sys$loadable_images: do not get
#	along with the linker. I get the following error:
#
#%LINK-F-NOLINKSTB, linker-generated symbol table file is illegal input
#        module PROCESS_MANAGEMENT file SYS$COMMON:[SYS$LDR]PROCESS_MANAGEMENT.STB;1
#
#	
#Do we have a dame-bramaged release of VMS AXP with a mix of VAX and Alpha
#Symbol table files?
#

To access the System wide globals that you use to obtain via SYS.STB is now
obtained by linking to the shareable image SYS$LOADABLE_IMAGES:SYS$BASE_IMAGE.EXE

Patrick L. Mahan

--- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------

Waking a person unnecessarily should not be considered  - Lazarus Long
a capital crime.  For a first offense, that is            From the Notebooks of
							  Lazarus Long
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: RE: Problems with POP3
From: busma@TGV.COM (Jeffrey D. Busma)
Date: Wed, 27 Jan 93 11:42:19 PST
Organization: Info-Multinet<==>Vmsnet.Networks.Tcp-Ip.Multinet Gateway
X-Gateway-Source-Info: Mailing List

 From: markp@yang.earlham.edu (Mark H Pearson)

>1/27/92 Problems with POP3 with Multinet 3.1
>I am using Nupop 1.03 on my PC which has performed flawlessly until today.
>It sneezed on 44 messages in newmail. Here's the grimy story :
>
>NUPop 1.0.3
>DOS version              = 5.0
>Win3 enhanced mode       = No
>DesqView active          = No
>TCP driver type          = Built-in NUTCP
>Heap space available     = 58352
>Virtual memory available = 1035233
>Buffer space available   = 67376
>TCPNew: OK
> found <yang.earlham.edu> in cache.TCPConnect:  OK
>Leaving TCPConnect
>Waiting for a line starting with a <+>
>Error signalled if line starts with a <->
><--"+OK YANG.EARLHAM.EDU MultiNet POP3 Server Process 3.1(1) at Wed 27-Jan-93 10
>   :57AM-EST"
>-->USER markp
>Waiting for a line starting with a <+>
>Error signalled if line starts with a <->
><--"+OK User name (markp) ok. Password, please."
>-->*************
>-->
>Waiting for a line starting with a <+>
>Error signalled if line starts with a <->
>  Timed out, network not responding
>  Timed out, network not responding
>TCPDisconnect: OK.
>TCPDispose entered: TCPDispose done.
>Error while reading from network
>TCPUnInit starts:  OK
>TCPUnInit finished.
>
	The POP client seems to be timing out waiting for the server to read all the
	mail in the mailbox and calcuate the length of all the messages before it send 
	the response back for the PASS command as specified in  RFC 1225.

	What is ths timeout period for the client and can you change it?

	There is a work around for this in 3.1 Rev-D  and 3.2 that sends the the +OK status back 	
	before the mailbox is read.

	Note that SYLOGIN.COM and LOGIN.COM are excuted so you may want to 
		$ if f$mode() .eqs. "NETWORK" .and. - 
		f$trnlnm("TT") .eqs. "MULTINET:POP3_SERVER.COM"  then exit 

	So you're not doing a lot of symbol assignment interactive things which can take time.

	I missed the part about POP sneezing on 44 messgaes. If you saying it corrupted the mail
	please open a support call by sendig mail to SERVICE@TGV.COM include the POP3_SERVER.LOG
	file. Your PC log just shows the PC is timing out, which should be configuable on the PC,
	while you wait for 3.2 which currently shipping.

							Jeff