ML> When you attach a crash flag to a message, it no longer is 
 ML> a Normal flavoured mail so is not processed by Squish hence 
 ML> typically handled by the mailer. So only give priviledged 
 ML> users Crash mail access on your BBS.

 DS>   I think that this observation about the effect of a crash flag is what
 DS>   I was not taking into account.

 DS>   It now seems to be working the way I would want, Thanks again.

Ok.

Do this,

  Change Crash Normal World
  Route Normal 1:123/500 World

The above will deal with Intermail's default Crash netmail (ie. you won't
have to fuss over changing message flavours from Crash to Normal due to
Intermail's default behaviour for netmail). However the problem with the
above configuration is that all crash flavoured mail will be converted to
normal -- therefore you lose the flexibility of explicitly creating any
on-the-fly crash netmail.

To fix that, based on your original route.cfg (ie. judging your intentions), 

   1: Send  Normal World
   2: Route normal 1:123/500 1:All 2:All 3:All 4:All 5:All 6:ALL
   3: Send  Crash  1:140/1
   4: Send  Crash  1:261/1
   5: Send  Crash  1:261/38
   6: Send  normal 1:123/500

you probably want to turn it into something like this:

  1: Change Crash  Normal    World
  2: Change Normal Crash     1:140/1 1:261/1 1:261/38
  3: Route  Normal 1:123/500 World

which will allow you to send real Crash mail to 1:140/1, 1:261/1 and
1:261/38 while routing everything else through 1:123/500.

You could get creative with Squish schedules if you like :)

--- Maximus 3.01