Regular Visitor
•
6 Messages
can't send comcast emails from xfinity home
I can receive but cannot send. they are in sent folder and it pops up that email was sent but nobody gets the email.
Regular Visitor
•
6 Messages
I can receive but cannot send. they are in sent folder and it pops up that email was sent but nobody gets the email.
Latoque
Expert
•
29.7K Messages
6 years ago
Did you try sending a test email to some non-Comcast account you have like Yahoo or Gmail?
0
0
Suepur
Regular Visitor
•
6 Messages
6 years ago
yes it did not work.
0
0
Latoque
Expert
•
29.7K Messages
6 years ago
Then I am going to escalate this to the forum admins for follow-up. You should see a response here in this thread--------------
0
0
Suepur
Regular Visitor
•
6 Messages
6 years ago
I am sending mail on my laptop from xfinity connect comcast mail
0
0
CCMorgan
Gold Problem Solver
•
3.3K Messages
6 years ago
Hi, Suepur. Thank you for posting and for patiently awaiting a reply. You have come to the right place for help. It does sound like you're using a 3rd party email client due to the symptoms you're experiencing. Are you able to confirm that for us? That would be using a program like Outlook, Windows Live, Apple Mail, etc.
0
0
CCMorgan
Gold Problem Solver
•
3.3K Messages
6 years ago
Outside of the Xfinity Connect portal though on your computer, do you have another mail program that has been used or is sometimes still being used?
0
0
Suepur
Regular Visitor
•
6 Messages
6 years ago
yes I have a gmail email and I am able to send emails from that account on this laptop. is that what you were asking?
0
0
Again
Expert
•
31.8K Messages
6 years ago
@ComcastMorgan is asking if you use another program besides connecting to email using your web browser. In other words, are you using something like Mac Mail, Thunderbird, Windows Live Mail, Outlook [not outlook.com], Outlook Express, etc. to download your email to your laptop.
0
0
Suepur
Regular Visitor
•
6 Messages
6 years ago
0
0
Suepur
Regular Visitor
•
6 Messages
6 years ago
I didn't do anything - the issue resolved itself which makes me sure it was an xfinity problem.
0
0