[376] in Moira

home help back first fref pref prev next nref lref last post

Re: Venezuela Mailing List

daemon@ATHENA.MIT.EDU (Ron M. Hoffmann)
Fri Apr 3 11:57:31 1992

Date: Fri, 03 Apr 92 11:55:00 EST
From: hoffmann@MIT.EDU (Ron M. Hoffmann)
To: herrera@Athena.MIT.EDU
Cc: postmaster@Athena.MIT.EDU, venezuela-request@Athena.MIT.EDU,

> From: herrera@Athena.MIT.EDU
> Subject: Venezuela Mailing List
> Date: Fri, 03 Apr 92 10:28:11 EST
> 
> The one thing that may have caused this is that we had just added
> full names in parentheses, in addition to e-mail addresses.
> I wonder if now the list is too long.
> 
Moira does not properly support the inclusion of personal
names along with string email addresses.  If you want to
do things in the supported manner, you need to get rid of
the appended names.

> I'd like to take this opportunity give you some feedback about other
> problems that we have had, similar to the current one.  The mailing list
> gets locked if there's an address "user@athena.mit.edu" and that account
> is removed.  We have been implementing the workaround and don't use
> fully qualified addresses for athena users.

The only correct way to include local Athena users in mailing lists
is to enter them as USERs, not STRINGs.  This guarantees that Moira
will be able to remove them from the mailing list when their accounts
are removed.  In the next release of Athena, Moira will be more picky
about preventing list maintainers from getting into trouble from
poorly formatted list entries.

  Another address that brought
> the list to a halt was:
> 
>         @gnv.ifas.ufl.edu:JMA@lal
> 
> We don't have any workarounds (or want to investigate them) for that.
> Fortunately the user has a new address.  Which brings me to the
> point: is there any way to investigate whether a given 'blanche'
> (moira?) list will be accepted that night by 'expn'?
>
Moira should support that form of address as it is legal in
RFC822.  We'll investigate what the problem might be.
 
> One more thing.  We just received a request from our first x.400
> user and we don't know what to do with him. The last time we tried to
> include a name with slashes:
> 
>         Bravo_Pedro/HP6650_11@hpesf.cup.hp.com
> 
> we had some problems.  This is the new user's address:
> 
>         /PN=RODOLFO.M.GUZMAN/O=ADLITTLE/ADMD=TELEMAIL/C=US/@sprint.com
> 
"/" is currently disallowed to prevent the execution of unix
programs by the mailer.  We'll have to figure out a way to
include X.400 addresses while preserving the security of the
email system.

Thanks for your comments.

-Ron Hoffmann
 <postmaster@mit.edu>

home help back first fref pref prev next nref lref last post