From:	MERC::"uunet!WKUVX1.BITNET!list-mgr" 11-JAN-1993 15:49:19.30
To:	MX-List@WKUVX1.BITNET
CC:	
Subj:	Re: Also need rewrite rules help

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