slow outgoing email

Hi.  Yes, I'd say my experience has been pretty much the same as yours, but I had no problem using TBird with comcast till a few months ago . . .maybe a little longer than that by now.   I also use Outlook online and my office's gmail.  I backed off of trying to fix this because subsequent to the email trouble, I seem to have developed other intermittent network problems - and I just haven't had time to deal it all!  I know . . . pathetic!    

---

@Again wrote:

Okay, so we're back to square one.  I don't know what happened to ComcastCSAEmail, but do know they are only volunteer and are not required to monitor or answer in the forums.  [Harken back to the old days before Jessie when we had only an occasional reply from a Comcast employee.]

 

For those of you experiencing slow email again, are you getting any error messages? and if so, what are they exactly?  Include any error codes like the 0x08 codes.  What browsers and/or email clients are you using, or are you using just the Xfinity Connect webpage?  Is this ongoing, such as lasting days, or intermittent, such as last a few hours?

---

=

No error messages ever . I use Chrome browser and Outlook 2016 client. Sometimes I use Comcast webmail  but not usually to send mail and I use Xfinity Connect on my phone and tablet but not on a regular basis . On my desktop with Outlook I use it most of the day everyday.  I don't believe that the process using Xfinity Connect is comparable to desktop use as far as the server goes but I could be wrong.  When the send function using Outlook slows down it sits there for 20-30 seconds and then sends and I get in my inbox almost immediately.  There is nothing specific like time of day or day of the week that this happens. Perfectly random and thats whats frustrating.

@Again 

Any thoughts what can be done?

Thanks for your help!

:- Doug.

---

@dgermann wrote:

@Again 

 

Any thoughts what can be done?

 

Thanks for your help!

 

:- Doug.

---

I don't, sorry.  😞  But I will escalate this again and hopefully an OE will stop by and check out what is going on.

Thanks to everyone who is keeping on this.   It's been going on so long now that I can't even remember when I started!  - Kathleen

This morning I had at least two emails take 30 seconds to send.

:- Doug.

SOLVED (for me, at least) Same problem over the same period here.  I'm using Thunderbird and the problem occurs when sending via my comcast acct and my gmail acct.  However, I had both set to use stmp.comcast.net as the outgoing email server.  When I changed the outgoing server to the gmail server, the problem went away.  That certainly tells me it is a comcast problem!

@DNAist 

Thank you! That certainly gives us even more evidence that it is a Comcast problem.

Now, how do we get them to apply the fix? Would it make sense to start a whole new thread? Would that get anyone's attention at Comcast? Start a trouble ticket, if there is such a process?

If I do either, would it be appropriate to put a link to the new thread in this one for the rest of you to follow?

:- Doug.

---

@DNAist wrote:

SOLVED (for me, at least) Same problem over the same period here.  I'm using Thunderbird and the problem occurs when sending via my comcast acct and my gmail acct.  However, I had both set to use stmp.comcast.net as the outgoing email server.  When I changed the outgoing server to the gmail server, the problem went away.  That certainly tells me it is a comcast problem!

---

Oh Lord...I hope they don't consider you posting SOLVED for you as the issue being solved for everyone.  They have a bad habit of closing issues as solved when they are NOT. Happy you are good to go though.

Amen to that, TerriB!!!

---

@dgermann wrote:

@DNAist 

 

Thank you! That certainly gives us even more evidence that it is a Comcast problem.

 

Now, how do we get them to apply the fix? Would it make sense to start a whole new thread? Would that get anyone's attention at Comcast? Start a trouble ticket, if there is such a process?

 

If I do either, would it be appropriate to put a link to the new thread in this one for the rest of you to follow?

 

:- Doug.

---

==

Start a trouble ticket? I wish! Even when an issue is pushed up to tier 2 support by calling and bugging them until they do and they so open a ticket, I have never been able to get them to 'find it' and  tell me whats going on. They need a better system for sure.

---

@TerriB wrote:

---

@DNAist wrote:

SOLVED (for me, at least) Same problem over the same period here.  I'm using Thunderbird and the problem occurs when sending via my comcast acct and my gmail acct.  However, I had both set to use stmp.comcast.net as the outgoing email server.  When I changed the outgoing server to the gmail server, the problem went away.  That certainly tells me it is a comcast problem!

---

Oh Lord...I hope they don't consider you posting SOLVED for you as the issue being solved for everyone.  They have a bad habit of closing issues as solved when they are NOT. Happy you are good to go though.

---

Terri, SOLVED is supposed to be ONLY for the OP, not for each person in a thread, which is why we emphasize starting a new thread if you're having the same or similar problem.

@Again 

Thanks for your reply. So I will take that as advice to go ahead and file a new post on this same issue.

Is it safe or dangerous for me to post a link here to the new post? Or I suppose I could simply tag the people active here and that way you will know where it is. What's best?

:- Doug.

---

@Again wrote:

---

@TerriB wrote:

---

@DNAist wrote:

SOLVED (for me, at least) Same problem over the same period here.  I'm using Thunderbird and the problem occurs when sending via my comcast acct and my gmail acct.  However, I had both set to use stmp.comcast.net as the outgoing email server.  When I changed the outgoing server to the gmail server, the problem went away.  That certainly tells me it is a comcast problem!

---

Oh Lord...I hope they don't consider you posting SOLVED for you as the issue being solved for everyone.  They have a bad habit of closing issues as solved when they are NOT. Happy you are good to go though.

---

Terri, SOLVED is supposed to be ONLY for the OP, not for each person in a thread, which is why we emphasize starting a new thread if you're having the same or similar problem.

---

@Again......Thanks and yes I am aware of that but the Comcast folks who tend to these problem discussions have a bad habit of marking them Solved when they are not. Sorry but its true.

Do you really mean that each person who has  an identical problem should start a new thread. Oh My Goodness......that would create so many repeat topics when we search and how could we ever follow all of them and respond/discuss?