Disable the local delivery

BlueCola

Verified User
Joined
Jan 12, 2012
Messages
72
Dear,

Today someone added the domain of a populair ISP to his domains (as a joke, ofcourse he didn't own this domain). Other customers where complaining that they couldn't send any more mail's to this domain. After some research, I found out what 'local delivery' was. Now is my question: how do I disable this?

Best Regards,
Marijn Kortstra
 
You'd better use

Code:
/usr/local/directadmin/data/templates/custom/forbidden_domains.list

just add domains there, and nobody will be able to add any of them to a hosting account, and enable

Code:
check_subdomain_owner
 
To disable the local delivery you should use smarthost route in exim on a server with DA. In this case you should have your own mail-relay, or ask your DC.
 
You'd better use

Code:
/usr/local/directadmin/data/templates/custom/forbidden_domains.list

just add domains there, and nobody will be able to add any of them to a hosting account, and enable

Code:
check_subdomain_owner

Ok, will do that. Thanks for the subdomain suggestion, I will enable it. But I will have a problem when I do it. If someone orders a hosting package without a domain, i let the API make a subdomain of my hosting company's domain. Is this than still possible (trough API)? Or how can I whitelist that domain?
To disable the local delivery you should use smarthost route in exim on a server with DA. In this case you should have your own mail-relay, or ask your DC.

Correct me if i'm wrong, smarthost route is making another server the mailhost, isn't it?
 
Correct me if i'm wrong, smarthost route is making another server the mailhost, isn't it?
Your server uses a smarthost to send outgoing email, and the smarthost server must know to accept all outgoing email from your server. It has nothing to do with incoming email, so I wouldn't call it the mailhost.

Note that a quick way to resolve the problem your user caused you without removing the domain would be to to uncheck the Use this server to handle my emails setting under MX Records for the domain. And of course warn the user.

Jeff
 
Your server uses a smarthost to send outgoing email, and the smarthost server must know to accept all outgoing email from your server. It has nothing to do with incoming email, so I wouldn't call it the mailhost.

Note that a quick way to resolve the problem your user caused you without removing the domain would be to to uncheck the Use this server to handle my emails setting under MX Records for the domain. And of course warn the user.

Jeff

Thanks for your quick response. With unchecking that box, what i'm actually doing is disable the local delivery for that domain? Isn't this possible to do for all domains?
 
Ok, will do that. Thanks for the subdomain suggestion, I will enable it. But I will have a problem when I do it. If someone orders a hosting package without a domain, i let the API make a subdomain of my hosting company's domain. Is this than still possible (trough API)? Or how can I whitelist that domain?

This might be a feature request, as for now it works globally without any exception, if nothing has changed since my last testing.

smarthost route is making another server

With smarthost you relay all outgoing emails through a self-standing SMTP server. And it would be much harder for your customers to deceive your mail-relay if you take care about separate DNS settings for your MAIL and Directadmin server.
 
This might be a feature request, as for now it works globally without any exception, if nothing has changed since my last testing.



With smarthost you relay all outgoing emails through a self-standing SMTP server. And it would be much harder for your customers to deceive your mail-relay if you take care about separate DNS settings for your MAIL and Directadmin server.
So, if I enable this setting, it wouldn't be possible to make subdomains for new orders? I'm gonna think about a second server for the SMTP, thanks for the information! :)
 
Thanks for your quick response. With unchecking that box, what i'm actually doing is disable the local delivery for that domain? Isn't this possible to do for all domains?
Sure you can disable local delivery for all domains, but then you better host incoming email for all domains on a different server, as none will be delivered on this server, as user scsi wrote in the original reply to this thread.

Jeff
 
Sure you can disable local delivery for all domains, but then you better host incoming email for all domains on a different server, as none will be delivered on this server, as user scsi wrote in the original reply to this thread.

Jeff

K, understood. Thank you all for your help, really usefull! :)
 
Back
Top