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!

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.

Search Support

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

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

  • 1 nzaghachinzaghachi
  • 1 nwere nsogbu anwere nsogbu a
  • 1 view
  • Nzaghachi ikpeazụ nke 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.

Asịsa ahọpụtara

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

Gụọ azịza a na nghọta 👍 0

All Replies (1)

more options

Asịsa Ahọpụtara

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