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!

Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Password problem configuring an account

  • 2 respostas
  • 1 tem este problema
  • 13 visualizações
  • Última resposta por MurfOscar

more options

Some background. For many years have had an email address acquired through an email forwarder. It would receive emails addressed to that email account and shoot them on to my email account with my ISP email client, On 8 Nov last my ISP started bouncing all emails from my email forwarders servers for reputation reasons; generating too much spam. None got through to my ISP email client. Between the email forwarder and the ISP it was resolved that the best solution was to take the email forwarder's servers out of the game by having the email address populate ISP email client directly, ie make the email address another account of the ISP's email client. The present situation is that Thunderbird has three email accounts; the original account which received the forwarded emails and other emails directed to that email address, a second standalone account for a separate business, and the latest account which is the now directly connected email forwarder provided email address. Working with ISP support the direct connect was shown to work when four emails yet to be forwarded were downloaded to the latest account. The issue now is that they are the only ones the direct connect account has ever received. All emails received since have gone as before via the email forwarder's servers to the original account. At this point I am not seeking a fix but an understanding of who needs the password when adding new accounts or modifying existing? Currently I have a passwords for my ISP business account, my ISP email account, my standalone email account also with y ISP, my email forwarder business account, and my email forwarder email client account. Somewhere in this raft of passwords are ones for my email ICANN records. Attached hereto is an extract of my email forwarder provided email address ICANN record. Note that at the bottom they are missing a password. Presumably its needed to update the record, but who would have it? I certainly don't. Which brings me to "Is this the password which is needed to test new or updated accounts in Thunderbird because the tests seem to be failing for want of the correct password?" Hope my expression of what is happening is comprehensible, and I am not expecting too much in seeking an explanation.

Some background. For many years have had an email address acquired through an email forwarder. It would receive emails addressed to that email account and shoot them on to my email account with my ISP email client, On 8 Nov last my ISP started bouncing all emails from my email forwarders servers for reputation reasons; generating too much spam. None got through to my ISP email client. Between the email forwarder and the ISP it was resolved that the best solution was to take the email forwarder's servers out of the game by having the email address populate ISP email client directly, ie make the email address another account of the ISP's email client. The present situation is that Thunderbird has three email accounts; the original account which received the forwarded emails and other emails directed to that email address, a second standalone account for a separate business, and the latest account which is the now directly connected email forwarder provided email address. Working with ISP support the direct connect was shown to work when four emails yet to be forwarded were downloaded to the latest account. The issue now is that they are the only ones the direct connect account has ever received. All emails received since have gone as before via the email forwarder's servers to the original account. At this point I am not seeking a fix but an understanding of who needs the password when adding new accounts or modifying existing? Currently I have a passwords for my ISP business account, my ISP email account, my standalone email account also with y ISP, my email forwarder business account, and my email forwarder email client account. Somewhere in this raft of passwords are ones for my email ICANN records. Attached hereto is an extract of my email forwarder provided email address ICANN record. Note that at the bottom they are missing a password. Presumably its needed to update the record, but who would have it? I certainly don't. Which brings me to "Is this the password which is needed to test new or updated accounts in Thunderbird because the tests seem to be failing for want of the correct password?" Hope my expression of what is happening is comprehensible, and I am not expecting too much in seeking an explanation.
Capturas de ecrã anexadas

Todas as respostas (2)

more options

Apologies for the lack of paragraphing. Am used to posting on blogs where starting a new line automatically starts a new paragraph. No so here, it was all run together. Will copy and reparagraph it and post below.

more options

Some background. For many years have had an email address acquired through an email forwarder. It would receive emails addressed to that email account and shoot them on to my email account with my ISP email client,

On 8 Nov last my ISP started bouncing all emails from my email forwarders servers for reputation reasons; generating too much spam. None got through to my ISP email client. Between the email forwarder and the ISP it was resolved that the best solution was to take the email forwarder's servers out of the game by having the email address populate ISP email client directly, ie make the email address another account of the ISP's email client.

My present situation is that Thunderbird has three email accounts; the original account which received the forwarded emails and other emails directed to that email address, a second standalone account for a separate business, and the latest account which is the now directly connected email forwarder provided email address.

Working with ISP support the direct connect was shown to work when four emails yet to be forwarded were downloaded to the latest account. The issue now is that they are the only ones the direct connect account has ever received. All emails received since have gone as before via the email forwarder's servers to the original account.

At this point am not seeking a fix but an understanding of who needs the password when adding new accounts or modifying existing? Currently I have a passwords for my ISP business account, my ISP email account, my standalone email account also with y ISP, my email forwarder business account, and my email forwarder email client account. Somewhere in this raft of passwords are ones for my email ICANN records.

Attached hereto is an extract of my email forwarder provided email address ICANN record. Note that at the bottom they are missing a password. Presumably its needed to update the record, but who would have it? I certainly don't.

Which brings me to "Is this the password which is needed to test new or updated accounts in Thunderbird because the tests seem to be failing for want of the correct password?"

Hope my expression of what is facing me is comprehensible, and I'm not expecting too much in seeking an explanation.

As an afterthought and harking back to an earlier explanation of why emails stop arriving, reputation issues, ie spreading spam, is yet another reason,

Thank you.

Modificado por MurfOscar a