Primary account not getting email, secondary can

[Mindlash]

As the subject implies. I'm having a difficult time tracking down why a particular user is having their emails deffered.

Example:
Owner of domain ower@domain.com is set up by default when the domain is created. When someone emails this person, they get an email back with simliar content:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

owner@dedicated.server.com
(ultimately generated from owner@domain.com)


If I were to create a new account test@domain.com that person can receive emails just fine, with none getting kicked back to the sender.

mainlog shows the email supposedly being sent properly, but also shows the email being sent back.

Example:

2004-01-02 00:15:24 1AcHee-00040L-JV <= sender@sender.com H=(senders.domain.com) [67.67.67.67] P=esmtp X=TLSv1:AES256-SHA:256 S=1364 id=CBENJAIAHIONLIODPLPLCEBKDAAA.sender@sender.com
2004-01-02 00:15:24 1AcHee-00040L-JV ** receiver@receivers.server.com <receiver@receiver.com> R=virtual_aliases:
2004-01-02 00:15:24 1AcHee-00040P-Lz <= <> R=1AcHee-00040L-JV U=mail P=local S=2235
2004-01-02 00:15:24 1AcHee-00040L-JV Completed
2004-01-02 00:15:24 1AcHee-00040P-Lz => sender@sender.com R=lookuphost T=remote_smtp H=sender.com [12.12.12.12] X=TLSv1:AES256-SHA:256
2004-01-02 00:15:24 1AcHee-00040P-Lz Completed

shortened version:
<= sender
** receiver
<= <>
Completed
=> sender
Completed

I don't get it.

Anyone?

[DirectAdmin Support]

Hello,

Make sure that nobody has created a domain as the hostname.. ie: dedicated.server.com. If you see that domain anywhere in DA, then you'll have to delete it, because all the system account emails would end up landing in catch-all for the dedicated.server.com domain account. This is because systemuser@domain.com is basically just a forwarder to systemuser@dedicated.server.com... where dedicated.server.com must NOT be in the /etc/virtual/domainowners file.

John

[Mindlash]

Hi john, thanks for the reply.

/etc/virtual/domainowners shows the proper domains, and non that look out of the ordinary.

[DirectAdmin Support]

Hello,

Is your hostname in that file?
If so, remove it.

To find out what it is, just type "hostname"

John

[Mindlash]

OOOH.. I see.

yeah

serverd1.myserver.com: webadmin



remove that entire line?

[DirectAdmin Support]

Yup :)

John

[Mindlash]

I'll give that a shot... thank you :-)

Anything I have to restart for this to take affect?

I did a:
service exim restart

:-)

[DirectAdmin Support]

Don't think you need to restart anything :) The file is checked every time.

John

[lucienj]

hi guys,
im having the same prob, but i have no clue what you were talking about to fix the prob cause im kind of a new-bie

none of the email accounts that i added will get mail.

is there anyway you can break it down for me?

[S2S-Robert]

That's a different problem, since his virtual accounts did get e-mails.

is your domain propagating correctly? If you do a ping on your domain does it show your ip address?

if you login using webmail http://domain.com/webmail/ do you see the e-mail there?

[lucienj]

the email account is there but theres nothing in it....
and the test emails still bounce:mad:

[DirectAdmin Support]

Hello,

Go through 4 steps I posted here and see if that helps.

http://www.directadmin.com/forum/showthread.php?s=&threadid=128&highlight=email+hostname+resolve

Also, go to www.dnsreport.com for dns/mail debugging.

John

[quackweb]

Hello,

I'm having the same problem as the original poster. Our hostname is whatcanbehere.com and I had a reseller account made for it. Before I use to get all the user@theirdomains.com emails from the catch-all email account I setup at whatcanbehere.com. Now I've deleted that account but my users still cannot receive email on their primary accounts, only other pop accounts made by them. I've check the domainowners files and whatcanbehere.com is no longer in it. Any ideas on how to fix this problem? Thanks for any advice.

Thanks,

Toph Lazarz
Quack Web Inc.
http://www.quackweb.com

[young]

Originally posted by quackweb
Hello,

I'm having the same problem as the original poster. Our hostname is whatcanbehere.com and I had a reseller account made for it. Before I use to get all the user@theirdomains.com emails from the catch-all email account I setup at whatcanbehere.com. Now I've deleted that account but my users still cannot receive email on their primary accounts, only other pop accounts made by them. I've check the domainowners files and whatcanbehere.com is no longer in it. Any ideas on how to fix this problem? Thanks for any advice.

Thanks,

Toph Lazarz
Quack Web Inc.
http://www.quackweb.com

i'm having the same problem as quackweb.

the admin's or main domain.com's catch all is getting the reseller's mail.

admin pop account name is admin.
reseller pop account name is like reseller. it isn't reseller@reseller.com.

emails that sent to reseller@reseller.com and that is forwarded to reseller@reseller.com is caught by the catch all.

sending email to reseller@topdomain.com goes to the catch all

[DirectAdmin Support]

Hello,

The easy way to fix it, is to change your hostname from domain.com to server.domain.com through the Admin Settings in DirectAdmin.

John

[young]

Originally posted by DirectAdmin Support
Hello,

The easy way to fix it, is to change your hostname from domain.com to server.domain.com through the Admin Settings in DirectAdmin.

John


still isn't working when i do that.

should i move everything in
/etc/virtual/main.com/ to /etc/virtual/server.main.com/ ?

do i have to add the 'server' as a subdomain?

when i change the hostname should i change it from directadmin -> server settings or is there some other way to change the hostname that appears when you use the hostname command?

[DirectAdmin Support]

Hello,

When you change your hostname through the admin settings, it will create all the required files, so no moving/copying is required. You will need to make sure that the A record for "server" does exist, as most email servers will refuse mail from a non-resolving hostname, adding a subdomain would work.

You can change it from the ssh shell using /usr/local/directadmin/scripts/hostname.sh (it's what DA uses). It changes a few files so I recommend using that over manual changing.

John

[S2S-Robert]

Originally posted by DirectAdmin Support
Hello,

When you change your hostname through the admin settings, it will create all the required files, so no moving/copying is required. You will need to make sure that the A record for "server" does exist, as most email servers will refuse mail from a non-resolving hostname, adding a subdomain would work. And I believe it's important to have a reverse DNS in place as well, usually the colo centre does this for you on request.

[young]

Originally posted by DirectAdmin Support

You can change it from the ssh shell using /usr/local/directadmin/scripts/hostname.sh (it's what DA uses). It changes a few files so I recommend using that over manual changing.

John


[root@main scripts]# ./hostname.sh server.main.com
Setting hostname to `server.main.com'
hostname: you must be root to change the host name
[root@mainscripts]#

[ProWebUK]

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

[young]

Originally posted by ProWebUK
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

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




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

[ProWebUK]

Originally posted by young
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



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

[young]

thanks for your help. changing the hostname to server.main.com seems to work.

[young]

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?

[DirectAdmin Support]

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

[young]

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 root@mymaindomain.com and the admin pop account catches the emails. but i cant get emails for root@server.mymaindomain.com which is where i think the cron daily emails are being send to.

[DirectAdmin Support]

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

[young]

Originally posted by DirectAdmin Support
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

in /etc/aliases, added:

root: admin

restarted exim and proftpd

sent mail to root@server.myserverdomain.com

Returned mail: delivery problems encountered

didn't work

[DirectAdmin Support]

Hello,

delivery problems encountered

more specifically?

Check /var/log/exim/mainlog for the exact error message.

John

[young]

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 <= root@server.mymaindomain.com 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 == root@server.mymaindomain.com 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 ** root@server.mymaindomain.com: 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 == root@server.mymaindomain.com 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 ** root@server.mymaindomain.com: retry timeout exceeded
2004-01-21 03:02:02 1AjDJK-0005Lz-Po root@server.mymaindomain.com: 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

[young]

how do i change the cron jobs setting so it sends emails to the right address? so it will send to root@main.com instead of root@server.main.com

[ProWebUK]

pico -w /etc/crontab

or alternatively just run:


echo -e "root:\tuser@email.com" >> /etc/mail/aliases


Replacing user@domain.com with your working email address

Chris

[frednoob]

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 ??

[DirectAdmin Support]

Admin Level -> Admin Settings -> Server Name

Also, this is a good checklist to go through to ensure everything is correct:
http://help.directadmin.com/item.php?id=16

John