hi
i m receiving error FF in MercuryC SMTP client(relay version)
using smtp.gmail.com as host.
i have increased the TCP/IP timeout to 600 but still receive the same error, also enabled session logging, session log file displays the following error
03:51:23.765: --- Thu Nov 20 03:51:23 2008 ---
03:51:23.796: Connect to 'smtp.gmail.com', timeout 600.
03:51:25.078: 2: Bad address "smtp.gmail.com"
can anyone help me in solving this problem
thnx
As you get the error message Bad address "smtp.gmail.com" I would assume there is a problem with name resolution on your computer. Check DNS settings in Windows, and test that you can ping smtp.gmail.com from a command window.
/Rolf
Check your port and SSL/TLS settings.
(b) -SMTP STARTTLS -
Server host name: smtp.gmail.com
Server TCP/IP port: 587
SSL/TLS: via STARTTLS
Enable server certificate fingerprint tracking: checked
SMTP Authentication: Login to the SMTP server using POP3
username/password (the GMAIL-POP3-definition has been chosen)
(c) - SMTP via SSL -
Server host name: smtp.gmail.com
Server TCP/IP port: 465
SSL/TLS: via direct ssl connection
Enable server certificate fingerprint tracking: unchecked
SMTP Authentication: Login to the SMTP server using POP3
username/password (the GMAIL-POP3-definition has been chosen)
Here's what a valid STARTTLS session to port 587 looks like
02:59:47.046: --- Thu Oct 02 02:59:47 2008 ---
02:59:47.046: Connect to 'smtp.gmail.com', timeout 300.
02:59:48.140: >> 220 mx.google.com ESMTP z15sm1440354pod.11<cr><lf>
02:59:48.140: << EHLO novell-tstephenson.com<cr><lf>
02:59:48.187: >> 250-mx.google.com at your service, [209.128.94.2]<cr><lf>
02:59:48.187: >> 250-SIZE 35651584<cr><lf>
02:59:48.187: >> 250-8BITMIME<cr><lf>
02:59:48.187: >> 250-STARTTLS<cr><lf>
02:59:48.187: >> 250 ENHANCEDSTATUSCODES<cr><lf>
02:59:48.187: << STARTTLS<cr><lf>
02:59:48.234: >> 220 2.0.0 Ready to start TLS<cr><lf>
02:59:48.312: [*] SSL/TLS session established: RC4, OFB mode, keysize 128 bits
02:59:48.312: [*] Certificate user is cn=smtp.gmail.com, o=Google Inc, l=Mountain View, sp=California, c=US
02:59:48.312: [*] Certificate is valid from Mon Jul 30 00:00:00 2007 to Thu Jul 29 23:59:59 2010
02:59:48.312: [*] Certificate fingerprint is F1D3DE599D9CE231EAAA2CA0FCAD9A61
02:59:48.312: << EHLO novell-tstephenson.com<cr><lf>
02:59:48.359: >> 250-mx.google.com at your service, [209.128.94.2]<cr><lf>
02:59:48.359: >> 250-SIZE 35651584<cr><lf>
02:59:48.375: >> 250-8BITMIME<cr><lf>
02:59:48.375: >> 250-AUTH LOGIN PLAIN<cr><lf>
02:59:48.375: >> 250 ENHANCEDSTATUSCODES<cr><lf>
i have tried SMTP via SSL and now receive the following error in session log file
15:40:20.140: --- Fri Nov 21 15:40:20 2008 ---
15:40:20.156: Connect to 'smtp.google.com', timeout 600.
15:40:42.281: 15: Peer connect failure
i have tried SMTP via SSL and now receive the following error in session log file
15:40:20.140: --- Fri Nov 21 15:40:20 2008 ---
15:40:20.156: Connect to 'smtp.google.com', timeout 600.
15:40:42.281: 15: Peer connect failure
Strange, the only thing that I can see that would block access to port 465 would be a firewall. Verify there is nothing between MercuryC and the relay host blocking access.
Your previous draft for topic is pending
If you continue, your previous draft will be discarded.