🚀 go-pugleaf

After much consideration Richard Clayton decided to share these wise
words:
>In article <o$GZOPA4m1u1EwK8@ubik.demon.co.uk>, Anthony Naggs
><amn@ubik.demon.co.uk> writes
>
>
>>+   fix mail transmit to use MX records, and fall back to using the
>>    smarthost when errors are encountered.
>
>I thought it did this

Wasn't there a problem with it only using A or CNAME records?  (I could
be wrong, as it really as several years since I used DISPC's ka9q.)


>>+   fix file read/write of '>' prefix on lines starting with 'From'
>
>I thought this was done correctly - the scheme in question is
>fundamentally flawed :( but KA9Q operates it as might be expected

Someone earlier in the thread, (at least in dis.pc), said that it broke
(in PCElm) when moving messages between mailboxes.


>>[At some point ka9q should support IPv6.  Heck I've already written code
>>to handle IPv6 in some Windows apps, (though I've not tested it for
>>obvious reasons!).]
>
>why ?
>
>there will be interworking with IPv4 for a long long time, why would you
>expect the entire stack to be rewritten ?

I don't fancy letting loose all my IPv6 code without testing it.  The
obvious place is on a private net.  With other IPv6 hosts.  I know it's
not urgent, and it probably more useful in other versions of ka9q.  (Eg
where it is used as a router.)  Anyway, even I didn't say it was urgent.


Obviously Demon are not at this point going to commit themselves to an
open ended round of development.  My little list was intended to help
the various parties come to some agreement on what the immediate
development targets would be.


Cheers,
      Tony
-- 
  Hmmm... what should I put in my .sig today?