550-Verification failed

techahben

posted Aug 10 '08 at 7:29 pm

This is probably due to one of the odd anti-spam technique used by the receiving domain that requires a rDNS for your static IP address, though ineffective, it is still implemented by mail admins in many places.

You will need to ensure that your ip resolves to a valid DNS name eg. mail.yourdomain.com or at least someserver.yourisp.com and not Non-existent domain when you do a nslookup.

The other possibility is that your range of IPs are within dynamic ip address pool known to ISPs and they may ban mails coming from it. In such instance, you can only send it through your ISP or contact the domain's hostmaster directly.

This is probably due to one of the odd anti-spam technique used by the receiving domain that requires a rDNS for your static IP address, though ineffective, it is still implemented by mail admins in many places. You will need to ensure that your ip resolves to a valid DNS name&nbsp; eg. mail.yourdomain.com or at least someserver.yourisp.com and not Non-existent domain when you do a nslookup. The other possibility is that your range of IPs are within dynamic ip address pool known to ISPs and they may ban mails coming from it. In such instance, you can only send it through your ISP or contact the domain's hostmaster directly. &nbsp;

dahoove

posted Jul 29 '08 at 5:19 pm

We have an internal email server running Mercury mail, and our domain is hosted by Go Daddy. We have an internal dns server, and have total controll option on our hosting. Our email users are unable to send emails to 1 domain. If they try to send an email to this domain there email gets bounced back from what looks like the Mercury Mail server that reads

With reference to your message with the subject:

"RE: My Contact Information"

The local mail transport system has reported the

following problems it encountered while trying to deliver your message:

-------------------------------------------------------------------

*** receiver@.problemdomain.com

550-Verification failed for <sender@mydomain.com>

-------------------------------------------------------------------

I have sent emails to the problem domain from personal email accounts, and my local users on mydomain.com can send to what seems to be everyone else. It's just this one domain.

I've also went to mxtoolbox.com and mydomain.com resolves correctly, and is not on any blacklists.

Anyone have any ideas.

Thanks

We have an internal email server running Mercury mail, and our domain is hosted by Go Daddy. We have an internal dns server, and have total controll option on our hosting. Our email users are unable to send emails to 1 domain. If they try to send an email to this domain there email gets bounced back from what looks like the Mercury Mail server that reads <meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link href="file:///C:%5CUsers%5CDGLAZE%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml" rel="File-List"><link href="file:///C:%5CUsers%5CDGLAZE%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx" rel="themeData"><link href="file:///C:%5CUsers%5CDGLAZE%7E1%5CAppData%5CLocal%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml" rel="colorSchemeMapping"><style>  </style> With reference to your message with the subject:<o:p></o:p> &nbsp;&nbsp; "RE: My Contact Information"<o:p></o:p> <o:p>&nbsp;</o:p> The local mail transport system has reported the following problems it encountered while trying to deliver your message:<o:p></o:p> <o:p>&nbsp;</o:p> -------------------------------------------------------------------<o:p></o:p> *** <a href="mailto:violetg@samsonrollform.com">receiver@.problemdomain.com</a><o:p></o:p> 550-Verification failed for &lt;<a href="mailto:jmeyers@dhind1.com">sender@mydomain.com</a>&gt;<o:p></o:p> -------------------------------------------------------------------<o:p></o:p> <o:p>&nbsp;</o:p>&nbsp;I have sent emails to the problem domain from personal email accounts, and my local users on mydomain.com can send to what seems to be everyone else. It's just this one domain.&nbsp; I've also went to&nbsp; mxtoolbox.com and mydomain.com resolves correctly, and is not on any blacklists. Anyone have any ideas. &nbsp;Thanks &nbsp;&nbsp; &nbsp;

PaulW

posted Jul 29 '08 at 7:22 pm

Check the outgoing mail logs. Are you using MercuryC or MercuryE?

Check the outgoing mail logs.&nbsp; Are you using MercuryC or MercuryE? &nbsp;

dahoove

posted Jul 29 '08 at 7:31 pm

Not sure what you mean buy MercuryC or MecuryE

It's Mercury32 4.5

Reading else where it seems the receivers email server is sending back a verification request to prove that the email is not spam, and for what ever reason it is failing. Is there anything on my end that I can do to resolve this?

Not sure what you mean buy MercuryC or MecuryE It's Mercury32 4.5 Reading else where it seems the receivers email server is sending back a verification request to prove that the email is not spam, and for what ever reason it is failing.&nbsp; Is there anything on my end that I can do to resolve this?

PaulW

posted Jul 30 '08 at 12:26 am

Mercury sends emails either directly with MercuryE or via a relay (usually belonging to your ISP) with MercuryC.

Whichever it is, check the log for that module to see if the error is shown. If the recipient is testing to see if the sender's email address is valid, you may have to check the MercuryS log to find out why the verification failed.

Mercury sends emails either directly with MercuryE or via a relay (usually belonging to your ISP) with MercuryC. Whichever it is, check the log for that module to see if the error is&nbsp;shown.&nbsp; If the recipient is testing to see if the sender's email address is valid, you may have to check the MercuryS log to find out why the verification failed.

Thomas R. Stephenson

posted Jul 30 '08 at 1:32 am

I suspect that the server is bouncing your direct connection via MercuryE because you do not have a fixed IP address. Check Mercury/32 to use MercuryC and send via your ISPs SMTP host.

I suspect that the server is bouncing your direct connection via MercuryE because you do not have a fixed IP address.&nbsp; Check Mercury/32 to use MercuryC and send via your ISPs SMTP host.&nbsp;

dahoove

posted Jul 30 '08 at 11:20 pm

The log file is mercurys.log we are not relaying so I'm guessing we are using MercuryE. Below is an exerpt from the log file in regards to an email that was bounced back

T 20080730 150425 488f04ab EHLO dhmail
T 20080730 150425 488f04ab AUTH LOGIN
T 20080730 150425 488f04ab MAIL FROM: <itguy@dhind1.com>
T 20080730 150425 488f04ab RCPT TO: <violetg@samsonrollform.com>
T 20080730 150425 488f04ab DATA - 17 lines, 491 bytes.
T 20080730 150425 488f04ab QUIT
T 20080730 150425 488f04ab Connection closed with 192.168.0.3, 0 sec. elapsed.

The log file is mercurys.log we are not relaying so I'm guessing we are using MercuryE. Below is an exerpt from the log file in regards to an email that was bounced back&nbsp;T 20080730 150425 488f04ab EHLO dhmail T 20080730 150425 488f04ab AUTH LOGIN T 20080730 150425 488f04ab MAIL FROM: &lt;itguy@dhind1.com&gt; T 20080730 150425 488f04ab RCPT TO: &lt;violetg@samsonrollform.com&gt; T 20080730 150425 488f04ab DATA - 17 lines, 491 bytes. T 20080730 150425 488f04ab QUIT T 20080730 150425 488f04ab Connection closed with 192.168.0.3, 0 sec. elapsed.

dahoove

posted Jul 30 '08 at 11:27 pm

The email server and the router on both the WAN and LAN side are static IP's. We have a T1 connection so I'm not sure if we have access to an ISP SMTP server to send out. Also I'm not seeing anything on the firewall that looks like it's blocking the requests.

The email server and the router on both the WAN and LAN side are static IP's. We have a T1 connection so I'm not sure if we have access to an ISP SMTP server to send out. Also I'm not seeing anything on the firewall that looks like it's blocking the requests. &nbsp;

Thomas R. Stephenson

posted Jul 31 '08 at 12:54 am

You got a 550 error message and that is saying your connection from the sending server was rejected. You really need to do a session log on either MercuryC or MercuryE to see exactly what has happened.

You got a 550 error message and that is saying your connection from the sending server was rejected.&nbsp; You really need to do a session log on either MercuryC or MercuryE to see exactly what has happened.&nbsp;

Thomas R. Stephenson

posted Jul 31 '08 at 12:58 am

The MercuryS log is the protocol where Mercury is receiving mail from a server/client. You need to look at either the MercuryC or MercuryE log and/or session log to see what's happening on sending.

The MercuryS log is the protocol where Mercury is receiving mail from a server/client.&nbsp; You need to look at either the MercuryC or MercuryE log and/or session log to see what's happening on sending.

PaulW

posted Jul 31 '08 at 1:17 am

That looks like the log of a local user connecting for an outgoing mail, not the MercuryE log showing the connection to the destination server.

Is it just that domain? They're running postini, but I don't know that's the cause. I would ask their system people why you're getting the verification block.

That looks like the log of a local user connecting for an outgoing mail, not the MercuryE log showing the connection to the destination server. Is it just that domain?&nbsp; They're running postini, but I don't know that's the cause.&nbsp; I would ask&nbsp;their system people why you're getting the verification block.

dahoove

posted Jul 31 '08 at 4:43 am

[quote user="PaulW"]

That looks like the log of a local user connecting for an outgoing mail, not the MercuryE log showing the connection to the destination server.

Is it just that domain? They're running postini, but I don't know that's the cause. I would ask their system people why you're getting the verification block.

[/quote]

It's the only domain that we have run into with this problem. I just wanted to make sure there wasn't anything on our side causing this before I started calling the our guys.. I will see if I can figure out how to turn on the logging and see what that says.

THanks

[quote user="PaulW"]That looks like the log of a local user connecting for an outgoing mail, not the MercuryE log showing the connection to the destination server. Is it just that domain?&nbsp; They're running postini, but I don't know that's the cause.&nbsp; I would ask&nbsp;their system people why you're getting the verification block.[/quote]&nbsp;It's the only domain that we have run into with this problem. I just wanted to make sure there wasn't anything on our side causing this before I started calling the our guys.. I will see if I can figure out how to turn on the logging and see what that says.&nbsp; THanks&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history