[Info-vax] %MAIL-E-INVITMLEN ?

[Phillip Helbig---undress to reply]

In article <jitpee$2fh$1 at online.de>, helbig at astro.multiCLOTHESvax.de
(Phillip Helbig---undress to reply) writes: 

> > No. On the version of TCP/IP you are running, you can create a file
> > called {username}.dis in the SMTP system directory containing a list of
> > email addresses a incoming email should be forwarded to when {username}
> > is sent a email. As of V5.6 ECO 5, this works just fine as I have it
> > in production use.

The directory in question is TCPIP$SMTP_COMMON.  The default definition 
is SYS$SPECIFIC:[TCPIP$SMTP].  I have defined this as a search list with 
the default definition as the first definition and a second definition 
on a non-system disk, so that one has just one directory for the entire 
cluster.

>    o  You can have an empty file, which results in an SMTP black hole
>       with no unpleasant side effects.

Useful if spam is sent to a non-existing address which (on older 
versions of TCPIP) cannot be rejected by the SMTP symbiont; just forward 
this address to the local list.

>    o  You can have local and remote names.

Useful if one wants to be able to view email both locally and remotely, 
either permanently or temporarily.  

>    o  In contrast to the VMS-MAIL forward, this will pass the SMTP 
>       message through as-as, i.e. all headers at the top, whereas the
>       VMS-MAIL forward will respect your configuration.  I like HEADERS
>       so that I can page through messages and just see the basic 
>       VMS-MAIL headers, but for relaying I want the SMTP headers to be
>       all at the top so that the receiving system processes them 
>       properly.

I use this for redistributing posts to a moderated newsgroup.

>    o  Such a list can be the goal of a VMS-MAIL SET FORWARD command, 
>       either done by the user or done by the system manager with
>       MAIL> SET FORWARD/USER=FOO BAR at nodename .

For "goal" read "target".  I like the SET FORWARD/USER=FOO <address>
stuff.  The @nodename is needed only if BAR is a list in
TCPIP$SMTP_COMMON.  Otherwise, it can be a username, an external email 
address or whatever.  Also, FOO doesn't have to be a username on the 
system; it doesn't even have to be a syntactically valid VMS username.
I often use this for times when I have to enter an email address but 
might not want to enter my "real" email address.  For example.  I can 
then enter FOO and use the command to forward it to wherever I want: my 
username, a list as discussed above or to an empty list if it starts 
getting spam and no longer any useful emails.