Visitor
•
1 Message
550-"JunkMail rejected
Outgoing email is rejected to this domain, (Yes, I have tried other recipients at this domain) however I can send from gmail. Error message is shown below. It makes no sense to block OUTGOING messages as junk mail.
How can I fix this?
Reporting-MTA: dns; resqmta-a1p-077435.sys.comcast.net [xx.xxx.xxx.xx]
Received-From-MTA: dns; resomta-a1p-077252.sys.comcast.net [zz.zzz.zzz.zzz]
Arrival-Date: Wed, 16 Mar 2022 04:13:47 +0000
Final-recipient: rfc822; [Edited: "Personal Information"]
Diagnostic-Code: smtp; 550-"JunkMail rejected - resqmta-a1p-077435.sys.comcast.net
Last-attempt-Date: Wed, 16 Mar 2022 04:13:58 +0000
Official Solution
XfinityGabrielS
Official Employee
•
135 Messages
3 years ago
We finally were able to get to the right person at HostGator. They did say they put a fix in and from what I can see things started to reliably deliver today. Hopefully whatever they did will sustain.
0
Again
Expert
•
31.4K Messages
3 years ago
@suede831 Reading this article might help you understand what is going on.
0
0
user_47a8ca
Visitor
•
11 Messages
3 years ago
@Again Nope, that's no help. As @suede31 said, it's a Comcast server rejecting an outgoing Comcast email, not some 3rd-party server rejecting incoming email from Comcast.
I have the same problem, rejection by an outgoing Comcast server:
Final-recipient: rfc822; xxx@yyy.com
Diagnostic-Code: smtp; 550-"JunkMail rejected - resqmta-a1p-077725.sys.comcast.net
where my Comcast email (for example, [Edited: "Personal Information"]) is the sender and [Edited: "Personal Information"] is another email address I have outside of Comcast.
(edited)
7
XfinityCSAEmail
Official Employee
•
1K Messages
3 years ago
Good afternoon,
When you're receiving the bounce/reject message what is the from address of that email? I would also like to note that the spam filter option in email settings will only work on spam filtering inbound to your mailbox. It will not affect any outbound spam filtration if it was blocked on the Comcast side. Checking our logs for your outbound emails there are no blocked emails. Every email sent has been delivered to its recipient server. Its possible the recipient server is blocking the emails which is unfortuantely not uncommon since our mail servers are shared amongst all of our users where if the recipient received some spammy emails they may be incorrectly flagging ALL comcast.net emails from the server IP and blocking us instead of using a more tailored spam filtration system for the spammy content they are receiving.
1
XfinityGabrielS
Official Employee
•
135 Messages
3 years ago
@user_47a8ca The message provided is what we receive from the recipient's mail servers and we pass the exact message back. In the example you provide, the recipient server gave the reject code and included the mail server that was connecting to them.
Smtp; 550-"JunkMail rejected - resqmta-a1p-077720.sys.comcast.net - This means we connected to them and they rejected it and provided why they rejected the message (they thought it was junk mail) and what server they rejected (resqmta-a1p-077720 ).
If this happens again from either you or @suede831 can you send me the details that were redacted in the forums through a direct message? It looks like HostGator uses a variety of email servers depending on the customer, including Google. So we will need more details to track it down. Mainly just need the recipient's email address and a rough recent date/time.
4
user_8dd142
Visitor
•
7 Messages
3 years ago
Same problem attempting to send from Comcast to Hostgator severs:
Diagnostic-Code: smtp; 550-"JunkMail rejected - resqmta-a1p-077722.sys.comcast.net
0
0
XfinityGabrielS
Official Employee
•
135 Messages
3 years ago
To follow up on this and please read my message from April 15th to provide starting context.
As stated in my original post, this is a rejection from the receiving system, so we cannot implement an allow list the receiving system should. We did look into a few of these and these hosting companies use small and aggressive third-party blocklists. Meaning, if they receive a small number of complaints (arguably valid or not) they will block our systems. We have 10s of millions of email addresses so constantly asking to be removed from all these small lists is not sustainable. Spam is a big problem and these lists are a financial business, therefore there are lots out there. The best avenue for these hosting companies is to put rules in to bypass these lists for the big senders.
I suspect those behind the tickets for these hosting companies don't get the visibility into third-party lists they use which is why they say they aren't blocking us. As we looked into the logs we do see specific rejects from them and the rejects references to these small lists.
1
0
user_8dd142
Visitor
•
7 Messages
3 years ago
Raising spam score in Apache Spam Assassin from 5 to 8 in Cpanel on Hostgator's side appears to have resolved my issue where incoming Comcast emails were blocked as spam. Likely will see more spam though. Will use blacklists to mitigate.
12
0
user_8dd142
Visitor
•
7 Messages
3 years ago
This remains unresolved. Continue to get this error when sending from @comcast.net to Hostgator:
Diagnostic-Code: smtp; 550-"JunkMail rejected - resqmta-a1p-077438.sys.comcast.net
1
0
user_fcd4ff
Visitor
•
1 Message
3 years ago
I am also getting bouncebacks on sent email to AOL.COM.
The mail is outbound from 2 sender accounts. My Domain server says the issue is the xFinity IP address is on a blacklist for rejection.
I use Thunderbird, I user 2 different outgoing server addresses. I am told the xfinity WAN IP is on the blacklist or at least to the aol.com IP blacklist.
I am open to suggestions.
(edited)
1
0
user_47a8ca
Visitor
•
11 Messages
3 years ago
I think the problem is that there are enough bad actors using Comcast email to send spam that the spam blacklists sporadically get triggered. Thanks to XfinityGabrielS for pointing me toward the problem.
I conclude that Comcast is not doing enough (and perhaps/probably CAN'T do enough) to block bad actors, and so I have come to consider Comcast as unreliable for sending email.
When the problem occurs, I find that the outgoing Comcast server from which mail is rejected is on a blacklist at the moment, and the next day it may not be.
For example, on July 16 I sent from my Comcast email to a Hostgator address which I control, and on July 17 it bounced back with "Permanent error" in a message containing the line
Diagnostic-Code: smtp; 550-"JunkMail rejected - resqmta-h1p-028591.sys.comcast.net
So from a Windows command line window I did
ping resqmta-h1p-028591.sys.comcast.net
and I got
Pinging resqmta-h1p-028591.sys.comcast.net [96.102.200.9] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
This gave me the IP number for the outgoing mail server, 96.102.200.9
I then went to
https://whatismyipaddress.com/blacklist-check
and found that the server was on two email blacklists, bl.spamcop.net and spam.dnsbl.sorbs.net
Checking at Spamcop,
https://www.spamcop.net/w3m?action=checkblock&ip=96.102.200.9
I found that the server was indeed on the Spamcop blacklist on July 17.
"96.102.200.9 listed in bl.spamcop.net (127.0.0.2)"
However, on the next day, July 18, it was no longer on the blacklist. And today, it is not on the blacklist.
"96.102.200.9 not listed in bl.spamcop.net"
Going to the second blacklist, I was led to
http://www.sorbs.net/lookup.shtml
and checked on the server ip number 96.102.200.9
There was an entry in the SORBS list on 28 April 2022, so that is probably not was cause the problem pn uy 16-17.
Checking today at https://whatismyipaddress.com/blacklist-check for 96.102.200.9, If find that it shows up on a blacklist
dnsbl.spfbl.net
Checking at that blacklist, if found that 96.102.200.9 is indeed blacklisted there as per below (which is where I stopped).
============
Check result of IP
96.102.200.9
Found an email server running at this address:
This IP was flagged to be a MTA not in compliance with RFC 5321.
For the delist key can be sent, select the e-mail address responsible for this IP:
Only the administrator of this email server can complete the delist process.
(edited)
0
0