Primary account not getting email, secondary can

ProWebUK said:
did you su - to root?

Under the login you are using ensure you can modify files such as /etc/hosts and /etc/sysconfig/network (they are the 2 main files involved with chnaging the hostname.)

Chis
Click to expand...

i was able to modify them.

should my hosts file have the following in it?
Usage: grep [OPTION]... PATTERN [FILE] ...
Search for PATTERN in each FILE or standard input.
Example: grep -i 'hello world' menu.h main.c

Regexp selection and interpretation:
-E, --extended-regexp PATTERN is an extended regular expression
-F, --fixed-strings PATTERN is a set of newline-separated strings
-G, --basic-regexp PATTERN is a basic regular expression
-P, --perl-regexp PATTERN is a Perl regular expression
-e, --regexp=PATTERN use PATTERN as a regular expression
-f, --file=FILE obtain PATTERN from FILE
-i, --ignore-case ignore case distinctions
-w, --word-regexp force PATTERN to match only whole words
-x, --line-regexp force PATTERN to match only whole lines
-z, --null-data a data line ends in 0 byte, not newline
Click to expand...


and when i put 'server' as a subdomain for 'server.main.com', should i 'A' it to 127.0.0.1 or the server ip?


and i also just got this message from direct admin..
Subject: This is e-mail notification to warn you that your hostname is setup improperly on your system.

Your hostname, main.com, and the servername you have set in DirectAdmin, server.main.com, do not match. It is recommended that these two values are the same.

Solution:

Either change the servername in DirectAdmin or run the 'hostname.sh' script via ssh to change your hostname
Click to expand...
 
Last edited:
young said:
i was able to modify them.

should my hosts file have the following in it?

Usage: grep [OPTION]... PATTERN [FILE] ...
Search for PATTERN in each FILE or standard input.
Example: grep -i 'hello world' menu.h main.c

Regexp selection and interpretation:
-E, --extended-regexp PATTERN is an extended regular expression
-F, --fixed-strings PATTERN is a set of newline-separated strings
-G, --basic-regexp PATTERN is a basic regular expression
-P, --perl-regexp PATTERN is a Perl regular expression
-e, --regexp=PATTERN use PATTERN as a regular expression
-f, --file=FILE obtain PATTERN from FILE
-i, --ignore-case ignore case distinctions
-w, --word-regexp force PATTERN to match only whole words
-x, --line-regexp force PATTERN to match only whole lines
-z, --null-data a data line ends in 0 byte, not newline
Click to expand...
Click to expand...

No, it should look like:

SERVER_IP |TAB| host.name.com |TAB| host
127.0.0.1 [TAB| localhost.localdomain |TAB| localhost

(replace |TAB| instances with your tab key)

Also check /etc/sysconfig/network and ensure your hostname is correct.

I also advise you to add an A record for your hostname also, yes.

Chris
 
thanks for your help. changing the hostname to server.main.com seems to work.
 
now im not getting emails from cron daemon to the root account.

Cron <root@xxxxx> run-parts /etc/cron.daily

do i have to add an mx for the server.main.com subdomain?
 
Hello,

"root" isn't an allowed user. Just create an alias like:

root: admin

in the /etc/aliases file to forward root emails somewhere else.

John
 
actually i didn't have a root email pop account. i think the catch all caught emails sent to root.

i can send emails to [email protected] and the admin pop account catches the emails. but i cant get emails for [email protected] which is where i think the cron daily emails are being send to.
 
Did you setup the root forwarder in /etc/aliases ? Sounds to me like you're refering to the /etc/virtual/domain.com/aliases file.

John
 
DirectAdmin Support said:
Did you setup the root forwarder in /etc/aliases ? Sounds to me like you're refering to the /etc/virtual/domain.com/aliases file.

John
Click to expand...

in /etc/aliases, added:

root: admin

restarted exim and proftpd

sent mail to [email protected]

Returned mail: delivery problems encountered

didn't work
 
this is the log during the time the daily cron email should be sent.

2004-01-21 02:53:02 End queue run: pid=19918
2004-01-21 03:02:02 1AjDJI-0005LB-SJ <= [email protected] U=root P=local S=754
2004-01-21 03:02:02 1AjDJI-0005LB-SJ User 0 set for local_delivery transport is on the never_users list
2004-01-21 03:02:02 1AjDJI-0005LB-SJ == [email protected] R=localuser T=local_delivery defer (-29): User 0 set for local_delivery transport is on the never_users list
2004-01-21 03:02:02 1AjDJI-0005LB-SJ ** [email protected]: retry timeout exceeded
2004-01-21 03:02:02 1AjDJK-0005Lz-Po <= <> R=1AjDJI-0005LB-SJ U=mail P=local S=1665
2004-01-21 03:02:02 1AjDJK-0005Lz-Po User 0 set for local_delivery transport is on the never_users list
2004-01-21 03:02:02 1AjDJK-0005Lz-Po == [email protected] R=localuser T=local_delivery defer (-29): User 0 set for local_delivery transport is on the never_users list
2004-01-21 03:02:02 1AjDJK-0005Lz-Po ** [email protected]: retry timeout exceeded
2004-01-21 03:02:02 1AjDJK-0005Lz-Po [email protected]: error ignored
2004-01-21 03:02:02 1AjDJK-0005Lz-Po Completed
2004-01-21 03:02:02 1AjDJI-0005LB-SJ Completed
2004-01-21 03:08:02 Start queue run: pid=20885
2004-01-21 03:08:02 End queue run: pid=20885
Click to expand...
 
Your hostname, server.domain.com, and the servername you have set in DirectAdmin, hub.domain.org, do not match. It is recommended that these two values are the same.

Solution:

Either change the servername in DirectAdmin or run the 'hostname.sh' script via ssh to change your hostname

how to change servername in DirectAdmin ??
 
You must log in or register to reply here.
Back
Top