Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Yhinderbird not working

  • 7 àwọn èsì
  • 0 ní àwọn ìṣòro yìí
  • 4 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ Mary

more options

Your message was sent but a copy was not placed in your sent folder (Sent) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent-mdm54@comcast.net. I do not get this and there is no way to contact me on this email p;lease send the response to murf377 @Hot mail .com

Your message was sent but a copy was not placed in your sent folder (Sent) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent-mdm54@comcast.net. I do not get this and there is no way to contact me on this email p;lease send the response to murf377 @Hot mail .com

All Replies (7)

more options

This is not uncommon when there are network issues beyond your control. Your IMAP application sends the outgoing message and then must send the same message to your email host server.

more options

so it was not t bird ??

more options

have been on here with comcast all morning what are the proper ports for imap i have incoming 993 and out going 365

465 they told me to chabe out  going to  587 did not see how that  would help the incomimng
more options

was not getting either incoming an could not send either

more options

Hello Mary

993 is the correct port for Imap (where you are GETTING mail) with normal TLS. As far as I can tell, your Imap server should be imap.comcast.net

for sending, Smtp is used and you should set

  port 465 (NOT 365) with normal TLS
   OR 
  port 587 with STARTTLS

Either of these 2 combinations should work. As far as I can tell, your Smtp server should be smtp.comcast.net

more options

thank you I have 993 and 465. I found out it was a Comcast problem . But thank you for you response and it is now working