cURL Error No:

0

cURL Error:

cURL Info:

Array
(
    [url] => https://api.smtp2go.com/v3/email/send
    [content_type] => application/json; charset=utf-8
    [http_code] => 200
    [header_size] => 157
    [request_size] => 422
    [filetime] => -1
    [ssl_verify_result] => 0
    [redirect_count] => 0
    [total_time] => 3.453317
    [namelookup_time] => 0.575747
    [connect_time] => 0.859073
    [pretransfer_time] => 1.528535
    [size_upload] => 288
    [size_download] => 362
    [speed_download] => 104
    [speed_upload] => 83
    [download_content_length] => 362
    [upload_content_length] => 288
    [starttransfer_time] => 3.45329
    [redirect_time] => 0
    [redirect_url] => 
    [primary_ip] => 172.233.132.16
    [certinfo] => Array
        (
        )

    [primary_port] => 443
    [local_ip] => 192.168.25.5
    [local_port] => 49406
    [http_version] => 2
    [protocol] => 2
    [ssl_verifyresult] => 0
    [scheme] => https
    [appconnect_time_us] => 1528335
    [connect_time_us] => 859073
    [namelookup_time_us] => 575747
    [pretransfer_time_us] => 1528535
    [redirect_time_us] => 0
    [starttransfer_time_us] => 3453290
    [posttransfer_time_us] => 1528530
    [total_time_us] => 3453317
    [effective_method] => POST
    [capath] => 
    [cainfo] => /etc/pki/tls/certs/ca-bundle.crt
)

Response:

{"request_id":"cea34a45-854e-4d70-8b5c-718ee054d6d6","data":{"succeeded":0,"failed":1,"failures":["An error occurred during the SMTP request: From header sender domain not verified (smtp2go.seochains.com)\nOn your Sending \u003e Verified Senders page\nverify the sender domain or email to be allowed to send. - Code(1XuTz4Cf4WjEsXSi1axUc3PlAo2)"],"email_id":""}}

Verbose Log:

* Host api.smtp2go.com:443 was resolved.
* IPv6: (none)
* IPv4: 172.233.132.16, 194.195.255.167, 185.3.92.204, 104.237.148.81, 139.162.140.14, 104.200.26.186
*   Trying 172.233.132.16:443...
*   Trying 194.195.255.167:443...
* ALPN: curl offers h2,http/1.1
* SSL Trust Anchors:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / secp256r1 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*   subject: CN=*.smtp2go.com
*   start date: May 26 00:00:00 2026 GMT
*   expire date: Dec 10 23:59:59 2026 GMT
*   issuer: C=GB; O=Sectigo Limited; CN=Sectigo Public Server Authentication CA DV R36
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (3072/128 Bits/secBits), signed using sha384WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
*   subjectAltName: "api.smtp2go.com" matches cert's "*.smtp2go.com"
* OpenSSL verify result: 0
* SSL certificate verified via OpenSSL.
* Established connection to api.smtp2go.com (172.233.132.16 port 443) from 192.168.25.5 port 49406 
* using HTTP/1.x
> POST /v3/email/send HTTP/1.1
Host: api.smtp2go.com
Content-Type: application/json
Accept: application/json
Content-Length: 288

* upload completely sent off: 288 bytes
< HTTP/1.1 200 OK
< Content-Type: application/json; charset=utf-8
< X-Forwarded-For: 182.176.112.82
< Date: Wed, 17 Jun 2026 10:06:04 GMT
< Content-Length: 362
< 
* Connection #0 to host api.smtp2go.com:443 left intact