@pablo dot livardo : I think that the problem you found is caused by the difference between the client/server encryption methods used.
The 465 port is used for SMTPS, and the server starts the encryption immediately it receives your connection. So, your code will work.
The 587 port is used for Submission (MSA or Mail Submission Agent) which works like the port 25. The server accepts your connection and doesn't activate the encryption. If you want an encrypted connection on the port 587, you must connect on it without encryption, you must start to dialog with the server (with EHLO) and after that you must ask the server to start the encrypted connection using the STARTTLS command. The server starts the encryption and now you can start as well the encryption on your client.
So, in few words, you can not use :
<?php $fp = fsockopen("tls://mail.example.com", 587, $errno, $errstr); ?>
but you can use:
<?php $fp = stream_socket_client("mail.example.com:587", $errno, $errstr); ?>
and after you send the STARTTLS command, you can enable the crypto:
<?php stream_socket_enable_crypto($fp, true, STREAM_CRYPTO_METHOD_SSLv23_CLIENT); ?>
P.S. My previous note on this page was totally wrong, so I ask the php.net admin to remove it.
:)
Genel Ağ Alanı: TCP, UDP, SSL ve TLS
ssl://, tls://,
sslv2:// ve sslv3:// desteklenmektedir.
Bilginize: Hiçbir aktarım belirtilmezse
tcp://öntanımlıdır.
127.0.0.1fe80::1mesela.domtcp://127.0.0.1tcp://fe80::1tcp://mesela.domudp://mesela.domssl://mesela.domsslv2://mesela.domsslv3://mesela.domtls://mesela.dom
Genel Ağ Alanının soketleri bir hedef adrese ek olara bir port numarası gerektirirler. fsockopen() işlevi için bu ikinci bir bağımsız değişken ile belirtilir, dolayısıyla port numarasının IP adresiyle birlikte bir aktarım URLsi olarak biçimlenmesine gerek kalmaz. stream_socket_client() ve ilgili diğer işlevler için ise geleneksel URL gösterimi kullanılır, yani port numarası aktarım URL'sinin sonuna iki nokta imi ile eklemlenir.
tcp://127.0.0.1:80tcp://[fe80::1]:80tcp://mesela.dom:80
Bilginize: Port numaralı IPv6 adresleri
Dikkat ederseniz, yukarıdaki örneklerden ikincisinde IPv6 adresi köşeli ayraçlarını arasına alınmıştır ([fe80::1]). Bunun sebebi IPv6 adresin iki noktalı ayraçlarının, port numarasını eklemleyen iki nokta iminden ayırd edilmesini sağlamaktır.
ssl:// ve tls:// aktarımları (sadece
PHP openssl desteği ile derlenmişse vardırlar) tcp://
aktarımının SSL şifrelemeli uzantılarıdır.
ssl:// aktarımı, uzak konağın yetenek ve tercihlerine
bağlı olarak SSL V2 veya SSL V3 bağlantısı kurmaya çalışacaktır. SSL V2
veya SSL V3 bağlantı istekleri sslv2:// ve
sslv3:// biçeminde açıkça belirtilebilir.
add a note
User Contributed Notes 4 notes
christian at lantian dot eu ¶
11 years ago
stefan at example dot com ¶
14 years ago
Actually, PHP is very able to start with an unencrypted connection and then switch to an encrypted one - refer to http://php.net/stream_socket_enable_crypto .
christian at lantian dot eu ¶
11 years ago
@pablo dot livardo : I think that the problem you found is caused by the difference between the client/server encryption methods used.
You tried to access the port 587 using TLS encryption, but the server uses the SSLv3 encryption on this port.
You can communicate with the Google server on port 465 because on this port the communication is encrypted using TLS and your client is configured to recognize the TLS.
So, if you want to connect on the Google server over the port 587, you simply must write:
<?php
$fp = fsockopen("ssl://mail.example.com", 587, $errno, $errstr);
?>
instead of:
<?php
$fp = fsockopen("tls://mail.example.com", 587, $errno, $errstr);
?>
:)
pablo dot livardo at gmail dot com ¶
15 years ago
I've been having a problem with a TLS connection.
<?php
$fp = fsockopen("tls://mail.example.com", 587, $errno, $errstr);
?>
Which gives me an error of:
SSL operation failed with code 1. OpenSSL Error messages: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
I believe this is caused by PHP not being able to start with an unencrypted connection and then switch to encryption even though the functionality is built into OpenSSL.
For Google Mail users you can avoid this by using port 465 instead of 587.
