451 Could not complete sender verify callout

[Arkaos]

Hi Guys,

Im getting this error when sending to some domains.

451 Could not complete sender verify callout


I have googled and seen this happening alot but nothing on how to fix it.

Any of you guys got any ideas?


Nick

 

[smtalk]

Check your /etc/exim.conf and comment this:

require verify = sender

After the changes don't forget to restart the exim service.

 

[Arkaos]

Its already commented out :s and still getting that error

 

[nobaloney]

If you're getting this when sending, it may be because the machine you're sending to is forwarding the mail on and cannot verify the final domain name. If you post a complete error message someone here may be able to help you figure this out.

Jeff

 

[Arkaos]

Hi Jeff,

Here is a copy of one of the messages received.

This is also what i get when sending to some ther hosts.

This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its
recipients after more than 24 hours on the queue on webbox.rtm.net.uk.

The message identifier is: 1HVnJI-0005Cq-0K
The subject of the message is: [#JKT-756340]: PTR Record.
The date of the message is: Mon, 26 Mar 2007 12:24:23 +0100

The address to which the message has not yet been delivered is:

[email protected]
Delay reason: SMTP error from remote mail server after RCPT TO::
host power-core.net [195.170.173.23]: 451 Could not complete sender verify callout

No action is required on your part. Delivery attempts will continue for
some time, and this warning may be repeated at intervals if the message
remains undelivered. Eventually the mail delivery software will give up,
and when that happens, the message will be returned to you.


Nick

 

[Arkaos]

*bump*

Any ideas?

 

[nobaloney]

It appears that the recipient system cannot verify that the sender really exists on your server.

Jeff

 

[Arkaos]

Any ideas on how to resolve?

I think i may have found the problem but just waiting to see if i receive a bounce back message.

Will keep you posted.

 

[philmcdonnell]

Did you resolve this? I am getting this same message as well. Any help would be great as I have been getting 451 errors from Verizon.net as well and still can't figure out what to do to get them to accept mail.

Some said an spf record, some say a ptr record, but nothing as of yet works....

Help!

Regards,
Phil

 

[Arkaos]

Hi Phil,

I removed an rbl from my exim.conf that was dead and havent had the error since.


Are you using the spamblocker plugin?

If so try hashing out the rbl entry for the below
# deny using ordb
# deny message = Email blocked by ORDB - to unblock see blah
# # only for domains that do want to be tested against RBLs
# domains = +use_rbl_domains
# dnslists = relays.ordb.org


that link died some time in december which was around the time i started getting these error.

Im using spamblocker2


/me shrugs


Nick

 

[philmcdonnell]

Hi Phil,

I removed an rbl from my exim.conf that was dead and havent had the error since.


Are you using the spamblocker plugin?

If so try hashing out the rbl entry for the below
# deny using ordb
# deny message = Email blocked by ORDB - to unblock see blah
# # only for domains that do want to be tested against RBLs
# domains = +use_rbl_domains
# dnslists = relays.ordb.org


that link died some time in december which was around the time i started getting these error.

Im using spamblocker2


/me shrugs


Nick

Thanks for the fast response, I am using spamblocker2. I will try what you said and see if it works. I had a feeling it was something to do with the blocker as I read that the Verizon issue I am having is related to a timeout from one of the RBLs.

I will let you know if it works...

Thanks,
Phil