Problems with mails to domains prior to moving

graphicscompany

Verified User
Joined
Mar 26, 2009
Messages
10
Hello, I am using DirectAdmin as a reseller.
Sometimes when a new client signs up with moving his domain from an other provider, he uses the email from this domain as his primary address.

When creating the account in DirectAdmin the email with login details goes to the newly created account, and not to the user's email inbox at his current provider. So he doesn't get the email with login details.

How can I prevent the email from going in to the mailbox of the account I just created? I need the smtp to look out of my own server before mailing it to a account on the same server...

Thanks in advance.
 
Hello,

When sending email MTA (Exim) checks if the host exists locally.
You can try to configure smart host with local exim and send emails via remote relay.
 
If you have no root access, another way is to state on your order system/form that new clients need to use another email address (ie. not the domain they intend to transfer to you). Thats the only work around I can think of.
 
Yes, that would be another option, but not my prefered option. ;)
Only if nothing else is possible, I could do that.

I have also send an email to the admin to request the change in exim.conf.
 
In the dns section there should be a check box to use external email server. I dont know if its possible to set automatically upon account creation.
 
In the dns section there should be a check box to use external email server. I dont know if its possible to set automatically upon account creation.

That's a good notice.

I think, it's possible to catch a moment, after domain's been added while creating a new account with post/pre scripts, disable «Local Mail Server» temporary, and later enable again after a greeting email's been send.

And take care about resolv.conf, use external DNS.

****************

Sorry, I've forgotten, the topic starter is a reseller.
 
The reseller's host can probably make the change.

@graphicscompany:

Are you using an automated signup system as a reseller? If you're setting up the site manually you shouldn't have the problem because the user isn't yet on the system when he's sent the email; you can uncheck the MX Settings solutions before sending the email, and then send it afterwards.

If the setup is done automatically through some kind of billing package, then setup the billing/setup package to use a different mailserver to send the email. Or host the billing/setup package on a different server.

If none of these ideas work please explain why not so we can help you further.

Jeff
 
Never thought of that, but then again, when you add the domain/user to DA, you still need to disable the MX setting, otherwise the welcome email will sit on that server, or even fail because no email accounts exists except for the main account, plus catch-all is set to Fail by default? Am I wrong?

Just we advise not to use the actual domain as their sign-up email because of this.
Or host the billing/setup package on a different server.
Off-topic but... This is our setup actually, our billing/help/status are on a separate server, so that if other servers go down, they can submit tickets etc.
 
Last edited:
@Peter Laws:

Are you missing something in my reply, or am i missing something in yours? Does your billing software send the welcome email? I'm presuming you are (as I presume most of us are) using our billing software to send a welcome email and have it turned off in DirectAdmin.

Not true?

Jeff
 
So, you mean, the welcome email that DA sends on account creation can be sent via API elsewhere? If so, I never knew that. If not, by all means explain, or link us :)
 
We use a billing software, that sends a greeting email instead of Directadmin.
Account is created via API with option "notify=no" and billing system sends an email, using SMTP. So the discussed problem is not our case.

The other thing, we forbidden our clients to use an email on domain, that is hosted by us. It is hard to inform the client on disc overusage and if account is blocked for any reason.
 
We use a billing software, that sends a greeting email instead of Directadmin.
May I ask which?

I guess the DA API pushes out all the user details and package details, such as disk space, email accounts, etc for the email via billing software?
 
May I ask which?

Sure, it is «rootpanel» (www.rootpanel.ru)

I guess the DA API pushes out all the user details and package details, such as disk space, email accounts, etc for the email via billing software?

Nothing of that kind. The billing system is very cheap. It allows users to order shred/vps/dedicated hosting, domains (send a greeting email with all ips, login and password to directadmin) and other services and pay invoices.

Now we gonna integrate some functions of this billing into directadmin.
 
This is going way off-topic.

I use ClientExec for billing and domain stuff...

I'm just thinking how the tokens get used in the email, like |nsubdomains|, etc, but I'm guessing I'm being too complex. Is the email manually written for each package?....

We manually add accounts to DA, although ClientExec has the API, and as I use multiple shared IPs per reseller for users, not to mention owned IPs, I'm not sure the API it has is up to date enough.
 
We have never used «ClientExec». I can say nothing about that. As far as I know DA's API is quite up to date. I've never seen any problem, while using it.

So coming back to the topic, it would be nice to have a possibility to make DA to send emails via remote SMTP (selected on Admin/Reseller level). It would solve this and some more problems. Because some clients do not inform us, when moving domains to other hosting before a paid period is over. Thus a mail (send from DA) could not be delivered to actual e-mail on other hosting.
 
So coming back to the topic, it would be nice to have a possibility to make DA to send emails via remote SMTP (selected on Admin/Reseller level).
How about making this a Feature Request so we can have a discussion on it.

Jeff
 
Back
Top