[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

1257.0. "dist list and remote mail" by MRKTNG::SKINNER () Mon Aug 17 1992 20:37

    Hi,
    
    I'm having an intermittent problem with a system distribution list.
    The list was created via the ALL-IN-1 toolkit. It has been assigned
    two editors.
    
    When one of the editors adds another entry to the list, ie,"Shari
    Skinner @ TTB", it comes back with "You cannot send to remote
    addressees on this system". You don't always get the error. You can
    edit the list again (without logging out/back in) and this time it
    will work.
    
    There are no problems with users sending mail off node.
    
    I'm running ALL-IN-1 2.4 and VMS 5.4-3.
    
    Any ideas?
    
    Thanks,
    
    Shari
T.RTitleUserPersonal
Name
DateLines
1257.1Beats me!IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue Aug 18 1992 09:4811
    Firstly this may be a problem with the toolkit, which we don't support
    here. There may be another conference for that.
    
    I think you only get the "cannot send" message if we think that you
    have decided not to use Message Router when you installed the product.
    This doesn't seem likely to be intermittent! Perhaps someone is messing
    around with the logicals OA$MTI* or something?
    
    Confused,
    
    Graham
1257.2more details?FORTY2::ASHGrahame Ash @REOTue Aug 18 1992 11:0913
I don't see how this can be intermittent either (though I should know better 
than to make statements like that!)

The way this used to work was that when MAIL INIT was called (typically the 
first time you hit the EM menu), it looked for its logicals and set their 
values inside the image - it never goes back to check if the logical has 
changed, to do that you have to exit and reenter ALL-IN-1.

And the logical looked for was MR$NODE.

Is the user really getting this error intermittently in the same session?

grahame
1257.3Humble suggestionSCOTTC::MARSHALLPearl-white, but slightly shop-soiledTue Aug 18 1992 13:2213
Hi,

Following on from .2

How about this:

The user enters ALL-IN-1, and tries to edit the DL, and gets the error because
mail isn't initialised.  Then they go to EM so that the mail logicals are picked
up, then go back to DL and, hey presto, it all works!?

Just a guess...

Scott
1257.4EM needs to be invoked firstMRKTNG::SKINNERTue Aug 18 1992 17:2517
    Hi,
    
    I think the previous repl may be on to something. I logged into her account.
    She starts at the Main menu. I immediately went to the DL menu. When I
    tried to add to it, I got the same error message. I then exited from
    the list and went to the EM menu. Then back to the DL menu. I was then
    able to add an entry to the list. I could duplicate this over and over.
    
    It also works when I invoke A1, go to the em menu, then to the DL menu.
    Then She is all set.
    
    I'm going to change her profile to go right to the em menu for now.
    Unless someone has a better fix.
    
    Thanks,
    
    Shari
1257.5Add MAIL INIT????IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeTue Aug 18 1992 18:474
    You could put a MAIL INIT (check spelling!) in the DL code. It's a
    no-op once it's been done once, so it's relatively cheap.
    
    Graham
1257.6Make it official...SCOTTC::MARSHALLPearl-white, but slightly shop-soiledWed Aug 19 1992 12:193
Has someone IPRed / SPRed this?  If not, I'll do it.

Scott
1257.7More possible fixes for possible future releasesSCOTTC::MARSHALLPearl-white, but slightly shop-soiledFri Aug 28 1992 10:2616
Hi,

As no-one's replied, I assume no-one's submitted a bug report.
Therefore I've IPRed it.

Please can I just remind everyone that this conference is an informal support
forum, and not an official bug reporting channel.  If you have a bug, please
SPR/SRF/IPR/whatever it, otherwise it (probably) won't be fixed.  In these
hard-pressed times, we can't justify fixing something just because it was
discussed in a notes conference; it needs to be an official bug.

I would hate to see the next (possible :-) version of ALL-IN-1 ship with lots
of silly little bugs just because everyone thought they were too trivial to
report.  Besides, we prefer fixing the easy ones :-)

Scott