6.0.0-beta1
7/5/25

[#8245] FTP auth fail if you have configured a realm
Summary FTP auth fail if you have configured a realm
Queue Forwards
Queue Version 3.1
Type Enhancement
State Rejected
Priority 1. Low
Owners
Requester mayala (at) unex (dot) es
Created 05/06/2009 (5904 days ago)
Due
Updated 11/13/2013 (4252 days ago)
Assigned
Resolved 11/13/2013 (4252 days ago)
Milestone
Patch No

History
11/13/2013 06:02:42 AM mayala (at) unex (dot) es Comment #3 Reply to this comment
Yes, I know, thanks.

This was a ticket I sent to you four years ago. Now we have lates 
horde/imp/ingo with mail filters working without problems.
11/13/2013 05:19:59 AM Michael Slusarz Comment #2
State ⇒ Rejected
Reply to this comment
Horde has long stopped support for "realm" configuration.  And 
forwards doesn't exist anymore.
05/12/2009 02:01:45 PM Jan Schneider Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ Accepted
 
05/06/2009 10:38:40 AM mayala (at) unex (dot) es Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ FTP auth fail if you have configured a realm
Queue ⇒ Forwards
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
We have a FRAMEWORK_3 installation of horde, imp, forwards, etc.



The horde auth is set as "let a Horde app..." and IMP is doing the 
user auth with a local imap service:



// $servers['imap'] = array(

//    'name' => 'alcazaba',

//    'server' => 'localhost',

//    'hordeauth' => false,

//    'protocol' => 'imap/notls',

//    'port' => 143,

//    'maildomain' => 'alcazaba.unex.es',

//    'smtphost' => 'localhost',

//    'smtpport' => 25,

//    'realm' => 'alcazaba.unex.es',

//    'preferred' => '',

//);



We have defined a realm to allow many others users of other servers to 
auth and not mix the users accounts.



This is our forwards config:



// $conf['server']['params']['default']['host'] = 'localhost';

// $conf['server']['params']['default']['port'] = 8051;

// $conf['server']['params']['default']['pasv'] = false;

// $conf['server']['params']['default']['ssl'] = false;

// $conf['server']['driver'] = 'forwards';

// $conf['enabled']['keeplocal'] = true;

// $conf['enabled']['authenticate'] = false;

// $conf['enabled']['fullemail'] = false;

// $conf['user']['refused'] = array('root', 'bin', 'daemon', 'adm', 
'lp', 'shutdown', 'halt', 'uucp', 'ftp', 'anonymous', 'nobody', 
'httpd', 'operator', 'guest', 'diginext', 'bind', 'cyrus', 'courier', 
'games', 'kmem', 'mailnull', 'man', 'mysql', 'news', 'postfix', 
'sshd', 'tty', 'www');

// $conf['menu']['apps'] = array();



This way, the app don't work. Always the user who try to auth is 
<user>@<realm> and the ftp driver can't auth it because it espects 
only <user>.



On the Vacation module this is solved on config setting the parameter:



// $conf['server']['params']['default']['norealm'] = true



and checking this on the code.



As a workaround we have copied some code from vacation and added it to 
forwards for made the things to work:



on Driver.php at the Forwards_Driver() construct function you have coded:



//        $this->_params = $params;

//        $this->_user = $user;



and we have added:



//        $this->_params = $params;

//>       if (explode('@', $user, 2)) {

//>           @list($user,) = explode('@', $user, 2);

//>       }

//        $this->_user = $user;



This way the module works on our installation with the indicated 
configuration.



May be you can add some parameter on configuration like the vacation 
one and check it to allow this kind of environmente to work.



Thanks!



Manuel P. Ayala

mayala@unes.es



F. Biblioteconomía y Documentación

Universidad de Extremadura

Badajoz (Spain)


Saved Queries