Archive-Date: Thu, 01 May 1997 00:01:54 CDT
Sender: owner-mx-list@wku.edu
Date: Thu, 01 May 1997 00:01:28 CDT
From: Hunter Goatley <goathunter@wku.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@LISTS.WKU.EDU
Message-ID: <009B394B.47DDC085.508@wku.edu>
Subject: MX-LIST Administrivia: Monthly Post

Posting statistics for list MX-LIST during April 1997

Total number of posts:                  92
Total number of posters:                28
Total number of subscribers:           292

Last modified: 28-SEP-1995 13:33 (Updated digest info)

Welcome  to  MX-List@LISTS.WKU.EDU,  an electronic mailing list established
for the discussion of the Message Exchange mail software.

This is a routine posting you will see from time to time on MX-List.

MX-List postings are also available in a daily digest format.  To subscribe
to the digest, send the following command in the body  of a mail message to
MXserver@LISTS.WKU.EDU:  SUBSCRIBE MX-List-Digest "Your real name here"

The  MX-List  archives  are maintained at ARCHIVES@LISTS.WKU.EDU.  To get a
copy of any month's postings, send an e-mail message  with  the  body  SEND
MX-List.yyyy-mm  to  ARCHIVES@LISTS.WKU.EDU,  where  "yyyy" is the year and
"mm" is the numeric representation of the month.  For example, the  message
SENDME MX-List.1992-04 will send the archives for April 1992.

MX itself is available via anonymous ftp from ftp.spc.edu in [.MX.MX041].
You can also get it via e-mail by sending the commands SEND MX and SEND
FILESERV_TOOLS on separate lines in the body of a mail message to
FILESERV@LISTS.WKU.EDU.

To  remove  yourself  from  the mailing list, send the following command to
MXserver@LISTS.WKU.EDU:

  SIGNOFF MX-List

MXserver supports a few other commands for your convenience.  The following
commands can be handled automatically by the list processor:

 SIGNOFF MX-List       - to remove yourself from the list
 REVIEW MX-List        - to get a list of subscribers
 QUERY MX-List         - to get the status of your entry on the list
 SET MX-List DIGEST    - to switch to digest mode
 SET MX-List NODIGEST  - to switch to non-digest mode
 SET MX-List NOMAIL    - to remain on the list but not receive mail
 SET MX-List MAIL      - to resume receiving mail from the list
 SET MX-List CONCEAL   - to not report your address in a REVIEW
 SET MX-List NOCONCEAL - to report your address in a REVIEW
 SET MX-List REPRO     - to receive posts you make to MX-List
 SET MX-List NOREPRO   - to not receive posts you make to MX-List
 LIST                   - to get a list of mailing lists served by WKU
 HELP                   - to receive a help file

By default, subscriptions are set to MAIL, REPRO, NOCONCEAL.

If  you have any questions, comments, or suggestions about MX-List, please
contact the list owner at the address below.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Hunter Goatley, Sr. OpenVMS Systems Programmer	       goathunter@MadGoat.com
Process Software
P.O. Box 51745
Bowling Green, KY 42102-6745
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
================================================================================
Archive-Date: Thu, 01 May 1997 08:09:26 CDT
Sender: owner-mx-list@wku.edu
Date: Thu, 01 May 1997 09:05:40 EDT
From: ambrose@conference-board.org
Reply-To: MX-List@MadGoat.com
To: mx-list@lists.wku.edu
Message-ID: <009B3997.4E19A4A0.3@papa.conference-board.org>
Subject: Help with MX

From:	NAME: Joseph Ambrose
	FUNC: Informaiton Technologies
	TEL: (212) 339-0443 <AMBROSE@A1@PAPA>
To:	NAME: Posting MX List <mx%"MX-List@LISTS.WKU.EDU"@mrgate>

I've received a peculiar error from a queued message in MX, Here is the 
entry 

Entry: 7, Origin: [UUCP]
<"papa::mrgate::\"A1::<user>\""@papa.conference-board.
org>
  Status: IN-PROGRESS, size: 186 bytes
  Created: 30-APR-1997 12:36:13.80, expires 30-MAY-1997 12:36:13.80
  Last modified 30-APR-1997 13:06:34.88
  SMTP entry #8, status: READY, size: 186 bytes, waiting for retry until
30-APR-
1997 13:36:43.60
    Created: 30-APR-1997 12:36:15.54, expires 30-MAY-1997 12:36:13.80
    Last modified 30-APR-1997 13:06:43.60
      Recipient #1: <thwriter@aol.com>, Route=aol.com
      Error count=2
      Last error: %MX_SMTP-W-MAILBOX_BUSY, action not taken: mailbox
temporarily
 unavailable

This is causing our e-mail to slow to a trickle. I have to shut it down
clear the queue and bring it back up to get rid of the problem, for a 
while.

After looking further, it may be connected to DECUS UUCP. We use it to 
bring the e-mail in from our outside net to the inside net. 

I know this looks crazy, but it works ( or did until now ) 

Any ideas on where I should be looking?

Version info:

Open VMS 6.1
MX 4.1
Multinet 3.5B (SMTP shut off )
DECUS UUCP 2.0

Joe Ambrose
The Conference Board
Net Admin


================================================================================
Archive-Date: Thu, 01 May 1997 08:16:08 CDT
Sender: owner-mx-list@wku.edu
Date: Thu, 1 May 1997 08:16:00 -1300
From: Hunter Goatley <goathunter@MadGoat.COM>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: AMBROSE@CONFERENCE-BOARD.ORG
Message-ID: <009B3990.5E18E9F1.13@ALPHA.WKU.EDU>
Subject: RE: Help with MX

ambrose@conference-board.org writes:
>
>      Recipient #1: <thwriter@aol.com>, Route=aol.com
>      Error count=2
>      Last error: %MX_SMTP-W-MAILBOX_BUSY, action not taken: mailbox
>temporarily
> unavailable
>
That appears to be the status AOL is returning to MX.  Basically, AOL is
overloaded right now, and has been for a while, as was discussed here
a few days ago.

There's really nothing you can do about this, other than hope that AOL
gets their problems straightened out soon.


Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Thu, 01 May 1997 09:31:18 CDT
Sender: owner-mx-list@wku.edu
Date: Thu, 01 May 1997 10:30:59 EDT
From: Brian Reed <reed@cbict3.cb.lucent.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.COM
Message-ID: <009B39A3.3999A0C8.1@cbict3.cb.lucent.com>
Subject: RE: Help with MX

>ambrose@conference-board.org writes:
>>
>>      Recipient #1: <thwriter@aol.com>, Route=aol.com
>>      Error count=2
>>      Last error: %MX_SMTP-W-MAILBOX_BUSY, action not taken: mailbox
>>temporarily
>> unavailable
>>
>Hunter replied:
>
>That appears to be the status AOL is returning to MX.  Basically, AOL is
>overloaded right now, and has been for a while, as was discussed here
>a few days ago.

It seems there was some confusion over the error message, since
VMS does have mailboxes, and the thought was the error was
coming from MX.

As a suggestion, if this error is coming from the remote site,
or due to the remote end not being able to answer,
is it possible to change the message to "remote mailbox temporarily
unavailable", so one knows it's a remote problem, and not local?

Brian D. Reed
Lucent Technologies
Columbus Works
bdreed1@lucent.com
614-860-6218
================================================================================
Archive-Date: Thu, 01 May 1997 10:12:38 CDT
Sender: owner-mx-list@wku.edu
Date: Thu, 01 May 1997 10:13:19 CST
From: turner@uamont.edu
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B39A0.C1759482.26@uamont.edu>
Subject: RE: Help with MX

================================================================================
Archive-Date: Thu, 1 May 1997 12:54:49 -1300
Sender: owner-mx-list@MadGoat.COM
Date: Thu, 1 May 1997 12:54:41 -0600
From: Hunter Goatley <goathunter@goat.process.com>
Reply-To: MX-List@MadGoat.COM
To: MX-List@LISTS.WKU.EDU
Message-ID: <009B39B7.4C5E67AC.6@goat.process.com>
Subject: test
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.COM?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

test
================================================================================
Archive-Date: Thu, 1 May 1997 14:36:18 -1300
Sender: owner-mx-list@MadGoat.com
Date: Thu, 01 May 1997 11:21:01 EDT
From: ambrose@conference-board.org
Reply-To: MX-List@MadGoat.com
To: mx-list@lists.wku.edu
Message-ID: <009B39AA.36D676C0.3@papa.conference-board.org>
Subject: Troubles with AOL
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

From:	NAME: Joseph Ambrose
	FUNC: Informaiton Technologies
	TEL: (212) 339-0443 <AMBROSE@A1@PAPA>
To:	NAME: Posting MX List <mx%"MX-List@LISTS.WKU.EDU"@mrgate>

Hunter,

Thanks for the TIp off about AOL. Someone else ( on comp.os.vms ) referred
to it, and I thought that he misread my posting. He was very gracous.

However, back to the problem.

These queue entries are slowing down MX tremendously. Is there a workaround
for this? 

	o Change some timeout parameter?
	o reroute the "aol.ocm" mail somewhere else?

My user's are getting ticked off that their mail is not as timely
as it usually is. 

Any ideas?

Joe Ambrose
+-----------------------------------------------------+
|Joseph J. Ambrose    |  ja@conference-board.org      |
|System Manager       |  ambrose@conference-board.org |
|  / DBA              |                               |
|---------------------|-------------------------------|
|The Conference Board | The opinions expressed here   |
|                     | are my own. I take            |
|EDP Services         | full responsiblity for them.  |
|845 Third Avenue     | They do not reflect the views |
|New York City, NY    | of the Conference Board.      |
|        10022-6679   |                               |
+-----------------------------------------------------+
|               O p e n   V M S                       |
| OpenVMS 6.2 /  6.1                                  |
| VMSCluster VAX 4500A                                |
|-----------------------------------------------------|
|             S o f t w a r e   A G                   |
| ADABAS 3.2/1             NATURAL 2.1/5              |
| ENTIRE NET-WORK 3.2/1    ADABAS SQL SERVER 1.3      |
+-----------------------------------------------------+
|                     P C                             |
| Dos / Windows for Workgroups 3.11 / 95 / NT         |
| Window NT Server 4.0                                |
| Microsoft Office Suite                              |
| Entire Net-Work for Windows 2.2.1.1                 |
| ADABAS ODBC CLIENT 1.1.2                            |
| ESPERANT 3.0.11                                     |
+-----------------------------------------------------+



================================================================================
Archive-Date: Thu, 1 May 1997 14:44:35 -1300
Sender: owner-mx-list@MadGoat.com
Date: Thu, 1 May 1997 14:44:32 -1300
From: Hunter Goatley <goathunter@MadGoat.COM>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: AMBROSE@CONFERENCE-BOARD.ORG
Message-ID: <009B39C6.A54CAECF.23@ALPHA.WKU.EDU>
Subject: RE: Troubles with AOL
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

ambrose@conference-board.org writes:
>
>These queue entries are slowing down MX tremendously. Is there a workaround
>for this? 
>
>	o Change some timeout parameter?
>	o reroute the "aol.ocm" mail somewhere else?
>
You could reroute them somewhere else, but it'll probably just cause
problems for that "somewhere else" system.

>My user's are getting ticked off that their mail is not as timely
>as it usually is. 
>
Unfortunately, there's not really anything you can do in MX V4.1 or
V4.2.  The next release does have some new code that would help.

The problem, I think, is that you've got a bunch of these in the
queue, and each one is being retried by the MX SMTP delivery agents.
In the next release of MX, the agents are a little smarter about
skipping entries for a destination that another agent just determined
is unreachable.

But, until that's released, I can't think of anything to suggest,
other than defining MX_FLQ_AUTOPURGE_FIN so that entries are
automatically deleted as soon as they're marked FINished.

Of course, you could also upgrade to an Alpha.  Ever since WKU moved
to their AlphaServer 4000/400, MX has flown.... ;-)

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Thu, 1 May 1997 14:56:46 -1300
Sender: owner-mx-list@MadGoat.com
Date: Thu, 1 May 1997 14:56:38 -0600
From: Hunter Goatley <goathunter@goat.process.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@LISTS.WKU.EDU
Message-ID: <009B39C8.55C436C1.6@goat.process.com>
Subject: test
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

test
================================================================================
Archive-Date: Mon, 5 May 1997 03:48:25 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 05 May 1997 11:46:28 GMT-2
From: "Najman Kahana. Ext:77313" <najman@hadassah.org.il>
Reply-To: MX-List@MadGoat.com
To: MX-LIST@MADGOAT.COM
CC: najman@hadassah.org.il
Message-ID: <009B3CD2.6E914A4E.31@HADASSAH.org.IL>
Subject: help creating list (beginer)
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>


Hello.

	I am trying to set up my very 1st list server, so, sorry if my
questions are trivial (but I did read the F manual :) )

	I am trying to set up a "read only" list.  It's purpose is to notify
my users on planned problems with the computers/networks.

	I created the list with the GROUP not having W privilege.
	BUT, there some users (managers of other sites from which we get
services) whom I would like to give posting privileges.  How do I do it ?
I prefer that they not have to post directly to me.

	Second, since the GROUP does not have W privilege, anyone who posts
gets a "privilege" message.  Is there a way of changing this message ?

Thank you for your time.

Najman Kahana


+--------+------------------+------------------------------+---------------+
!      NAJMAN KAHANA        ! Hadassah University Hospital ! thanks,       !
!  Najman@hadassah.org.il   !    Jerusalem, Israel         !   we have our !
!                           ! (visit our capital soon)     !   own viruses !
+--------+------------------+------------------------------+---------------+

+--------+------------------+------------------------------+---------------+
!      NAJMAN KAHANA        ! Hadassah University Hospital ! thanks,       !
!  Najman@hadassah.org.il   !    Jerusalem, Israel         !   we have our !
!                           ! (visit our capital soon)     !   own viruses !
+--------+------------------+------------------------------+---------------+
================================================================================
Archive-Date: Mon, 5 May 1997 07:01:19 -1300
Sender: <owner-MX-List@MadGoat.com>
Message-ID: <199705051201.NAA04005@muttley.cen.hw.ac.uk>
To: MX-List@MadGoat.com
Reply-To: MX-List@MadGoat.com
References: <199704302041.VAA25406@bonzo.cen.hw.ac.uk>
Subject: Re: Advice sought on MX SITE issues
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 05 May 1997 13:01:07 +0100
From: "David J. Morriss" <cendjm@ccen.hw.ac.uk>
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

On Wed, 30 Apr 1997 22:01:06 +0200  "GWDVMS::MOELLER" wrote:

> In order to return undeliverable mails, I'm using a 
> home-grown BISON(yacc)/VAXC program, starting like
> 
> 	%{
> 	/* parse some RFC822 header fields ...

[...]

> Would you be interested?

Yes please. 

While we're on the subject of MX Site, I'd like to use MX_EXE:MX_SITE_IN as a
way of injecting non-standard messages into the queue. These are housekeeping
messages between various systems here, and I'd like them to have special
headers (of the "X-header:" variety) for software at the other end to
recognise and handle.

A quick test (from a privileged account) shows that this is possible, but I
can't find any information on what privileges I'd need to allow our Help Desk
personnel to do it (I envisage their using an installed-with-privs program to
invoke it). Is it just SYSPRV (as with MLFAKE)?

Does anyone have any information on this?


--  
David Morriss, Computing Services,           | Tel: +44 (0)131 451 3262 (DDI)
Heriot-Watt University, Edinburgh, EH14 4AS, | FAX: +44 (0)131 451 3261
Scotland, UK                                 | D.J.Morriss@hw.ac.uk 

================================================================================
Archive-Date: Mon, 5 May 1997 07:16:36 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 5 May 1997 07:16:31 -1300
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3CAC.B84E9B0F.68@ALPHA.WKU.EDU>
Subject: RE: help creating list (beginer)
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

"Najman Kahana. Ext:77313" <najman@hadassah.org.il> writes:
>
>	I created the list with the GROUP not having W privilege.
>	BUT, there some users (managers of other sites from which we get
>services) whom I would like to give posting privileges.  How do I do it ?
>I prefer that they not have to post directly to me.
>
You can make them owners of the list.  Unfortunately, that's the only
thing you can do with MX right now.  (You can always use the MX SITE
interface to write your own routines that allow posts from them to get
through one way or another.)

>	Second, since the GROUP does not have W privilege, anyone who posts
>gets a "privilege" message.  Is there a way of changing this message ?
>
No, it's hardcoded in MX.

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Mon, 5 May 1997 07:39:48 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 5 May 1997 07:39:30 -1300
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3CAF.EE77410E.1@ALPHA.WKU.EDU>
Subject: RE: help creating list (beginer)
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

"Najman Kahana. Ext:77313" <najman@hadassah.org.il> writes:
>
>       I created the list with the GROUP not having W privilege.
>       BUT, there some users (managers of other sites from which we get
>services) whom I would like to give posting privileges.  How do I do it ?
>I prefer that they not have to post directly to me.
>
You can make them owners of the list.  Unfortunately, that's the only
thing you can do with MX right now.  (You can always use the MX SITE
interface to write your own routines that allow posts from them to get
through one way or another.)

>       Second, since the GROUP does not have W privilege, anyone who posts
>gets a "privilege" message.  Is there a way of changing this message ?
>
No, it's hardcoded in MX.

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Mon, 5 May 1997 14:42:48 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 05 May 1997 14:42:26 EDT
From: Robert Byer <byer@mail.all-net.net>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3CEB.0389DF20.19@mail.all-net.net>
Subject: QUESTION: MX In Clustered Environments...
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

-----BEGIN PGP SIGNED MESSAGE-----


I have a question about MX and clustered environments.

Two machines, one a 6210 with VMS 5.5-2HW with Wollongong TCP/IP v5.2 and
a VAXServer-3300, VMS 5.5-2HW and CMU TCP/IP and they are clustered 
together and share the UAF and appropiate mail configuration files.

The 6210 with Wollongong has a problem with MX v4.2 in that it will load
and startup, and the SMTP Server accepts incomming connections, but the
local SMTP processes sending e-mail out just sit and do nothing.  When I
turn on all the debugging, the logs for the Local SMTP are created, but
they are empty.  So we are stuck with MX v4.1 and we think the problem
is NETLIB v2.0 as if we just load NETLIB and something that requires it
it does the same sort of thing.

Anyway, these machines are clustered together and I know that MX will work
in a clustered environment so here's my question...

If I run and install the SMTP and such on the VAXServer-3300, and I also 
tell MX to load the DECNet SMTP on the 6210, will the 6210 be able to send 
e-mail to the internet through the DECNet-SMTP?

If I run and install the SMTP on the VAXServer-300 AND the 6210, will the 
6210 be able to send InterNet e-mail even through the differences in the 
TCP/IP packages?

I'm trying to find a way to get these clustered machines to both be able to
send e-mail to then InterNet with the VAXServer-3300 as the primary e-mail
server.

Thanks in advance.


 +------------------------+--------------------------------------------+
 | Robert Alan Byer       | A-Com Computing, Inc.                      |        
 | Vice-President         | 115 W. Washington Street, Suite 1165       |
 | A-Com Computing, Inc.  | Indianapolis, IN 46204                     |
 | Phone: (317)673-4204   | http:\\www.all-net.net\                    | 
 +------------------------+-----+--------------------------------------+
 | byer@mail.all-net.net        | I don't want to take over the world, |
 | http://www.all-net.net/~byer | just my own little part of it.       |
 +------------------------------+--------------------------------------+
 | Send an E-mail request to obtain my PGP key.                        |
 +---------------------------------------------------------------------+

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBM23xSKVSqzlBVJbBAQEQrAgApfeV9fW0h9gpF9+02eJLzIqAsSoz6JIi
esh7pyhJhVm5wXqtSYworPCUCiQ9aS1lNFbSov8XOA/6wjZ2KwTpPoTQkaRyc1Z1
me+pKyHCp3MlJoIkWlNYOVc+6YykQh/oiqtM/A0jn7fhO3d6FkJ7V3piz7r3pb1O
63X3DfgiU2hg9ct6RROCIrIn0ch6pYAJDBj6nGECkS0BSq6v5OIc9ROGMUsKwCo9
f2+amltoCdyOsuKpvZLqdx4jFYDH8JIw3uozMvbYTV51DnHHHZQStu8WE1mIFSKJ
3/ykCt/OmYQGlW0Vq3QIW0mTcyOP6/MplFcAlXzBrhALw8fQb8VQBg==
=95t5
-----END PGP SIGNATURE-----
================================================================================
Archive-Date: Mon, 5 May 1997 15:19:27 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 05 May 1997 16:18:30 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3CF8.6EEF8AA0.7@swdev.si.com>
Subject: RE: QUESTION: MX In Clustered Environments...
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

Robert Byer (byer@mail.all-net.net) writes:

>Two machines, one a 6210 with VMS 5.5-2HW with Wollongong TCP/IP v5.2 and
>a VAXServer-3300, VMS 5.5-2HW and CMU TCP/IP and they are clustered 
>together and share the UAF and appropiate mail configuration files.
<snip>
>If I run and install the SMTP and such on the VAXServer-3300, and I also 
>tell MX to load the DECNet SMTP on the 6210, will the 6210 be able to send 
>e-mail to the internet through the DECNet-SMTP?
>
>If I run and install the SMTP on the VAXServer-300 AND the 6210, will the 
>6210 be able to send InterNet e-mail even through the differences in the 
>TCP/IP packages?

If these machines are clustered, share the mail profile, and have
MAIL$SYSTEM_FLAGS set approriately (i.e., 7), you don't need the
SMTP-over-DECnet agent at all.  Just run MX_STARTUP.COM on both nodes, which
will define the MX logicals on the non-agent system, which will then be able to
stick messages in the MX queue file, which the other node (the CMU one) will
process.
================================================================================
Archive-Date: Mon, 5 May 1997 20:23:11 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 05 May 1997 20:22:51 EDT
From: Robert Byer <byer@mail.all-net.net>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3D1A.91A4EAA0.3@mail.all-net.net>
Subject: RE: QUESTION: MX In Clustered Environments...
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

-----BEGIN PGP SIGNED MESSAGE-----

>
>If these machines are clustered, share the mail profile, and have
>MAIL$SYSTEM_FLAGS set approriately (i.e., 7), you don't need the
>SMTP-over-DECnet agent at all.  Just run MX_STARTUP.COM on both nodes, which
>will define the MX logicals on the non-agent system, which will then be able to
>stick messages in the MX queue file, which the other node (the CMU one) will
>process.
>

Thanks, that's what I was needing to know.

So if I have this straight, I install MX on the cluster and tell it to run
the SMTP on both nodes, run the MX startup on each node and everything
should work, right?

The VAXServer-3300 is sharing the mail profile, SYSUAF, RIGHTSLIST and 
NETPROXY files just fine, but I didn't know about the MAIL$SYSTEM_FLAGS.

Do I have to set the MAIL$SYSTEM_FLAGS to "7" on all the machines on the
cluster or just the one serving the e-mail?

Thanks.

 +------------------------+--------------------------------------------+
 | Robert Alan Byer       | A-Com Computing, Inc.                      |        
 | Vice-President         | 115 W. Washington Street, Suite 1165       |
 | A-Com Computing, Inc.  | Indianapolis, IN 46204                     |
 | Phone: (317)673-4204   | http:\\www.all-net.net\                    | 
 +------------------------+-----+--------------------------------------+
 | byer@mail.all-net.net        | I don't want to take over the world, |
 | http://www.all-net.net/~byer | just my own little part of it.       |
 +------------------------------+--------------------------------------+
 | Send an E-mail request to obtain my PGP key.                        |
 +---------------------------------------------------------------------+

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBM25BEqVSqzlBVJbBAQEQxwgA0UVZ4lWUQ1+9LgbMOqbnwt+Jfm/EGIvI
iHW2Wvl51l0I+W/bp9nnWmZNuu3m3Gx6DCrBWLMy3rYCHtSqhVcYXjdrupdmuuoJ
iluIoBDUgVuM1H/V3/sUrumu4KPbrOaPM+6G5MIMPXp5pNTWgjvcDbAJv4ei8jIo
HDvExnygiCAGeNP/u+/J43zEVH23HkneAWSdvMYdCV0NpxowugEEIpypZrkoy2Ce
kpIvW8aesvQFKBhDishKGjq/Ur4NXf1nxIV5kFss6tTF/SE7b+bb7YaMmvt0SL82
ybx1duT6YKVWJud8sRNhlj5WzlEFnHitB9yxFp7F0AvXZY5tKeEQXw==
=y6l/
-----END PGP SIGNATURE-----
================================================================================
Archive-Date: Mon, 5 May 1997 20:35:56 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 05 May 1997 21:35:12 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: byer@mail.all-net.net
Message-ID: <009B3D24.AD042A40.1@swdev.si.com>
Subject: RE: QUESTION: MX In Clustered Environments...
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

Robert Alan Byer (byer@mail.all-net.net)

>So if I have this straight, I install MX on the cluster and tell it to run
>the SMTP on both nodes, run the MX startup on each node and everything
>should work, right?

No, run all MX agents, if you wish, on the system where everything works.  Run 
the startup procedure on all nodes.

Alternatively, run the SMTP and SMTP_SERVER agents on the CMU node and the other 
agents on the Wollongong* node.

>Do I have to set the MAIL$SYSTEM_FLAGS to "7" on all the machines on the
>cluster or just the one serving the e-mail?

A homogeneous cluster (with respect to mail) will have MAIL$SYSTEM_FLAGS set to 
7 on all nodes.

*Wollongong, of course, doesn't exist and your version of their TCP/IP is quite 
old.  You should upgrade.  The current version is Attachmate Pathway V3.0.
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Mon, 5 May 1997 21:11:32 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Mon, 05 May 1997 19:09:06 PDT
From: Virtual Bill <powers@gtewd.mtv.gtegsc.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@WKUVX1.WKU.EDU
Message-ID: <009B3D10.44313BC0.48@gtewd.mtv.gtegsc.com>
Subject: DEC's Delta-Time Limitation Problem
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

	I am running MX V4.0-1 and VMSV5.5-2.  I'd like to know if MX
	will have a problem with DEC's Delta-
	Time limitation problem due to happen on 19 May.  If
	so, have you got a fix for the problem?

	Thanks in advance.

				Bill Powers
===================================================================
| Disclaimer:  The contents of this message reflects my personal  
| opinion and not those of my employer or the organization through
| which Internet was accessed.                                    
-------------------------------------------------------------------
| Bill Powers         GTE Government Systems                      
| (415) 966-2757      internet: powers@powers.mtv.gtegsc.com      
|                     fax: (415) 966-3401                         
===================================================================
   
================================================================================
Archive-Date: Tue, 6 May 1997 04:08:13 -1300
Sender: <owner-MX-List@MadGoat.com>
From: Ian.Miller@softel.co.uk (Ian Miller)
Subject: Re: POP crashes!
Date: 6 May 1997 08:44:34 GMT
Message-ID: <slrn5mtvcu.m4041v.Ian.Miller@dylan.softel.co.uk>
Reply-To: MX-List@MadGoat.com
To: MX-List@WKUVX1.WKU.EDU
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>


On Wed, 30 Apr 1997 11:02:08 -0600, goralj@vax.grc.nia.nih.gov <goralj@vax.grc.nia.nih.gov> wrote:
>The IUPOP server on one of our local nodes keep crashing, several times a
>day..  When it does it gives us the following error message:
>
>VAX2 - %CONV-F-OPENIN, error opening !AS as input
>
>We haven't been able to ascertain what the problem might be.  Does anyone
>have a clue???
>
>Thanks,
>
>Joe Goral
>Sys. & Netwrks., NIH's Gerontology Research Center, Balto, MD
>
>-------------------==== Posted via Deja News ====-----------------------
>      http://www.dejanews.com/     Search, Read, Post to Usenet

It could be the IUPOP3 server trying to do convert/reclaim operation on a 
VMSMAIL file that someone is also reading using VMSMAIL. Have you got the
lastest version of IUPOP3 from 

http://www.tci.uni-hannover.de/extrakt/pop.html

(also available by ftp). 

You should should try the iupop3 users mailing list at 

	iupop3-users@indiana.edu

-- 
****************************************************************************
Ian Miller			    "The time has come",the walrus said 
Teletext Dept.,Softel 		    "to speak of many things".
Tel: +44 118 9842151 		     from "Through the looking glass" 
Ian.Miller@softel.co.uk		     by Lewis Carrol.
PSImail: 243273400398::IAN		
Disclaimer - I said this stuff myself. My employer had nothing to do with it.
*****************************************************************************
================================================================================
Archive-Date: Tue, 6 May 1997 07:03:40 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 6 May 1997 07:03:34 -1300
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3D74.13E6C99B.25@ALPHA.WKU.EDU>
Subject: RE: DEC's Delta-Time Limitation Problem
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

Virtual Bill <powers@gtewd.mtv.gtegsc.com> writes:
>
>	I am running MX V4.0-1 and VMSV5.5-2.  I'd like to know if MX
>	will have a problem with DEC's Delta-
>	Time limitation problem due to happen on 19 May.  If
>	so, have you got a fix for the problem?
>
I thought I posted about this a few weeks ago?  In any case, no, MX
will not be affected by the by the May 19 delta-time limit, at least
as far as I can tell.  (MX itself won't have problems; I'm assuming
that nothing VMS is doing under MX will have problems.)

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Tue, 6 May 1997 07:27:59 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 06 May 1997 05:27:45 PDT
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: henrym@sacto.mp.usbr.gov
Message-ID: <009B3D66.B103F840.25@sacto.mp.usbr.gov>
Subject: RE: DEC's Delta-Time Limitation Problem
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

> From:	MX%"MX-List@MadGoat.com"  6-MAY-1997 05:19:31.91
> Subj:	RE: DEC's Delta-Time Limitation Problem

Hunter,

> Virtual Bill <powers@gtewd.mtv.gtegsc.com> writes:
> >
> >	I am running MX V4.0-1 and VMSV5.5-2.  I'd like to know if MX
> >	will have a problem with DEC's Delta-
> >	Time limitation problem due to happen on 19 May.  If
> >	so, have you got a fix for the problem?
> >
> I thought I posted about this a few weeks ago?  In any case, no, MX
> will not be affected by the by the May 19 delta-time limit, at least
> as far as I can tell.  (MX itself won't have problems; I'm assuming
> that nothing VMS is doing under MX will have problems.)
> 

	You did, but there is some late breaking news which in itself 
does not directly effect MX, but is probably good in general.  Last 
Friday, DEC released the Delta Time patch kits for VMS 5.2, 5.3 and 5.4. 
(Sorry, no kit for 5.1, and I still have a 5.1 system running!)

> Hunter
> ------
> Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
> <goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html


-HWM
================================================================================
Archive-Date: Tue, 6 May 1997 07:49:12 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 06 May 1997 08:48:25 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: POWERS@POWERS.MTV.GTEGSC.COM
Message-ID: <009B3D82.B989A480.28@swdev.si.com>
Subject: RE: DEC's Delta-Time Limitation Problem
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

Bill Powers (powers@powers.mtv.gtegsc.com) writes:

	I am running MX V4.0-1 and VMSV5.5-2.  I'd like to know if MX
	will have a problem with DEC's Delta-
	Time limitation problem due to happen on 19 May.  If
	so, have you got a fix for the problem?

The obvious fix is to apply the patch.  I doubt if MX will have a problem,
though, since it affects mostly threaded applications and I don't believe MX is
one of them.

By the way, since MX V4.2 is current, with V4.3 (or V5.0 or whatever MadGoat
decides to call it) due out soon.
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Tue, 6 May 1997 09:38:43 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 6 May 1997 7:38:35 -0700
From: Matt Madison <Madison@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <970506073835.2298fd85@Cisco.COM>
Subject: RE: DEC's Delta-Time Limitation Problem
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

Virtual Bill <powers@gtewd.mtv.gtegsc.com> writes:
>
>	I am running MX V4.0-1 and VMSV5.5-2.  I'd like to know if MX
>	will have a problem with DEC's Delta-
>	Time limitation problem due to happen on 19 May.  If
>	so, have you got a fix for the problem?

MX should not be affected by the delta-time problem, *except* if you use
MultiNet's (now obsolete) MM mail reader.  There is a time computation
for generating the header that goes into the MM mail file that will break.
The fix for this would be to install the LIBRTL patch from Digital.

If you don't use MM, though, then you should be fine.

-Matt

-- 
Matthew Madison |                                           | madison@cisco.com
Cisco Systems   | 101 Cooper St. | Santa Cruz, CA 95060 USA | +1 408 457 5390
================================================================================
Archive-Date: Tue, 6 May 1997 11:18:48 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 06 May 1997 11:16:21 EDT
From: Robert Byer <byer@mail.all-net.net>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3D97.63FC8040.17@mail.all-net.net>
Subject: Re: POP crashes!
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

-----BEGIN PGP SIGNED MESSAGE-----

>>The IUPOP server on one of our local nodes keep crashing, several times a
>>day..  When it does it gives us the following error message:
>>
>>VAX2 - %CONV-F-OPENIN, error opening !AS as input
>>
>>We haven't been able to ascertain what the problem might be.  Does anyone
>>have a clue???
>>

We had this problem and it turned out that the user had used up all his
disk quota and the POP server couldn't remove any messages.

We also had this problem when one of our user disks went off-line.


 +------------------------+--------------------------------------------+
 | Robert Alan Byer       | A-Com Computing, Inc.                      |        
 | Vice-President         | 115 W. Washington Street, Suite 1165       |
 | A-Com Computing, Inc.  | Indianapolis, IN 46204                     |
 | Phone: (317)673-4204   | http:\\www.all-net.net\                    | 
 +------------------------+-----+--------------------------------------+
 | byer@mail.all-net.net        | I don't want to take over the world, |
 | http://www.all-net.net/~byer | just my own little part of it.       |
 +------------------------------+--------------------------------------+
 | Send an E-mail request to obtain my PGP key.                        |
 +---------------------------------------------------------------------+

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBM28SeaVSqzlBVJbBAQF/iQgA0xMvuNzR5ixEBJEywWLrgx/6g3IxYL0m
6dmiT4jp+aWvBuJ0wWSWuTLnsI4xpToJgApiCnTRjjCh6lfVBcuvUNGPD0yytVzs
9bJseGrRmIZUovNIb/8ehSlLhPPLj6g/9sDPsme0rbSUFa6OVFmMD0ZXf8egB44P
yxn8PJnFzp28a9co7qTv2DXqNZBMzh8TfvX9NiRvNRL3wd3EL3mZ0PvJOwKVfkHx
lwPzwxukOwr+5T1fobjkNwM5zcaMvZZ8NdGx4EE2O+XMp5j5/1R0HfbTkzUtDFvE
Zo0ZLp7WLqIJdImLsUvx28tpMm4Vl88Smt2tNT+cw9dzePCnVOZYcA==
=HydQ
-----END PGP SIGNATURE-----
================================================================================
Archive-Date: Tue, 6 May 1997 12:26:41 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 06 May 1997 10:26:18 PDT
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: henrym@sacto.mp.usbr.gov
Message-ID: <009B3D90.65E805CA.42@sacto.mp.usbr.gov>
Subject: Re: POP crashes!
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

> From:	MX%"MX-List@MadGoat.com"  6-MAY-1997 09:35:09.25
> Subj:	Re: POP crashes!

> -----BEGIN PGP SIGNED MESSAGE-----
> 
> >>The IUPOP server on one of our local nodes keep crashing, several times a
> >>day..  When it does it gives us the following error message:
> >>
> >>VAX2 - %CONV-F-OPENIN, error opening !AS as input
> >>
> >>We haven't been able to ascertain what the problem might be.  Does anyone
> >>have a clue???
> >>
> 
> We had this problem and it turned out that the user had used up all his
> disk quota and the POP server couldn't remove any messages.
> 

	It's always a good policy to periodically monitor the disk usage 
and perform mail purges and compressions on the user's behalf.  
Defragmenting the disk periodically helps performance as well.  You 
might also want to periodically backup and restore the users mail 
directories, and make sure that the cluster size of the user disk is 
reasonable for the size of the mail files that you typically process.

	Finally, this little trick:

$ SET FILE/LOG/EXTEN=80 device:[directory]MAIL.MAI

	helps prevent the mail file from getting too fragmented quickly.
All of these little tricks help mail and POP run a little more smoothly 
and faster, and may alleviate some of the other problems.

> We also had this problem when one of our user disks went off-line.
> 

	That'll do it big time...

> 
>  +------------------------+--------------------------------------------+
>  | Robert Alan Byer       | A-Com Computing, Inc.                      |        
>  | Vice-President         | 115 W. Washington Street, Suite 1165       |
>  | A-Com Computing, Inc.  | Indianapolis, IN 46204                     |
>  | Phone: (317)673-4204   | http:\\www.all-net.net\                    | 
>  +------------------------+-----+--------------------------------------+
>  | byer@mail.all-net.net        | I don't want to take over the world, |
>  | http://www.all-net.net/~byer | just my own little part of it.       |
>  +------------------------------+--------------------------------------+
>  | Send an E-mail request to obtain my PGP key.                        |
>  +---------------------------------------------------------------------+
> 


-HWM
================================================================================
Archive-Date: Tue, 6 May 1997 14:46:24 -1300
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 06 May 1997 12:46:10 PST
From: Ed Bates <ebates@vms1.cc.uop.edu>
Reply-To: MX-List@MadGoat.com
To: MX-LIST@MADGOAT.COM
Message-ID: <009B3DA3.F01EE606.17@vms1.cc.uop.edu>
Subject: Multiple list owners and returned messages
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

I'm using MX 4.2 on OpenVMS 5.5-2.  I co-moderate several
lists, many of which are related.  I set up a separate list
for the owners (moderators) which is used in the /ERRORS_TO
qualifier for each.  Before upgrading to MX 4.2, the errors
were going to all of the owners, but now they only come to
me.

I didn't see anything in the release notes about this.  Has
anyone else experienced this phenomenon?

-- Ed

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 Edwin J. "Ed" Bates            Systems Administrator            . .  _   _
 Office of Computing Services   VAX/UNIX/Internet/NetWare        |#| / \ | \
 University of the Pacific      Internet:  ebates@uop.edu        |#| | | |_/
 877 W. Stadium Dr.             Telephone: (209) 946-2251        |#| | | |
 Stockton, CA  95211            Fax:       (209) 946-2898        \_/ \_/ |
================================================================================
Archive-Date: Tue, 6 May 1997 15:37:21 -1300
Sender: <owner-MX-List@MadGoat.com>
Message-ID: <3.0.32.19970506153700.00fb8c5c@Bible.acu.edu>
Date: Tue, 06 May 1997 15:37:02 -0500
To: MX-List@MadGoat.com
From: Tom Dolan <Dolan@Bible.acu.edu>
Reply-To: MX-List@MadGoat.com
Subject: Re: Multiple list owners and returned messages
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
X-List-Help: <http://www.madgoat.com/>

At 12:46 PM 5/6/97 PST, you wrote:
>I'm using MX 4.2 on OpenVMS 5.5-2.  I co-moderate several
>lists, many of which are related.  I set up a separate list
>for the owners (moderators) which is used in the /ERRORS_TO
>qualifier for each.  Before upgrading to MX 4.2, the errors
>were going to all of the owners, but now they only come to
>me.
>
>I didn't see anything in the release notes about this.  Has
>anyone else experienced this phenomenon?

Yes,

I found that MX 4.2 lists (any list you create) will not accept
messages from the user SYSTEM - therefore you can't post error
messages to a list (of course this is a good thing to keep a loop
from occuring!)  So when error messages are posted to the error
moderators list, they are sent only to the /ERRORS_TO person for
the error moderators list (not the whole list.)

I'm not a programming type person so I never figured out how to
build a SITE procedure to change error message headers from
specific lists to come from something other than SYTEM and then
post them to the outgoing error moderators list. (if you come up
with a SITE procedure, please share the details!)

It would be nice if one could specify more than one address in the
/ERRORS_TO qualifier......


Tom Dolan  Dolan@Bible.acu.edu  202 Bible Building
Systems Manager                 ACU Box 29454
College of Biblical Studies     Abilene, TX 79699
Abilene Christian University    915.674.3706
================================================================================
Archive-Date: Tue, 6 May 1997 17:52:38 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 06 May 1997 15:52:26 PST
From: Ed Bates <ebates@vms1.cc.uop.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3DBD.F55289A6.7@vms1.cc.uop.edu>
Subject: Re: Multiple list owners and returned messages

On Tue, 06 May 1997 at 15:37:02 -0500, Tom Dolan <Dolan@Bible.acu.edu> wrote:
>At 12:46 PM 5/6/97 PST, you wrote:
>>I'm using MX 4.2 on OpenVMS 5.5-2.  I co-moderate several
>>lists, many of which are related.  I set up a separate list
>>for the owners (moderators) which is used in the /ERRORS_TO
>>qualifier for each.  Before upgrading to MX 4.2, the errors
>>were going to all of the owners, but now they only come to
>>me.
>>
>>I didn't see anything in the release notes about this.  Has
>>anyone else experienced this phenomenon?
>
>Yes,
>
>I found that MX 4.2 lists (any list you create) will not accept
>messages from the user SYSTEM - therefore you can't post error
>messages to a list (of course this is a good thing to keep a loop
>from occuring!)  So when error messages are posted to the error
>moderators list, they are sent only to the /ERRORS_TO person for
>the error moderators list (not the whole list.)

Of course!  Thank you for pointing this out.  The release notes
mentioned this, but I failed to associate it with what I was
doing.
>
>I'm not a programming type person so I never figured out how to
>build a SITE procedure to change error message headers from
>specific lists to come from something other than SYTEM and then
>post them to the outgoing error moderators list. (if you come up
>with a SITE procedure, please share the details!)

Maybe the option to turn off the filter could be added to the
ever-growing wish list.

-- Ed

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 Edwin J. "Ed" Bates            Systems Administrator            . .  _   _
 Office of Computing Services   VAX/UNIX/Internet/NetWare        |#| / \ | \
 University of the Pacific      Internet:  ebates@uop.edu        |#| | | |_/
 877 W. Stadium Dr.             Telephone: (209) 946-2251        |#| | | |
 Stockton, CA  95211            Fax:       (209) 946-2898        \_/ \_/ |
================================================================================
Archive-Date: Tue, 6 May 1997 19:55:17 -0500
Sender: <owner-MX-List@MadGoat.com>
From: dwing@cisco.com (Dan Wing)
Subject: Re: Multiple list owners and returned messages
Date: 7 May 1997 00:19:01 GMT
Message-ID: <5kohpl$lco$1@cronkite.cisco.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@WKUVX1.WKU.EDU

In article <3.0.32.19970506153700.00fb8c5c@Bible.acu.edu>, Tom Dolan <Dolan@Bible.acu.edu> writes:
>I found that MX 4.2 lists (any list you create) will not accept
>messages from the user SYSTEM - therefore you can't post error
>messages to a list (of course this is a good thing to keep a loop
>from occuring!)  

We've had posts from SYSTEM@host to Info-MultiNet (which is exploded 
with MX) for as long as I can remember.

>So when error messages are posted to the error
>moderators list, they are sent only to the /ERRORS_TO person for
>the error moderators list (not the whole list.)
>
>I'm not a programming type person so I never figured out how to
>build a SITE procedure to change error message headers from
>specific lists to come from something other than SYTEM and then
>post them to the outgoing error moderators list. (if you come up
>with a SITE procedure, please share the details!)
>
>It would be nice if one could specify more than one address in the
>/ERRORS_TO qualifier......

You can have /ERRORS_TO point to a private MX list which is for 
bounces, if you want something like that.  I've never found bounces 
quite that interesting -- we just log them to a file and Remove users 
that are causing bounces every month or so.

-Dan Wing
================================================================================
Archive-Date: Wed, 7 May 1997 15:16:04 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Wed, 7 May 1997 15:15:59 -0500
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3E82.0818C488.20@ALPHA.WKU.EDU>
Subject: Re: Multiple list owners and returned messages

Tom Dolan <Dolan@Bible.acu.edu> writes:
>
>I found that MX 4.2 lists (any list you create) will not accept
>messages from the user SYSTEM - therefore you can't post error
>messages to a list (of course this is a good thing to keep a loop
>from occuring!)

As Dan Wing mentioned, MX MLF accepts posts from SYSTEM just fine. 
However, it does reject messages from postmaster, mailer-daemon, uucp,
mxserver, listserv, and a couple of other, similar addresses.

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Thu, 8 May 1997 08:59:37 -0500
Sender: <owner-MX-List@MadGoat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 08 May 1997 08:59:16 +0700
To: mx-list@madgoat.com
From: Rick Stacks <stacks@adpce.lrk.ar.us>
Reply-To: MX-List@MadGoat.com
Subject: mail forwarding question
Message-ID: <19970508085920.0043bbfe.in@pc-185-60.osmre.gov>

I'm trying to figure out something that probably has a very simple answer
but I guess I'm in the middle of a brain burp.

I would like to set a username (joebagodoughnuts) to forward all mail to
three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
VMS Mail to no avail.  Is there a workable solution to this?  

I know this is not strictly a MX question but I've been trying to use MX to
solve this to no avail.  Anyone have a solution that they would like to share?

Many thanks in advance! ;-)

-- Rick
   Rick Stacks  stacks@adpce.lrk.ar.us |
   Systems Applications Supervisor     | They that give up essential liberty
   Ark Dept of Pollution Control       | to obtain a little temporary safety
   8001 National Dr. / POB 8913        | deserve neither liberty nor safety
   Little Rock, AR 72219 USA           |   -- Benjamin Franklin, 1759

================================================================================
Archive-Date: Thu, 8 May 1997 09:14:48 -0500
Sender: <owner-MX-List@MadGoat.com>
From: "Robert H. McClanahan" <rmcclanahan@tis.aecc.com>
To: MX-List@MadGoat.com
Date: Thu, 8 May 1997 09:14:33 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: Re: mail forwarding question
Reply-To: MX-List@MadGoat.com

On  8 May 97 at 8:59, Rick Stacks wrote:

> I'm trying to figure out something that probably has a very simple answer but
> I guess I'm in the middle of a brain burp.
> 
> I would like to set a username (joebagodoughnuts) to forward all mail to
> three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
> VMS Mail to no avail.  Is there a workable solution to this?  
> 
> I know this is not strictly a MX question but I've been trying to use MX to
> solve this to no avail.  Anyone have a solution that they would like to
> share?

Rick,

The way that solved this problem was to create a mailing list with MLF,
subscribe all of the desired users to that list and forward mail for the
phantom username to the list.

RHM

+--+
Robert H. McClanahan, Mgr, Tech Info Systems, rmcclanahan@tis.aecc.com  <[]><
Arkansas Electric Coop Corp, PO Box 194208, Little Rock, AR 72219-4208 USA

"Age is a question of mind over matter. If you don't mind, it doesn't matter."
       Satchel Paige
================================================================================
Archive-Date: Thu, 8 May 1997 09:27:16 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 8 May 1997 07:26:33 PDT
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: henrym@sacto.mp.usbr.gov
Message-ID: <009B3F09.9EA9B488.23@sacto.mp.usbr.gov>
Subject: RE: mail forwarding question

> From:	MX%"MX-List@MadGoat.com"  8-MAY-1997 07:15:16.16
> Subj:	mail forwarding question

Rick,

> I'm trying to figure out something that probably has a very simple answer
> but I guess I'm in the middle of a brain burp.
> 
> I would like to set a username (joebagodoughnuts) to forward all mail to
> three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
> VMS Mail to no avail.  Is there a workable solution to this?  
> 
> I know this is not strictly a MX question but I've been trying to use MX to
> solve this to no avail.  Anyone have a solution that they would like to share?
> 
> Many thanks in advance! ;-)
> 

	Why not just set up a teeny-tiny list with three addresses in 
it, and forward mail for that mailbox to the list name?

> -- Rick
>    Rick Stacks  stacks@adpce.lrk.ar.us |
>    Systems Applications Supervisor     | They that give up essential liberty
>    Ark Dept of Pollution Control       | to obtain a little temporary safety
>    8001 National Dr. / POB 8913        | deserve neither liberty nor safety
>    Little Rock, AR 72219 USA           |   -- Benjamin Franklin, 1759
> 


	Occam's Razor wins by a whisker...

-HWM
================================================================================
Archive-Date: Thu, 8 May 1997 09:28:59 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 08 May 1997 10:28:25 EST
From: John Hasstedt <manager@nuclear.physics.sunysb.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3F23.06820786.24@nuclear.physics.sunysb.edu>
Subject: RE: mail forwarding question

Rick Stacks <stacks@adpce.lrk.ar.us> wrote

> I would like to set a username (joebagodoughnuts) to forward all mail to
> three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
> VMS Mail to no avail.  Is there a workable solution to this?  
> 
> I know this is not strictly a MX question but I've been trying to use MX to
> solve this to no avail.  Anyone have a solution that they would like to share?

I have done this with the site interface.  I did

  DEFINE PATH FORWARD SITE/ROUTE=FORWARD

I then added code to process the forwarding address to SITE_DELIVER.COM (I have
included the code at the bottom of this message).

I can then set forwarding addresses as

 SET FORWARD/USER=joebagodoughnuts  "MX%""joe+sam+bill@FORWARD"""

or for nonlocal addresses

 SET FORWARD/USER=smith  "MX%""smith+smith%other.node@FORWARD"""

I add an _ to the beginning of each local username so a person can keep
a copy of each message and forward a copy to someone else.

==========================================================================
John Hasstedt                 Internet: John.Hasstedt@sunysb.edu
Physics Department            Phone: 516-632-8169 or 516-632-8153
State University of New York  FAX: 516-632-8573
Stony Brook, NY  11794-3800


$ SET NOON
$ GOTO 'P1'
$ EXIT 1
$ !
$FORWARD:
$ SET NOON
$ FILE = F$ELEMENT (1, "]", P2)
$ FILE = "MULTINET_SPOOL:" + F$ELEMENT (0, ";", FILE)
$ OPEN/READ NAMES 'P3'
$ READ NAMES REC
$ CLOSE NAMES
$ NAMES = F$ELEMENT (0, "@", REC) - "<"
$ OPEN/WRITE ADDR 'FILE'
$ N = 0
$FORWARDLOOP:
$ NAME = F$ELEMENT (N, "+", NAMES)
$ IF (NAME .EQS. "+") THEN GOTO FORWARDDONE
$ USER = F$ELEMENT (0, "%", NAME)
$ NODE = F$ELEMENT (1, "%", NAME)
$ IF (NODE .EQS. "%")
$ THEN
$   IF (F$EXTRACT (0, 1, USER) .NES. "_") THEN USER = "_" + USER
$   NODE = "nuclear.physics.sunysb.edu"
$ ENDIF
$ WRITE ADDR "<", USER, "@", NODE, ">"
$ N = N + 1
$ GOTO FORWARDLOOP
$FORWARDDONE:
$ CLOSE ADDR
$ MX_ENTER = "$MX_EXE:MX_SITE_IN"
$ MX_ENTER 'P2' 'FILE' "''P4'"
$ DELETE 'FILE';*
$ EXIT 1
================================================================================
Archive-Date: Thu, 8 May 1997 09:52:06 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 08 May 1997 10:51:05 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: stacks@adpce.lrk.ar.us
Message-ID: <009B3F26.31596140.13@swdev.si.com>
Subject: RE: mail forwarding question

Rick Stacks (stacks@adpce.lrk.ar.us) writes:

>I would like to set a username (joebagodoughnuts) to forward all mail to
>three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
>VMS Mail to no avail.  Is there a workable solution to this?  

As you've discovered, VMS Mail won't forward to more than one name.  But how 
about this:

$ define/system joebagodoughnuts "User1,User2,User3"

I know this works on a per-process basis.
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Thu, 8 May 1997 10:28:40 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 08 May 1997 10:27:40 CDT
From: metze@vmetze.mrl.uiuc.edu
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: metze@vmetze.mrl.uiuc.edu
Message-ID: <009B3F22.EBA538F7.60@vmetze.mrl.uiuc.edu>
Subject: Re: mail forwarding question



VMS also allows you to use a logical for a name in the mail
command.  You can set up a mailing list, and then use the
name of that mailing list in your 'to' field.

However, there is a downside.  If you do all of this within
VMS mail, the recipients know who each other are.  This
annoys UNIX zealots.

Ginny
> 
> On  8 May 97 at 8:59, Rick Stacks wrote:
> 
> > I'm trying to figure out something that probably has a very simple answer but
> > I guess I'm in the middle of a brain burp.
> > 
> > I would like to set a username (joebagodoughnuts) to forward all mail to
> > three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
> > VMS Mail to no avail.  Is there a workable solution to this?  
> > 
> > I know this is not strictly a MX question but I've been trying to use MX to
> > solve this to no avail.  Anyone have a solution that they would like to
> > share?
> 
> Rick,
> 
> The way that solved this problem was to create a mailing list with MLF,
> subscribe all of the desired users to that list and forward mail for the
> phantom username to the list.
> 
> RHM
> 
> +--+
> Robert H. McClanahan, Mgr, Tech Info Systems, rmcclanahan@tis.aecc.com  <[]><
> Arkansas Electric Coop Corp, PO Box 194208, Little Rock, AR 72219-4208 USA
> 
> "Age is a question of mind over matter. If you don't mind, it doesn't matter."
>        Satchel Paige
> 
================================================================================
Archive-Date: Thu, 8 May 1997 10:51:31 -0500
Sender: <owner-MX-List@MadGoat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 08 May 1997 10:50:59 +0700
To: MX-List@MadGoat.com
From: Rick Stacks <stacks@adpce.lrk.ar.us>
Reply-To: MX-List@MadGoat.com
Subject: RE: mail forwarding question
Message-ID: <19970508105107.00a9ed3e.in@pc-185-60.osmre.gov>

>I originally wrote:
>
>>I would like to set a username (joebagodoughnuts) to forward all mail to
>>three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
>>VMS Mail to no avail.  Is there a workable solution to this?  
>

Many Thanks to all that have replied!  :-)  I'll try each and see which one
works the best for my site.

Again, thanks all,
-- Rick

================================================================================
Archive-Date: Thu, 8 May 1997 14:03:31 -0500
Sender: <owner-MX-List@MadGoat.com>
Message-ID: <3.0.32.19970508140318.00e7d26c@Bible.acu.edu>
Date: Thu, 08 May 1997 14:03:20 -0500
To: MX-List@MadGoat.com
From: Tom Dolan <Dolan@Bible.acu.edu>
Reply-To: MX-List@MadGoat.com
Subject: Re: Multiple list owners and returned messages
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 03:15 PM 5/7/97 -0500, you wrote:
>Tom Dolan <Dolan@Bible.acu.edu> writes:
>>
>>I found that MX 4.2 lists (any list you create) will not accept
>>messages from the user SYSTEM - therefore you can't post error
>>messages to a list (of course this is a good thing to keep a loop
>>from occuring!)
>
>As Dan Wing mentioned, MX MLF accepts posts from SYSTEM just fine. 
>However, it does reject messages from postmaster, mailer-daemon,
uucp,
>mxserver, listserv, and a couple of other, similar addresses.

My mistake - in any case an MX mailing list rejects error messages
forwarded to it from the /ERRORS_TO qualifier of another MX mailing
list (they must be coming from postmaster or mxserver - I can't
remember what the debug said.)

Is there some way we could be able to put several addresses in the
/ERRORS_TO field?


Tom Dolan  Dolan@Bible.acu.edu  202 Bible Building
Systems Manager                 ACU Box 29454
College of Biblical Studies     Abilene, TX 79699
Abilene Christian University    915.674.3706
================================================================================
Archive-Date: Thu, 8 May 1997 14:56:07 -0500
Sender: <owner-MX-List@MadGoat.com>
Message-ID: <3.0.32.19970508145554.0077f9fc@Bible.acu.edu>
Date: Thu, 08 May 1997 14:55:56 -0500
To: MX-List@MadGoat.com
From: Tom Dolan <Dolan@Bible.acu.edu>
Reply-To: MX-List@MadGoat.com
Subject: RE: mail forwarding question
CC: ebates@vms1.cc.uop.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

Ed Bates said:
>>I'm using MX 4.2 on OpenVMS 5.5-2.  I co-moderate several
>>lists, many of which are related. (I want to forward errors from
the lists to >several recipients.)
Tom Dolan said:
>MX 4.2 will not allow one to forward errors from a mailing list
onto another >mailing list to be distributed. 

Ed,

Of course in the very next MX-List thread we have the answer to our
problem!  John Hasstedt has this cool SITE procedure shown below.

Here's how it could work, for example to send the errors from a
list called MYLIST@BIBLE.ACU.EDU to multiple recipients:

1. At the MCP> prompt put in the command DEFINE PATH FORWARD
SITE/ROUTE=FORWARD

2. At the VMS mail prompt, MAIL> , input the proper SET FORWARD
command.  For example I want the errors for my mailing list to go
to Dolan@Bible.acu.edu, Tom@genesis.acu.edu and Ralph@somewhere.com
 So I put in the following command at the MAIL> prompt:

SET FORWARD/USER=mylisterrros
"MX%""Dolan%Bible.acu.edu+Tom%genesis.acu.edu+Ralph%somewhere.com@FO
RWARD"""

3. I go into MCP> and set the list /ERRORS_TO qualifier to be sent
to MYLISTERRORS@BIBLE.ACU.EDU:

MCP>MODIFY LIST MYLIST /ERRORS=MYLISTERRORS@BIBLE.ACU.EDU

4. (This step can cause problems if you mess up the
SITE_DELIVER.COM file - make sure to keep a good clean unedited
copy of SITE_DELIVER.COM around!)  Edit the SITE_DELIVER.COM file
and add the code John Hasstedt provided to the bottom of your
MX_EXE:SITE_DELIVER.COM file.  I already had some code in
SITE_DELIVER.COM so I had to add the following code to the top of
the file so it would execute the proper part of the code for any
email addressed to somebody @FORWARD:

$ if P1 .eqs. "FORWARD" then goto FORWARD

That should do the job!  Error messages from mylist@Bible.acu.edu
are sent to mylisterrors@Bible.acu.edu.  VMS mail forwards the
messages sent to mylisterrors on to
Dolan%Bible.acu.edu+Tom%genesis.acu.edu+Ralph%somewhere.com@FORWARD
 MX SITE sees the @FORWARD domain in the address, executes the
SITE_DELIVER.COM FORWARD code, strips the embedded addresses out of
the @FORWARD address and sends a copy of the message via MX to each
of the three recipients!

Cool!

Thanks John Hasstedt!

It would still be nice if MX would allow more than one /ERRORS_TO
qualifier...

Here is John Hasstedt instructions in case mine are not clear....

>I have done this with the site interface.  I did
>
>  DEFINE PATH FORWARD SITE/ROUTE=FORWARD
>
>I then added code to process the forwarding address to
SITE_DELIVER.COM (I have
>included the code at the bottom of this message).
>
>I can then set forwarding addresses as
>
> SET FORWARD/USER=joebagodoughnuts  "MX%""joe+sam+bill@FORWARD"""
>
>or for nonlocal addresses
>
> SET FORWARD/USER=smith  "MX%""smith+smith%other.node@FORWARD"""
>
>I add an _ to the beginning of each local username so a person can
keep
>a copy of each message and forward a copy to someone else.
>
>===================================================================
=======
>John Hasstedt                 Internet: John.Hasstedt@sunysb.edu
>Physics Department            Phone: 516-632-8169 or 516-632-8153
>State University of New York  FAX: 516-632-8573
>Stony Brook, NY  11794-3800
>
>
$ SET NOON
$ GOTO 'P1'
$ EXIT 1
$ !
$FORWARD:
$ SET NOON
$ FILE = F$ELEMENT (1, "]", P2)
$ FILE = "MULTINET_SPOOL:" + F$ELEMENT (0, ";", FILE)
$ OPEN/READ NAMES 'P3'
$ READ NAMES REC
$ CLOSE NAMES
$ NAMES = F$ELEMENT (0, "@", REC) - "<"
$ OPEN/WRITE ADDR 'FILE'
$ N = 0
$FORWARDLOOP:
$ NAME = F$ELEMENT (N, "+", NAMES)
$ IF (NAME .EQS. "+") THEN GOTO FORWARDDONE
$ USER = F$ELEMENT (0, "%", NAME)
$ NODE = F$ELEMENT (1, "%", NAME)
$ IF (NODE .EQS. "%")
$ THEN
$   IF (F$EXTRACT (0, 1, USER) .NES. "_") THEN USER = "_" + USER
$   NODE = "nuclear.physics.sunysb.edu"
$ ENDIF
$ WRITE ADDR "<", USER, "@", NODE, ">"
$ N = N + 1
$ GOTO FORWARDLOOP
$FORWARDDONE:
$ CLOSE ADDR
$ MX_ENTER = "$MX_EXE:MX_SITE_IN"
$ MX_ENTER 'P2' 'FILE' "''P4'"
$ DELETE 'FILE';*
$ EXIT 1


Tom Dolan  Dolan@Bible.acu.edu  202 Bible Building
Systems Manager                 ACU Box 29454
College of Biblical Studies     Abilene, TX 79699
Abilene Christian University    915.674.3706
================================================================================
Archive-Date: Thu, 8 May 1997 15:49:22 -0500
Sender: <owner-MX-List@MadGoat.com>
From: welchb@woods.uml.edu (Brendan Welch, W1LPG)
Reply-To: MX-List@MadGoat.com
Subject: RE: mail forwarding question
Date: 8 May 97 16:38:34 -0500
Message-ID: <1997May8.163834.1@aspen>
To: MX-List@WKUVX1.WKU.EDU

> 
> 	Why not just set up a teeny-tiny list with three addresses in 
> it, and forward mail for that mailbox to the list name?
> 

I hope I am not missing the point.
I just tried using VMS mail, rather than MX.

Presuming user TOM wants mail forwarded to DICK and HARRY,
I logged in as TOM, created a distribution list named (in)appropriately
FORWARD.DIS, with entry lines for DICK and HARRY, and then
MAIL>set forward @forward

But when I tested it, by sending mail to TOM, the system balked
immediately; it could not or would not translate the "@forward" as legal. 
This surprised me, considering the stuff I have seen being syntactically
accepted by the "set forward" command, and the stuff I have seen it
translate (such as the < and > characters surrounding a name). 

It seems to me to be possibly easier if Digital would change VMS mail,
adding the ability to forward to many, with the option of a copy to
the recipient.  Is this administratively and techinically disastrous,
because it enables a potentially-endless loop and/or elsewise?
-- 
Brendan Welch, system analyst, UMass/Lowell, W1LPG,  welchb@woods.uml.edu
================================================================================
Archive-Date: Thu, 8 May 1997 15:59:37 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 08 May 1997 15:58:39 CDT
From: metze@vmetze.mrl.uiuc.edu
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: metze@vmetze.mrl.uiuc.edu
Message-ID: <009B3F51.28655159.30@vmetze.mrl.uiuc.edu>
Subject: RE: mail forwarding question



In the past one used to be able to use FORWARD to forward to
more than one person though a little trick was needed.  The
last I tried it the little trick no longer worked and you
simply can't forward to more than one person.

You have to get the message you want to forward on the screen, 
and then use the forward command, and specify the mailing list
to which you want to forward it on the 'to' line.

Ginny

> 
> > 
> > 	Why not just set up a teeny-tiny list with three addresses in 
> > it, and forward mail for that mailbox to the list name?
> > 
> 
> I hope I am not missing the point.
> I just tried using VMS mail, rather than MX.
> 
> Presuming user TOM wants mail forwarded to DICK and HARRY,
> I logged in as TOM, created a distribution list named (in)appropriately
> FORWARD.DIS, with entry lines for DICK and HARRY, and then
> MAIL>set forward @forward
> 
> But when I tested it, by sending mail to TOM, the system balked
> immediately; it could not or would not translate the "@forward" as legal. 
> This surprised me, considering the stuff I have seen being syntactically
> accepted by the "set forward" command, and the stuff I have seen it
> translate (such as the < and > characters surrounding a name). 
> 
> It seems to me to be possibly easier if Digital would change VMS mail,
> adding the ability to forward to many, with the option of a copy to
> the recipient.  Is this administratively and techinically disastrous,
> because it enables a potentially-endless loop and/or elsewise?
> -- 
> Brendan Welch, system analyst, UMass/Lowell, W1LPG,  welchb@woods.uml.edu
> 
================================================================================
Archive-Date: Thu, 8 May 1997 16:16:38 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 08 May 1997 17:15:59 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: welchb@woods.uml.edu
Message-ID: <009B3F5B.F5FE28C0.7@swdev.si.com>
Subject: RE: mail forwarding question

Brendan Welch (welchb@woods.uml.edu) writes:

>It seems to me to be possibly easier if Digital would change VMS mail,
>adding the ability to forward to many, with the option of a copy to
>the recipient.

VMS V4.x used to accept forwarding to a distribution list (@file), but it was 
removed back in V5.something because it could lead to problems.  I can't find 
the articles that described the problems, though.
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Fri, 9 May 1997 06:43:59 -0500
Sender: <owner-MX-List@MadGoat.com>
Message-ID: <2.2.32.19970509114409.00933880@opi158.openplus.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 09 May 1997 21:44:09 +1000
To: MX-List@MadGoat.com
From: Michael Czapski <MCzapski@openplus.com.au>
Reply-To: MX-List@MadGoat.com
Subject: Re: mail forwarding question

Hello Rick,

Like it or not (I did not, really) you need to use DELIVER.  It is a piece of 
freeware, in so far as I can tell, which permits you to process VMSmail
on receipt using DCL, 3GL, or what not, including forwarding to multiple
receipients, etc..  Your imagination is your limit there.
I don't have the location to hand but if you are interested I will find it
for you when I get to the office on Monday.


>I would like to set a username (joebagodoughnuts) to forward all mail to
>three (3) other users (joe, sam, bill).  I've tried setting up forwarding in
>VMS Mail to no avail.  Is there a workable solution to this?  
>
>I know this is not strictly a MX question but I've been trying to use MX to
>solve this to no avail.  Anyone have a solution that they would like to share?
>
>Many thanks in advance! ;-)
>
>-- Rick
>   Rick Stacks  stacks@adpce.lrk.ar.us |
Cheers ...

Michael Czapski
OPEN PLUS International, Ph. +61 2 452 5000, Fax. +61 2 452 5022

================================================================================
Archive-Date: Fri, 9 May 1997 11:07:48 -0500
Sender: <owner-MX-List@MadGoat.com>
From: dwing@cisco.com (Dan Wing)
Reply-To: MX-List@MadGoat.com
Subject: Re: mail forwarding question
Date: Fri, 9 May 1997 09:05:13 -0700
Message-ID: <MPG.ddceb13776878cc989696@news.kjsl.com>
To: MX-List@WKUVX1.WKU.EDU

In article <2.2.32.19970509114409.00933880@opi158.openplus.com.au>, 
MCzapski@openplus.com.au says...
> Hello Rick,
> 
> Like it or not (I did not, really) you need to use DELIVER.  It is a piece of 
> freeware, in so far as I can tell, which permits you to process VMSmail
> on receipt using DCL, 3GL, or what not, including forwarding to multiple
> receipients, etc..  Your imagination is your limit there.
> I don't have the location to hand but if you are interested I will find it
> for you when I get to the office on Monday.

Deliver is available for Anonymous FTP from ftp.innosoft.com.  However it 
exposes a security hole in VMS V7.x and higher and should not be used on 
V7.x or higher of VMS.

-Dan Wing
================================================================================
Archive-Date: Fri, 9 May 1997 11:07:53 -0500
Sender: <owner-MX-List@MadGoat.com>
From: dwing@cisco.com (Dan Wing)
Reply-To: MX-List@MadGoat.com
Subject: Re: Name resolution for SMTP outgoing.
Date: Fri, 9 May 1997 09:07:36 -0700
Message-ID: <MPG.ddceba449b8a1c3989697@news.kjsl.com>
To: MX-List@WKUVX1.WKU.EDU

In article <33731AFD.7566@lsl.co.uk>, bill@lsl.co.uk says...
> We are trying to fix a problem with name resolution - it is stopping
> MX SMTP from sending to our local POP3 server. We have turned on
> MX_SMTP_DEBUG and are curious as to what name resolution mechanisms
> are being used.
> 
> The lines:
> 
>  9-MAY-1997 13:19:05.85   SMTP_SEND: DSN_MXLOOK status is 00000134
>  9-MAY-1997 13:19:05.95   SMTP_SEND: Attempting to start session with 
> lsls4e [192.9.200.60]
>  9-MAY-1997 13:19:05.96   SMTP_SEND: Connected
> 
> occur quite often, followed by a successful transfer to a local
> machine, despite an apparent error here.
> 
> The lines:
> 
>  9-MAY-1997 13:19:07.55   SMTP_SEND: looking up host name pop
>  9-MAY-1997 13:19:37.56   SMTP_SEND: DSN_MXLOOK status is 00000001
>  9-MAY-1997 13:19:37.94   SMTP_SEND: Attempting to start session with 
> mail.corpex.com. [194.74.216.5]
>  9-MAY-1997 13:19:37.94              -- failed, status=00002094
>  9-MAY-1997 13:19:38.03   SMTP_SEND: Attempting to start session with 
> relay.bt.net. [194.72.6.52]
>  9-MAY-1997 13:19:38.03              -- failed, status=00002094
>  9-MAY-1997 13:19:38.03   SMTP_SEND: Failed, sts=00002094
> 
> are our problem, where the "mail.corpex.com. [194.74.216.5]" and
> "relay.bt.net. [194.72.6.52]" are quite incorrect (not us, while
> 'pop' is one of our machines.
> 
> How does UCX figure in the name resolution? We have the UCX name service
> enabled on the MX machines, and UCX SHOW HOST pop returns the right 
> answer. We are confused!
> 
> MX 4.1 with UCX (Digital TCP/IP Services for OpenVMS Alpha) V4.1.

What is the fully-qualified name of the host you're sending mail to?  I'm 
guessing there is a DNS problem with your Primary and Secondaries 
disagreeing.  Are all of your Primary and Secondaries accessible from the 
Internet so you can post to the list and someone can debug them using 
NSLOOKUP.

Also, does anyone know if UCX's "SHOW HOST" command examines DNS, host 
tables, or both (and if both, which order?).

-Dan Wing
================================================================================
Archive-Date: Fri, 9 May 1997 11:26:18 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Fri, 09 May 1997 12:25:14 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B3FFC.82CF8BE0.10@swdev.si.com>
Subject: Re: Name resolution for SMTP outgoing.

>Also, does anyone know if UCX's "SHOW HOST" command examines DNS, host 
>tables, or both (and if both, which order?).

SHOW HOST examines the local host tables, then the DNS.  SHOW HOST/LOCAL will 
examine only the local tables and SHOW HOST/NOLOCAL only the DNS.
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Fri, 9 May 1997 12:07:13 -0500
Sender: <owner-MX-List@MadGoat.com>
From: "Robert H. McClanahan" <rmcclanahan@tis.aecc.com>
To: MX-List@MadGoat.com
Date: Fri, 9 May 1997 12:07:01 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: Odd Entries in Queue
Reply-To: MX-List@MadGoat.com

Greetings,

I just installed MX 4.2 from scratch on a VAXstation 4000-90 running VMS 
V5.5-2 and UCX V2.0. I'm seeing some odd entries in the queue. One entry 
appears each night at 00:15 and never goes away, until I CANCEL it.

Any ideas as to what is generating these entries? I've been running MX for
several years on a VAX 4000-300 and have never seen this before.

Thanks,
RHM

+--+
Robert H. McClanahan, Mgr, Tech Info Systems, rmcclanahan@tis.aecc.com  <[]><
Arkansas Electric Coop Corp, PO Box 194208, Little Rock, AR 72219-4208 USA

"Age is a question of mind over matter. If you don't mind, it doesn't matter."
       Satchel Paige
================================================================================
Archive-Date: Sat, 10 May 1997 03:22:17 -0500
Sender: <owner-MX-List@MadGoat.com>
From: dwing@cisco.com (Dan Wing)
Subject: Re: Any creative TCP/IP solutions to stop junk E-Mail?
Date: 10 May 1997 00:39:28 GMT
Message-ID: <5l0g40$8j4$1@cronkite.cisco.com>
Reply-To: MX-List@MadGoat.com
To: Info-VAX@Mvb.Saic.Com

In article <5l02j2$3po@top.mitre.org>, lewis@jag.mitre.org (Keith A. Lewis) writes:
>"Randy N. Baker" <RBAKER@gc1.georcoll.on.ca> writes in article <970507084415.d98@gc1.georcoll.on.ca> dated Wed, 7 May 1997 8:44:15 -0400:
>>I am getting tired of finding unsolicited junk E-Mail, and I don't think
>>sending E-Mail back to the originating sender does, or will do any good.

Nope, it won't.  Your complaint to them is proof they have a 'live'
email account that someone uses - there couldn't be a better place to
send those advertisements!  They aren't going to stop out of the 
kindness of their hearts.

>I'd settle for a system-level filter that would drop or bounce messages from
>specific domains.  I run UCX SMTP and MX over UCX.  Can anybody point me to
>a solution?

The next version of MX includes such a feature.

-Dan Wing
================================================================================
Archive-Date: Mon, 12 May 1997 20:23:03 -0500
Sender: <owner-MX-List@MadGoat.com>
From: dwing@cisco.com (Dan Wing)
Reply-To: MX-List@MadGoat.com
Subject: Re: Is MX the right solution for this?
Date: Mon, 12 May 1997 19:19:05 -0700
Message-ID: <MPG.de16f773cd3f51c989699@news.kjsl.com>
To: MX-List@WKUVX1.WKU.EDU

In article <1997May12.100219.1089@flying-disk.spamblock.com>, 
frisbie@flying-disk.spamblock.com says...
> Outgoing mail is the problem.   The users have to address mail as:
> 
>      OLDVAX::UUCP%"user@domain.com"
> 
> To it bluntly, this is more than some of them can handle.   I would
> like them to be able to simply address outgoing mail as:
> 
>      user@domain.com
> 
> and let all the forwarding/translation go on behind their backs.
> Also, this is essential if "REPLY" is to work transparently.
> Is this the sort of thing that MX is designed to do?   Is there
> an easier solution?

MX works great over UUCP and can hide all the address rewriting ugliness.  
MX also provides a slew of other features which you'll probably find 
pretty useful.

-Dan Wing

================================================================================
Archive-Date: Tue, 13 May 1997 15:24:24 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 13 May 1997 17:24:04 EDT
From: Irv Eisen <irv@ccstat.mc.duke.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B434A.EB3C9A50.88@ccstat.mc.duke.edu>
Subject: Re: Any creative TCP/IP solutions to stop junk E-Mail?

<In article <5l02j2$3po@top.mitre.org>, lewis@jag.mitre.org (Keith A. Lewis)
<writes:
>"Randy N. Baker" <RBAKER@gc1.georcoll.on.ca> writes in article <970507084415.d98@gc1.georcoll.on.ca> dated Wed, 7 May 1997 8:44:15 -0400:
>>I am getting tired of finding unsolicited junk E-Mail, and I don't think
>>sending E-Mail back to the originating sender does, or will do any good.

>I'd settle for a system-level filter that would drop or bounce messages from
>specific domains.  I run UCX SMTP and MX over UCX.  Can anybody point me to
>a solution?

I receive the following message in March. I did not respond to it because
it is basically another spam, therefore I am not in any way endorsing it.
But if it's for real it might be a good thing. The web page is there; they
have a phone number and the nameserver has a listing for netchem.com. That's
a lot more real than your typical spam. I'm just not sure I want my name on
another list.

Has anyone else seen this or heard of anyone responding to this?

Thanks,
================================================================
Irv Eisen, Systems Manager      
Cancer Center Information Systems  Email: IRV@CCSTAT.MC.DUKE.EDU
Duke University Medical Center                                  
DUMC Box 3958                      Voice: (919) 681-5405
Durham, NC 27710                   Fax  : (919) 681-8028
================================================================


===========================================================================

From:	MX%"remove@netchem.com" 22-MAR-1997 11:05:34.80
To:	IRV
CC:	
Subj:	Please Help Yourself, Help Others & Help the Internet

Dear Sir/Madam,

Your email address is on many spammers' lists.
That is why you received so much junk email lately.

Most of the spammers will stop sending you junk email
if you ask them to remove your email address from their lists.

But the problem is that there are too many spammers.
The spammers are not supposed to send you junk email in the first place.
Why do you even have to spend your time to reply?

We are compiling a REMOVE list.  It is much faster for the spammers
to remove your email address if we send them the list because most
of the spammers use automated software.

To add your name to the REMOVE list, simply reply to this email. 
You do not have to write anything. It is FREE!

We are also compiling a blacklist of spammers. If you receive junk email
from someone, please forward the original message to list@netchem.com.

Please do not use spammers to advertise your product on the Internet.
It is not easy to send out 1 million email. The spammer will take your
money and disappear. 

To avoid further spamming, we send out this message only to limited number 
of users. Please forward this email to your friends if you think it is
useful to them. 

Sincerely,
Jerry

-------------------------------------------------
Jerry Wang, PhD, Chemechanics, Inc.					 
http://www.netchem.com, mailto:jerryw@netchem.com 
-------------------------------------------------

================================================================================
Archive-Date: Tue, 13 May 1997 15:54:19 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 13 May 1997 14:53:58 -0700
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: henrym@sacto.mp.usbr.gov
Message-ID: <009B4335.F31ADA30.5@sacto.mp.usbr.gov>
Subject: Re: Any creative TCP/IP solutions to stop junk E-Mail?

> From:	MX%"MX-List@MadGoat.com" 13-MAY-1997 14:41:37.64
> Subj:	Re: Any creative TCP/IP solutions to stop junk E-Mail?

> <In article <5l02j2$3po@top.mitre.org>, lewis@jag.mitre.org (Keith A. Lewis)
> <writes:
> >"Randy N. Baker" <RBAKER@gc1.georcoll.on.ca> writes in article <970507084415.d98@gc1.georcoll.on.ca> dated Wed, 7 May 1997 8:44:15 -0400:
> >>I am getting tired of finding unsolicited junk E-Mail, and I don't think
> >>sending E-Mail back to the originating sender does, or will do any good.
> 
> >I'd settle for a system-level filter that would drop or bounce messages from
> >specific domains.  I run UCX SMTP and MX over UCX.  Can anybody point me to
> >a solution?
> 
> I receive the following message in March. I did not respond to it because
> it is basically another spam, therefore I am not in any way endorsing it.
> But if it's for real it might be a good thing. The web page is there; they
> have a phone number and the nameserver has a listing for netchem.com. That's
> a lot more real than your typical spam. I'm just not sure I want my name on
> another list.
> 
> Has anyone else seen this or heard of anyone responding to this?
> 

	Dunno.  I just forwarded a copy to the List Managers list; will 
report back.

-HWM

> Thanks,
> ================================================================
> Irv Eisen, Systems Manager      
> Cancer Center Information Systems  Email: IRV@CCSTAT.MC.DUKE.EDU
> Duke University Medical Center                                  
> DUMC Box 3958                      Voice: (919) 681-5405
> Durham, NC 27710                   Fax  : (919) 681-8028
> ================================================================
> 
> 
> ===========================================================================
> 
> From:	MX%"remove@netchem.com" 22-MAR-1997 11:05:34.80
> To:	IRV
> CC:	
> Subj:	Please Help Yourself, Help Others & Help the Internet
> 
> Dear Sir/Madam,
> 
> Your email address is on many spammers' lists.
> That is why you received so much junk email lately.
> 
> Most of the spammers will stop sending you junk email
> if you ask them to remove your email address from their lists.
> 
> But the problem is that there are too many spammers.
> The spammers are not supposed to send you junk email in the first place.
> Why do you even have to spend your time to reply?
> 
> We are compiling a REMOVE list.  It is much faster for the spammers
> to remove your email address if we send them the list because most
> of the spammers use automated software.
> 
> To add your name to the REMOVE list, simply reply to this email. 
> You do not have to write anything. It is FREE!
> 
> We are also compiling a blacklist of spammers. If you receive junk email
> from someone, please forward the original message to list@netchem.com.
> 
> Please do not use spammers to advertise your product on the Internet.
> It is not easy to send out 1 million email. The spammer will take your
> money and disappear. 
> 
> To avoid further spamming, we send out this message only to limited number 
> of users. Please forward this email to your friends if you think it is
> useful to them. 
> 
> Sincerely,
> Jerry
> 
> -------------------------------------------------
> Jerry Wang, PhD, Chemechanics, Inc.					 
> http://www.netchem.com, mailto:jerryw@netchem.com 
> -------------------------------------------------
> 
> --------------------------------------------------------------------------------
> Return-Path: <owner-MX-List@MadGoat.com>
> Received: from alpha.wku.edu (161.6.18.4) by sacusr.mp.usbr.gov (MX C5.0) with
>           ESMTP; Tue, 13 May 1997 14:41:17 -0700
> X-ListName: Message Exchange Discussion List <MX-List@MadGoat.com>
> Warnings-To: <>
> Errors-To: <owner-MX-List@MadGoat.com>
> Sender: <owner-MX-List@MadGoat.com>
> Date: Tue, 13 May 1997 17:24:04 EDT
> From: Irv Eisen <irv@ccstat.mc.duke.edu>
> Reply-To: MX-List@MadGoat.com
> To: MX-List@MadGoat.com
> Message-ID: <009B434A.EB3C9A50.88@ccstat.mc.duke.edu>
> Subject: Re: Any creative TCP/IP solutions to stop junk E-Mail?
> X-List-Subscribe: <mailto:MX-List-request@MadGoat.com?body=subscribe>
> X-List-Unsubscribe: <mailto:MX-List-request@MadGoat.com?body=unsubscribe>
> X-List-Help: <http://www.madgoat.com/>
================================================================================
Archive-Date: Wed, 14 May 1997 21:22:25 -0500
Sender: <owner-MX-List@MadGoat.com>
From: dwing@cisco.com (Dan Wing)
Subject: Re: MX under VMS 7.1
Date: 15 May 1997 02:45:47 GMT
Message-ID: <5ldtcr$iht$1@news-sj-3.cisco.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@WKUVX1.WKU.EDU

In article <5ldrpb$t00@top.mitre.org>, lewis@omega.mitre.org (Keith A. Lewis) writes:
>I just upgraded from VMS (AXP) 6.2 to 7.1, and I get the following message
>during MX_STARTUP.
>
>%INSTALL-E-FAIL, failed to CREATE entry for DISK$CLUST62:<VMS$COMMON.PUBLIC_SOFT
>WARE.MX.ALPHA_EXE>MX_MAILSHRP.EXE
>-INSTALL-E-SYSVERDIF, system version mismatch - please relink
>
>I went into the MX_ROOT:[SRC] directory and tried to rebuild, but the macro
>code seems to be obsolete.  Is it possible to build MX under VMS 7.1?
>It's MX version 4.2.

Just reinstall MX.  MX will relink itself during installation - no
need to recompile from sources. 

-Dan Wing
================================================================================
Archive-Date: Thu, 15 May 1997 15:31:15 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 15 May 1997 22:30:51 +0100
From: Mark E Williamson <M.E.Williamson@bolton.ac.uk>
Reply-To: MX-List@MadGoat.com
To: MX-LIST@MADGOAT.COM
Message-ID: <009B4508.1B66E1A9.38@basil.acs.bolton.ac.uk>
Subject: Local process failing - %MX-F-MEMALLOC

Date sent:  15-MAY-1997 22:25:17 

Hello, I don't think I have seen this before on the list, I have having a 
problem with MX_LOCAL dying with the following message:

>%%%%%%%%%%%  OPCOM  15-MAY-1997 22:12:59.26  %%%%%%%%%%%
>Message from user SYSTEM on BASIL
>MX Local (pid 2020858C) exiting, status = 1C278034
>
>%MX-F-MEMALLOC, error allocating memory from zone !AS   

This is the debug output from the dying process:

>15-MAY-1997 22:11:53.71 Processing queue entry number 182
>15-MAY-1997 22:11:54.88   Checking local name: ADC1CSS
>15-MAY-1997 22:11:55.01   LOCAL_USER:  User ADC1CSS definitely local.
>15-MAY-1997 22:11:55.01     This is a regular delivery.
>15-MAY-1997 22:11:55.01   Checking local name: JWA1CSS
>15-MAY-1997 22:11:55.43   LOCAL_USER: Non-MX fwdg address JAMES.APPLETON@VIRGIN.
>NET; treat as local.

OK, I see whats happening the user didn't put the MX% in:

MAIL> sh forw/user=jwa1css
JWA1CSS has mail forwarded to JAMES.APPLETON@VIRGIN.NET

 should this crash MX_LOCAL ?

>15-MAY-1997 22:11:55.43     This is a regular delivery.
>15-MAY-1997 22:11:55.68   DELIVER: mime_headers = 9
>15-MAY-1997 22:11:55.68   DELIVER: fdlstr = ""
>15-MAY-1997 22:11:55.80   DELIVER:  Using MX%"acm@hotmail.com",MX%"adc1css@bolto
>n.ac.uk",MX%"d.burns@virgin.net",MX%"limb@mersinet.co.uk",MX%"gnom@stmarys.medfo
>rd.or.us",MX%"petecamp@mersinet.co.uk",MX%"jwa1css@bolton.ac.uk",MX%"james.apple
>ton@virgin.net",
>15-MAY-1997 22:11:55.83   DELIVER:  Using  as VMS MAIL To address.
>15-MAY-1997 22:11:55.83   DELIVER:  Using  as VMS MAIL CC address.
>15-MAY-1997 22:11:55.84   DELIVER:  Using "write me you gets!" as subject.
>15-MAY-1997 22:11:57.76   DELIVER:  Delivering to ADC1CSS
>15-MAY-1997 22:11:58.49   DELIVER:  Status=00000001 from MAIL$ routines
>15-MAY-1997 22:11:58.70   DELIVER:  Delivering to JAMES.APPLETON@VIRGIN.NET
>

The process fails when trying to deliver to  JAMES.APPLETON@VIRGIN.NET   

I think I have the latest MX_LOCAL 

         image name: "MX_LOCAL"
                image file identification: "V4.2-A"
                link date/time:  7-DEC-1996 00:36:35.18
                linker identification: "V11-36"


	Thanks in Advance

+-----------------------------------------------+------------------------------+
| Mark Williamson , Network Manager             | Mail: Bolton Institute of HE |
|                                               |       Deane Campus           |
| E-mail     : M.E.Williamson@Bolton.ac.uk      |       Deane Road             |
| Phone      : +44 1204 528851                  |       Bolton UK              |
| Fax        : +44 1204 399074                  |       BL3 5AB                |
+-----------------------------------------------+------------------------------+
================================================================================
Archive-Date: Thu, 15 May 1997 15:47:47 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 15 May 1997 15:47:33 -0500
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: M.E.WILLIAMSON@BOLTON.AC.UK
Message-ID: <009B44CF.C4913349.67@ALPHA.WKU.EDU>
Subject: RE: Local process failing - %MX-F-MEMALLOC

Mark E Williamson <M.E.Williamson@bolton.ac.uk> writes:
>
>Hello, I don't think I have seen this before on the list, I have having a 
>problem with MX_LOCAL dying with the following message:
>
>>%%%%%%%%%%%  OPCOM  15-MAY-1997 22:12:59.26  %%%%%%%%%%%
>>Message from user SYSTEM on BASIL
>>MX Local (pid 2020858C) exiting, status = 1C278034
>>
>>%MX-F-MEMALLOC, error allocating memory from zone !AS   
>
[...]
>The process fails when trying to deliver to  JAMES.APPLETON@VIRGIN.NET   
>
>I think I have the latest MX_LOCAL 
>
>         image name: "MX_LOCAL"
>                image file identification: "V4.2-A"
>                link date/time:  7-DEC-1996 00:36:35.18
>                linker identification: "V11-36"
>
No, you don't.  The current image on ftp.madgoat.com in
[.MX.MX042.PATCH] fixes this problem.  Sort of.  The mail still won't
be delivered, but it won't kill MX_LOCAL.

For more information, check out the original message I posted about
this.  You can find it by using the URL below and searching the
February 1997 archive for "new local image" (without the quotes):

http://www.madgoat.com/scripts/mxarchive/as_init.com?MX-List

Or use (just concatenate the two lines to make one URL):

http://www.madgoat.com/scripts/mxarchive/archive_search.com?
TEXT=R194852-196946-anonymous_root%3A%5Blists.mx-list%5Dmx-list.1997-02

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Fri, 16 May 1997 09:34:25 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Fri, 16 May 1997 09:34:08 -0500
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: MadGoat-Announce@MadGoat.com
Message-ID: <009B4564.C484B5EF.4@ALPHA.WKU.EDU>
Subject: DECUS

Hi.  I'll be at DECUS, but only through Monday (I'm helping with two
seminars this weekend).  Because of my short time there, I don't have
time to do an MX/MadGoat BOF, but I am scheduled to work in the
Process Software booth Monday morning from 10 AM to 1:30 PM.  Feel
free to drop by and say "Hi!", if you you want to.

Just don't beat me up for some feature you've asked for that hasn't
been implemented yet.... ;-)

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Tue, 20 May 1997 09:48:06 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 20 May 1997 09:47:59 -0500
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: Info-MadGoat@MadGoat.com, MX-List@MadGoat.com
Message-ID: <009B488B.5DAA619B.15@ALPHA.WKU.EDU>
Subject: FYI: Process has bought MultiNet from Cisco

From: Jim collum <collum@Cisco.COM>
Newsgroups: vmsnet.networks.tcp-ip.multinet
Subject: Process Software to Assume Ownership of MultiNet for OpenVMS Products
Date: Mon, 19 May 1997 07:21:47 -0700

Cisco Systems and Process Software are announcing at DECUS today the sale
of the MultiNet for OpenVMS product line to Process Software. If you are
attending DECUS, and wish additional information, please visit the Process
Software booth. Attached is the announcement letter and Q&A.

Contact for additional information can be found below. All customers will
be receiving a letter from Cisco regarding this agreement.


	thank you

	Jim Collum
	Manager, Multinet Support
	collum@cisco.com



=================================================================


Cisco MultiNet Product Line

Cisco Sells Cisco MultiNet Product Line to Process Software, Inc.


The Cisco MultiNet product line, which includes the Cisco MultiNet and
Cisco MultiNet Secure/IP products, has been sold to Process Software, Inc.
Formerly acquired from TGV in March 1996, the Cisco MultiNet product line
provides a complete TCP/IP suite for the OpenVMS VAX and Alpha platforms.

Beginning June  1, 1997, Process Software will assume sales and support of
the MultiNet product line. All sales calls received at Cisco regarding the
product line, including new orders, will be routed to Process Software.
However, support calls will be transitioned to Process Software over a
nine-month period to ensure customer satisfaction. Current Cisco MultiNet
pricing for both licenses and support will remain in effect.


Selecting Process Software
Process Software is a leading provider of TCP/IP products for the OpenVMS
market. It was selected because of its strong TCP/IP for OpenVMS technical
expertise, customer service organization, sales channels, and its long-term
commitment to ongoing TCP/IP for OpenVMS development. This agreement
ensures that OpenVMS customers can continue to grow their current business
within a TCP/IP environment while receiving best-in-class support. 

Process Software will sell and support MultiNet as well as its own product
line, TCPware.


Orderability and Support Road Map:
The following road map will help you direct customer calls regarding
orderability and renewal of product and support:

	For sales prior to June 1, 1997, contact Doug Blaisdell at dougb@cisco.com
 or call 408 527-8108.

	For new Cisco MultiNet orders and support contracts after June 1, 1997,
contact  Process Software at (508) 879 6994 and ask for MultiNet Sales 

	Current support problems are handled by Cisco Systems in the following
regions:

		North America	1 800 553-2447
					408 526-7209
					tac@cisco.com

		Europe		32 2 788 42 42
					euro-tac@cisco.com

		Asia-Pacific	61 2 9935 4107
					asiapac-tac@cisco.com

		Australia		1 800 805-227




Cisco MultiNet for OpenVMS 

PUBLIC Q&A


Q:	Why did Cisco stop selling the MultiNet product line?

A:	We looked at the long term options for MultiNet's development and
support because of the decreasing number of OpenVMS engineers on the West
Coast of the United States. We felt Process Software could best implement
next-generation solutions for this specialized marketplace because of its
location, ongoing partnership, and relationship with Digital.  Support for
Cisco customers will transfer to Process Software Corporation effective
June 1, 1997.  We are committed to making this a smooth transition for all
our customers.  


Q:	Why did Cisco choose Process Software?

A:	Process Software has been developing and supporting TCP/IP for OpenVMS
for over ten years.  Its flagship product, TCPware for OpenVMS is a leading
alternative solution to MultiNet and is well respected for its reliability,
performance, and functionality.  In addition, Process Software is
responsible for the development and backline support of Digital's TCP/IP
services for OpenVMS product.  Process Software is firmly committed to the
OpenVMS market and to ongoing TCP/IP development as evidenced by their
commitment to Year 2000 compliance, IPv6 for OpenVMS, and other
leading-edge development.


Q. Whom should you call to place an order for MultiNet licenses or to renew
a MultiNet support contract?

A. Until May 31, 1997, customers should call Doug Blaisdell at 408 527-8108
to place new license orders, or John Masterson at 408 527-2248 for renewal
sales or new support contracts. Effective June 1, 1997, Cisco will no
longer sell MultiNet for OpenVMS licenses or service contracts. There are
no changes in pricing, but all orders should be placed through Process
Software Corporation by dialing 800 722-7770 and ask for MultiNet Sales.


Q. Whom should the customer call for technical support for MultiNet?

A. For the time being, the customer should continue to place technical
support calls with Cisco, who will then transfer these calls gradually to
Process Software. The transition of all support calls will be completed by
January 1, 1998. During this time, currently supported customers will be
notified by Cisco as to when they should contact Process Software directly
for technical support.

For current support problems, contact Cisco Systems in the following regions:

North America 1 800 553-2447
408 526-7209
tac@cisco.com

Europe 32 2 788 42 42
euro-tac@cisco.com

Asia-Pacific 61 2 9935 4107
asiapac-tac@cisco.com

Australia 1 800 805-227



Q. Whom should Cisco MultiNet business partners call for questions on the
transition?

A. Until May 31, 1997, partners can contact Doug Blaisdell at
dougb@cisco.com or 408 527-8108. Effective June 1, 1997, partners can call
Process Software at 508 879-6994 and ask for MultiNet Sales.


Q:	Will MultiNet customers be forced to replace their MultiNet software
with Process Software's TCPware?

A:	No, Process is committed to providing full support for both MultiNet and
its TCPware product.


Q:	When will Cisco officially discontinue the product?

A:	All orders should be placed through Process Software Corporation
effective June 1, 1997.  Cisco will continue to field technical support
calls for several months, but will gradually transfer those calls to
Process Software. Cisco will notify customers throughout the transition
period as to when they should call Process Software directly.


Q:	Why did Cisco originally decide to acquire TGV?

A:	Cisco is committed to offering value-added Internet software capable of
delivering valuable applications and services.  When we acquired the
company, TGV was a leading supplier of Internet software products that
enable connectivity between disparate computer systems over LAN, WAN, and
global computing networks.  Technologies and engineering resources from TGV
have and will continue to be integrated into Cisco's software and hardware
product lines to build corporate intranets and support the growing Internet.


Q:	What are Cisco's plans for other TGV products?

A:	TGV has contributed both talented staff and innovative technology to
Cisco, including technologies of Domain Name System (DNS)/Dynamic Host
Configuration Protocol (DHCP)  and security.  These technologies will
continue to be integrated into existing and new Cisco products.  

Q: Does this agreement include other TGV products, such as the Cisco Suite
100 (formerly called Cisco MultiNet for Windows) or MultiWare?


A. No. This agreement applies only to Cisco MultiNet and Cisco MultiNet
Secure/IP. The Cisco Suite 100 is still being sold by Cisco. The MultiWare
product was retired on April 1996 and is no longer sold. Cisco support for
MultiWare ends on July 31, 1997.





================================================================================
Archive-Date: Tue, 20 May 1997 10:07:54 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 20 May 1997 11:06:57 EDT
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B4896.654A15C0.19@swdev.si.com>
Subject: RE: FYI: Process has bought MultiNet from Cisco

>Cisco Systems and Process Software are announcing at DECUS today the sale
>of the MultiNet for OpenVMS product line to Process Software.

Holy cow!!!  That's quite an announcement!  I wonder...  is Process Software 
going to relabel Multinet as TCPware or are they going to ashcan Multinet?
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Tue, 20 May 1997 15:38:48 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 20 May 1997 15:38:42 -0500
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B48BC.5BCED6FD.26@ALPHA.WKU.EDU>
Subject: RE: FYI: Process has bought MultiNet from Cisco

"Brian Tillman, x8425" <tillman@swdev.si.com> writes:
>
>>Cisco Systems and Process Software are announcing at DECUS today the sale
>>of the MultiNet for OpenVMS product line to Process Software.
>
>Holy cow!!!  That's quite an announcement!  I wonder...  is Process Software 
>going to relabel Multinet as TCPware or are they going to ashcan Multinet?

Neither.  The plan is to maintain and enhance both product lines. 
They may eventually merge, but that's a long time from now.

For more info, you might check out vmsnet.networks.tcp-ip.multinet.

MultiNet customers need not fear the transition!!

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Wed, 21 May 1997 02:31:28 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Wed, 21 May 1997 00:30:34 MST
From: Ray Harwood -- Data Basix <rharwood@Basix.COM>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: rharwood@Basix.COM
Message-ID: <009B4906.A8FFE5D6.9@Basix.COM>
Subject: RE: FYI: Process has bought MultiNet from Cisco

> Cisco Systems and Process Software are announcing at DECUS today the sale
> of the MultiNet for OpenVMS product line to Process Software.

Maybe this explains why Cisco hasn't fixed my screwed-up maintenance records...
has anybody else been quoted DOUBLE the TGV prices for Multinet maintenance
under Cisco???  I hope Process has a more reasonable maintenance fee structure!

Ray
================================================================================
Archive-Date: Wed, 21 May 1997 08:25:12 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Wed, 21 May 1997 09:25:04 EDT
From: Irv Eisen <irv@ccstat.mc.duke.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B4951.5406DA0E.45@ccstat.mc.duke.edu>
Subject: RE: FYI: Process has bought MultiNet from Cisco

<>Holy cow!!!  That's quite an announcement!  I wonder...  is Process Software 
<>going to relabel Multinet as TCPware or are they going to ashcan Multinet?
<
<Neither.  The plan is to maintain and enhance both product lines. 
<They may eventually merge, but that's a long time from now.
<
<For more info, you might check out vmsnet.networks.tcp-ip.multinet.
<
<MultiNet customers need not fear the transition!!
<
<Hunter
<------
<Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html

Will the MadGoat brothers, Matt Madison and Hunter Goatley, get to work
together -- for pay, this time? Ironic how Matt goes from RPI to TGV, to
Cisco  and Hunter comes from Ky. and you both end up at Process. Have you
had any problems avoiding conflicts of interest between your MadGoat
software and the work you do for your companies? I hope that's not a touchy
subject or too personal.

================================================================
Irv Eisen, Systems Manager      
Cancer Center Information Systems  Email: IRV@CCSTAT.MC.DUKE.EDU
Duke University Medical Center                                  
DUMC Box 3958                      Voice: (919) 681-5405
Durham, NC 27710                   Fax  : (919) 681-8028
================================================================

================================================================================
Archive-Date: Wed, 21 May 1997 09:10:37 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Wed, 21 May 1997 09:10:32 -0500
From: goathunter@MadGoat.COM
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B494F.4C5BADB6.1@ALPHA.WKU.EDU>
Subject: RE: FYI: Process has bought MultiNet from Cisco

Irv Eisen <irv@ccstat.mc.duke.edu> writes:
>
>Will the MadGoat brothers, Matt Madison and Hunter Goatley, get to work
>together -- for pay, this time? Ironic how Matt goes from RPI to TGV, to
>Cisco  and Hunter comes from Ky. and you both end up at Process.

No.  The deal was for the software only; none of the TGVers come to
Process in the deal, though we do hope some of them would like to
make the switch.

>Have you
>had any problems avoiding conflicts of interest between your MadGoat
>software and the work you do for your companies? I hope that's not a touchy
>subject or too personal.
>
Not at all.  In the case of Process, they've encouraged to keep doing
the MadGoat work....

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Thu, 22 May 1997 08:18:44 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 22 May 1997 09:18:39 EST
From: Rick Morrison - Wayne State University <morrison@oncvx1.roc.wayne.edu>
Reply-To: MX-List@MadGoat.com
To: mx-list@madgoat.com
Message-ID: <009B4A19.9939EDE0.6@oncvx1.roc.wayne.edu>
Subject: SMTP_Server dying

My SMTP_Server component keeps shutting itself down after being up only
about 1.5 hours ... with status=10248074 (see below).  This just started
happening.  Only change to the system I've made is to install the delta-time
patch from DEC (library update v6.0).  System is OpenVMS v7.0.

Any ideas?  Thanks in advance!

Rick Morrison
Wayne State University

22-MAY-1997 07:53:42.36:  MX SMTP Server (pid 00000D27) starting
22-MAY-1997 09:10:18.93:  MX SMTP Server (pid 00000D27) exiting, 
status = 10248074
================================================================================
Archive-Date: Thu, 22 May 1997 09:33:17 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 22 May 1997 07:32:55 -0700
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: henrym@sacto.mp.usbr.gov
Message-ID: <009B4A0A.D3F922B6.47@sacto.mp.usbr.gov>
Subject: RE: SMTP_Server dying

> From:	MX%"MX-List@MadGoat.com" 22-MAY-1997 07:00:24.48
> Subj:	SMTP_Server dying

Rick,

> My SMTP_Server component keeps shutting itself down after being up only
> about 1.5 hours ... with status=10248074 (see below).  This just started
> happening.  Only change to the system I've made is to install the delta-time
> patch from DEC (library update v6.0).  System is OpenVMS v7.0.
> 
> Any ideas?  Thanks in advance!
> 
> Rick Morrison
> Wayne State University
> 
> 22-MAY-1997 07:53:42.36:  MX SMTP Server (pid 00000D27) starting
> 22-MAY-1997 09:10:18.93:  MX SMTP Server (pid 00000D27) exiting, 
> status = 10248074


	Whoa! "%STR-F-STRTOOLON, string is too long (greater than 65535)"
I know that Hunter and Matt did a lot of work to fix these too-long 
strings, normally send my SPAMMER's trying to hit a zillion mailing 
lists or adresses in one shot - looks like you hit the jackpot!

	Have you installed the 4.2A kits that Hunter produced a few 
months ago to deal with this issue?

-HWM
================================================================================
Archive-Date: Thu, 22 May 1997 09:42:32 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 22 May 1997 09:42:27 -0500
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: MORRISON@ONCVX1.ROC.WAYNE.EDU
Message-ID: <009B4A1C.EC293DC5.22@ALPHA.WKU.EDU>
Subject: RE: SMTP_Server dying

Rick Morrison - Wayne State University writes:
>
>My SMTP_Server component keeps shutting itself down after being up only
>about 1.5 hours ... with status=10248074 (see below).  This just started
>happening.  Only change to the system I've made is to install the delta-time
>patch from DEC (library update v6.0).  System is OpenVMS v7.0.
>
That error is:

ALPHA$ set mess mx_msg
ALPHA$ write sys$output f$message(%x10248074)
%STR-F-STRTOOLON, string is too long (greater than 65535)
ALPHA$

which is caused by an incoming message with a To: or CC: header that's
longer than 64K characters (a spam message).

This problem was fixed several months ago by the new SMTP_SERVER.*
images that can be found on ftp.madgoat.com in [.MX.MX042.PATCH].

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Thu, 22 May 1997 10:04:43 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 22 May 1997 11:04:39 EST
From: Rick Morrison - Wayne State University <morrison@oncvx1.roc.wayne.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B4A28.682BCD40.17@oncvx1.roc.wayne.edu>
Subject: RE: SMTP_Server dying

>>
>>My SMTP_Server component keeps shutting itself down after being up only
>>about 1.5 hours ... with status=10248074 (see below).  This just started
>>happening.  Only change to the system I've made is to install the delta-time
>>patch from DEC (library update v6.0).  System is OpenVMS v7.0.
>>
>That error is:
>
>ALPHA$ set mess mx_msg
>ALPHA$ write sys$output f$message(%x10248074)
>%STR-F-STRTOOLON, string is too long (greater than 65535)
>ALPHA$
>
>which is caused by an incoming message with a To: or CC: header that's
>longer than 64K characters (a spam message).
>
>This problem was fixed several months ago by the new SMTP_SERVER.*
>images that can be found on ftp.madgoat.com in [.MX.MX042.PATCH].
>
>Hunter
>------
>Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
><goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
>

That seems to have fixed it.  Thanks everyone!

Rick Morrison
Wayne State University
================================================================================
Archive-Date: Thu, 22 May 1997 12:43:24 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 22 May 1997 13:43:15 EDT
From: Irv Eisen <irv@ccstat.mc.duke.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B4A3E.8FD6C965.135@ccstat.mc.duke.edu>
Subject: RE: SMTP_Server dying

<My SMTP_Server component keeps shutting itself down after being up only
<about 1.5 hours ... with status=10248074 (see below).  This just started
<happening.  Only change to the system I've made is to install the delta-time
<patch from DEC (library update v6.0).  System is OpenVMS v7.0.
<
<Any ideas?  Thanks in advance!
<
<Rick Morrison
<Wayne State University
<
<22-MAY-1997 07:53:42.36:  MX SMTP Server (pid 00000D27) starting
<22-MAY-1997 09:10:18.93:  MX SMTP Server (pid 00000D27) exiting, 
<status = 10248074

This started happening to me, too, about two weeks ago, same status number,
varying amounts of time between crashes, sometimes as little as 2-3
minutes.

I have not applied the delta-time patch. Am running VMS 5.5-2, MX 4.1 VAX,
Digital TCPIP Services 4.0 and IUPOP3. I have smtp_server_debug defined but
have not seen anything in those logs to indicate what is going on. I checked
through the archives on the MadGoat web site and saw references to SMTP
Server crashes but no solutions. I kludged around it by having a .com file
resubmit itself every two hours to shut down mx and restart it. (I can see
the virtual cringes now.)

My faith in MX leads me to believe that this is just a likely to be a TCPIP
Services problem as an MX problem, but I am not getting any hints from
TCPIP Services.

Thanks,
================================================================
Irv Eisen, Systems Manager      
Cancer Center Information Systems  Email: IRV@CCSTAT.MC.DUKE.EDU
Duke University Medical Center                                  
DUMC Box 3958                      Voice: (919) 681-5405
Durham, NC 27710                   Fax  : (919) 681-8028
================================================================

================================================================================
Archive-Date: Fri, 23 May 1997 10:07:18 -0500
Sender: <owner-MX-List@MadGoat.com>
Message-ID: <3.0.1.16.19970523160500.793fd6f2@alpha1.actfs.co.uk>
Date: Fri, 23 May 1997 16:05:00 +0100
To: MX-List@MadGoat.com
From: John Rourke <John.Rourke@actfs.co.uk>
Reply-To: MX-List@MadGoat.com
Subject: MX & DEC's UCX POP server
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

I have just installed UCX V4.1 ECO 8 and rapidly removed it again.  

Messages read in VMS mail have the normal FROM: line of MX%"user@host.domain"

Reading them via the POP server changes the FROM line to

"MX%\"user@host.domain\""@host.domain

which MX objects to if I try to reply to the messages.

This behvaiour appears not to happen if i try the same thing on a 'pure'
UCX system (i.e. not using MX.  The FROM: line in VMS mail is then user
@host.domain (there is no SMTP% part)

Can I do anything about this or is it DEC's way of trying to stop me using MX?

John Rourke

================================================================================
Archive-Date: Fri, 23 May 1997 12:31:34 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Fri, 23 May 1997 11:31:25 MST
From: wam@upi.uhcolorado.edu
Reply-To: MX-List@MadGoat.com
To: MX-LIST@LISTS.WKU.EDU
Message-ID: <009B4AF5.4FAAFAC0.3@upi.uhcolorado.edu>
Subject: MX Version


	What is the most recent version of MX for VAX?

We are running V4.1, and I have been asked to look into upgrading.

Thanks!  -Bill


Bill Monday
University Physicians, Inc.
(303) 372-2337
wam@upi.uhcolorado.edu

================================================================================
Archive-Date: Fri, 23 May 1997 13:26:33 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Fri, 23 May 1997 14:26:20 EDT
From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: hardis@garnet.nist.gov
Message-ID: <009B4B0D.BF0CD920.13@garnet.nist.gov>
Subject: RE: MX Version

> What is the most recent version of MX for VAX?
>
> We are running V4.1, and I have been asked to look into upgrading.

V 4.1 is the current version.  However, there have been a couple of 
intermediate patches made and uploaded to the MX ftp server.

Version 4.2 is under development.

  - Jonathan
================================================================================
Archive-Date: Fri, 23 May 1997 14:30:24 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Fri, 23 May 1997 14:30:19 -0500
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B4B0E.4D66713A.3@ALPHA.WKU.EDU>
Subject: RE: MX Version

"Jonathan E. Hardis" <hardis@garnet.nist.gov> writes:
>
>> What is the most recent version of MX for VAX?
>>
>> We are running V4.1, and I have been asked to look into upgrading.
>
>V 4.1 is the current version.  However, there have been a couple of 
>intermediate patches made and uploaded to the MX ftp server.
>
>Version 4.2 is under development.
>
Actually, V4.2 is the current version and V5.0 is in beta-test.

Hunter
------
Hunter Goatley, Process Software (TCPware for OpenVMS), http://www.process.com
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Tue, 27 May 1997 16:25:49 -0500
Sender: <owner-MX-List@MadGoat.com>
Subject: Re: MX v5.0?
Message-ID: <LEVITTE.97May28000911@devil.bofh.se>
From: levitte@lp.se (Richard Levitte - VMS Whacker)
Reply-To: MX-List@MadGoat.com
Date: 27 May 1997 22:09:11 GMT
MIME-Version: 1.0
Content-Type: Text/Plain; Charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
To: MX-List@WKUVX1.WKU.EDU

In article <338AFFED.41C6@merrimack.edu> Rand P Hall <rand@merrimack.edu> writes:

   A few days ago (Javier ?) said something about using MX v5.0. Is
   this how Hunter's getting those great X-List-xxx headers into the
   info-madgoat list? I can't wait for that!

Yes.

5.0 is right now in beta, being tested by a few.  Another feature is
blocking of mail from senders as specified by the system manager.


-- 
R Levitte, Levitte Programming;  Spannv. 38, I;  S-161 43  Bromma;  SWEDEN
      Tel: +46-8-26 52 47;  Cel: +46-10-222 64 05;  No fax right now
  PGP key fingerprint = A6 96 C0 34 3A 96 AA 6C  B0 D5 9A DF D2 E9 9C 65
   Check http://www.lp.se/~levitte for my public key.   bastard@bofh.se
================================================================================
Archive-Date: Tue, 27 May 1997 16:34:00 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 27 May 1997 18:33:49 EDT
From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: hardis@garnet.nist.gov
Message-ID: <009B4E54.FB8B9540.9@garnet.nist.gov>
Subject: Re: MX v5.0?

> 5.0 is right now in beta, being tested by a few.  Another feature is
> blocking of mail from senders as specified by the system manager.

How will this work?

  * Will the mail just be sent to NLA0:?
  * Will the sender get an inviting error message?
  * Will the sender get an uninviting error message?
  * Will the VAX act as if the SMTP server isn't there at all?

  - Jonathan
================================================================================
Archive-Date: Tue, 27 May 1997 16:36:48 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 27 May 1997 15:36:42 -0700
From: Matt Madison <Madison@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <970527153642.2064ec4f@Cisco.COM>
Subject: Re: MX v5.0?

>> 5.0 is right now in beta, being tested by a few.  Another feature is
>> blocking of mail from senders as specified by the system manager.
>
>How will this work?
>
>  * Will the mail just be sent to NLA0:?
>  * Will the sender get an inviting error message?
>  * Will the sender get an uninviting error message?
>  * Will the VAX act as if the SMTP server isn't there at all?

The SMTP server will simply return an error status code for the MAIL FROM:
command.  It will be up to the sending mailer to generate the return
error message.

-Matt

-- 
Matthew Madison |                                           | madison@cisco.com
Cisco Systems   | 101 Cooper St. | Santa Cruz, CA 95060 USA | +1 408 457 5390
================================================================================
Archive-Date: Tue, 27 May 1997 16:46:39 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Tue, 27 May 1997 16:46:34 -0500
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B4E45.FFE6AFB0.74@ALPHA.WKU.EDU>
Subject: Re: MX v5.0?

"Jonathan E. Hardis" <hardis@garnet.nist.gov> writes:
>
>> 5.0 is right now in beta, being tested by a few.  Another feature is
>> blocking of mail from senders as specified by the system manager.
>
>How will this work?
>
>  * Will the mail just be sent to NLA0:?
>  * Will the sender get an inviting error message?
>  * Will the sender get an uninviting error message?
>  * Will the VAX act as if the SMTP server isn't there at all?
>
The 3rd one:

	553 Programmed rejection for this source host/address.


Hunter
------
Hunter Goatley, Process Software, http://www.process.com
TCPware & MultiNet: The Best TCP/IP for OpenVMS
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Wed, 28 May 1997 09:51:50 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Wed, 28 May 1997 11:49:43 +0000
From: "Rand P. Hall" <RAND@merrimack.edu>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Subject: Re: MX v5.0?
Message-ID: <Pine.VMS.3.91-b12-vms.970528114731.1110B-100000@canyon.merrimack.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> 
> 5.0 is right now in beta, being tested by a few.  Another feature is
> blocking of mail from senders as specified by the system manager.

Hunter and Matt are starting to look real good to me, if you get my drift :-)

Happy beta testing!

Cheers,
rand

--
Rand P. Hall, Manager of Systems and Networking
Merrimack College, North Andover, MA, USA      rand@merrimack.edu

================================================================================
Archive-Date: Thu, 29 May 1997 09:17:27 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 29 May 1997 11:16:15 -0400
From: "Brian Tillman, x8425" <tillman@swdev.si.com>
Reply-To: MX-List@MadGoat.com
To: mx-list@madgoat.com
Message-ID: <009B4FAA.2FE01180.15@swdev.si.com>
Subject: Handling the Resent- headers

We have VMS Mail aliases (i.e., addresses added with SET FORWARD/USER) set up 
here to that people can send to LASTNAME_FIRSTNAME and the mail will arrive on 
whatever platform the recipient uses for Email.  For those who use cc:Mail at 
our site, the forward would look like this:

SET FORWARD/USER=DOE_JANE mx%"""<doe_jane@smtpgwy>"""

where "smtpgwy" is the name of the system running a package called "ccMail Link 
to SMTP", which is a Lotus product.

One result of this is that, assuming that Jane Doe reads her Email with cc:Mail 
on a PC, VMS Mail sent to DOE_JANE and DOE_JOHN from TILLMAN will properly 
arrive in cc:Mail, and will have a From address of tillman@swdev.si.com, To 
addresses of doe_jane@swdev.si.com and doe_john@swdev.si.com, and Bcc to Jane 
Doe (the latter is Jane's cc:Mail address) in Jane's mail and a Bcc to John Doe 
in John's mail, which I can understand.  It is the Bcc addresses by which the 
mail is delivered. There is no actual BCC header in the RFC822 headers or the 
incoming message.

If Jane then replies, choosing the "Reply to sender and all recipients", the 
message actually gets sent to tillman@swdev.si.com, doe_jane@swdev.si.com, and 
doe_john@swdev.si.com.  The messages go back to the VMS system, where MX 
delivers locally to TILLMAN, and reforwards to DOE_JANE and DOE_JOHN, adding 
Resent-Date, Resent-From, and Resent-To headers.  The result is that when John 
receive's Jane's reply, it appears to come from doe_john@swdev.si.com, because 
Lotus has elected to use the Resent-From header instead of the (correctly 
addressed) From and Reply-To headers.

Now, the RFC does not dictate how an SMTP mailer is supposed to interpret the 
Resent headers, so Lotus is certainly implementing one correct interpretation.
Were I to have written it, however, I would have done it differently.

All of this leads to me question: can I get MX to leave those Resent headers 
off?  I know about SET LOCAL/HEADERS of course, and since doe_jane@swdev.si.com 
and doe_john@swdev.si.com look like local deliveries to the router (or so it 
would seem to me), I suspected that eliminating them would work.  I added the 
following command to the configuration file:

SET LOCAL/RETRY_INTERVAL="   0 00:10:00.00" -
  /CC_POSTMASTER /MAXIMUM_RETRIES=144 -
  /HEADERS=(TOP=NOALL, BOTTOM=(ALL,NORESENT_BCC,NORESENT_DATE,NORESENT_FROM, -
                                   NORESENT_MESSAGE_ID,NORESENT_REPLY_TO, -
                                   NORESENT_SENDER,NORESENT_TO))

and then reset all agents.  I then tried a test and when the message arrived at 
cc:Mail, the Resent headers were there still.

Did I specify something wrong?
--
 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 4141 Eastern Ave., MS239        Addresses modified to prevent
 Grand Rapids, MI 49518-8727     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company
================================================================================
Archive-Date: Thu, 29 May 1997 09:38:58 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 29 May 1997 09:38:53 -0500
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: TILLMAN@SWDEV.SI.COM
Message-ID: <009B4F9C.959646B1.26@ALPHA.WKU.EDU>
Subject: RE: Handling the Resent- headers

"Brian Tillman, x8425" <tillman@swdev.si.com> writes:
>
>All of this leads to me question: can I get MX to leave those Resent headers 
>off?

The best way to do this is with the ADDRESS_REWRITER (use the sample
one in ftp.madgoat.com in [.MX.EXAMPLES]ADDRESS_REWRITER.ZIP).

WKU uses the address rewriter to do the same thing you're trying to do
(redirect mail to a cc:Mail SMTP gateway).  Because the address
rewriter intercepts messages in MX Router and rewrites the envelope
address, no Resent-* headers are ever added.

The sample is written in BLISS, but should be easy to implement for
all sites.  You can also use it as a template for writing your own
rewriter in whatever compiled language you want.

Hunter
------
Hunter Goatley, Process Software, http://www.process.com
TCPware & MultiNet: The Best TCP/IP for OpenVMS
<goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html
================================================================================
Archive-Date: Thu, 29 May 1997 20:42:06 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Thu, 29 May 1997 19:41:51 -0700
From: "Henry W. Miller" <henrym@sacto.mp.usbr.gov>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
CC: henrym@sacto.mp.usbr.gov
Message-ID: <009B4FF0.D19DFF78.19@sacto.mp.usbr.gov>
Subject: RE: Handling the Resent- headers

> From:	MX%"MX-List@MadGoat.com" 29-MAY-1997 09:00:32.62
> Subj:	RE: Handling the Resent- headers

> "Brian Tillman, x8425" <tillman@swdev.si.com> writes:
> >
> >All of this leads to me question: can I get MX to leave those Resent headers 
> >off?
> 
> The best way to do this is with the ADDRESS_REWRITER (use the sample
> one in ftp.madgoat.com in [.MX.EXAMPLES]ADDRESS_REWRITER.ZIP).
> 
> WKU uses the address rewriter to do the same thing you're trying to do
> (redirect mail to a cc:Mail SMTP gateway).  Because the address
> rewriter intercepts messages in MX Router and rewrites the envelope
> address, no Resent-* headers are ever added.
> 

	We've got a similar set of rewrite rules in place here in the MP 
region of USBR, to get the addresses into the gawdawful format that some 
headquarter's "genius" decided that they should be in.

> The sample is written in BLISS, but should be easy to implement for
> all sites.  You can also use it as a template for writing your own
> rewriter in whatever compiled language you want.
> 

	I should add that since the BLISS compiler is now freely 
available, use it!  BLISS is not that scary - it's pretty close to "C" 
and the other ALGOL class languages.  Two major distictions:

1)	No GOTO statement, or the like.

2)	No native I/O facility - you define the I/O to use the native 
I/O of your operating system via macros.

> Hunter
> ------
> Hunter Goatley, Process Software, http://www.process.com
> TCPware & MultiNet: The Best TCP/IP for OpenVMS
> <goathunter@MadGoat.com>     http://www.madgoat.com/hunter.html


-HWM
================================================================================
Archive-Date: Sat, 31 May 1997 23:01:58 -0500
Sender: <owner-MX-List@MadGoat.com>
Date: Sun, 1 Jun 1997 00:01:38 -0500
From: Hunter Goatley <goathunter@MadGoat.com>
Reply-To: MX-List@MadGoat.com
To: MX-List@MadGoat.com
Message-ID: <009B51A7.70F1ED5D.29@wku.edu>
Subject: MX-LIST Administrivia: Monthly Post

Posting statistics for list MX-LIST during May 1997

Total number of posts:                  80
Total number of posters:                35
Total number of subscribers:             0

Last modified: 28-SEP-1995 13:33 (Updated digest info)

Welcome  to  MX-List@LISTS.WKU.EDU,  an electronic mailing list established
for the discussion of the Message Exchange mail software.

This is a routine posting you will see from time to time on MX-List.

MX-List postings are also available in a daily digest format.  To subscribe
to the digest, send the following command in the body  of a mail message to
MXserver@LISTS.WKU.EDU:  SUBSCRIBE MX-List-Digest "Your real name here"

The  MX-List  archives  are maintained at ARCHIVES@LISTS.WKU.EDU.  To get a
copy of any month's postings, send an e-mail message  with  the  body  SEND
MX-List.yyyy-mm  to  ARCHIVES@LISTS.WKU.EDU,  where  "yyyy" is the year and
"mm" is the numeric representation of the month.  For example, the  message
SENDME MX-List.1992-04 will send the archives for April 1992.

MX itself is available via anonymous ftp from ftp.spc.edu in [.MX.MX041].
You can also get it via e-mail by sending the commands SEND MX and SEND
FILESERV_TOOLS on separate lines in the body of a mail message to
FILESERV@LISTS.WKU.EDU.

To  remove  yourself  from  the mailing list, send the following command to
MXserver@LISTS.WKU.EDU:

  SIGNOFF MX-List

MXserver supports a few other commands for your convenience.  The following
commands can be handled automatically by the list processor:

 SIGNOFF MX-List       - to remove yourself from the list
 REVIEW MX-List        - to get a list of subscribers
 QUERY MX-List         - to get the status of your entry on the list
 SET MX-List DIGEST    - to switch to digest mode
 SET MX-List NODIGEST  - to switch to non-digest mode
 SET MX-List NOMAIL    - to remain on the list but not receive mail
 SET MX-List MAIL      - to resume receiving mail from the list
 SET MX-List CONCEAL   - to not report your address in a REVIEW
 SET MX-List NOCONCEAL - to report your address in a REVIEW
 SET MX-List REPRO     - to receive posts you make to MX-List
 SET MX-List NOREPRO   - to not receive posts you make to MX-List
 LIST                   - to get a list of mailing lists served by WKU
 HELP                   - to receive a help file

By default, subscriptions are set to MAIL, REPRO, NOCONCEAL.

If  you have any questions, comments, or suggestions about MX-List, please
contact the list owner at the address below.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Hunter Goatley, Sr. OpenVMS Systems Programmer	       goathunter@MadGoat.com
Process Software
P.O. Box 51745
Bowling Green, KY 42102-6745
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-