owner@domian.com can't recieve mail, but user@domain.com can ?!

[joris]

I've searched here but can't seem to find a solution.
Problem is:
I've created some domains with DA but I can't recieve any owner mails... For other users on those domains I can.

also in the "Pop Accounts" menu the login for the owner is just "owner" and for a user it is user@domain??

I tried owner and owner@domain but they don't show any mail.

[S2S-Robert]

Make sure the hostname of the server doesn't exist as a domain. I.E. Use server.domain.com instead of domain.com.

[joris]

hmm well my servername is da.kakatoo.com ... and not kakatoo.com or should it be server.kakatoo.com?

J!

[DirectAdmin Support]

Hello,

da.kakatoo.com should be fine as long as there are no domains on the server with that name (kakatoo.com is fine, but da.kakatoo.com isn't). Also, make sure that it resolves.. it doesn't currently resolve for me, so you need to add an A record for da.kakatoo.com.

If that's all fine, remember that the "owner" email login is just "username" .. and not "username@domain.com" ... "user@domain.com" is reserved for virtual pop accounts.

John

[philmcdonnell]

I have a reseller account I created that does not get email. But the account under the resellers domain do receive email fine. What did I do wrong?

Phil

[DirectAdmin Support]

Hello,

Go back to the top of this thread and start over :)

You probably have a hostname set that matches the domain that exists in DA. Set the hostname to a non-domain, ie server.domain.coin instead of domain.com. That way you can host domain.com through DA and receive email too.

John

[philmcdonnell]

Originally posted by DirectAdmin Support
Hello,

Go back to the top of this thread and start over :)

You probably have a hostname set that matches the domain that exists in DA. Set the hostname to a non-domain, ie server.domain.coin instead of domain.com. That way you can host domain.com through DA and receive email too.

John

No this is a weird problem... I have my server setup like this...

The main domain (server.domain.com) is the hostname... I also have the (domain.com) as a domain hosted.

Now I setup a reseller account - domain2.com with a username of john the default email is supposed to be john@domain2.com correct?

Well I don't receive any email at that address... This domain has nothing to do with the server or hostname.

I changed the reseller to login as a dummy name and setup a pop account for his real name (john@domain2.com) this works fine, but why doesn't the default (master-reseller) name receive email. I can login to the webmail with the name but nothing gets received.

Thanks,
Phil

[DirectAdmin Support]

Hello,

Note that a system account gets forwarded from the domain:

john@domain2.com -> john@server.domain.com

This is why the hostname cannot exist. All I can think of, is make sure that server.domain.com hasn't been added anywhere in DA (except the hostname field in the admin settings).

Failing that, just check /var/log/exim/mainlog to see where it's going.

John

[SeLLeRoNe]

ive got a question about this...

i can call server hostname like server.domain.com and have domain.com in directadmin? i can also create a subdomain called server that will be server.domain.com?

thanks

[jlasman]

i can call server hostname like server.domain.com and have domain.com in directadmin?
Yes.
i can also create a subdomain called server that will be server.domain.com?
Not recommended. Untested.

Jeff

[SeLLeRoNe]

ive tryed to delete server.domain.com from admin domain list (/server hostname is server.domain.com) but nothing changed, user@domain always get "unrouteable address" error.

Any idea?

Thanks

[DirectAdmin Support]

"Unrouteable address" means either the domain doesn't resolve, or else the daily limit has been reached, thus lookups fail.

To test the dns, type:dig MX domain.comThe dns servers used are specified in your /etc/hosts file. You can change them to 127.0.0.1 if you want to use your own nameserver.

If it's the daily limit being reached, then /etc/virtual/limit will have a non-zero value.. and the /etc/virtual/usage/usernmae will be the size in bytes of the number in the limit file. So for example, if you have a 200 email limit, that file would be greater or equal to 200 bytes (size is how we track usage)

John

[SeLLeRoNe]

my hosts file is

127.0.0.1 localhost.localdomain localhost
ServerIP server.domain.com




so i think that is correct, but, i didnt understand what ive to do with "dig MX domain.com" if create a mx record called dig or if dig is a line command, cause, in shell he say that is not a command...

thanks for ur support

[jlasman]

Dig is a linux/unix command. If it's not installed on your server you should install it; it's an important diagnostic tool. If you're not logged in as root your installation may not be able to find it. To find it try:
$ whereis dig
and then run it with the complete path.

Jeff

[jlasman]

The dns servers used are specified in your /etc/hosts file. You can change them to 127.0.0.1 if you want to use your own nameserver.
That's a rather simplistic answer these days, John.

If your local nameserver is also used as a caching nameserver then most DNS checking routines (including the ones used by companies verifying your eCommerce solution) will report that your DNS is exploitable. We've been recommending turning of caching in your local nameserver for over a year now, with this line:
recursion no;
as the bottom line of the options section of your named.conf file.

In fact, with this line in place your server isn't vulnerable to that now famous caching exploit lots of folk are writing about, simply because it isn't caching.

We recommend using either your upstream's nameservers, or if for some reason they don't work for you (they may not have been patched and may be vulernable) then that you use OpenDNS. If you use OpenDNS you do need to create an account, and add your server main IP#(s), and turn off their proxying, so their DNS will work properly in a server environment.

Jeff

[SeLLeRoNe]

>whereis dig
dig:
[16:46:27] root [/]
>apt-get install dig
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
E: Impossibile trovare dig

dig is not installed and with apt-get say that cannot found dig :)

Is debian 4.0, how can i install it?

thanks again for your patience

[scsi]

apt-get install dnsutils

[jlasman]

Googling apt-get dig found me this (http://linux.derkeiler.com/Mailing-Lists/Debian/2006-11/msg01957.html).

It should be in the dnsutils package. If it's not let's hope someone else responds; I don't use debian.

Jeff

[SeLLeRoNe]

fantastic,

for who need it too is easy to install, just apt-get install dnsutils

now, dig say this:

>dig MX crazynetwork.it

; <<>> DiG 9.3.4-P1.1 <<>> MX crazynetwork.it
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58014
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;crazynetwork.it. IN MX

;; ANSWER SECTION:
crazynetwork.it. 7200 IN MX 10 mail.crazynetwork.it.

;; AUTHORITY SECTION:
crazynetwork.it. 7200 IN NS ns1.crazynetwork.it.
crazynetwork.it. 7200 IN NS ns2.crazynetwork.it.

;; ADDITIONAL SECTION:
mail.crazynetwork.it. 7200 IN A 194.177.98.220

;; Query time: 8 msec
;; SERVER: 213.92.5.54#53(213.92.5.54)
;; WHEN: Tue Nov 11 20:27:27 2008
;; MSG SIZE rcvd: 106


is that correctly set?

[jlasman]

Is your server IP# 194.177.98.220? If so, then your mx record is pointing to your server.

Jeff

[SeLLeRoNe]

yes, that is ip server.. so i think that is correct but... user@domain account still not working :/

[jlasman]

All user accounts, or just that one?

Someone who knows and understands DirectAdmin email is going to have to log on to your server and figure out what is wrong.

Jeff

[SeLLeRoNe]

every user@domain got that error on 3 different server... same configurations.

Im gonna check logs so.. i hope to find something useful...

[vadimc]

i have a very similar issue, but a bit different.

1) I set up a new user from my main admin account via the HTM_ACCOUNT_USER_CREATE page
2) i set up a new domain for this user.

i would like to use the email user@newdomain.tld to send and receive emails, but unfortunatelly i cant login to the mailbox. emails are getting to the /var/spool/mail , but i cant retrieve them - where do i need to check on the server to see if there is a password for this user? when i go to change the password via the CP it doesnt mention anything about the email change.

just to confirm - if i add a new email account such as user2@newdomain.tld everything is working fine - i can log in via outlook and via squirelmail.

thanks

[vadimc]

sorry guys, i sorted it out by adding the new user's name to the /var/spool/virtual/newdomain.tld as a blank file :)

i figured it out by adding a new email user via the CP and then searched the server for the new user and there we go! directadmin rocks!

btw, to log in I use just the user and password, not user@newdomain.tld

:)

[vadimc]

spoke too early. i can log in from squrelmail and send mail via smtp, but unfortunately i cant login via pop3 - it prompts me for the password all the time - anyone has any suggestions please?

[vadimc]

all sorted - your KB had the solution - http://help.directadmin.com/item.php?id=134

[SeLLeRoNe]

in mail.log i just found those errors:

Nov 26 18:36:21 Psycho dovecot[28690]: auth(default): shadow(USER@DOMAIN,82.57.177.52): unknown user
Nov 26 18:36:21 Psycho dovecot[28690]: auth(default): passwd-file(USER@DOMAIN,82.57.177.52): unknown user

where else i can look?

[scsi]

You can ignore those errors.

[SeLLeRoNe]

mmmh ok, but when i sent email to USER@DOMAIN i receive that:

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:

USER@SERVER_HOSTNAME
(ultimately generated from USER@DOMAIN)
Unrouteable address
USER@SERVER_HSOTNAME
(ultimately generated from USER@DOMAIN)
Unrouteable address

[scsi]

I dont understand what you are doing but if you are trying to login to the user the account was created under they have no @domain as their login.

It will just be:

username

password

Unless you create a new pop3 account.

[SeLLeRoNe]

i know that, is not loggin into email, that is the error when i try to send an email to OWNER@DOMAIN example admin@domain.com

[scsi]

Strange OWNER@DOMAIN works on my server with no problems. Do you have the latest exim.conf and exim.pl.

[SeLLeRoNe]

i think yes, how can i check or update for be sure?

[jlasman]

If you're using SpamBlocker exim 3-beta, the latest version is available here (http://www.nobaloney.net/downloads/spamblocker/DirectAdminSpamBlocker3/exim.conf.3.1-beta). If you use SpamBlocker exim.conf version 2.x or the standard exim.conf file included with DirectAdmin, the latest version is available here (http://files.directadmin.com/services/exim.conf). Note that SpamBlocker 3-beta is only available for Dovecot/Maildir, and that the SpamBlocker exim.conf version 2 file by default only supports the mbox format and to support Dovecot/Maildir must be patched by this patch (http://files.directadmin.com/services/exim.conf.dovecot.patch).

The exim.pl file may be found here (http://files.directadmin.com/services/exim.pl).

Jeff

[SeLLeRoNe]

mmmh, im using exim with spamassassin, i would like to upgrade everithing, and pass to dovecot but i dont know how to do it and what that will change to my usual work and for my customers, i mean, ive some customers that created email into uebimiau and i would like to know if that will keep it fine...

[jlasman]

Changing to Dovecot on your server should NOT affect email stored in any UebiMiau. It might change dates or read-flags on other webmail solutions that use IMAP, but UebiMiau stores everything except the inbox in proprietary directories and files.

Jeff

[SeLLeRoNe]

So dovecot will be used as main and exim should be deleted right?

How can i make this upgrade?

[jlasman]

Exim is your mta (mail transport agent); it uses the SMTP protocol to deliver email across the Internet. It has nothing to do with delivery of email to local users using POP or IMAP.

Dovecot offers both IMAP and POP3 services; it has nothing to do with routing email across the Internet.

All three protocols are required. Installing Dovecot will delete the IMAP and POP3 servers currently running on your DirectAdmin server, and will replace them with Dovecot.

You must NOT remove exim. There is a required change to the exim.conf file. My SpamBocker 3-beta exim.conf file makes that change and only works with Dovecot. If you're using any other exim.conf file supplied by me or by DirectAdmin, then installing Dovecot using the procedure recommended by DirectAdmin will install the required change to exim.conf.

Instructions for converting can be found here (http://help.directadmin.com/item.php?id=143).

Jeff

[sintsu]

Hi all,
It's feel bad that still have to work even X'mas ...

I have the same problem that when I create a user or retailer account for example "cht" with a domain "cht.com", system will open a default mail account cht@cht.com.

My problem is the mail account cht@cht.com can send mail through webmail, but cannot receive any mail from others, and who send mail to cht@cht.com will receive a "permanent error message" from the sender's mail server with the content below

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:

cht@"myserver's domain"
(ultimately generated from cht@cht.com)
retry timeout exceeded
cht@"myserver's domain"
(ultimately generated from cht@cht.com)
retry timeout exceeded

------ This is a copy of the message, including all the headers. ------

Return-path: <sintsu@gmail.com>
Received: from rv-out-0708.google.com ([209.85.198.244])
by "myserver's domain" with esmtp (Exim 4.69)
(envelope-from <sintsu@gmail.com>)
id 1LFWFf-0004F5-Qs
for cht@cht.com; Thu, 25 Dec 2008 00:06:28 +0800
Received: by rv-out-0708.google.com with SMTP id k29so3189787rvb.8
for <cht@cht.com>; Wed, 24 Dec 2008 08:09:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:mime-version:content-type;
bh=EDEFTVSxV4y4zrK69cKDxBKm3ZVWhRbip4i6h6pgw/E=;
b=OT1aSQuh7PacJfYjHNT3YgpnpsuGhhqlBYHFukUuyVgt0UITUbky1qwBaWt/lqrvAj
kZ0l8csfkaEIAgW/2Fbn4y/0WPCfUyhVxIvp30hT9M5WfhYlDL6AUeV900kPniDiFaLZ
dsEk3wRClyAkVHFsc6CNtIBX4mn/XjkmKw4O4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=message-id:date:from:to:subject:mime-version:content-type;
b=UHR/vOEul6AxkR/uYy5ltkpWn5Djcx7G4zEOc/WDcic886ABCWrFUqv+Bmala6fR5N
4XKxbXDGvlE7jjkJziXYMsPGA3YnUrPdjjN1XxfvAgcJw214ZVoK0rhxOa9i00D1WGAs
Pb/du/uapQBGGONtQzH/PVlYqI2X+myTzza9c=
Received: by 10.141.153.16 with SMTP id f16mr4318356rvo.283.1230134985838;
Wed, 24 Dec 2008 08:09:45 -0800 (PST)
Received: by 10.140.44.6 with HTTP; Wed, 24 Dec 2008 08:09:45 -0800 (PST)
Message-ID: <5edf1e500812240809k1760f58ci9a70a75bf0f64962@mail.gmail.com>
Date: Thu, 25 Dec 2008 00:09:45 +0800
From: Sintsu <sintsu@gmail.com>
To: cht <cht@cht.com>


And my server's error message in /var/log/exim/mainlog is
2008-12-25 00:06:28 1LFWFf-0004F5-Qs <= sintsu@gmail.com H=rv-out-0708.google.com [209.85.198.244] P=esmtp S=2080 id=5edf1e500812240809k1760f58ci9a70a75bf0f 64962@mail.gmail.com T="test" from <sintsu@gmail.com> for cht@cht.com
2008-12-25 00:06:28 1LFWFf-0004F5-Qs == cht@"myserver's domain" <cht@cht.com> R=lookuphost defer (-1): remote host address is the local host
2008-12-25 00:06:28 1LFWFf-0004F5-Qs == cht@"myserver's domain" <cht@cht.com> R=lookuphost defer (-1): remote host address is the local host
2008-12-25 00:06:28 1LFWFf-0004F5-Qs ** cht@"myserver's domain" <cht@cht.com>: retry timeout exceeded
2008-12-25 00:06:28 1LFWFf-0004F5-Qs ** cht@"myserver's domain" <cht@cht.com>: retry timeout exceeded

But every virtual user account under the domain "cht.com" can normaly receive mail from others, I also try to reinstall dovecot but it doesn't work at all, really hope some one can give me a hint to solve this annoying error, thanks alot.

[DirectAdmin Support]

Hello,

I'm guessing your hostname is not set properly.
This is the related guide:
http://help.directadmin.com/item.php?id=16

I'm assuming that the hostname is set to domain.com, when you'd want it to be set to something like server.domain.com

Admin Level -> Admin Settings -> Servername

to change it.

Make sure it resolves as well.
The hostname value must not be a domain you're using.. so cht.com cannot be your hostname, but server.cht.com can be.

John

[sintsu]

Thanks for your reply,
At the beginning of the DA installation, I saw the readme file wrote that cannot use domain.com as the server's domain, so I already use xxx.domain.com as my server's domain, and cht.com is my client's domain not my domain registry in the DA, so I'm surprised this situation happens.
Is there any possibility that could cause this situation ? thanks.

[njm]

if you guys still having this problem that owner of a domain..can't recieve email....and in EXIM mainlog you get a FROZEN msgs...

just change (inside DA panel) the owner of the domain password...

and everything will flow...i don't know why..but i had that problem in the beginning...i've changed domain owner passwd and all went well..

Stay Fresh!

[jlasman]

Interesting. The only way that could happen is if you didn't download email and filled up all the allowed user space. Then if with a new password you could download your email, you'd get the space back.

If email is frozen it's because it cannot be delivered to a mailbox. Mailbox delivery has NOTHING at all to do with whether or not a user can log in with a password to get the email, except of course, if because of that the mailbox gets filled.

Jeff