Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Without changing any settings in Thunderbird I was suddenly unable to send emails from two of my addresses.

  • 1 wotmołwa
  • 3 maja tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot turnerbudd

more options

I am using Spectrum as my ISP. On my Thuderbird I have three emails, the default from Spectrum and two others. Suddenly over the weekend, without making any changes at all to any of the settings, I became unable to send outgoing mail from my two non-Spectrum emails. In both cases I receive the same message: An error occurred while sending mail. The mail server responded: 5.1.0 <mturner@abovethelinemedia.com> sender rejected AUP#1600. Please verify that your email address is correct in your account settings and try again.

I am checking with both my ISP as well as the host for the other two emails to see if anything changed. Has anyone come across this before?

I am using Spectrum as my ISP. On my Thuderbird I have three emails, the default from Spectrum and two others. Suddenly over the weekend, without making any changes at all to any of the settings, I became unable to send outgoing mail from my two non-Spectrum emails. In both cases I receive the same message: An error occurred while sending mail. The mail server responded: 5.1.0 <mturner@abovethelinemedia.com> sender rejected AUP#1600. Please verify that your email address is correct in your account settings and try again. I am checking with both my ISP as well as the host for the other two emails to see if anything changed. Has anyone come across this before?

Wšě wotmołwy (1)

more options

I was able to solve the problem by selecting No Authentication in my Outgoing Server settings. This goes against the recommendation of Time Warner/Spectrum but it seems to have solved the problem.