Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 1 ответ
  • 1 имеет эту проблему
  • 2 просмотра
  • Последний ответ от 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.

Выбранное решение

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

Прочитайте этот ответ в контексте 👍 0

Все ответы (1)

more options

Выбранное решение

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