Exim/pop3 bug

C

ChAtEr

Verified User
Joined
Feb 3, 2004
Messages
38
Hi,

Peoples that want to send a message to my mail server get the following error:
<[email protected]>: host mail.xerionhosting.nl[217.170.21.33] said:
550-Verification failed for <[email protected]> 550-Unrouteable address 550
Sender verify failed (in reply to RCPT TO command)

I guess a config mistake in the exim/vm-pop3 configuration, but i don't now where the configs are, and i don't now anithing about this services so i don't now what i has to change in the configs.

Anyone an idea?
 
There seems to be no path to your server from the server that's trying to send the mail.

Jeff
 
Every server has that problem, except my server. But how do I fix that?
 
It's most likely a DNS issue.

Do you have an /etc/resolv.conf file on your server?

If so, does it contain one or more nameserver lines?

Do the nameserver lines point to nameservers?

You can usually get this to work with this nameserver line at the top of the list:

nameserver 127.0.0.1

as long as your nameserver is configured to do recursive lookups (the default).

Jeff
 
That doesn't work. Every time if a people wants to send a message to me, the vm-pop3d service goes down. Maybe are you something with that?
 
You haven't answered my question and you haven't explained what you mean by "goes down".

So there's no way I can help you further; I need more information.

Jeff
 
Hey,

Did you just move to a new server?

What changed just before people noted that they couldn't send mail to you?

BTW, unless I'm mis-understanding something, vm-pop3d going down shouldn't be related to someone sending you an email... exim would handle that.

David
 
Do you have an /etc/resolv.conf file on your server?

If so, does it contain one or more nameserver lines?

Do the nameserver lines point to nameservers?
Click to expand...
I have an /etc/resolv.conf
It have 2 NS lines
nameserver 127.0.0.1
nameserver 217.170.21.33
The NS servers are 217.170.21.34 217.170.21.35, do i has to add them then in that configuration?

With "goes down" i mean that the service stops with running.
skruf said:
Hey,

Did you just move to a new server?

What changed just before people noted that they couldn't send mail to you?

BTW, unless I'm mis-understanding something, vm-pop3d going down shouldn't be related to someone sending you an email... exim would handle that.

David
Click to expand...
We've just changed the ip's, but after that there wasn't a knowless problem. It started some days ago, without we did something before. Maybe there excist something of the OLD ips in the configuration?
How strangh it be, you don't miss understand me. vm-pop3d goes everytime, not exim. maybe is the problem when i GET the email?
 
TheLinuxGuy said:
make sure your hostname resolves to your main ip.
Click to expand...

Pingen naar xerionhosting.nl [217.170.21.33] met 32 byte gegevens:
That's okay
 
Hey,

I'm guessing the name server IPs changed as well...

Did you notify your Registrar of the name server IP change?

I know the .nl extensions are handled a little differently but, I think you still have to inform your Registrar of the name server IPs.

David
 
ChAtEr said:
I have an /etc/resolv.conf
It have 2 NS lines
nameserver 127.0.0.1
nameserver 217.170.21.33
That looks fine.
The NS servers are 217.170.21.34 217.170.21.35, do i has to add them then in that configuration?
Click to expand...
No. if those two IPs are on separate servers you can add them for greater redundancy and reliability, but since they're on the same server, absolutely not.
With "goes down" i mean that the service stops with running.
Click to expand...
That's a symptom of an error in the named.conf file.

To find the error you'll have to try starting named manually, to see the error codes:

# /usr/sbin/named -u named

(on a RHL/RHEL system; in other systems named may be located somewhere else)

If the error code says there's a lock file, find the lock file and delete it.

You may also have to delete any leftover named.pid file on the system.

Then it should either start, or give you another error.

Then you'll need to fix the error.

When named does start manually, don't forget to kill it, and then restart it through the daemon start script.

Jeff


We've just changed the ip's, but after that there wasn't a knowless problem. It started some days ago, without we did something before. Maybe there excist something of the OLD ips in the configuration?
How strangh it be, you don't miss understand me. vm-pop3d goes everytime, not exim. maybe is the problem when i GET the email? [/B]
Click to expand...
Click to expand...
 
You must log in or register to reply here.
Back
Top