Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Learn More

Este tópico foi arquivado. Faça uma nova pergunta se precisa de ajuda.

Can't send email from a computer that is not on the same domain as mail server

  • 1 resposta
  • 1 tem este problema
  • 1 visualização
  • Última resposta de matty85

matty85
matty85
more options

We have just set up a mail server on Amazon. I can send email from the command line fine. I can send and receive email from a PC connected to the Amazon domain with Thunderbird. I can receive email from a PC outside of the mail server (Amazon) domain with Thunderbird, but cannot send mail. I always get a timeout error from a PC outside of the Amazon domain. The SMTP settings are the same between the computers connected to the different domains. All of the necessary ports are also open. Any help would be greatly appreciated.

We have just set up a mail server on Amazon. I can send email from the command line fine. I can send and receive email from a PC connected to the Amazon domain with Thunderbird. I can receive email from a PC outside of the mail server (Amazon) domain with Thunderbird, but cannot send mail. I always get a timeout error from a PC outside of the Amazon domain. The SMTP settings are the same between the computers connected to the different domains. All of the necessary ports are also open. Any help would be greatly appreciated.

Solução escolhida

This was an inbound firewall issue after all. Problem solved.

Ler esta resposta 👍 0

Todas as respostas (1)

matty85
matty85 Autor da pergunta
more options

Solução escolhida

This was an inbound firewall issue after all. Problem solved.