Some emails are not working

Well, I still don't know why after each reboot, the ehosting.ro ehosting appears after 127.0.0.1?

Is this normal?

How about your /etc/hosts file guys? It looks the same as mine with the domain name after the local address, or after the local address 127.0.0.1, you have only localhost localhost.localdomain.
 
Here's what mine looks like, from my live DirectAdmin system:
Code: 
[jlasman@da1 etc]$ ls -al hosts
-rw-r--r--    1 root     root          177 Nov 22 16:51 hosts
[jlasman@da1 etc]$ cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
65.58.240.229           da1.ns-one.net
[jlasman@da1 etc]$
and from my testbed system:
Code: 
[jlasman@datest etc]$ ls -al hosts
-rw-r--r--    1 root     root          181 Oct 10 11:21 hosts
[jlasman@datest etc]$ cat hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
67.112.189.218          datest.ns-one.net
[jlasman@datest etc]$
Jeff
 
Well, as I told before when the file have these lines, works good:

Code: 
127.0.0.1 localhost localhost.localdomain
64.5.40.184 server.ehosting.ro

But after each reboot the first line is changed and ehosting.ro ehosting is added after the 127.0.0.1 :confused:, so the new file becomes:

Code: 
127.0.0.1 ehosting.ro ehosting localhost localhost.localdomain
64.5.40.184 server.ehosting.ro

I just don't know what is the problem.
 
Last edited:
Hello,

It must be a script somehwhere doing it. It will just have to be found and put to rest. Just search the scripts for reference to /etc/hosts and hopefully, it can be tracked down. Perhaps the people you got the server from might know where the script is.

John
 
Ohhh, I just rapaired a mistake of the last post, now you should understand better, what is happening. The ehosting.ro ehosting is added after 127.0.0.1.

And in Direct Admin it shows that the server's name is server.ehosting.ro (probabily it takes the data from /usr/local/directadmin/conf/directadmin.conf), but if I type hostname in SSH it shows ehosting.ro.

But remember, if I change the server's name from DA to ehosting.ro, and the change it back to server.ehosting.ro (I think there are 2 reboots there), it works fine, and the file /etc/host does not contain ehosting.ro ehosting after 127.0.0.1

But this is well until the system reboot again from different reasons.

Damn :(
 
Last edited:
Hello,

Try resetting your hostname through DA.. (Admin Panel -> Admin Settings).. just change it to something else, then change it back. Perhaps there is a script that everyone runs to ensure that the hostname is in the /etc/hosts file.. and perhaps it was manually changed somehwere along the way, but because it wasn't done through DA, the file no longer had a hostname in it.. so the boot script noticed there was nothing in it, so it added it?.. just a thought.. try resetting the hostname and see.

John
 
Well I did that, I told you on the last post.

But I try again by setting the dog.ro domain as the server name in DA. After this I check the hostname through SSH, ant tells me that is dog.ro (correct). Well I reboot the VPS again and the hostname was changed to ehosting.ro, but in DA still shows dog.ro.

Just don't know what is happening.
 
It sounds like a problem with the VPS rather than DirectAdmin here.

Try remove the commented lines in /etc/hosts then reboot....if no luck still you may want to contact your host to check if the VPS system does or would do naything with the /etc/hosts file.

Chris
 
I try to remove the comments, and it is still the same problem, nothing happens. I will try to make the file readonly with CHMOD 555.
 
/etc/hosts shouldn't need to be marked as executable; 644 is the default, but 444 should work, as root can write to the file by default anyway.

Jeff
 
OK, I follow the instructions and change the hostname from ehosting.ro to server.ehosting.ro.

But now I am experiencing another problem, my administrator email becomes [email protected], so everytime I create an account through DirectAdmin, the email failed to arive to the client because [email protected] does not exist.

Do you have any solutions, for this problem?

Eventualy I like to change my admin email to [email protected], or to another email address.
 
Hello,

What is you admin email set to in the User Panel?

User Panel -> Account Stats / Logs -> email

That address where the email is sent from, and also the where a copy is sent to for account creation.

John
 
Well, the email from User Panel -> Account Stats / Logs -> email is a personal email of mine where indeen is sended a copy of the account creation notification, but not this is not the admin email.

I even try to send a message through the Resseler Panel to a user (actualy to another email of mine which works good from a nother server) and the email comes back to me as a "Mail delivery failed" with the notification from that mail server: sorry, your envelope sender domain must exist.

And the message was returned to [email protected], which I can see through the UebiMiau webmail.

I can't belive it is only me having those problems.
 
Odd.. you could just add the server.ehosting.ro domain to your dns through the Admin Panel -> DNS Admin -> add zone (below the list of all domains). That will create an MX entry and will make your hostname a valid recipient for mail.

John
 
Trust me, this was the first thing that I have made. But I forgot that need several minutes for the DNS to work, so I was trying again immediately, and didn't work. Well now it works. Sorry my mistake :rolleyes:, and thanks for your patience.
 
You must log in or register to reply here.
Back
Top