> Look at this stupid set of DNS records:
>
> ibase.com. MX 20 mailhost.ibase.com.
> ibase.com. MX 30 inbound.firstnet.net.uk.
> ibase.com. MX 55 relay.firstnet.net.uk.
> ibase.com. MX 666 non-mail.ibase.com.
Simple, don't touch MX's with a 666 priority! =)
> ibase.com. MX 10 mail.ibase.com.
> mail.ibase.com. A 62.105.94.141
> mailhost.ibase.com. A 62.105.94.141
> non-mail.ibase.com. A 127.0.0.1
> inbound.firstnet.net.uk. A 212.103.224.21
> relay.firstnet.net.uk. A 212.103.224.41
>
> Somebody I know discovered them when trying to make use of @mx_any in an
> Exim configuration. Because of the 127.0.0.1 the domain ibase.com
> matches @mx_any.
So now I know why I don't use it =)
> Does the list think that the default for @mx_any matching should be
> changed to ignore 127.0.0.0/8 and 0.0.0.0 as is the case for the
> dnslookup router in the default configuration? (It's a very simple
> patch.) Does there need to be an option?
Keeping in tune with configurability, I would have to vote to have the
option (even though I wouldn't use the option).
> And finally, to satisfy my curiosity: what on earth do you suppose the
> above set of records is supposed to achieve?
They're evil! =)
--
Lab tests show that use of micro$oft causes cancer in lab animals
