Topic: Turn off mail for a domain 6.0

[Jim Huneycutt]

I know I've seen this in the forum but no amount of searching has turned it up again. I have cases where virtual domains are hosted for the web site only and email is handled outside of the SME servers, typically by using forwarding services such as that at easyDNS.

I need to tell the (6.0) SME server to  "look up the external mx record and deal with it like you would for an 'external' domain", and ignore the fact that the domain is hosted internally.

Perhaps the only way is to install the Dungog vdomain rpm, which I have not used. If I can avoid installing a module on a running production server, I would rather do that. I need to solve this in a day or so and that is not enough time to test the effects of a new rpm. I was hoping for a simple config setting or similar parameter.

Thanks to anyone who can tell me how to do this.

jim

[Boris]

You don't have to disable e-mail on SME if you don't want to use it.
For external senders don't point MX record to your(clients) SME server and e-mail will not be routed to it. For internal users you can configure their e-mail client program like you normaly would if where is no SME in place at all, by pointing it to what ever their e-mail providers server are.

[Jim Huneycutt]

Thanks for the reply, Boris. Here are some more details to clarify the situation.

I.) The MX record for "mydomainA" is setup properly at easyDNS to use the easyDNS servers and email forwarding  to Client-A's 15 ISP email boxes.

2.) "Mydomain" is hosted on an SME 6.0 server at another related site - call it Client-B.

3.) When external users (those not at the Client-B site) send email, eveything is fine.

4.) When Client-B users (from behind the SME server) try to send email to Client-A users, the mail bounces with "unknown user" since the SME server never looks "outside" its own managed domains for the MX record.

My question is how to "force" the SME server to go outside for this domain and thus deliver email from Client-B to Client-A. Again, I think I saw this solution here but now can no longer find it.

I know I can setup duplicate forwarding addresses at the SME server, and have done this in similar cases where I have only a couple of email addresses. But this is double maintenance and a source of problems if one of the addresses changes and both forwarding addresses are not updated.

I should have added these details in the first post but was trying to avoid a long post.
Thanks again for any and all replies.
jim

[Boris]

> 4.) When Client-B users (from behind the SME server) try to send email to Client-A users, the mail bounces with "unknown user" since the SME server never looks "outside" its own managed domains for the MX record.

This is because e-mail program (outlook, eudora or whatever they use) configured to use SME server as their e-mail server. Change settings on the clients e-mail program to use ISP's e-mail server.

[Jim Huneycutt]

Thanks again, Boris. I understand your point, but in this case hte Client B that has the SME server is actually a small ISP. Therefore they are the end of the line and I must use SME for email handling. I just want to tell it to skip this one domain, and maybe more later.

Thanks,
jim

[marco]

Are you using mail.domain.com for your servers in the e-mail client?
Is the mail being handled by another server at a static address?
If so, you can setup pop, smtp, etc.  as a hostname in the Hostnames & Addresses section of the server and have it point to the remote e-mail server (or modify the mail setting address)so that everyone sees the server address you want them to see.

HTH

[ryan]

If you have to make this work, I would set up a second SME server on low end hardware just for SMTP services.  Make this SME server domain:  mydomain.lan instead of .com.  or it can be a completely different name.

ryan