[comp.unix.admin] "Authorization" in MMDF ?

chap@art-sy.detroit.mi.us (j chapman flack) (05/19/91)

Please forgive the crossposting--there are probably groups more appropriate
that I didn't include because art-sy doesn't get them.

SCO Open Desktop (SysV/386 3.2) includes the MMDF mailer.  The man page for
the mmdftailor file mentions syntax for some "authorization" feature(s),
but with no explanation.  I'm guessing I might be able to restrict who
can mail to a list-outgoing address, or to certain aliased pipes, etc.
Whatever it is, it could well be useful to me.

Where can I find documentation?  SCO doesn't provide the MMDF source.

Thanks!
-- 
Chap Flack                         Their tanks will rust.  Our songs will last.
chap@art-sy.detroit.mi.us                                    -MIKHS 0EODWPAKHS

Nothing I say represents Appropriate Roles for Technology unless I say it does.

john@sco.COM (John R. MacMillan) (05/22/91)

|SCO Open Desktop (SysV/386 3.2) includes the MMDF mailer.  The man page for
|the mmdftailor file mentions syntax for some "authorization" feature(s),
|but with no explanation.  I'm guessing I might be able to restrict who
|can mail to a list-outgoing address, or to certain aliased pipes, etc.
|Whatever it is, it could well be useful to me.
|
|Where can I find documentation?  SCO doesn't provide the MMDF source.

The authorization features are not yet supported by SCO, but they are
available (unsupported) in the product, with a few caveats.  The
papers ``Configuring MMDF Authorisation'' by Steve Kille, and
``Authorisation and Accounting'' by Kille and D.H. Brink are available
with the rest of the documentation available from the University of
Delaware.

One big caveat is that because the SCO provided mail user agents use a
common setuid program to submit mail, user-based authorization does
not work on mail generated on the local machine.  You can still use
user-based authentication in many situations.  For example, if your
connection to uunet is from a central hub, and the users that you wish
to block from passing mail through uunet are not local to that hub,
you can do it.

The other caveat, again, is that authorization is not a supported
feature, so you can't call support if you're having trouble with it.