not getting cron.daily

R

rldev

Verified User
Joined
May 26, 2004
Messages
1,003
I'm not certain what the problem is, but suddenly I stopped receiving cron.daily emails. cron.daily is indeed running. DA Support pointed me to the following article:

http://help.directadmin.com/item.php?id=16

I really don't understand some of the things in this article.

3) The hostname must *not* be in the /etc/virtual/domainowners file.

5) The directory /etc/virtual/hostname must exist.. (eg: /etc/virtual/server.domain.com). It must not contain any files.

6) Any domains that you want to use for email (eg: domain.com) must be in both the /etc/virtual/domains file and the /etc/virtual/domainowners file. The directory /etc/virtual/domain.com must exist and the files /etc/virtual/domain.com/passwd and /etc/virtual/domain.com/aliases exist.


How is mail supposed to work for the hostname if you follow such directions? If you want to use mail for the hostname then how does point number 5 make any sense? I removed these files and of course mail did not work. with no passwd or aliases file, mail can not work properly for the domain. Perhaps I am missing something.
 
Your hostname should NOT be a domain name, and it should not accept mail.

What's your hostname?

Is it something like example.com, or something like host.example.com?

If the former, it's wrong.

Yes, the information in the DA knowledgebase is right.

However, concerning item five, we do have an aliases file (only) in that directory, and it contains:
Code: 
abuse: admin
hostmaster: admin
postmaster: admin
webmaster: admin
root: admin
bin: admin
daemon: admin
nobody: admin
ftp: admin
operator: admin
uucp: admin
admin: [email][email protected][/email]

where of course [email protected] is replaced with a real email address. That way email to all of these specific addresses will work, and get forwarded to the admin alias.

Note that you cannot have a wildcard in the aliases file or all email for the server will stop working.

Jeff
 
Thanks Jeff,
The hostname is tp1.web-host-servers.com

I'm not sure why I thought this should be setup under the user account for the master DA admin account. I guess I will have to change my setup.

So I am assuming in a two server setup.

server name: tp1.web-host-servers.com
master domain: web-host-servers.com


server 2:

server name: tp2.web-host-servers.com
master domain: ???

name servers: ns1.web-host-servers.com
ns2.web-host-servers.com
 
I'm not sure what you mean by:
I'm not sure why I thought this should be setup under the user account for the master DA a
admin account. I guess I will have to change my setup.[/quote
so I won't comment on it. Can you clarify what you mean?

Each server must have it's own hostname, which could be:

one.example.com

and

two.example.com

or

one.example.com

and

one.exampletwo.com

But I prefer to use the same domain; all my servers are hosted at ns-one.net; they have hostnames da1, da2, da3, etc.

Jeff
Click to expand...
 
Yes and this is what I am trying to do as well. tp1, tp2, tp3 etc.

What do you set as the main domain for each server? In my case I want resellers to be using web-host-servers.com. For my clients I want to use my own domain name.
 
Last edited:
The complete hostname will always show up in mail headers, etc., so if you're doing reselling it's important that you use a relatively anonymous name that doesn't point users directly to your own reselling site.

Register a unique but innocuous domain, for example: unitedwebhostingservices.net (which is available as I write this) and use tp1.unitedwebhostingservices.net, etc.

Jeff
 
You must log in or register to reply here.
Back
Top