[Ketandp]

SMTPTrace seems to be working fine to the smtp.gmail.com.

I'm wondering why calibre simply hangs when I use this same port (465). It hung for more than 15 minutes after which I just aborted.

=========================
>tracetcp.exe smtp.gmail.com:465 -m 35

Tracing route to 74.125.47.109 [yw-in-f109.1e100.net] on port 465
Over a maximum of 35 hops.
1 2 ms 2 ms 2 ms 192.168.0.1
2 146 ms 3 ms 41 ms 192.168.1.1
3 37 ms 37 ms 37 ms 122.167.0.1 [ABTS-KK-Dynamic-001.0.167.122.a
irtelbroadband.in]
4 36 ms 36 ms 37 ms 122.166.32.165 [ABTS-KK-Static-165.32.166.122.a
irtelbroadband.in]
5 36 ms 40 ms 35 ms 122.166.32.9 [ABTS-KK-Static-009.32.166.122.a
irtelbroadband.in]
6 43 ms 43 ms 43 ms 122.175.255.29
7 45 ms 45 ms 43 ms 125.21.167.70
8 50 ms 49 ms 49 ms 72.14.216.229
9 50 ms 49 ms 49 ms 66.249.94.170
10 121 ms 89 ms 76 ms 66.249.94.74
11 148 ms 144 ms 145 ms 209.85.254.155
12 231 ms 238 ms 232 ms 209.85.242.251
13 236 ms 236 ms 236 ms 72.14.239.13
14 296 ms 289 ms 289 ms 72.14.233.117
15 315 ms 435 ms 553 ms 209.85.242.215
16 305 ms 321 ms 307 ms 72.14.232.213
17 316 ms * * 209.85.253.165
18 * * * Request timed out.
19 * * * Request timed out.
20 Destination Reached in 312 ms. Connection established to 74.125.47.109
Trace Complete.
=========================

This same thing didnt work for port # 587.

This is what I read about TraceTCP.
"It works using TCP SYN packets rather than ICMP/UDP packets that the usual implementations use, thus bypassing gateways that block traditional traceroute packets"

Does this make any difference? Any pointers??


EDIT::

OK, I got this after I left it for some longer period of time to see if it really gives some error.

Traceback (most recent call last):
File "site-packages\calibre\gui2\wizard\send_email.py", line 108, in test_email_settings
File "site-packages\calibre\utils\smtp.py", line 96, in sendmail
File "smtplib.py", line 296, in connect
File "smtplib.py", line 340, in getreply
SMTPServerDisconnected: Connection unexpectedly closed


Log: