[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
1990.0. "docdb & DQ" by MSAM01::SOWWAN () Fri Dec 18 1992 09:15
Hi,
My customer is using ALL-IN-1 V2.4 and Desktop V1.1.
Recently, they complaint of receiving old messages (as old as
Jan, March, April etc), but the new mail count didn't show the same
number of mails as in the inbox.
I have a few questions here :
1) Some of the DOCDB.DAT have very recent creation dates (eg 12th DEC
92) but the DOCDB.DAT is definitely not being recreated on that date
nor restored. What could have caused this ? Housekeeping tasks ?
2) When I did a DQ, I found a lot of entries in the queue and were as
old as JAN 1992 ! Does it mean that these mails have not been sent and
are actually waiting to be sent ? However, users are still receiving
their messages on time and only a few of them suddenly receive some
old mail recently.
3) This is a standalone ALL-IN-1 system and no remote node user.
However, there is some errors in MTIERR.LOG :
"%EMD-E-OPENERR, error opening MESSAGE ROUTER link..."
Any suggestions?
Thanks!
Regards.
T.R | Title | User | Personal Name | Date | Lines |
---|
1990.1 | Deferred ? | SUBURB::BROWNSTONE | Out to lunch | Fri Dec 18 1992 13:09 | 6 |
| Just a stab in the dark....
Are these deferred messages (D status in the L/R column of DQ) ?
Chris
|
1990.2 | Some other guesses | IOSG::WICKSA | Left alone in IOSG's rabbit warren | Fri Dec 18 1992 13:27 | 19 |
| Sowwan,
There is a housekeeping task that reorganises DOCDB but without
documentation or STARS I can't remember whether it's ROA or not
also the user option FCO might do this too.
I think chris got number two right.
As to the MR error - is the entry in A1CONFIG for remote mail set to
0 so that when a user attempts to send mail to user@A1@node they
get an error message such as "you cannot send remote mail". With
a little detective work matching the time of the error in MTIERR to
a particular message in MTILOG you could find out which mail is causing
this error - it could be one of those old deferred messages trying to
send something off-node.
regards,
Andrew.D.Wicks
|
1990.3 | | MSAM02::SOWWAN | | Mon Dec 21 1992 07:32 | 9 |
| Hi Chris and Andrew,
Thanks for your suggestions!
Regarding my problem (2), those messages are with status L or R and
a couple is P, but no D at all. The retry count is 0 for all of them.
Why would all these messages be stuck there while users are still
receiving their new mails?
Thanks.
Regards
|