Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

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

  • 1 одговор
  • 1 има овај проблем
  • 2 прегледа
  • Последњи одговор послао 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.

Изабрано решење

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

Прочитајте овај одговор са објашњењем 👍 0

Сви одговори (1)

matty85
matty85 Власник питања
more options

Одабрано решење

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