On Tue, 09 Jul 2002 11:09:48 GMT MJ Ray wrote:
Something is doing a double-lookup to resolve the name, perhaps. I doubt that, as I don't think lists had its own IP before. Other possibility is incorrect details in the subscription info. Can a recent subscriber confirm or deny that, please?
lists.alug.org.uk hasn't had it's own IP address before? I don't believe my configuration was any different to Jonathan's. It doesn't have it's own IP address now - look:-
lists.alug.org.uk is an alias for lists.blackcatnetworks.co.uk. lists.blackcatnetworks.co.uk has address 212.135.138.137 and 212.135.138.137 resolves to terry.blackcatnetworks.co.uk.
Can we block main@anyotherdomain at the MTA on that computer, please? My first suggestions would be to either use header filters or virtual-host alias files.
I would seriously consider trying Mailman 2.1. Despite being a beta, it is considered to be stable and it has *proper* per domain virtual hosting (hooray!) which 2.0.11 and below doesn't do that well.
Regards,
Martyn the Postman