Re: [9fans] /mail/lib/rewrite and net!$smtp

2019-12-07 Thread Steven Stallion
> Thanks! Unfortunately my MX host only exposes port 587 for relaying > mail outside of the domain. I suppose I could update cs to permit > specifying a port number in ndb for $smtp, but I'm not sure that's any > better than just specifying the relay host directly in rewrite. I did some more

Re: [9fans] /mail/lib/rewrite and net!$smtp

2019-12-07 Thread Steven Stallion
> Don't give up yet, it works for me: > > term% ndb/csquery /net/cs 'net!$smtp!smtp' > /net/tcp/clone 93.93.130.6!25 > /net/tcp/clone 93.93.131.52!25 > /net/tcp/clone 2a00:1098::86:1000:0:2:1!25 > /net/tcp/clone 2a00:1098::82:1000:0:2:1!25 > > In my /lib/ndb/local I have this: > >

Re: [9fans] /mail/lib/rewrite and net!$smtp

2019-12-07 Thread Richard Miller
> % ndb/csquery /net/cs 'net!$smtp!smtp' > translating net!$smtp!smtp: cs: can't translate address: dns: name > does not exist Don't give up yet, it works for me: term% ndb/csquery /net/cs 'net!$smtp!smtp' /net/tcp/clone 93.93.130.6!25 /net/tcp/clone 93.93.131.52!25

Re: [9fans] /mail/lib/rewrite and net!$smtp

2019-12-06 Thread kvik
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 --

Re: [9fans] /mail/lib/rewrite and net!$smtp

2019-12-06 Thread Alex Musolino
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:

[9fans] /mail/lib/rewrite and net!$smtp

2019-12-06 Thread Steven Stallion
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