[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | VAX MAILGATE for MEMO |
|
| Moderator: | STKHLM::OLSSON |
|
| Created: | Sat Feb 25 1989 |
| Last Modified: | Tue May 14 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 216 |
| Total number of notes: | 933 |
41.0. "Don't let anybody stop the gateway" by BRSDVP::WAUTERS (Philipovitch) Wed Jul 04 1990 16:23
This is the way any MEMO user can blow up the MEMO gateway very easily :
*************
When logged in the IBM using MEMO, sending a message to
OAS.CEWAUPH..MRGATE..COV
! ! !- node running MRGATE
! !- addressee's username on VAX
!- DGN
works fine.
Now, if you have a blank username ( this was the case here with a bad
symbol substitution leading to the symbol left blank ), you try to send to
OAS...MRGATE..COV
!- Notice : 3 dots !!!
This message will never go through the gateway but will also never be
cleared. So, once this message is at the top of the messages queue, you get
errors in the MRMEMO1.LOG file ( see further ) and the traffic from I.B.M.
to VAX is locked.
The only way to correct this situation is to purge this message on the
I.B.M.
The MRMEMO1.LOG file grows up rapidly : >3000 blocks in one day.
Is this a known problem ?
Can you reproduce this ?
Is there a way to avoid it ?
Do you agree we cannot risk that any MEMO user can stop the message
traffic via the gateway ? ( I suppose you do )
Looking forward for your help.
Regards.
- Philippe Wauters -
---------------------------------------------------------------------------
$ set noon
$! M r m e m o . C o m - comments and copyright notice at the end
$!
$ set noon
$ set verify
$ define tt nl:
$ run/nodebug sys$system:mrmsrv
Time: 1990-07-02 10:21:02.79; message from server MRMEMO1:
%MRMEMO-I-NEWACCOUNT, opening new accounting file: DISK_A1:[MRMEMO]MRMEMOACC1.DAT;222
Time: 1990-07-02 14:40:23.23; message from server MRMEMO1:
%MRIF-E-MISSUSERID, missing userid
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, receiving from MEMO after data received from MEMO
-MRMEMO-I-RING, ring: '1A 1A 1A 1A 1A 1A 13 3A 3A 36.', substates: 00000070
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3597 000001BB 000BE2AF
----- above condition handler called with exception 0935E83A:
%MRIF-E-MISSUSERID, missing userid
----- end of exception message
SRVMRC SRV$MRC_POST 4401 0000005B 000C1546
SRVACT POST_MEMO 4518 0000003B 000C5823
SRVACT SRV$ACT_R 4839 0000020E 000C5BEE
SRVDSP SRV$DSP_FSM 3007 000002A6 000BDF4A
SRVMMO SRV$MMO_ONE_LIFE 3955 000001EF 000BBD5F
SRVMMO SRV$MMO_MAIN 3787 00000017 000BBB63
001112C2 001112C2
KOTERM KOTERM 804 00000039 0010ECB6
0011129D 0011129D
KODOC KODOC 1768 00000097 0010BEF8
0011129D 0011129D
00166BB2 00166BB2
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 0009FC0E
0011129D 0011129D
Time: 1990-07-02 14:41:31.20; message from server MRMEMO1:
%MRIF-E-MISSUSERID, missing userid
%MRMEMO-W-TRACE, traceback forced from the Server Handler
-MRMEMO-I-FSM, receiving from MEMO after data received from MEMO
-MRMEMO-I-RING, ring: '1A 1A 1A 1A 1A 1A 1A 1A 13 36.', substates: 00000030
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
SRVLOG SRV$LOG_HANDLER 3597 000001BB 000BE2AF
----- above condition handler called with exception 0935E83A:
%MRIF-E-MISSUSERID, missing userid
----- end of exception message
SRVMRC SRV$MRC_POST 4401 0000005B 000C1546
SRVACT POST_MEMO 4518 0000003B 000C5823
SRVACT SRV$ACT_R 4839 0000020E 000C5BEE
SRVDSP SRV$DSP_FSM 3007 000002A6 000BDF4A
SRVMMO SRV$MMO_ONE_LIFE 3955 000001EF 000BBD5F
SRVMMO SRV$MMO_MAIN 3787 00000017 000BBB63
001112C2 001112C2
KOTERM KOTERM 804 00000039 0010ECB6
0011129D 0011129D
KODOC KODOC 1768 00000097 0010BEF8
0011129D 0011129D
00166BB2 00166BB2
ADA$ELAB_DDS ADA$ELAB_DDS 0000000E 0009FC0E
0011129D 0011129D
.
.
.
( repeated once every minute )
---------------------------------------------------------------------------
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 41.1 | Fixed in next release | STKHLM::OLSSON | Anders Olsson, LEG Sweden | Thu Jul 05 1990 09:33 | 34 |
| .0>
.0> OAS...MRGATE..COV
.0> !- Notice : 3 dots !!!
.0>
.0> This message will never go through the gateway but will also never be
.0> cleared. So, once this message is at the top of the messages queue, you get
.0> errors in the MRMEMO1.LOG file ( see further ) and the traffic from I.B.M.
.0> to VAX is locked.
.0>
.0> Is this a known problem ?
Yes
.0> Can you reproduce this ?
Yes
.0> Is there a way to avoid it ?
No - except avoiding to use addresses like this from MEMO
.0> Do you agree we cannot risk that any MEMO user can stop the message
.0> traffic via the gateway ? ( I suppose you do )
Of course we agree to that!
.0> Looking forward for your help.
This problem is fixed in MRMEMO V2.1, which is now in external field test.
Since the release of V2.1 isn't too far away, we have not spent any time
evaluating the possibility of creating a patch for V2.0.
Anders
|
| 41.2 | Thanks | BRSDVP::WAUTERS | Philipovitch | Thu Jul 05 1990 10:06 | 10 |
| Thanks a lot for this very quick answer : it is really nice to see you
react so promptly.
Also glad to know it has already been fixed.
Waiting for the next release ...
Regards.
- Philippe -
|