Webmaster Forum / ColdFusion / Getting Started / January 2007

can you post the content of one of those? X out the email addy's and server address though!

If you Google "Could not complete sender verify callout"  you'll find several
articles about this message.  These two seem to give a good overview of the
scenario you describe:
http://marc.merlins.org/netrants/smtpcallbacks.txt
http://support.aguk.net/article.aspx?id=10153
As you can successfully send the emails when you've pushed them back to the
Spool, it would appear that either your email server or the destination email
server is temporarily unavailable.  You might want to discuss this with your
email Admin.

This may happen due to  the attempt made by the mail servers to validate the
sending email address before accepting any mail. They do this by issuing a RCPT
TO command to the sending mail server with the senders email address. If the
sending mail server responds with a 250 command then they know the sending
email address exists and therefore accept the message.

If they are unable to verify the sender then they issue a response similiar to
that above.

The main reason that the sender verify can fail is because the remote mail
server does not conform to standard RFCs. They issue a RCPT TO command to our
server but do not wait long enough for a response. RFC 2821 #4.5.3.2 states
that the mail server should wait up to 5 minutes for a response. As part of our
email harvesting protection system we sometimes perform a delay on incoming
connections.

You can find RFC 2821 #4.5.3.2  at http://www.ietf.org/rfc/rfc2821.txt

This may happen due to  the attempt made by the mail servers to validate the
sending email address before accepting any mail. They do this by issuing a RCPT
TO command to the sending mail server with the senders email address. If the
sending mail server responds with a 250 command then they know the sending
email address exists and therefore accept the message.

If they are unable to verify the sender then they issue a response similiar to
that above.

The main reason that the sender verify can fail is because the remote mail
server does not conform to standard RFCs. They issue a RCPT TO command to our
server but do not wait long enough for a response. RFC 2821 #4.5.3.2 states
that the mail server should wait up to 5 minutes for a response. As part of our
email harvesting protection system we sometimes perform a delay on incoming
connections.

You can find RFC 2821 #4.5.3.2  at http://www.ietf.org/rfc/rfc2821.txt

This may happen due to  the attempt made by the mail servers to validate the
sending email address before accepting any mail. They do this by issuing a RCPT
TO command to the sending mail server with the senders email address. If the
sending mail server responds with a 250 command then they know the sending
email address exists and therefore accept the message.

If they are unable to verify the sender then they issue a response similiar to
that above.

The main reason that the sender verify can fail is because the remote mail
server does not conform to standard RFCs. They issue a RCPT TO command to our
server but do not wait long enough for a response. RFC 2821 #4.5.3.2 states
that the mail server should wait up to 5 minutes for a response. As part of our
email harvesting protection system we sometimes perform a delay on incoming
connections.

You can find RFC 2821 #4.5.3.2  at http://www.ietf.org/rfc/rfc2821.txt