| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 304.1 | /CONFIRM | CLOSET::DYER | Define `Quality' | Wed Sep 03 1986 08:39 | 7 |
| Well, one nice feature would be the ability to confirm
whether or not you want those no-longer-a-user-here records
to be taken away. Sometimes it's nice to keep one of those
records around, forwarding mail to the user's new node. I
even have some nonexistant users in there on purpose, so mail
can be sent to an alias here.
<_Jym_>
|
| 304.2 | | 43406::MACKAY | Kit Kye | Wed Sep 03 1986 09:03 | 10 |
| re .-1
Agree with that point. We have some non-existent users defined on
our system - they are more function users. They are used by the world to
contact the current holder of the function, for example RDGENG::FCNS
points to myself. It means that I can pass on this business to some other
user without having to broadcast to the world that it has changed - the
world doesn't care as long as contact is made and it gets service. This
could cause problems if a (new) overzealous system manager got to work with
a clean-up routine!
|
| 304.3 | /CONFIRM Functionality? | 8587::DUTKO | Nestor Dutko | Wed Sep 03 1986 12:37 | 14 |
| Yep, I too have that in the verify routine already.
I have a question on functionalality though. Currently, the verb
is of the form: VERIFY [/CONFIRM] [/LOG]
If you specified just VERIFY, would you like to see
a) All records deleted what did not have a cooresponding will
be removed without any warning, or
b) It will ask for a confirmation even though you have not
asked for it via /CONFIRM.
-- Nestor (Still coding and looking for enhancements...)
|
| 304.4 | Code sent | DELNI::CANTOR | Dave Cantor | Thu Sep 04 1986 00:17 | 13 |
| I sent a copy of the enhancements I've made to MAILUAF.COM to the
author of .0. Included are
1. Single line execution; _e.g._, $ @MAILUAF SHO FOOBAR
2. Adjust the new mail count
3. Rename a user record, by copying the record (thus transferring
the new mail count, forwarding, etc.) and zeroing the new mail
count in the old record.
Dave C.
|
| 304.5 | Notes file created | 8587::DUTKO | Nestor Dutko | Thu Sep 04 1986 00:36 | 7 |
| Thanks for all the suggestions. In order to keep additional
information getting around about the utility, I have create a notes
file on my home node. It is CSC32::MAILUAF
To add it in, simply hit the PF7 key.
-- Nestor
|
| 304.7 | Please submit it to the toolshed | NANDI::LAMIA | Cheap, fast, good -- pick two | Thu Sep 04 1986 09:22 | 4 |
| Please don't forget to submit this useful tool to the Toolshed.
Press Select to add the Toolshed notes catalog conference to your
notebook. It's on METOO::TOOLS$LIBRARY:SW_TOOLS_CATALOG.
|
| 304.8 | Official | VAXUUM::DYER | Working For The Yankee Dollar | Thu Sep 04 1986 10:06 | 3 |
| Or, better yet, you might want to submit it to the VMSmail
people!
<_Jym_>
|
| 304.9 | callable interface maybe? | CRVAX1::LAMPSON | Noter on board! | Thu Sep 04 1986 10:32 | 7 |
| Maybe you should talk to the VMSMAIL people/person (Rob Posniak, I
believe) and try to get a copy of the callable interface
guidelines. That way, your utility won't need to be rewritten
when the VMSMAIL.DAT file structure changes (sure to happen
in VMS V5).
-&Mike
|
| 304.10 | | CRVAX1::LAMPSON | Noter on board! | Thu Sep 04 1986 10:38 | 6 |
| Re: .9
Of course, I'm assuming that the callable interface can access
the VMSMAIL.DAT file, not just send mail. ;^)
-&Mike
|
| 304.11 | re:.7 - You forgot one of those * things... | 33975::MITCHAM | -Andy in Atlanta | Thu Sep 04 1986 11:14 | 1 |
| I pressed <SELECT> and got some message about no conference to select...
|
| 304.12 | .7 now has /CONF set | NANDI::LAMIA | Cheap, fast, good -- pick two | Thu Sep 04 1986 14:48 | 3 |
| Sorry, I lost track of where I was, and forgot to finish the job.
.7 is now fixed. Thanks for the note.
|