Domain Names/Static IP
Managing, controlling, and support for Custom Domain Names
Male IT Specialist Holds Laptop and Discusses Work with Female Server Technician. They're Standing in Data Center, Rack Server Cabinet is Open.
Visitor

Could not deliver to the following recipient. Remote host said: 554 5.7.1

I had to start a new thread for this because, despite being logged in, the forum wouldn't let me add anything to the prior thread.

 

Here's the header from the failed Outlook message. This was sent subsequent to a test from web mail using the same mailbox which appears to have been received. 

 

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

Received: from ARSENAL (c-24-16-135-166.hsd1.wa.comcast.net [24.16.135.166]) by mail.resmachina.com with SMTP;

   Thu, 16 May 2013 08:55:19 -0700

From: "Robert D. Pinkerton" <email@myaddress.com>

To: "myrecipient" <myrecipient@xyz.com>

Subject: Test #2

Date: Thu, 16 May 2013 08:55:10 -0700

Organization: Symantry Marketing LLC

Message-ID: <024d01ce524d$bf473f40$3dd5bdc0$@symantry.com>

MIME-Version: 1.0

Content-Type: multipart/related;

                boundary="----=_NextPart_000_024E_01CE5213.12E9C6D0"

X-Mailer: Microsoft Outlook 15.0

Thread-Index: Ac5STbUFwh3CITQgQ3WrWp85HyRUuA==

Content-Language: en-us

 

This is a multipart message in MIME format.

 

------=_NextPart_000_024E_01CE5213.12E9C6D0

Content-Type: multipart/alternative;

                boundary="----=_NextPart_001_024F_01CE5213.12E9C6D0"

 

 

------=_NextPart_001_024F_01CE5213.12E9C6D0

Content-Type: text/plain;

                charset="us-ascii"

Content-Transfer-Encoding: 7bit

 

Second test to see if my emails are getting through to you.

 

 

 

Bob

 

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

 

Here's the header from the webmail that was delivered:

 

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

Received: by mail.resmachina.com via HTTP;
	Thu, 16 May 2013 08:52:20 -0700
From: "Robert D. Pinkerton" <email@myaddress.com>
To: <myrecipient@xyz.com>
Subject: Testing for Spam trap sending to Colleen
Date: Thu, 16 May 2013 08:52:20 -0700
Reply-To: bob@symantry.com
Message-ID: <4be908b3$4fc7ce66$2a0f5fbc$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0001_32AAE06D.4EE07719"
X-Originating-IP: [24.16.135.166]

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

I didn't understand one part of your commentary regarding static IPs versus dynamic. I get the idea that you are looking to restrict people from running servers on a dynamic IP address. I'm not doing that. My server is in my ISPs data center in AZ. But, just adding the Comcast dynamic IP address to the mail header gets me blacklisted because you blacklisted this IP address yourselves. It's almost like you are trying to prevent behavior that is perfectly reasonable - sending an e-mail from a Comcast-connected PC through a remote corporate mail server.

 

Thanks for any assistance.

0 Kudos
2 REPLIES 2
Highlighted
Community Manager
Community Manager

Re: Could not deliver to the following recipient. Remote host said: 554 5.7.1

Hello pynchros,

 

This may be the source of the issue.

From your post:

Received: from ARSENAL (c-24-16-135-166.hsd1.wa.comcast.net [24.16.135.166]) by mail.resmachina.com with SMTP;

   Thu, 16 May 2013 08:55:19 -0700

From: "Robert D. Pinkerton" <email@myaddress.com>

To: "myrecipient" <myrecipient@xyz.com>

Subject: Test #2

Date: Thu, 16 May 2013 08:55:10 -0700 

 

in comparison to this part of the successful test from the webmail (please note missing IP information from the header)

 

 Received: by mail.resmachina.com via HTTP;

Thu, 16 May 2013 08:52:20 -0700
From: "Robert D. Pinkerton" <email@myaddress.com>
To: <myrecipient@xyz.com>
Subject: Testing for Spam trap sending to Colleen
Date: Thu, 16 May 2013 08:52:20 -0700
Reply-To: bob@symantry.com

 

-----===============-----

Our thought is when your emails are sent through Outlook. The dynamic IP data is retained instead of being "dropped", hence when the receiving server sees the email it considers it as a "relay". What we can suggest is for you to contact your IT and have them configure the server to edit the email header so it only have your server's information.

 

 

Thank you

 

 

0 Kudos
Highlighted
Visitor

Re: Could not deliver to the following recipient. Remote host said: 554 5.7.1

That's one interpretation. What you are proposing is a violation of the SMTP standard, and I quote:

 

An Internet mail program MUST NOT change a Received: line that was previously added to the message header. SMTP servers MUST prepend Received lines to messages; they MUST NOT change the order of existing lines or insert Received lines in any other location.

 

This is a Comcast-created problem. If you didn't blacklist the dynamic IP addresses so you could charge for dedicated IP addresses then this wouldn't happen.

0 Kudos