MAG@IBM.COM (09/26/90)
How can I set how far back the update command will look at messages.
The"update" seems to only look at up to 4 days old messages. Here is
what CUIdisplays:
CUI> update drafts
Looking for new mail in ~/Mailbox
No new messages in ~/Mailbox
Checking drafts ...
First time updating /u/mag/.MESSAGES/drafts
Starting with messages from 4 days ago. . .
No new messages.
I would also like to set it, so the update command will look at all
themessages in given folder. Regardless of the date.
Is there anyway to stop "messages" from reading mail automatically?,
whenit's first executed.
I have set in the /AndrewSetup file; AMS_UseShortFileNames;yes (In order
tohave filenames under 14 characters long). However, this does not seem
toapply to the CKP files written while checkpointing. So, in my home
directory Ihave a bunch of CKP files which never dissapear. Is this how
it's suppose towork?. Should CKP files be deleted once you quit out of
the application?
Where can I find documentation on flags for messages, and how do I use
theseflags with the "messages" interface?.( I have already looked at all
the cuihelp files).
How does one set "urgent" for a message, using the "messages" interface?
Thanks!!
Marlon
Watson AIX Information Center
mag@ibm.com
(914)784-7334nsb@THUMPER.BELLCORE.COM (Nathaniel Borenstein) (09/26/90)
"update" only behaves that way the first time you ever read a folder -- after the first time, it should do exactly what you said you want. The different first-time behavior is intended to avoid obnoxiousness on large bboards you've just started reading. You can always look at old stuff using the "headers" command. It sounds like there is indeed a bug in naming the .CKP files for short-file-name systems. I'm not sure what you mean by "stopping meessages from reading mail automatically" when first executed, but not other times -- you'll need to explain what you want more clearly, I think. I think all the documentation you need is in the help files -- what kinds of flags were you interested in? Finally, I don't think we ever implemented the "urgent" feature in the Messages user interface, only in CUI. -- Nathaniel
MAG@IBM.COM (09/26/90)
Excerpts from mail: 25-Sep-90 Re: CUI update command, and.. Nathaniel Borenstein@thu (837) > "update" only behaves that way the first time you ever read a folder -- > after the first time, it should do exactly what you said you want. The > different first-time behavior is intended to avoid obnoxiousness on > large bboards you've just started reading. You can always look at old > stuff using the "headers" command. It doesn't seem to work for me. I've tried several times after I created the folder. Anyhow, let me tell you what I am trying to do, maybe there is a better way. I am writing a script which translates MH mail to AMS. Here are the steps: - Execute cui in order to create the .AMS_* files and directory. - Move everything under (MH) Mail directory to .MESSAGES. - Using CUI create all the folders. - Reconstruct all the folders. Here is the problem. If I look at the folders via messages, it thinks all the messages are unread (e.g. folderx (Mail; 20 new of 20)), but all the messages have the check symbol next to them. I don't want the user to have to traverse these old messages in order to bring the folder header up to date (Mail;0 new of 20). Therefore, I thought I could use the following command "cui update folderx ; skip 99; next; quit" to bring the folder into sync. Is this right, or is there an easier method to translate MH to AMS? > It sounds like there is indeed a bug in naming the .CKP files for > short-file-name systems. How do I summit this bug? ( I am new to the ATK) > > I'm not sure what you mean by "stopping meessages from reading mail > automatically" when first executed, but not other times -- you'll need > to explain what you want more clearly, I think. When you first start messages, it says "Checking for new messages in ~/Mailbox" (something like that), and then it brings the new messages into your mail folder. How can I tell messages not to bring in new messages? Thanks! Marlon T.J.Watson AIX Information Center mag@ibm.com (914)784-7334
Craig_Everhart@TRANSARC.COM (09/26/90)
You can use the ``headers <folder>'' or ``headers <folder> since
<date>'' CUI commands to let you see further back. The ``update''
command wasn't designed for browsing backwards, but for keeping current
with your subscriptions.
Give Messages the name of a folder on the startup line and it won't
check your mail. Thus, I could say
messages ; to read old&new mail and bboards
messages -m ; to read only old&new mail
messages mail ; to read only old mail; new mail not incorporated
messages foo.bar.baz ; to read only that one folder; new mail
not incorporated
I don't know the answer to the question about checkpointing and the
14-char limit; perhaps Nathaniel can comment.
Excerpts from internet.info-andrew: 25-Sep-90 CUI update command, and
mes.. MAG@IBM.COM (1292+0)
> Where can I find documentation on flags for messages, and how do I use
> these flags with the "messages" interface?.( I have already looked at
> all the cui help files).
> How does one set "urgent" for a message, using the "messages" interface?
There is no sensible way to deal with flags (other than ``examined'' or
``deleted'') in Messages. That's a limitation of the interface. Sigh.
Craignsb@THUMPER.BELLCORE.COM (Nathaniel Borenstein) (09/27/90)
Excerpts from internet.info-andrew: 26-Sep-90 Re: CUI update command, and.. MAG@ibm.com (2024) > Here is the problem. If I look at the folders via messages, it thinks > all the messages are unread (e.g. folderx (Mail; 20 new of 20)), but all > the messages have the check symbol next to them. I don't want the user > to have to traverse these old messages in order to bring the folder > header up to date (Mail;0 new of 20). Therefore, I thought I could use > the following command "cui update folderx ; skip 99; next; quit" to > bring the folder into sync. Is this right, or is there an easier method > to translate MH to AMS? Very interesting -- I'd never thought about this problem before, and nobody else who has written such conversion scripts seems to have mentioned it either. I don't think the skip 99 approach you described would really work very well, particularly with very large folders. However, if your script knows the number of messages in the folder (which it can find out pretty easily with something like NUMMSGS=`ls | wc`) you can probably do what you want with an ugly CUI command line like this one: cui set term 0 \; headers foldername \; set seenlast $NUMMSGS \; quit The trick here is that if you start out with "headers foldername", it will print all the captions out in order, and the last one will be numbered $NUMMSGS. "set seenlast" can then do what you want. (The "set term 0" just gets rid of "more mode" when it shows you all those headers.) Note also that this command will generate a lot of output, which can probably be sent to /dev/null. Hope that helps! -- Nathaniel PS -- To report the bug in short-name checkpoint files, send mail to info-andrew-bugs+@andrew.cmu.edu. I think Craig answered your other question about starting up the Messages program. Good luck! -- Nathaniel
MAG@ibm.com (10/09/90)
Excerpts from atk.ams: 27-Sep-90 Re: CUI update command, and.. Nathaniel Borenstein@thu (1817+0) > Excerpts from internet.info-andrew: 26-Sep-90 Re: CUI update command, >> and.. MAG@ibm.com (2024) Here is the problem. If I look at the folders >> via messages, it thinks all the messages are unread (e.g. folderx (Mail; >> 20 new of 20)), but all the messages have the check symbol next to them. >> I don't want the user to have to traverse these old messages in order >> to bring the folder header up to date (Mail;0 new of 20). Therefore, I >> thought I could use the following command "cui update folderx ; skip 99; >> next; quit" to bring the folder into sync. Is this right, or is there >> an easier method to translate MH to AMS? > > if your script knows the number of messages in the folder (which it can > find out pretty easily with something like NUMMSGS=`ls | wc`) you can > probably do what you want with an ugly CUI command line like this one: > cui set term 0 \; headers foldername \; set seenlast $NUMMSGS \; quit > The trick here is that if you start out with "headers foldername", it > will print all the captions out in order, and the last one will be > numbered $NUMMSGS. "set seenlast" can then do what you want. Good > luck! -- Nathaniel > Well, I've tried the "seenlast" with no luck. There is even more weird behavior; if the user reads all the messages and clicks on the folder header, it displays "(Mail; 0 new of 5)", which is fine. But if he clicks one more time on the folder header, it displays "(Mail; 2 new of 5)". I have no idea what's going on. Has anyone else encountered the same problems I am having?. Could it be that my AMS is setup with the following options in /AndrewSetup : ThisDomainAliases: watson.ibm.com, watson # # AMS options for no AFS or AMSD # AMS_OnAIX:yes AMS_NonAMSDelivery:yes AMS_DefaultToAFSCellMail:no AMS_WSRunsQueuemail:no AMS_ThisDomainAuthFromWS:yes AMS_NonViceHost:yes DefaultMSPath:$MAIL AMS_MailBoxPrefix:/usr/mail MessagesAutoBugAddress:mag@prefect.watson.ibm.com # # For white pages to work under AFS but no AMSD ThisDomainWPDirectory:/afs/test.ibm.com/service/wp # # short file names for AIX on RT AMS_UseShortFileNames:yes # # Validate hostname validation AMS_ValidateDestHosts:no I don't know what else to try. Can someone explain how AMS sets flags (read,unread, deleted) to messages and folders. Can I set them using CUI? Could there be a bug with the "reconstruct" command?. Can someone can tell me which sources files are used? Thanks Marlon IBM T.J. Watson Research mag@ibm.com (914)784-7334 > >