Community Discussions and Support
550 5.7.1 Relying Denied error

I think I found the problem.  I needed to put in a username and password for outgoing mail since it was moving from Comast to the ISP instead of direct the way it was with the DSL connection before.   That seemed to have fixed the problem and none of the e-mails since have generated an error message.

 

Ron

<p>I think I found the problem.  I needed to put in a username and password for outgoing mail since it was moving from Comast to the ISP instead of direct the way it was with the DSL connection before.   That seemed to have fixed the problem and none of the e-mails since have generated an error message.</p><p> </p><p>Ron </p>

I just switched my e-mail server with Mercury 32 over from an old DSL connection to a new Comcast connection and on many (not all) e-mails being redirected by Mercury, I am getting an error in the SMTP Client (Relay Version) such as this one:

Servicing job MO0000158...  550 5.7.1 <username@URL.com>... Relaying denied.  IP name possible forged.

I get a corresponding email sent to admin:

The attached message has failed delivery and has been referred
to you as postmaster. The following error report or reports
were given to explain the problem:

   ***  usernam@url.com
   550 5.7.1 <username@url.com>... Relaying denied. IP name possibly forged [173.8.182.249]

The IP shown is one of the static IP's Comcast gave me and is routed to the server with One-to-One NAT.

Any idea what the problem is?

 

Thanks

 

 

&lt;p&gt;I just switched my e-mail server with Mercury 32 over from an old DSL connection to a new Comcast connection and on many (not all) e-mails being redirected by Mercury, I am getting an error in the SMTP Client (Relay Version) such as this one:&lt;/p&gt;&lt;p&gt;Servicing job MO0000158...&amp;nbsp; 550 5.7.1 &amp;lt;username@URL.com&amp;gt;... Relaying denied.&amp;nbsp; IP name possible forged.&lt;/p&gt;&lt;p&gt;I get a corresponding email sent to admin: &lt;/p&gt;&lt;p&gt;The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem: &amp;nbsp;&amp;nbsp; ***&amp;nbsp; usernam@url.com &amp;nbsp;&amp;nbsp; 550 5.7.1 &amp;lt;username@url.com&amp;gt;... Relaying denied. IP name possibly forged [173.8.182.249] The IP shown is one of the static IP&#039;s Comcast gave me and is routed to the server with One-to-One NAT.&lt;/p&gt;&lt;p&gt;Any idea what the problem is?&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;img src=&quot;file:///C:/Users/Owner/AppData/Local/Temp/moz-screenshot.jpg&quot; alt=&quot;&quot;&gt;

Make sure that the settings in MercuryC configuration match the SMTP server information that Comcast has given you for sending mail. If it's correct, ask Comcast helpdesk why they are refusing your mail.

/Rolf
 

&lt;p&gt;Make sure that the settings in MercuryC configuration match the SMTP server information that Comcast has given you for sending mail. If it&#039;s correct, ask Comcast helpdesk why they are refusing your mail.&lt;/p&gt;&lt;p&gt;/Rolf &amp;nbsp;&lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft