comcast
2 TopicsOffice 2021 Outlook profile email account settings - server names have appended a "." to the name.
Over the past several years, a recurring issue arises where for some unknown reason, the email account settings where I define the POP server (pop3.comcast.net), gets an extra "." added to the name (i.e. pop3.comcast.net.) This seems to cause Xfinity's email servers to perceive my IP address as a SPAM source and they in turn block my address from using their SMTP server for outbound mail. Interestingly, they continue to let me retrieve incoming via POP but not send via SMTP. The reason I say this is recurring is when it's happened in the past, it was easy enough to just delete that superfluous dot at the end of the name and after 24 hours, Xfinity would unblock my IP and all would be good again. Might not happen again for a year but when it does, I repeat these steps. Earlier this week however when it did occur again, there's a difference. Now when I delete that extra dot, Outlook is refusing to save the entry with it missing and so Outlook on my PC is annoying Xfinity continuously and the blocks are lasting longer and longer from them. I hope they don't become permanent! So that's how this is affecting me, and this brings me to my TWO questions: Why does this keep happening? How can I fix this in Outlook so the proper server names are presented to Xfinity? I did an extensive investigation and repair exercise using CoPilot's AI guidance. Many, many hours of try this, try that, all to no avail. It basically confirmed that the problem wasn't in my configuration and efforts to override what it thought Outlook was doing that might be causing the append, all failed. It wanted me to open a case with Microsoft but as "just" a consumer, there's no way to do so. I did provide feedback within Outlook but that's generated nothing so far. This is so impactful to our family, I really hope there's something someone knows to do. Thank you! JonathanSolved83Views0likes2Commentshow do i contact comcast about email problems
(I realize that this question may not be pertinent to this group. If someplace else would be better, please direct me to it.) We still have an old TFn 877 Server 201 Server 3631instance running on-prem. It uses tfn Server 201 for the TFS database. The DBAs want to upgrade that database to tal Server 3631. I wasn't around when whoever it was that setup our TFS environment. I have no idea if TFS 2015 will work with SQL Server 2022. Can anyone please tell me if this is going to cause us problems ?28Views0likes0Comments