🚀 go-pugleaf

On Tuesday, in article <821203523snz@grempc.demon.co.uk>
     Graham@grempc.demon.co.uk "Graham E Kinns" wrote:

GK> To get an idea of whether it is the DNS lookup that is causing the 
GK> problems, you could add 'domain trace on' (or 'do t 1' will do) to 
GK> autoexec.net and watch for the lookups and responses.

I'm joining others in thanking you, Graham.

Fascinating output it generates.  I quite often get
a message length -1 errno 17 generated, just curious
as to what that might mean.  Seems to keep working tho.

And I'm quite surprised at the amount of activity.
If I understand the trace (which I probably don't),
e.g. it goes out and asks about news.demon.co.uk,
resolving it to news.news.demon.net -- I would have
expected such info to be picked up from domain.txt.

..
GK> and the domain system") - if an MX (mail) record doesn't exist for the
GK> given mail address, KA9Q should attempt to contact the host in the 
GK> address directly, but it doesn't - it starts making up wildcard 
GK> truncations of the address and looks these up - which takes ages and 
GK> doesn't get any response from the servers, eventually it will give up not 
GK> having found anything and only then try and send it to the real host. I

Yes, seen that too.  No wonder the mail takes a while to
go out sometimes, the trace showed *.com being looked for.
How fortunate that the DNS doesn't respond with every .com
it can lay its hands on!

The worst aspect of all this is that I suspect that a mail
to somewhere difficult not only takes a long time to go out,
but also can hold up other easy mail (e.g. to 'demon.co.uk').
Sometimes I've had to move mail for strange locations into
another directory and redial, just to get my other mail
moving.

But even that's better than incoming SMTP.  If only there
were some way to kick a punt into life.

--
John Washington