| 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 |
Hello Customer just upgrade from ALL-IN-1 2.4 to 3.0 and everything
went semi smooth . One major problem that we are experiencing today
is message router .
The Fetcher is is picking up the messages as complete but message
router is rejecting them , making them undeliverable .
Messages going from ALL-IN-1 to the other side ok no problem ,
Messages coming back is where the problem is being experienced ,
Currently its is being worked through telephone support , but
seem to be going nowhere .
Any Ideas , Hints
Thank you
Frank Bernal
210-821-0474 ( pager )
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3926.3 | Thank you for the support | DPDMAI::BERNAL | set a goal and go for it | Fri Mar 04 1994 00:22 | 8 |
Many thanks to support and ENG for working the issue .
The fix , was ( my understanding ) by using the MTI object in
the library from version 3.0 .
Please contact your support organization for further details .
thank you
Frank BErnal
| |||||
| 3926.4 | Clarification | IOSG::MARSHALL | A glitch in reality | Fri Mar 04 1994 11:28 | 22 |
If this is the call I'm thinking of, then I should clarify .3 to prevent panic: .3 said (implied) the fix is to revert V3.0-1 or V3.0A mail code to V3.0, as (according to .0) the later mail code causes large-scale non-deliveries. Such a statement implies a serious problem in V3.0-1 and V3.0A, which is not the case. These patches improve error handling in the mail code, and in this specific case caused the fetcher to reject badly-formed NBS files. V3.0 doesn't contain the check, so will deliver (part of) the mail message. I'm not sure which is best - rejecting corrupt messages or "having a go" at delivering them anyway. The bad NBS files were being produced by a customer's own application (I don't have any more details), not by ALL-IN-1 or any other Digital software. So the real fix is for them to fix their application. They have apparently chosen to accept partially-delivered (and probably corrupt) messages as a stop-gap. So this topic does not in any way imply general fetcher problems in any release of ALL-IN-1, or that there is any need for the ALL-IN-1 community in general to de-install any of the V3.0 patches. Scott | |||||