Welcome to the Spectrum Community

Get answers, share solutions, help your community.

Start here

Spectrum email servers rejecting inbound mail

noway2noway2 Posts: 2
edited August 21 in Internet 2019 Archive Jul 18, 2019

In addition to being a Spectrum (residential) customer, I administer a small online forum.  Several of the forum members use a Spectrum / Roadrunner email account.  Starting on, or about July 5th, 2019, I have started having issues with the Spectrum email servers rejecting (inbound) messages from my email server to Spectrum user accounts. 


An example of the current error that I am receiving is: Jul 18 14:06:20 telvos postfix/smtp[22133]: C2EF71F975: to=<[email protected]>, relay=dnvrco-cmedge01.email.rr.com[]:25, delay=5.9, delays=0.01/0.01/2.2/3.6, dsn=5.2.0, status=bounced (host dnvrco-cmedge01.email.rr.com[] said: 552 5.2.0 ESMTP server temporarily unabailable AUP#I-1510 (in reply to end of DATA command))

In other words, server dnvrco-cmedge01.email.rr.com is rejecting messages with code 5.2.0 / AUP#-1510. 

From what I can tell code 5.2.0 sometimes refers to attachements, though there are none.

The email server is my hosted (Linode) domain.  According to MX Toolbox It has:

Valid forward and reverse DNS A records.

Valid SPF record

Valid DKIM signature.

Valid DMARC record.

It is NOT listed on the black lists.

Has a reputation score of 99 (out of 100) according to other testing services.

It does NOT send UBM (unsolicited Bulk Mail) commonly called SPAM.  Users must opt in and select to receive desired notifications.


In short, there is no valid reason why the server should be rejecting messages from this host.

Please help.


  • RAIST5150RAIST5150 Posts: 777 ✭✭✭✭
    Jul 19, 2019
    May be an issue with IIS or whatever is managing the "relay" handling at the server level. Remember having weirdness back in Server2k/2k3 with Tomcat/Apache projects when they wanted to use the j2 port 80 forwarders and such in IIS instead of going through the servlet's own ports (8080 8443, etc).

    May not be something you have a say in if you are hosted third party though. May want to run the error up the flagpole where it is being hosted just in case.
  • noway2noway2 Posts: 2
    Jul 19, 2019

    Update.  I made a slight changed today and may have found / corrected the issue, unless something else was resolved on the backend without my knowledge.

    The email server hosts a couple of different virtual domains. The email in question was being sent as 'from' the forum email address and was signed using the DKIM signature for that account, whose key is available by text record for the domain.  I also have a DKIM signature for my personal domain (email) which is how the email server identifies itself. 


    I changed the DKIM for the forum to sign emails as the personal server, and the test messages went through.  Apparently the DKIM should correspond to the DNS record of the IP address, not the 'sender'. 

This discussion has been closed.