mail/BIND/svcorder/MX annoying problem

[William Lynch]

I can't believe we're the only ones with this problem.  We're running
3.1/2.2 on DECstations, and when using BIND, binmail really blows using MX
records for mail which should be forwarded through some remotely local site
(did I say that?).  Here's the good part though: it works fine if bind is
the FIRST thing in the /etc/svcorder file!  I suppose that binmail looks in
the svcorder file (the string is in the executable, anyway) to see if you
are BINDing, but somehow figures it doesn't need MX records unless bind is
the first thing in the file (?).  

We of course have a workaround of putting bind first in the svcorder file,
but the number of other things that breaks due to local aliasing is rather
impressive.  Does anyone have any other ideas/fixes/causes?  Can anyone
empathize?  Does anyone know if this is fixed in 4.0 (we did report it)?

Bill
lynch at umunhum.stanford.edu

PS our VAXstations don't have this problem.