interfasys
Verified User
I would find it very useful to be able to disable the MX server for aliases, because when you register a domain name you don't necessarily want to get emails through that domain, but rather through the main one.
FR: Option to disable MX server for domain pointers
- Thread starter interfasys
- Start date
nobaloney
NoBaloney Internet Svcs - In Memoriam †
I don't see how you can disable the MX server for the alias, because if you remove the MX record for a (sub)domain, mailservers will use the A record. I think that's even in the RFCs somewhere, and even if it isn't, there are a lot of broken domains out there so it's probably a good idea that mailservers do that.
And even if it's not a good idea, it's how the world works, so if you're going to accept mail you're going to live with it.
Once mail arrives at your server you can block it with a local blocklist; see my ACLs and local blocklists in exim.conf now for examples on how to do that.
Jeff
interfasys
Verified User
I already add those domain names to a list and block messages, but it's not automatic, so I thought, a little tick box in the domain pointer form to decide whether we accept messages for that domain or not would be nice.
What I meant is to not add the domain to /etc/virtual/domains, so that messages are rejected since nobody is listening on the other end.
That's what DA does when you stipulate that your MX is a remote one.
What I meant is to not add the domain to /etc/virtual/domains, so that messages are rejected since nobody is listening on the other end.
That's what DA does when you stipulate that your MX is a remote one.
nobaloney
NoBaloney Internet Svcs - In Memoriam †
I suppose it would be nice; DirectAdmin has never managed anything in my SpamBlocker exim.conf file, and it's the SpamBlocker exim.conf file which handles the blocklists.
There were two exim.conf plugins out there; one was free and one had a cost. I'm not certain but I believe the one with a cost is no longer available.
Neither is available yet for SpamBlocker3.
In any event, since there'll be some changes once SpamBlocker3 is final (you don't have to remind me how late I am) I'd suggest to DirectAdmin staff that they wait until it's finished and they've decided whether to use it by default or not, before implementing this.
Jeff
There were two exim.conf plugins out there; one was free and one had a cost. I'm not certain but I believe the one with a cost is no longer available.
Neither is available yet for SpamBlocker3.
In any event, since there'll be some changes once SpamBlocker3 is final (you don't have to remind me how late I am) I'd suggest to DirectAdmin staff that they wait until it's finished and they've decided whether to use it by default or not, before implementing this.
Jeff