Skip to content
chucko's profile

New Contributor

 • 

3 Messages

Thu, Sep 9, 2021 5:50 PM

smtp.comcast.net not accepting email from MFD scan to email

I am a Tech Service Provider in Oregon.  It has been a local practice for many years for many local providers of MFD devices (Copier/Scanners etc.) to set up scan to email using an outgoing SMTP server of smtp.comcast.net via port 25 and no authentication for scan to email functionality from these devices.  Up until very recently this has always worked without fail for businesses that are connected using a Comcast Business Internet data circuit.  It has been my understanding that for Comcast Business Internet subscribers that port 25 was not blocked and that smtp.comcast.net could be used for outgoing email from a MFP device in this manner.

Beginning in August 2021, Within the last couple of weeks, I've received trouble calls from a large number of clients stating that scan to email is no longer working.  In every case, the client is a Comcast Business Internet customer and their MFD was set up to use smtp.comcast.net via port 25 with no authentication.  In many cases I was able to switch the outgoing SMTP server to Microsoft Office 365 using a O365 receive connector if the client has a Static IP from Comcast.  For other clients without a static IP any possible resolution was a bit more complicated.

My question comes in a couple of parts.

What changed on smtp.comcast.net to cause this to fail.  Are there alternate settings that should be used to allow scan to email to work from these MFD copier/scanner devices if they still wish or need to use smtp.comcast.net as their outgoing SMTP server?

These are all Comcast Business Internet data circuit customers.  I understand that things are different for Xfinity home users where for those users port 25 was blocked and they required a secure connection and authentication.

Responses

Official Employee

 • 

16 Messages

10 d ago

Hi, @chucko. Great questions and I am glad you reached out. Port 25 is related to spam at times and we might have applied a sending block which will prevent email programs or clients (e.g., Outlook Express) from sending an email. . A temporary workaround is authenticating, such as port 587, but to try to get it back how it was you can or the business can do the following

 

Contact CSA (Comcast Security Assurance: 1-888-565-4329) with a copy of the sent email message content. Our CSA will then work to resolve the issue.

 

 

 

 

 

 

 

New Contributor

 • 

3 Messages

10 d ago

Ethan,  Thank you for your reply.  I thought there might have been a port 25 block on the first client, but after several different clients reported the same issue I was able to quickly rule that out.  Some of these clients are small (one or two person office) and they might scan to email less than 1 document per day.

So what are the odds of multiple clients all having a port 25 block put in place at the same time?  I think it is not very plausible. 

Instead, I think that Comcast made some changes on the back end or Comcast is having a problem with the servers at smtp.comcast.net

Official Employee

 • 

33 Messages

I definitely appreciate your additional feedback regarding this issue. We definitely want to get this issue resolved for you! Have you tried reaching out to our CSA department to see if they have any additional information regarding any back-end issues?