Subj : Crash mail behaviour
To   : Marcus Roeckrath
From : Michael Kleefeld
Date : Mon Aug 28 2000 07:20 am

Marcus,

You wrote to Johannes Beekhuizen (22.08.2000 07:53)

 JB>> I noticed the following tonight:
 JB>> The current event has the CM flag on.
 JB>> I put mail ready with status Crash for a node who does /not/ have
 JB>> the CM flag in the nodelist Portal of Power started dialing out to
 JB>> that node. I expected Portal of Power to wait with that until ZMH:
 JB>> the node is only guaranteed to be available during ZMH, so Portal
 JB>> of Power has no right to call him yet Is Portal of Power doing it
 JB>> incorrectly or am I misunderstanding?

 MR> This is the way it was designed by the "original" Portal Team. If you
 MR> dial out a non cm node manually you have to confirm the call. Maybe I
 MR> can change the code so that a non cm node isn't called except ZMH.

This will be the correct behavior. But ..

 MR> But all zones have different ZMH's and I did not know to handle this.

... i see the problem. If i want to call a nonCM node in another zone, Portal 
must know the ZMH of this zone ..

 MR> If you have a crash mail to a non cm node in your own zone the ZMH you
 MR> defined in setup can be used to decide if this node should be called or
 MR> not. But for nodes of other zones there is a problem.

 MR> Help me, in which way we should try to handle it.

I think it is better Portal don't call any nonCM nodes automaticly in events 
with CM flag. And the sysop can construct something to call this nodes as 
immediat/important via special event, outbound manager or something else.

 MR> An external file in which all zones and there ZMH's are layed down?

Nooo.

|X|
| |icha

--- FMailX 1.22
 * Origin: * Astronik * CM MO V34 X75 * noCS * (2:2468/9963)

.