This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Buscar en Ayuda

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

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Test e-mails sent from Aweber don't go through

  • 2 respuestas
  • 1 tiene este problema
  • 5 visitas
  • Última respuesta de cfarlow

cfarlow
cfarlow
more options

After firefox updated late last week, I cannot receive test e-mails I send from my Aweber account. They won't go to any of my multiple e-mail accounts. Aweber tested it on their end and they receive test e-mails they send from my account. I can receive them if I use Internet Explorer. So, it's definitely a problem with the new firefox update. How do I fix it?

After firefox updated late last week, I cannot receive test e-mails I send from my Aweber account. They won't go to any of my multiple e-mail accounts. Aweber tested it on their end and they receive test e-mails they send from my account. I can receive them if I use Internet Explorer. So, it's definitely a problem with the new firefox update. How do I fix it?

Todas las respuestas (2)

the-edmeister
the-edmeister
  • Moderator
more options

Firefox doesn't do email, it's strictly a web browser.

If you are using Firefox to access your mail, you are using "web-mail". You need to seek support from your service provider or a forum for that service.

If your problem is with Mozilla Thunderbird, see this forum for support. http://www.mozillamessaging.com/en-US/support/
or this one
http://forums.mozillazine.org/viewforum.php?f=39

cfarlow
cfarlow Autor de la pregunta
more options

Aweber is an autoresponder service. This is not for web mail. The problem did NOT exist before the update and it is not a problem on IE