🚀 go-pugleaf

[f-ups out of d.s]

In article <878398739snz@smof.demon.co.uk>
           tim@smof.demon.co.uk "Tim Illingworth" writes:

>post.mail.demon.net.   879 IN A     194.217.242.27
>post.mail.demon.net.   879 IN A     194.217.242.154
>post.demon.co.uk.    45415 IN CNAME post.mail.demon.net.
>punt-2.mail.demon.net. 573 IN A     194.217.242.8
>punt-2.mail.demon.net. 573 IN A     194.217.242.9
>punt-2.mail.demon.net. 573 IN A     194.217.242.5
>punt-2.mail.demon.net. 573 IN A     194.217.242.6
>*.demon.co.uk.       45939 IN MX 10 punt-2.mail.demon.net.

>reading upwards, as appears to be right, KA9Q attempts to deliver to
>post.demon.co.uk (because that's in the first line of the .WRK file).
>Now post.demon.co.uk is a subset of *.demon.co.uk, so mail goes off
>to punt-2, which won't accept it.

Close :)  The MX resolving code takes it upon itself to try and do 
wildcard lookups for higher level domains when an MX query fails -
this is completely broken since the wildcard expansion should be a
function of the server :(

An MX query is made using the first line of the .WRK file - this will 
currently fail for post.demon.co.uk so the client tries *.demon.co.uk
and of course this matches the #*?!ing wildcard MX so the mail goes to
punt-2 :(

Presumably it's been this way since the MX list for post.demon.co.uk
disappeared (which must be some time ago now) and the wildcard has
been in place.

FWIW I've had it fixed here for a couple of years and never noticed
any of my list mail go astray.  (There is another bug in the MX code
when CNAMEs are present for the domain queried - I think it's possible
but unlikely that this could cause mail to be routed to a wrong
address).

At the moment I can't see a way that it could fail for 
post.mail.demon.net though (although it would try *.mail.demon.net,
*.demon.net and *.net first before the A record) ...

Cheers, Graham.
-- 
Graham E. Kinns
Graham@grempc.demon.co.uk