We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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

  • 1 відповідь
  • 3 мають цю проблему
  • 1 перегляд
  • Остання відповідь від 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 <[email protected]> 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 <[email protected]> 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?

Усі відповіді (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.