HDTenEightyP/NetNews huggingface dataset:
From: churchwell@vms.ocom.okstate.edu (Kimberly B. Churchwell)
Subject: testing, ignore please
Organization: OSU College of Osteopathic Medicine
Date: Mon, 4 Jan 1993 19:00:37 GMT

Just testing.
-- 
Kimberly B. Churchwell, Prog./Analyst, Okla. State U.  | TANSTAAFL, but
Osteopathic College--churchwell@vms.ocom.okstate.edu   | even so, I never
BIX--kchurchwell  AOL--KChurchwel  CIS--72170,1552     | quit hoping.
From: dierker@tweety.digsys.com
Newsgroups: vmsnet.test
Subject: Test
Date: 7 Jan 93 22:25:40 CST
Organization: DSC: Digital Systems Consultants, INC.

Testing, testing, 1.2.3. Are we on the air now?
From: kschwab@wrdis01.af.mil (Kerry Schwab 653CCSG/SCLCP)
Newsgroups: vmsnet.test
Subject: Test
Date: 8 Jan 93 16:24:29 GMT
Organization: 1926CCSG Robins AFB

checking the From: address.

--
Sgt. Kerry R. Schwab
From: sys_hjk@LIFRA.LIF.DE (Hans-Joachim Koch)
Newsgroups: vmsnet.mail.mx
Subject: Looking for rewriting rules
Date: 9 Jan 93 15:27:34 GMT
Reply-To: koch@lifra.lif.de
Organization: Lahmeyer International GmbH, Frankfurt/Main, Germany

Hello,

can someone please give me a hint where I can find the rules for address 
rewriting (for MX of course).

I have no problems to rewrite simple adresses, but now I have a rather 
complicated one. Our VAX routes all mail to a SUN. Problems arises, when 
I send some mail to *.uucp. The SUN tries to transfer the mail with uucp 
(nothing is set up for that purpose), rather than sending it via our 
ISDN link to the EUnet mail server. I know, we should fix it in the SUN 
routing, but didn't succeed until know.

I thought I could fix it with a rewrite rule in MX.

Address: hamcall.ampr.org!hamcall@uucphost.uucp (strange!)
It works, when I send to: 
hamcall.ampr.org!hamcall%uucphost.uucp@germany.eu.net

How can I deal with this situation? Is there a multitoken variable, like
{everything@uucphost.uucp}->{everything%uucphost.uucp@germany.eu.net},
because I never know the number of tokens of the first part...

Hans.
-- 
Hans-Joachim Koch, Computer department of Lahmeyer International
Lyoner Strasse 22, POB 71 06 51, D-6000 Frankfurt (Main) 71, Germany
Phone: +49 69 6677-642, Fax: +49 69 6677-571, Tx: 413478 li d
EUnet: koch@lifra.lif.de, AMPRnet: dk9om@db0lj.ampr.org
From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
Newsgroups: vmsnet.mail.mx
Subject: RE: Looking for rewriting rules
Date: 10 Jan 1993 19:59:47 -0500 (EST)
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

> can someone please give me a hint where I can find the rules for address
> rewriting (for MX of course).

The Message Exchange Management Guide, edition of March 1992, for MX V3.1,
page 3-1.

> How can I deal with this situation? Is there a multitoken variable, like
> {everything@uucphost.uucp}->{everything%uucphost.uucp@germany.eu.net},
> because I never know the number of tokens of the first part...

To quote from the above reference, "the rule processor treats the addresses
as ordinary text strings and does not understand the syntax of RFC 821
addresses."  In other words, don't worry about tokenizing.

MCP> DEFINE REWRITE_RULE "<{u}@{h}.uucp>" "<{u}%{h}.uucp@germany.eu.net>"
MCP> SAVE
MCP> RESET

More to the point, why fool with rewrite rules?

MCP> DEFINE PATH *.UUCP    SMTP/ROUTE="germany.eu.net"
                           ^^^^-or different, as appropriate

(Remember that the order of the DEFINE commands is important; you may have
to edit CONFIG.MCP and start over.)
From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
Newsgroups: vmsnet.mail.mx
Subject: RE: Name resolution
Date: 10 Jan 1993 21:26:26 -0500 (EST)
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

> I'm a newcomer, and have just installed MX 3.1c  over CMUIP 6.6. Name
> completion for outgoing smtp isn't working; what am I doing wrong?

MX refers to what you want as "host name expansion."  It happens "just
before PATH identification."  So, if this step failed, you shouldn't be
surprised if the mail was sent to the literal address, rather than to the
expanded address.

Do you have the following logical defined:

(LNM$SYSTEM_TABLE)

  "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION"

And is that file present?

I rather suspect that there's nothing wrong with C**/T** (formerly CMU/TEK)
TCP/IP, since IPNCP works alright.  All I can tell you is that version
6.6-4 of IP_ACP and MX 3.1c do correctly expand addresses on my system, and
I didn't have to do anything special to make it happen.

A difference between my system and yours, though, is that your addresses
apparently only have MX records on the nameserver, not A records.  So, the
search to see which addresses are "valid" might not work.
From: pat@che.phys.Virginia.EDU
Newsgroups: vmsnet.mail.mx
Subject: "opcode reserved to DIGITAL fault" still killing SMTP
Date: Fri, 08 Jan 1993 10:59:09 EST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

A few days ago I wrote (in part):

>Now I have a new question:  my SMTP process is dying on me as soon as I try
>to SEND.  The appropriate *.HDR_INFO, *.MSG_TEXT, *.SRC_INFO and *.SMTP_INFO
>files are being created in the (now correctly-defined) FLQ_DIR directory,
>but they all end up stranded there because SMTP has died.  The VMS accounting
>utility tells me that SMTP is dying with status code 1000043C,

>%SYSTEM-F-OPCDEC, opcode reserved to DIGITAL fault at PC=!XL

>Does this ring a bell with anyone?  A bug in MX 3.1 (i.e., "Try 3.1C, dummy!),
>or am I still doing something wrong?

>(A review of my MX environment:  7-node Vaxcluster, all nodes running VMS 5.5
> and CMU-TEK 6.6-5.  MX 2.0 currently running successfully on all nodes with
> the exception of occasional failures to deliver, particularly to CERN in
> Europe (addresses ending in .CH).  ROUTER, LOCAL and MLF run on 3 of the
> 7 nodes; SMTP runs on these 3 plus 1 other node, and all 7 nodes run
> SMTP Server.)

Well, I've just tried reinstalling MX 3.1 from scratch, creating a new
CONFIG.MCP, etc., and I'm getting the same "opcode reserved to DIGITAL fault"
error.  Any ideas?  Any more information I can supply?  Thanks.

- Patrick Walsh
  University of Virginia Department of Physics
  pw@virginia.bitnet, pw@virginia.edu, pat@gomez.phys.virginia.edu
Newsgroups: vmsnet.mail.mx
From: madison@tgv.com (Matt Madison)
Subject: Re: mx supports which tcp/ip packages?
Reply-To: madison@tgv.com
Organization: The Foundation for Dinner Peas
Date: Fri, 8 Jan 1993 18:31:07 GMT

In article <1993Jan8.073208.369@condor.navsses.navy.mil>, system@condor.navsses.navy.mil writes:
>What tcp/ip packages does the current version of MX support?

    CMU-Tek V6.4 and later
    DEC VMS/ULTRIX Connection V1.2 and later 
       (as of V2.0 called TCP/IP Services for VMS)
    TGV MultiNet V2.2 and later
    Process Software TCPware (no known version restrictions)

-Matt
--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
From: Hunter Goatley <goathunter@WKUVX1.BITNET>
Newsgroups: vmsnet.mail.mx
Subject: RE: "opcode reserved to DIGITAL fault" still killing SMTP
Date: Fri, 08 Jan 1993 10:20:35 CST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

pat@che.phys.Virginia.EDU writes:
>
>A few days ago I wrote (in part):
>
>>Now I have a new question:  my SMTP process is dying on me as soon as I try
>>to SEND.  The appropriate *.HDR_INFO, *.MSG_TEXT, *.SRC_INFO and *.SMTP_INFO
[....]
>Well, I've just tried reinstalling MX 3.1 from scratch, creating a new
>CONFIG.MCP, etc., and I'm getting the same "opcode reserved to DIGITAL fault"
>error.  Any ideas?  Any more information I can supply?  Thanks.
>
The first thing to do, if you haven't already, is to turn on SMTP
debugging by defining the following logical:

        $ define/sys/exec mx_smtp_debug true

That'll create log files in MX_SMTP_DIR: that might help provide more
info.

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251
From: Hunter Goatley <goathunter@WKUVX1.BITNET>
Newsgroups: vmsnet.mail.mx
Subject: RE: "opcode reserved to DIGITAL fault" still killing SMTP
Date: Fri, 08 Jan 1993 10:18:51 CST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

From:   MX%"MX-List@WKUVX1.BITNET"  8-JAN-1993 10:12:10.76
To:     GOATHUNTER
CC:
Subj:   "opcode reserved to DIGITAL fault" still killing SMTP

Return-Path: <list-mgr@WKUVX1.BITNET>
Received: from WKUVX1 (WKUVX1::MXMAILER) by HUNTER (MX V3.1C) with SMTP
          (DECnet); Fri, 08 Jan 1993 10:12:06 CST
Errors-To: list-mgr@WKUVX1.BITNET
X-ListName: Message Exchange Discussion List <MX-List@WKUVX1.BITNET>
Received: from watson.acc.Virginia.EDU (MAILER) by WKUVX1 (MX V3.1C) with
          BSMTP; Fri, 08 Jan 1993 10:07:32 CST
Received: from WATSON by watson.acc.Virginia.EDU (Mailer R2.07) with BSMTP id
          3389; Fri, 08 Jan 93 11:01:30 EST
Received: from Virginia.EDU by WATSON.ACC.VIRGINIA.EDU (IBM VM SMTP V2R1) with
          TCP; Fri, 08 Jan 93 11:01:29 EST
Received: from che.phys.virginia.edu by uvaarpa.Virginia.EDU id aa27979; 8 Jan
          93 10:59 EST
Date: Fri, 08 Jan 1993 10:59:09 EST
From: pat@che.phys.Virginia.EDU
Reply-To: MX-List@WKUVX1.BITNET
To: mx-list@WKUVX1.BITNET
CC: pat@gomez.phys.Virginia.EDU
Subject: "opcode reserved to DIGITAL fault" still killing SMTP

A few days ago I wrote (in part):

>Now I have a new question:  my SMTP process is dying on me as soon as I try
>to SEND.  The appropriate *.HDR_INFO, *.MSG_TEXT, *.SRC_INFO and *.SMTP_INFO
>files are being created in the (now correctly-defined) FLQ_DIR directory,
>but they all end up stranded there because SMTP has died.  The VMS accounting
>utility tells me that SMTP is dying with status code 1000043C,

>%SYSTEM-F-OPCDEC, opcode reserved to DIGITAL fault at PC=!XL

>Does this ring a bell with anyone?  A bug in MX 3.1 (i.e., "Try 3.1C, dummy!),
>or am I still doing something wrong?

>(A review of my MX environment:  7-node Vaxcluster, all nodes running VMS 5.5
> and CMU-TEK 6.6-5.  MX 2.0 currently running successfully on all nodes with
> the exception of occasional failures to deliver, particularly to CERN in
> Europe (addresses ending in .CH).  ROUTER, LOCAL and MLF run on 3 of the
> 7 nodes; SMTP runs on these 3 plus 1 other node, and all 7 nodes run
> SMTP Server.)

Well, I've just tried reinstalling MX 3.1 from scratch, creating a new
CONFIG.MCP, etc., and I'm getting the same "opcode reserved to DIGITAL fault"
error.  Any ideas?  Any more information I can supply?  Thanks.

- Patrick Walsh
  University of Virginia Department of Physics
  pw@virginia.bitnet, pw@virginia.edu, pat@gomez.phys.virginia.edu
From: ake@dayton.saic.com (Earle Ake)
Newsgroups: vmsnet.mail.mx
Subject: Re: MX and Disk Space Quota
Date: 5 Jan 1993 17:18:08 -0500
Organization: Science Applications Intl Corp - Dayton, Ohio
NNTP-Posting-Host: dayton.saic.com
X-Newsreader: TIN [version 1.1 PL8]

wbradford@UDCVAX.BITNET wrote:

: DEC's solution: Remove EXQUOTA and SETPRV from the user id that is sending
:                the mail message.

:  The problem with DEC's solution is that our MX Mailer account is setup with
: EXQUOTA privileges.

: Our software configuration is: VMS V5.4-3, JNET V3.5 and MX V3.1

: My questions:

:  1) Has any seen or heard of this problem before?
:  2) Can we remove the EXQUOTA privilege from our MX mailer account without
:    any problems to MX?

	I don't think you can remove the SETPRV quota.  You could probably
remove the EXQUOTA as long as you give the mailer account plenty of
quota!


-Earle
-- 
Earle Ake  Internet: <ake@dayton.saic.com>  NSI-DECnet (SPAN): 28276::ake
From: system@condor.navsses.navy.mil
Newsgroups: vmsnet.mail.mx
Subject: mx supports which tcp/ip packages?
Date: 8 Jan 93 12:32:08 GMT
Organization: NSWCCD, Naval Ship Systems Eng Sta, Phila PA

What tcp/ip packages does the current version of MX support?

-- 
Mike Jacobi
NAVSSES VAXCluster system manager
System@Eagle.Navsses.Navy.Mil
System@Condor.Navsses.Navy.Mil

Disclaimer - I speak for myself.  No-one else.
From: VAX SYSTEM MANAGER - 0224-318611 x2111
      <SYSTEM@MACAULAY-LAND-USE.SCOT-AGRIC-RES-INST.AC.UK>
Newsgroups: vmsnet.mail.mx
Subject: MX HHELP CONFIG.
Date: Thu, 7 Jan 93  17:15 GMT
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List


  Hello,


       I would be grateful if you could answer the following questions
  relating to MX as this product is a new one on me.

  I can send mail from VAX - SUN and vice-versa using MX
  I can set incomming mail to VAX to forward to any SUN workstation

  Q. What will MX offer me in terms of facilities over and above the above
     mentioned ?. Will it allow me to use SMTP over X25

     i.e MX%"SYSTEM@UK.AC....ETC"

     I really need to send mail from SUN route through the VAX to the
     outside world. Does MX offer this routing capability ?

  Q. I am unclear when running the configuration program when configuring
     for using MX over X25 what is the exact requirement in terms of ROUTER
     node spec and REMOTE user spec. I think this is where I am going wrong
     because I get unknown user and unknown node error messages when sending
     mail using MX. (would it be possible to have a look at an example CONFIG
     file) ?




     Many thanks


      Tony Sunman
From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
Newsgroups: vmsnet.mail.mx
Subject: RE: Reverse rewrite rules??
Date: 10 Jan 1993 19:00:24 -0500 (EST)
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

> The situation is this: I have defined a rewrite rule to establish a PSI
> gateway so that addresses of the format J.Bloggs@12345678.psigate... are
> translated to psi%12345678::J.Bloggs. This works wonderfully well except the
> recipients see 'psi%12345678::J.Bloggs'@psigate... which some mailers don't
> like. The idea is to translate the From address back to
> J.Bloggs@12345678.psigate... which is generally acceptable so people can do
> replies.

I don't understand -- is J.Bloggs the sender or the recipient of the
message?

In any event, I think you can do what you want to do with a SITE agent.
With the understanding that I know nothing about PSI gateways, if you
explain again what you want to do I can show you how the SITE command file
can call the editor to fiddle what you want to fiddle.

  - Jonathan
Newsgroups: vmsnet.mail.mx
Subject: Reverse rewrite rules??
From: wykesn@fri.cri.nz (Nick Wykes, Forestry Corporation of New Zealand)
Date: 11 Jan 93 11:24:45 +1300
Organization: New Zealand Forest Research Institute

Hi all

Just a quick question on rewrite rules. Are they designed to work in reverse?
That is, am I able to rewrite outgoing addresses so the recipients get a
globally acceptable From: address?

The situation is this: I have defined a rewrite rule to establish a PSI
gateway so that addresses of the format J.Bloggs@12345678.psigate... are
translated to psi%12345678::J.Bloggs. This works wonderfully well except the
recipients see 'psi%12345678::J.Bloggs'@psigate... which some mailers don't
like. The idea is to translate the From address back to 
J.Bloggs@12345678.psigate... which is generally acceptable so people can do
replies.

Any thoughts?

Cheers
Nick Wykes
N.Wykes@fcnz.co.nz
From: hardis@garnet.nist.gov (Jonathan E. Hardis)
Newsgroups: vmsnet.mail.mx
Subject: RE: what is mx ?
Date: 11 Jan 93 00:15:07 GMT
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

> Can somebody tell me what is MX ( well I know it does SMTP on a VAX ). Or
> my question should be: I have UCX 2.0, what would MX do for me that UCX
> does not provide ? Or is there a FAQ ?

In the words of its author:

Message Exchange V3.1

Message Exchange (MX) is electronic mail distribution and routing software
for VMS V5.0 or later.  It supports Internet mail over TCP/IP using CMU-Tek,
DEC VMS/ULTRIX Connection, TGV MultiNet, and Process Software Corporation's
TCPware, as well as SMTP over DECnet and X.25; BITNET mail over Jnet; also
interfaces with DECUS UUCP.

MX uses VMS Mail for local message entry and delivery, and includes support
for mailing lists and mail-based file servers.  Support is included for
interfacing MX with a custom mail transport and for providing custom address
handling routines.

V3.1 includes the following new features over previous releases:

    * SMTP over X.25 is now supported, using VAX P.S.I.
    * The Jnet interface no long requires a special account to run.
    * Mailing list processor supports NOCASE, CONCEAL, and NOREPRO flags
      for subscriber entries.
    * A NAME_CONVERSION module is included in the examples save set that
      handles address conversions for both DECnet and MRGATE users.
    * MX processes now log their startups and exits to log files, and
      will also log to an operator class, if desired.
    * New STATUS command added to MCP that lists all running MX processes.
    * Several other minor improvements and bug fixes.

MX V3.1, including installation kit, docs, and sources, is available via
anonymous FTP on ftp.spc.edu, in directory [.MX].

If you do not have FTP access, you can obtain MX by requesting it via
E-mail.  Send the following commands in the body of a mail message to
MXSERVER@WKUVX1.BITNET:

SEND MX031
SEND FILESERV_TOOLS

It's a huge package and, because of BITNET delays, make take a few
days for all the pieces to arrive.
From: byrnee@woods.ulowell.edu
Newsgroups: vmsnet.mail.mx
Subject: Mailworks/MRGATE and nasty quotes
Date: 5 Jan 93 19:57:14 GMT
Organization: University of Lowell

We are about to switch our users from VAXmail to Mailworks.  Users groaned
a lot when they had to address VAXmail to MX:
        
          MX%"user@node.blah.edu"

You can image the groans we'll hear when under Mailworks/Message Router
they will have to enter:

        "MX%""user@node.blah.edu"""@MRGATE

Has anyone out there in MX land figured out a simpler way to address?  I
just can't find any way around those quotes. 

Eileen
From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
Newsgroups: vmsnet.mail.mx
Subject: RE: Also need rewrite rules help
Date: 10 Jan 1993 19:40:38 -0500 (EST)
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

I want to re-route all incoming Internet mail through MRGATE to users'
Mailworks accounts. (The mailbox in MRGATE is "AM")

To do this from VAXmail I would type:

TO: mx%"'MRGATE::AM::username'@nodex.ulowell.edu"

> What rewrite rule would essentially translate:
>
> username@nodex.ulowell.edu    to    'MRGATE::AM::username'@nodex.ulowell.edu ?
>
> I have tried every combination I can think of, but nothing works.

Have you tried:

MCP> DEFINE REWRITE_RULE "<{u}@nodex.ulowell.edu>" -
_MCP>                            "<""MRGATE::AM::{u}""@nodex.ulowell.edu>"
MCP> SAVE
MCP> RESET
Newsgroups: vmsnet.mail.mx
From: madison@tgv.com (Matt Madison)
Subject: Re: Also need rewrite rules help
Reply-To: madison@tgv.com
Organization: The Foundation for Dinner Peas
Date: Mon, 11 Jan 1993 17:48:48 GMT

In article <1993Jan10.170816.1@woods.ulowell.edu>, byrnee@woods.ulowell.edu writes:
>To do this from VAXmail I would type:
>
>TO: mx%"'MRGATE::AM::username'@nodex.ulowell.edu"
>
>What rewrite rule would essentially translate:
>
>username@nodex.ulowell.edu    to    'MRGATE::AM::username'@nodex.ulowell.edu ?
>
>I have tried every combination I can think of, but nothing works.  I would
>like to avoid the obvious, which is setting all VAXmail accounts to Mailworks.
>(NOT a pretty solution for 13,000 accounts!)

What I would suggest is to set up a new domain name - call it something
like mrgate.nodex.ulowell.edu or something like that - with an MX record
pointing to nodex.  That makes the rewrite simple:

    "<{user}@mrgate.nodex.ulowell.edu>" ->
    "<""MRGATE::AM::{user}""@nodex.ulowell.edu>"

If you have MX V3.1C, you could also use the improved name_conversion interface
in that version that lets you rewrite an entire address, so your users'
return addresses would look cleaner.  A bit of coding would be required,
though.

If you didn't want to add the extra record in the DNS, you should still be
able to work it with the following pair of rewrite rules:

    "<""MRGATE::{anything}""@nodex.ulowell.edu>" ->
    "<""MRGATE::{anything}""@nodex.ulowell.edu>"

and

    "<{user}@nodex.ulowell.edu>" -> "<""MRGATE::AM::{user}@nodex.ulowell.edu>"

The first rewrite rule, which does nothing to the address, prevents the
gatewayed addresses from getting rewritten any further.

Using the extra DNS host name has the added advantage that users could then
choose whether they wanted to use VMS Mail or MAILworks.

-Matt
--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
Newsgroups: vmsnet.mail.mx
From: byrnee@woods.ulowell.edu
Subject: Also need rewrite rules help
Organization: University of Lowell
Date: Sun, 10 Jan 1993 22:08:16 GMT

I also need help with re-write rules.

I applied the [mx.examples]name_conversion module and defined the re-write
rules as indicated in the 00README.NAME_CONVERSION instructions, but am 
having no luck.

I want to re-route all incoming Internet mail through MRGATE to users'
Mailworks accounts. (The mailbox in MRGATE is "AM")

To do this from VAXmail I would type:

TO: mx%"'MRGATE::AM::username'@nodex.ulowell.edu"

What rewrite rule would essentially translate:

username@nodex.ulowell.edu    to    'MRGATE::AM::username'@nodex.ulowell.edu ?

I have tried every combination I can think of, but nothing works.  I would
like to avoid the obvious, which is setting all VAXmail accounts to Mailworks.
(NOT a pretty solution for 13,000 accounts!)

Thanks,

Eileen Byrne
From: martineau@MacMartineau.ccr.hydro.qc.ca (Alain Martineau)
Subject: what is mx ?
Followup-To: vmsnet.mail.mx
Organization: Hydro Quebec
Date: Sat, 9 Jan 1993 15:51:10 GMT

Can somebody tell me what is MX ( well I know it does SMTP on a VAX ). Or
my question should be: I have UCX 2.0, what would MX do for me that UCX
does not provide ? Or is there a FAQ ?

Alain Martineau
Hydro Quebec
martineau@macmartineau.ccr.hydro.qc.ca
From: wbradford@UDCVAX.BITNET
Newsgroups: vmsnet.mail.mx
Subject: MX and Disk Space Quota
Date: Tue, 05 Jan 1993 15:38:57 EST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List


 We have run into a strange problem that may be linked to MX.

 We recently noticed that some user accounts on our system have exceeded
disk quota storage with mainly mail messages.

 For example:

A user is given a permanent disk quota of 5000 blocks and 100 blocks
overdraft, but, that user has 28000 blocks tied up with mostly .MAI files.

 After contacting our software support at DEC, it was confirmed that this is
due to a change in DEC's VMS and VMS MAIL software. As a result, any user,
who has EXQUOTA or SETPRV privileges, can send a mail message and that mail
message would go into the target user's mail file whether they had the spare
disk space or not. DEC is still researching to find out when this change came
about. We have had JNET running on our system for several years and have never
seen this problem before. As for MX, we are coming up on our first year of
running it.

DEC's solution: Remove EXQUOTA and SETPRV from the user id that is sending
               the mail message.

 The problem with DEC's solution is that our MX Mailer account is setup with
EXQUOTA privileges.

Our software configuration is: VMS V5.4-3, JNET V3.5 and MX V3.1

My questions:

 1) Has any seen or heard of this problem before?
 2) Can we remove the EXQUOTA privilege from our MX mailer account without
   any problems to MX?


 Any suggestions would be appreciated. Thank you.

                                       William Bradford
                                       WBRADFOR@UDCVAX.BITNET