Ok, thanks for all the help and trouble. I found out about an smtp host here at work, so I guess I'm stuck with that one...
Cheers,
Casa
Hi,
I've been a happy pmail user for over 10 years now. The problem I'm experiencing right now is certainly a problem on my side...
I recently put pmail on a USB-stick so I'm able to use it at home as well as at work. It seems that my ISP won't let me send mails from work, so i set pmail up to use my gmail account to send messages in all identities. Unfortunately it doesn't work.
when using -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)
the result is:
--- Mon, 10 Sep 2007 10:33:23 ---
Connect to 'smtp.gmail.com' port 587, timeout 30.
10:33:24.354 15: Peer connect failure (the host has refused the connection).
when using - 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)
the result is:
--- Mon, 10 Sep 2007 10:33:23 ---
Connect to 'smtp.gmail.com' port 465, timeout 30.
10:38:08.453 15: Peer connect failure (the host has refused the connection).
This is probably caused by the port number. When I use port 25 (STARTTLS) at least there is a connection with the gmail server:
--- Mon, 10 Sep 2007 10:09:14 ---Any ideas as to how to solve this issue? If the problem is caused by the network settings at work, is there another solution (e.g. different smtp server)?
Thanks in advance,
Casa
Checkout via telnet what exactly you are connecting to via port 25, it's not a GMail server with that 220 ****************** string in there. I suspect both ports 587 and 465 are being blocked and port 25 is being redirected.
Here's how I have the setup and here's a couple of session logs up to sending the AUTH command.
(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)
--- Mon, 10 Sep 2007 07:27:25 ---
Connect to 'smtp.gmail.com' port 465, timeout 300.
07:27:25.218 [*] Connection established to 64.233.163.111
07:27:26.515 [*] SSL/TLS session established: 3DES, CBC mode, keysize 192 bits
07:27:26.515 [*] Certificate user is cn=smtp.gmail.com, o=Google Inc, l=Mountain View, sp=California, c=US
07:27:26.546 [*] Certificate is valid from Mon Jul 30 16:58:07 2007 to Tue Jul 29 16:58:07 2008
07:27:26.546 [*] Certificate fingerprint is 32666C0ADC4F2DF9832EB4AA22A7E0E7
07:27:26.546 >> 0040 220 mx.google.com ESMTP m1sm4375875nzf\0D\0A
07:27:26.546 << 0020 EHLO [192.168.1.5]\0D\0A
07:27:26.625 >> 0051 250-mx.google.com at your service, [209.128.94.2]\0D\0A
07:27:26.625 >> 0019 250-SIZE 28311552\0D\0A
07:27:26.625 >> 0014 250-8BITMIME\0D\0A
07:27:26.625 >> 0022 250-AUTH LOGIN PLAIN\0D\0A
07:27:26.625 >> 0025 250 ENHANCEDSTATUSCODES\0D\0A
07:27:26.640 << 0012 AUTH LOGIN\0D\0A
--- Mon, 10 Sep 2007 07:39:30 ---
Connect to 'smtp.gmail.com' port 587, timeout 300.
07:39:30.171 [*] Connection established to 64.233.163.111
07:39:31.265 >> 0040 220 mx.google.com ESMTP i5sm4387117nzi\0D\0A
07:39:31.265 << 0020 EHLO [192.168.1.5]\0D\0A
07:39:31.343 >> 0051 250-mx.google.com at your service, [209.128.94.2]\0D\0A
07:39:31.343 >> 0019 250-SIZE 28311552\0D\0A
07:39:31.343 >> 0014 250-8BITMIME\0D\0A
07:39:31.343 >> 0014 250-STARTTLS\0D\0A
07:39:31.343 >> 0025 250 ENHANCEDSTATUSCODES\0D\0A
07:39:31.359 << 0010 STARTTLS\0D\0A
07:39:31.437 >> 0030 220 2.0.0 Ready to start TLS\0D\0A
07:39:31.640 [*] SSL/TLS session established: 3DES, CBC mode, keysize 192 bits
07:39:31.640 [*] Certificate user is cn=smtp.gmail.com, o=Google Inc, l=Mountain View, sp=California, c=US
07:39:31.640 [*] Certificate is valid from Mon Jul 30 16:58:07 2007 to Tue Jul 29 16:58:07 2008
07:39:31.640 [*] Certificate fingerprint is 32666C0ADC4F2DF9832EB4AA22A7E0E7
07:39:38.046 << 0020 EHLO [192.168.1.5]\0D\0A
07:39:38.156 >> 0051 250-mx.google.com at your service, [209.128.94.2]\0D\0A
07:39:38.156 >> 0019 250-SIZE 28311552\0D\0A
07:39:38.156 >> 0014 250-8BITMIME\0D\0A
07:39:38.156 >> 0022 250-AUTH LOGIN PLAIN\0D\0A
07:39:38.156 >> 0025 250 ENHANCEDSTATUSCODES\0D\0A
07:39:38.156 << 0012 AUTH LOGIN\0D\0A
Hi!
Thanks for your fast response and sorry about my late one...
As you can see my settings are the same as yours (I copied them from another of your posts at this forum ;)).
I tried via telnet to connect to both the gmail and my isp's smtp server through various ports but all with the same result: no connection.
Any other suggestions to enable sending mails from my work?
Thanks,
Casa
[quote user="Casa"]
Hi!
Thanks for your fast response and sorry about my late one...
As you can see my settings are the same as yours (I copied them from another of your posts at this forum ;)).
I tried via telnet to connect to both the gmail and my isp's smtp server through various ports but all with the same result: no connection.
Any other suggestions to enable sending mails from my work?
Thanks,
Casa
[/quote]
How about trying a bit of a test. Try using the SMTP host tstephenson.com and send on port 587 using the username casa and password auth for the ESMTP AUTH. This will test to see if the port 587 is open through the firewall. You can first try this via telnet to see if you can connect at all. If this does not work then your only solution is to use one of the SMTP servers at work.
FWIW, email was completely shut down at my company, both ports 587 and 25 were blocked and you could not even use web mail. They did this because the internal lan was getting infected with viruses on a regular basis. I setup Mercury/32, Apache, PHP and SquirrelMail at host and then worked via SquirrelMail and port 80. ;-)
If you meant to use server tstephenson.com on port 587 with smtp authentication, login to the SMTP server using the details: casa/auth, then it didn't work ;(
15: Peer connect failure (the host has refused the connection).
[quote user="Casa"]
If you meant to use server tstephenson.com on port 587 with smtp authentication, login to the SMTP server using the details: casa/auth, then it didn't work ;(
15: Peer connect failure (the host has refused the connection).
[/quote]
Port 587 is open so I guess that all of the low ports are being blocked on your end.
