I'd start by making sure $smtp is expanded
from the environment or the ndb at all.
The error message:
translating net!$smtp!smtp:
seems to suggest it isn't.
Try poking the ndb directly, like so:
ndb/query ipnet 9front smtp
--
9fan
> I haven't found much other than a thread dating back to 2013 from fgb,
> which appears related but doesn't seem to have a solution that works
> for me.
Apologies, this was a thread from 2007 though fgb was not the original
poster.
After digging a little more based on one of steve's suggestions
What about:
% ndb/csquery /net/cs 'net!$smtp!25'
Or even:
% ndb/csquery /net/cs 'tcp!$smtp!25'
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tf5f20e4ab86fee91-M6401d7abb306e5837d2593aa
Delivery options: https://9fans.
All,
I was reviewing my mail setup this evening and I came across an old
kludge to forward mail to a relay host on my network in
/mail/lib/rewrite. I used a host-specific dial string rather than
net!$smtp. For kicks, I reverted back to the classic behavior to try
and sort out why the lookup fail
yeah, that's what i mean. i was worried it wouldn't be a subset of
neon: i.e. that they might keep neon and get rid of vfp at some
point...
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T12f163bbd73cfb63-M823e9f92726c189cc0cd9465
Delive
> is it worth using vfp when neon is around?
Plan 9 arm source uses "vfp" as a generic term to mean modern
hardware floating point instruction set (as opposed to the old
arm7500 instruction set, which I suspect has always been purely
emulated since processors implementing this set were quite rare)
is it worth using vfp when neon is around?
just curious...
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T12f163bbd73cfb63-M558f1e2af20c27f2a58ccc46
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
