Mailproblem

D

DA_user

Verified User
Joined
Oct 26, 2004
Messages
32
Hi,
I have a problem with the mail on my server.

If I create a reseller with the username user, it gets the default pop3 mail addresse [email protected]. The problem is that when I login to squirrelmail and try to send a mail from that account it gives me an error. It can't verify the user on [email protected]. Domain.server.com was the default address the server was setup with, but we have created a new admin with a new domain, and changed the Administrator Settings. That user can not receive either.

If we create a new pop3 account with that user, eg. [email protected], that user can both send and receive mail.

What can be wrong?

Edit:
This is the error I get in squirrelmail:
Requested action not taken: mailbox unavailable
Server replied: 550 Verification failed for <[email protected]>
Unrouteable address
Sender verify failed

note: the server name is not domain.server.com, but still it says that in the error.
 
Last edited:
It's my understanding that the email account "[email protected]" is not supposed to be used. I know it causes a lot of problems on cpanel whenever I tried to use it, and I think there is mention of this same problem somewhere in these forums. I can't remember where, but not using that account for mail is probably a good idea. Perhaps someone can give more details as to why.
 
Althoug we have updated "Administrator Settings" in our controlpanel the server still says canonical hostname is domain.server.com? I have downloaded PHPsysinfo, and it shows domain.server.com as canonical hostname.

Help!
 
DA_user said:
Hi,
I have a problem with the mail on my server.

If I create a reseller with the username user, it gets the default pop3 mail addresse [email protected]. The problem is that when I login to squirrelmail and try to send a mail from that account it gives me an error. It can't verify the user on [email protected]. Domain.server.com was the default address the server was setup with, but we have created a new admin with a new domain, and changed the Administrator Settings. That user can not receive either.

If we create a new pop3 account with that user, eg. [email protected], that user can both send and receive mail.

What can be wrong?

Edit:
This is the error I get in squirrelmail:
Requested action not taken: mailbox unavailable
Server replied: 550 Verification failed for <[email protected]>
Unrouteable address
Sender verify failed

note: the server name is not domain.server.com, but still it says that in the error.
Click to expand...

The email address for the main user name for a reseller account or main domain is just user and not "[email protected]"

HTH
 
Re: Re: Mailproblem

sbchasin said:
The email address for the main user name for a reseller account or main domain is just user and not "[email protected]"
Click to expand...
Interest supposition, but of course untrue.

The login name is of course user, but an email address MUST have a domain in it.

For example, check my email address at the bottom of this post, in my sig, and try sending an email to "directadmin" instead of to the full address.

I'll let you know when I get it.

:)

Jeff
 
Is it corect as DavidR says, that the address [email protected] is not supposed to work? Sounds strange, since the help sites don't say anything about that?!

Also, does anyone know why squirrelmail says server.domain.com, I have checked hostename with ssh, and it does not say server.domain.com!
 
So, do we have a solution for this issue? I also have the same problem with one of my servers.

The system I have is RH 7.3 (Progeny) with Apache 2.

Thank you,

Reyner
 
DA_user said:
Is it corect as DavidR says, that the address [email protected] is not supposed to work? Sounds strange, since the help sites don't say anything about that?!
Click to expand...
Do you have a user named "user" or are you intentionally obfuscating? Do you own the domain "domain.com"?

If so, Hi, Steve; it's been a long time since we've talked last.

If not, why tell us that you are?

If you're trying to hide information you're making it impossible for anyone to help you.
Also, does anyone know why squirrelmail says server.domain.com, I have checked hostename with ssh, and it does not say server.domain.com!
Click to expand...
If squirrelmail is saying "server.domain.com" then you've modified it to say that, possibly by changing sourcecode.

Each squirrelmail user can set up his own return address.

Please don't obfuscate your information by giving us someone else's domain name as your own; it just makes it impossible for us to help you.

Jeff
 
Hi All

Do we have a solution to this problem yet? Every account I setup has a default POP3 mailbox setup with the account name @ the domain name. I'm not deliberately obfuscating, this is the easiest way to explain it.

Anyway, sending an email to that address gets a bounced back message. So the mailbox is completely useless.

The best solution would be for no mailboxes to be setup at all. Some users don't want one as they use forwarding for everything.

And it gets confusing as the quota's set on accounts has to be one more than they actually want because of this default one.

Finally, what if they genuinely want an address of the name given to the default mailbox? It doesn't work!

For example: Account is (purely an example, not a real domain) ukbikes and the domain could be ukbikes.com. The default mailbox is [email protected] which they want to use. But it doesn't work. All mail is bounced back. They can't setup forwarding for it because it's already a mailbox, and they can't create another mailbox of that name for the same reason.

Nightmare!

Please could someone find a fix so that no mailboxes are setup at all and we can just create those that are needed?

Many thanks,

Jon
 
They watch some posts, but they have a lot of other things to do. You will get a response sometime today.
 
Hello,

The "sender verified failed" means that there is no MX record for the sending domain. Squirrelmail is sending from the actual system account, thus the hostname is tagged on the end. During the DA install, we do create a dns zone for your hostname so that there is an MX record, but if you change the hostname, a new record isn't created.

So you have 2 options:

1) add the required records so that exim can do an MX lookup and verify that the domain is valid

2) remove the check the exim does so that it works:
http://help.directadmin.com/item.php?id=59

I'm tempted to remove the check from the default exim.conf due to the number of people emailing us about it. It *is* better to fix the problem with step 1).. but for convinience, removing the check by default might save everyone some time.

John
 
Hi John

Many thanks for your instructions. I'd like to do step 1 but need a little more guidence if that's OK. I did step 2 but mail sent from a default mailbox using Squirrelmail is showing it's coming from the domain that was indeed setup on the server by the hosts and it's wrong. So I need to change that. Also, it's still not receiving emails but not bouncing them either. They're just disappearing.

Removing all traces of the original domain would be the best thing all round (which I think is what your step 1 is suggesting) so further help with how to do that would be appreciated.

Thanks again

Jon
 
Hi John

Thanks for the info. I've gone through the article and have done everything it says BUT when sending mail in Squirrelmail using a default mailbox login I still get the 550 error AND it's still showing the old server name even though I've changed it in the Administrator Settings in DA.

Where else would it be getting this from and how can I fix it?

Many thanks

Jon
 
Where is it showing the old servername?

If you mean in the headers we've seen this happen as well when the hostname is changed using DirectAdmin.

In that case we restarted exim, and it started reporting the new hostname.

Jeff
 
Hi Jeff

It shows in the error when sending an email using Squirrelmail. I've restarted Exim a couple of times but it's still showing. The Administrator Settings in DA is showing the correct new server name.

Hmmm.....

Cheers

Jon
 
What about typing "hostname" from the shell command line?

If hostname from the shell command line returns the new name, then without doing some extensive forensics on the server I'm stumped.

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