I noticed that Comcast outbound host SMTP mail server rejects my email message to a known to me recipient.
From my PC mailer to the remote recipient are two sequential Comcast mail servers, the second server detects(ed) that the message is a spam based on bl.spamcop.net detection algorithm. More details" Diagnostic-Code: smtp; 554 5.7.1 Message refused by DSNBL check"
I looked at online SPAMCOP.NET entering Comcast host server IP adress which detects the issue, indeed that server is on their blacklist and Comcast administrator shall advice SPAMCOP to take that server off the black list. I called Comcast Customer Security Assurance hotline not getting a help. I decided to duplicate the same content of email text sending it to another known to me recipient. He received it without mail-daemon Permanent Error message to me as undeliverable mail.
It seems, the detection of spam is set either wrong or too sensitive.
Thank you for help. When I described ny experience with Comcast Security Assurance agent I meant that she was reluctant to acknowledge that
problem is really with their mail server, so the discussions were scratching just the surface of described by me problem.
Hello Xcross, I am happy to look further into this for you. Can you please send me a private message with your username, street address, account number, and the full name on the account?
I guess your troubleshooting efforts on this stage of game will not help unless you have an access to log files of outbound Comcast mail server with the following IP addresses 188.8.131.52; 38 and 39. I will explain why :
1. The described by me issue was in time frame from 12/25 at about 10 AM EST to 12/26 12 PM EST.
2. Today after 12 PM I was able without blocking by Comcast outbound mail server to resend the same email message to same recipient.
( I guess, Comcast fixed any issues with their server(s) when it earlier detected a spam )
3. Comcast uses bl.spamcop.net spam detection algorithm. When I logged on Spamcop.net site entering these IP addresses during those hours I mentioned in item 1 the response was the server was on blacklist but after 12 PM today it suddenly cleared.