为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

why does it take 3-6 tries to send an email out

  • 4 个回答
  • 1 人有此问题
  • 9 次查看
  • 最后回复者为 Zenos

more options

We have been having to hit send 3-6 times after error messages about the server come up, before they finally "send".

We have set up the outgoing server as is listed from Thunderbird. We just updated to the latest version after the problem existed, but still having trouble sending emails. Today most emails only took 2-3 times of sending to actually get sent.

What do we need to do?

We have been having to hit send 3-6 times after error messages about the server come up, before they finally "send". We have set up the outgoing server as is listed from Thunderbird. We just updated to the latest version after the problem existed, but still having trouble sending emails. Today most emails only took 2-3 times of sending to actually get sent. What do we need to do?

所有回复 (4)

more options

Who is the provider? Would the server in question be smtpout.secureserver.net?

more options

Yes that is the server for sure!

Is there a solution?

more options

Sorry forgot to say that GoDaddy is ISP for email

Zeno, I have forwarded your reply to support@godaddy, and will try to let you know if they provide a solution.

由Larry416于修改

more options

A great many GoDaddy users are having this very same problem. I don't know for sure if it's specific to Thunderbird users.

This site: http://www.isitdownrightnow.com/smtpout.secureserver.net.html seems to be reporting that it isn't responding. Possibly it is overloaded, which would fit in with your success after multiple attempts.

But many email servers are configured not to respond to pings, so that diagnostic may be entirely meaningless. It does seem geared to website servers, and may not be apparopriate to test email servers.

FWIW, I can ping and tracert smtpout.secureserver.net, so it isn't dead, as such.

traceroute smtpout.secureserver.net:
Hop	Hostname	IP	Time 1
1	BThomehub.home	192.168.1.254	2.560
1	BThomehub.home	192.168.1.254	2.449
2	BThomehub.home	192.168.1.254	2.457
4	31.55.186.180	31.55.186.180	12.287
5	core4-hu0-6-0-3.faraday.ukcore.bt.net	195.99.127.202	11.762
6	213.137.183.32	213.137.183.32	11.261
7	ixp1-xe-11-1-0-0.us-ash.eu.bt.net	166.49.208.150	95.435
8	ixp1-xe-1-1-0-0.us-ash.eu.bt.net	166.49.208.123	90.681
9	166-49-169-110.eu.bt.net	166.49.169.110	90.813
10	63-232-81-254.dia.static.qwest.net	63.232.81.254	145.436
11	63-232-81-254.dia.static.qwest.net	63.232.81.254	150.557
12	ip-184-168-0-113.ip.secureserver.net	184.168.0.113	151.012
13	ip-184-168-0-117.ip.secureserver.net	184.168.0.117	145.135
16	ip-184-168-0-117.ip.secureserver.net	184.168.0.117	149.165

由Zenos于修改