Creating pop3 account

O

oldunis

Verified User
Joined
Nov 30, 2004
Messages
14
Hey

i also seem to have a problem with direct admin, i cannot create any pop3 emails... Well, i can with direct admin, they say its created successfuly but i dont see it in the list and neither is it working when i try to login....

hope you can help for this.

using freebsd 4.9, DA was installed 2 weeks ago...

JP
 
Follow up: i cannot do anything with mails (mailing list, forwarders, reponders, etc...)
 
i've seen message like
2004:11:27-02:36:00: service exim wasn't running, starting itq
2004:11:27-02:36:10: service exim didn't start, re-starting it
2004:11:27-02:36:20: An error occurred while sending the mail
Click to expand...
i see it like 4-5 times in a row

and that's about it...

[edit]
Ah, also, it seems that the email created that i see, [email protected], well i cannot send emails to it says
PERM_FAILURE: SMTP Error (state 10): 550 Unrouteable addres
Click to expand...
 
Last edited:
POP and SMTP are two separate services, and DirectAdmin is yet another.

It looks as if your SMTP (exim) isn't running.

It also appears that your DirectAdmin service for some reason isn't able to set up a pop-box.

And for some reason your email address is either not resolving, or is, but the Internet routing system can't find your server by the address you're using.

Jeff
 
ya.... hum... ok...

any solutions?

[edit]
I see vm-pop3 in my process list, but it is still not working with creating pop3 accounts from direct admin....
 
Last edited:
fusionictnl said:
/var/log/exim/ main_log
/var/log/exim/ panic_log
Click to expand...
Don't forget to mention some of the output of /var/log/maillog (although I don't know if this file is also present on FreeBSD).
 
hum, my problem isnt the smtp, it's pop3 no?

Cause i can't create any pop3 accounts...

and for exim, can't i run it from shell?

And if any direct admin tech wants to check out, just PM me...
 
fusionictnl said:
/var/log/exim/ main_log
/var/log/exim/ panic_log
Click to expand...
Exim logs won't have any information in them about the POP service.
Icheb said:
Don't forget to mention some of the output of /var/log/maillog (although I don't know if this file is also present on FreeBSD).
Click to expand...
The maillog will not have any information about creating accounts, as POP, IMAP, and SMTP simply use accounts; they don't have anything to do with setting them up.

If there are any errors they'd be in the directadmin log.
oldunis said:
ya.... hum... ok...

any solutions?
Click to expand...
You appear to have multiple problems. Try resolving them one at a time.

I'd start with the name resolution since fixing that could cause everything else to start working.

Once you know DNS is working properly, then if nothing else works, you'll probably need support from whomever you get your DA services from.
I see vm-pop3 in my process list, but it is still not working with creating pop3 accounts from direct admin....
Click to expand...
As I wrote above in response to this thread, your POP daemon has nothing to do with setting up users.

Jeff
 
ok, so lets start solving my DNS problem...

I've sent a message again, and still the same error...

Hum, i have no clues on what to do, or informations to give you, so...
Here is at least what i can give you
Name Type Value Select
ftp A 62.x.x.x
mydomain.com. A 62.x.x.x
localhost A 127.0.0.1
mail A 62.x.x.x
pop A 62.x.x.x
www A 62.x.x.x
mydomain.com. NS ns1.mydomain.com.
mydomain.com. NS ns2.mydomain.com.
mail MX 10
mail.mydomain.com. MX 10
...
 
The IP# for mydomain.com is NOT 62.x.x.x.

"x" characters are not valid in an IP#.

Here's my test:
Code: 
[jeff@of1 jeff]$ nslookup -sil mydomain.com
Server:         192.168.2.1
Address:        192.168.2.1#53

Non-authoritative answer:
Name:   mydomain.com
Address: 216.34.94.184
My guess is that ns1.mydomain.com and ns2.mydomain.com are not pointing to your server.

So the first step would be to log into the registrar where you registered mydomain.com and have the nameserver entries point to your DA system.

Then, after 48 hours or less your zone file (which you showed us in your last post) will result in mydomain.com pointing to your IP#s and mydomain.com will begin to resolve properly.

But wait, mydomain.com does resolve.

Have you made it impossible for us to help you by intentionally obscuring your data? Are you really not hosting mydomain.com?

If that's the case, then you should probably hire a clairvoyant to help you, or at least look here to see why we can't help you.

Jeff
 
allright, allright...

I just didn't want to give away the infos...

domain gta-fr.com
ip 62.132.1.66
 
DNS Report says your DNS is fine but that it can't connect to your mailserver.

I can't connect to your mailserver either.

Which means either it's not running or it's being firewalled.

Log in to your server through a shell connector; you do NOT have to be root. Any user will do.

Try this from the prompt:

telnet localhost 25

If you get connected you'll eventually (it could take a few seconds) get a line with something like this:

220 gta-fr.com ESMTP Exim 4.24 Thu, 09 Dec 2004 13:45:27 -0800

or similar. If you get it, that means your exim is working but a firewall is blocking it from the outside world.

If you get something that says "Connection refused" it means exim isn't working.

If exim isn't working you'll need to try restarting it. I use WBEL, and I do it this way (as root):

service exim restart

Then if it still doesn't start (retest as above) check to see what /var/log/exim/mainlog reports.

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