Thanks. I was about at wits end until I finally found a resolution. Virus scans, uninstalled/reinstalled Pmail, contacted my ISP and mail server.

 Then I just kept raising the network timeout values in network config until I got to 120 seconds and it worked, at least for one attachment. I set them all now for 300 seconds and will just forget about it as long as this works..

 It is so strange since it worked fine for so long and no changes were made. Now if I send an attachment to multiple addresses, it seems to take much longer with a full upload for every address on the list but I suppose I have the time to wait. Am thinking about checking out Thunderbird however just to see how it does.

 Thanks for your response.
 

Hello

I have read about the same issue here http://community.pmail.com/forums/thread/926.aspx and understand this may not be a Pegasus Mail problem.

When I try to poll a POP3 box or send mail to a newly created Googlemail account I get a Socket Read Timeout error.

POP3:
--- Tue, 01 Jul 2008 10:17:08 ---
Connect to 'pop.googlemail.com' port 995, timeout 15.
10:17:08.281 [*] Connection established to 66.249.93.16
10:17:23.281 8: Socket read timeout.
10:17:23.281 --- Connection closed normally at Tue, 01 Jul 2008 10:17:23. ---\0A\0A

SMTP report says the host did not respond.

I have tried increasing the timeout value on the Internet Properties page and on the POP3 and SMTP configuration dialogs to 30 seconds. I have configured the router and the firewall to allow traffic through on the 995 and 465 ports to both pop.googlemail.com and smtp.googlemail.com 

Using MS Office Outlook 2003, it connects immediately.

Anyone have any tips or tricks that I might try to get this working please?

Thanks

I suspect this is a firewall problem becase the pop.googlemail.com is a CNAME fot the real POP3 server.

Answer Section:
    pop.googlemail.com, CNAME, googlemail-pop.l.google.com
    googlemail-pop.l.google.com, A, 72.14.205.29
    googlemail-pop.l.google.com, A, 72.14.205.16
 

Try opening Pegasus Mail to connect to any system on 465 and 995 and see what happens.  FWIW, I use pop.gmail.com for the server without problems so this also might just be a DNS problem as well.

Thanks, Thomas.

I do not think it is a firewall or DNS problem as MS-Office Outlook 2003 is able to connect to the account from the same machine. I can also ping all forms of the address, including the real POP3 server addresses you quote above.

Cheers!

[quote user="Greenman"]

...

I have configured the router and the firewall to allow traffic through on the 995 and 465 ports to both pop.googlemail.com and smtp.googlemail.com 

Using MS Office Outlook 2003, it connects immediately.

[/quote]

Are you using a harware and/or a software firewall ?

Sorry to disagree but Outlook 2003 is not being blocked by the firewall and WinPMail is based on what you have shown. 

We use a software firewall on all the PC's in the network. I have configured this to allow access to googlemail.com, and both the ports.

We also use a router and I have configured this to allow traffic through similarly.

Why do you think it may be a firewall issue? If it was a firewall issue, then MS-Office Outlook 2003 would not be able to connect either.

Edit:

Just saw your reply Thomas. I don't understand how this can be. Pegasus Mail has never been blocked - hang on - going to try my BT account.

I've following settings for the Google SMTP Server, maybe you can try that to see

if it works for you:

Server: smtp.googlemail.com

Port: 25

Timeout: 30 seconds

SSL: STARTTLS

Authentification with username and password

kind regards

Well, I don't know what is going on here. I have been able to get Pegasus to talk to my BT account, but I still get a socket timeout error for google. I'm certain I'm using the correct address etc ????

Edit:

@Tigershark: Tried that and got the same socket error. Thanks for the suggestion.

Your firewall/router  may be blocking these ports from WinPMail.  Turn off the firewall and see what happens.  Any time you get a reject before the server ever answers at all it probably related to something blocking access to the internet.  This is done specifically by application in the Windows firewall and the firewall/router can also be blocking specific ports.

Hi Thomas

Tried turning off the firewall and connecting, but the same thing happens:

POP3 Internet Session Log:
--- Wed, 02 Jul 2008 08:29:17 ---
Connect to 'pop.googlemail.com' port 995, timeout 30.
08:29:17.000 [*] Connection established to 66.249.93.16
08:29:47.000 8: Socket read timeout.
08:29:47.000 --- Connection closed normally at Wed, 02 Jul 2008 08:29:47. ---\0A\0A

I've one more question :-)

Can you connect to the GMail IMAP service, or do

you have the same problem there ?

[quote user="Greenman"]Connect to 'pop.googlemail.com' port 995, timeout 30.
08:29:17.000 [*] Connection established to 66.249.93.16[/quote]

What happens if you manually telnet? 'telnet pop.googlemail.com 995'

I can't get a response on that port, using name or IP - have you switched on ssl?

It also resolves to a different IP for me - 216.239.59.16

Thanks for the responses :)

When I connect using IMAP, the connection is made but I get an error: 'The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform. The operation cannot be completed'.

When I try telnet from the command line (which I have never used before) using your example, a new blank window appears. Does that mean it has connected?

SSL is enabled as per the instructions on Google's page

When I create an IMAP profile for the account in MS-Outlook 2003 it works fine.

[quote user="Greenman"]SSL is enabled as per the instructions on Google's page[/quote]

It's not gettimg the ssl session established.  It's now working for me (different IP this time):

Connect to 'pop.googlemail.com' port 995, timeout 30.
20:26:52.737 [*] Connection established to 66.249.93.29
20:26:52.031 [*] SSL/TLS session established: RC4, OFB mode, keysize 128 bits
20:26:52.032 [*] Certificate user is cn=pop.googlemail.com, o=Google Inc, l=Mountain View, sp=California, c=US
20:26:52.032 [*] Certificate is valid from Fri Mar 14 23:23:24 2008 to Sat Mar 14 23:23:24 2009
20:26:52.032 [*] Certificate fingerprint is 1625F9975881CC05029737ACABDE0103
20:26:52.042 >> 0066 +OK Gpop ready for requests from 212.159.70.14 j33pf2345820ugc.0\0D\0A
20:26:52.042 << 0012 USER atest\0D\0A

What's the full log you get with the IMAP failure (blank out password)?

Hi PaulW, thanks for the response.

I get the following:

--- Thu, 03 Jul 2008 12:23:16 ---
Connect to 'imap.googlemail.com' port 993, timeout 30.
12:23:17.921 [*] Connection established to 66.249.83.16
12:23:47.921 8: Socket read timeout.
12:23:47.921 --- Connection closed normally at Thu, 03 Jul 2008 12:23:47. ---\0A\0A

On the security tab, Via STARTTLS is selected

 --- Thu, 03 Jul 2008 12:27:11 ---
Connect to 'pop.googlemail.com' port 995, timeout 30.
12:27:11.500 [*] Connection established to 66.249.93.16
12:27:41.500 8: Socket read timeout.
12:27:41.500 --- Connection closed normally at Thu, 03 Jul 2008 12:27:41. ---\0A\0A

--- Thu, 03 Jul 2008 12:27:41 ---
Connect to 'smtp.googlemail.com' port 465, timeout 30.
12:27:42.625 [*] Connection established to 64.233.183.29
12:28:12.625 8: Socket read timeout.
12:28:15.031 --- Connection closed normally at Thu, 03 Jul 2008 12:28:15. ---\0A\0A

Bleugh.

[quote user="Greenman"]I get the following:

--- Thu, 03 Jul 2008 12:23:16 ---
Connect to 'imap.googlemail.com' port 993, timeout 30.
12:23:17.921 [*] Connection established to 66.249.83.16
12:23:47.921 8: Socket read timeout.
12:23:47.921 --- Connection closed normally at Thu, 03 Jul 2008 12:23:47. ---\0A\0A

On the security tab, Via STARTTLS is selected[/quote]

TLS?  None of these work for me with tls, I get timeouts like you. They work only with ssl.  These port numbers (995 & 993) are usually only for the older ssl protocol.

Thank you!

OK, after seeing the 'warning' about direct SSL, I assumed it was to be avoided. Have checked 'via direct SSL connect' and it's working great. Assumed this was something different to the the question 'This server requires an encrypted connection (SSL)' presented by Outlook, thought that 'direct' was something antiquated and to be avoided.

Man - these things often have a very simple solution. Sorry for the 'extended' discussion about this, and thanks to everyone for their help.

Glad you've got it working.

[quote user="Greenman"]

thought that 'direct' was something antiquated and to be avoided.

[/quote]

No, just Outlook [:P]