6.0.0-beta1
7/5/25

[#12747] Smtp auth port 465
Summary Smtp auth port 465
Queue IMP
Queue Version 6.1.4
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester par.aronsson (at) telia (dot) com
Created 10/09/2013 (4287 days ago)
Due
Updated 10/09/2013 (4287 days ago)
Assigned
Resolved 10/09/2013 (4287 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
10/09/2013 06:57:29 AM par (dot) aronsson (at) telia (dot) com Comment #3 Reply to this comment
It worked!

I've been using IMP since before the last ice age. The ssl:// thing 
may have been from then.

Thanks alot.
10/09/2013 06:45:04 AM Michael Slusarz Comment #2
State ⇒ Not A Bug
Priority ⇒ 1. Low
Reply to this comment
         'host' => 'ssl://smtp.host.com',
This has never been supported in IMP.  (It may have worked, but that 
was a fortunate circumstance.)
As suggested in backends.php I've tried with removing the "ssl://" 
prefix from the host directive and changing to port 587. It doesn't 
work, the connectin times out.

Is this a regression? How can I conf to get things running again?
'secure' => 'ssl'
10/09/2013 06:30:12 AM par (dot) aronsson (at) telia (dot) com Comment #1
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Smtp auth port 465
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
ref: http://bugs.horde.org/ticket/12255

I previous version of IMP I had to mod my conf as descibed in ticket 
12255 to get smtp auth to work with my ISP when sending mail. Using 
backends.local.php :
<?php
$servers['imap']['smtp'] = array(
         'horde_auth' => false,
         'auth' => true,
         'debug' => false,
         'host' => 'ssl://smtp.host.com',
         'imp_auth' => false,
         'localhost' => 'localhost',
         'username' => 'myuname',
         'password' => 'mypass',
         'port' => 465,
);

This no longer works with IMP H5 (6.1.4) Final. It croaks with syslog msg:
HORDE: [imp] Error connecting to SMTP server. [0] 
php_network_getaddresses: getaddrinfo failed:

As suggested in backends.php I've tried with removing the "ssl://" 
prefix from the host directive and changing to port 587. It doesn't 
work, the connectin times out.

Is this a regression? How can I conf to get things running again?


Saved Queries