[horde] User not authorized for Mail

Michael J Rubinsky mrubinsk at horde.org
Sun Jun 25 14:54:25 UTC 2017


Quoting James Mohr <horde at jimmo.com>:

> Greetings,
>
> I have a brand new installation of Horde Groupware 5.2.19. I am  
> running openSUSE 42.2 and I have updated the system (zypper update).
>
> HTTP basic authentication is set up for the Horde directory, I am  
> prompted to input the username and password and I can login  
> successfully. Kronolith is set up as the default app and I can  
> create events. On the Horde start page, I have several blocks in the  
> portal setup, two for Email (Mailbox summary and Newest Unseen  
> Messages). In both cases, the title is Error and in the box I see  
> "User XXX is not authorized for Mail". When I click on Mail in the  
> menu bar, I get a prompt to input my username and password. However,  
> the user name and password do not work.

What authentication backend are you using for Horde? Are you really  
using HTTP authentication?


>
> In the system logs (journalctl) I see:
>
> [imp] [login] Server does not support TLS connections.
>
> That seems clear enough so after googling I changed  
> backends.local.php so it now looks like this:
>
> // IMAP server
> $servers['imap'] = array(
>     'disabled' => false,
>     'name' => 'localhost',
>     'hostspec' => 'myhost.mydomain.'tld,
>     'hordeauth' => false,
>     'protocol' => 'imap',
>     'secure' => 'false',
> );

Are you requiring your users to login separately to Email?



> No change. My biggest question at this point is to what exactly is  
> Horde connecting. IMAP? POP3? My assumption is IMAP because of the  
> complete log entry:

Yes, according to the above configuration stanza, you are connecting  
to an IMAP server running on 'myhost.mydomain.tld'. I'm assuming the  
misplaced quotation mark in your stanza is a typo, as that would cause  
a parse error in PHP when loaded.


> Jun 24 16:32:37 sonne-new HORDE[3058]: [imp] [login] Server does not  
> support TLS connections. [pid 3058 on line 730 of  
> "/data/home/user/public_html/horde/imp/lib/Imap.php"]

You either need to configure your IMAP server to use TLS or disable it  
in your configuration.

> However, from what I googled, the "secure=false" entry above should  
> tell horde not to use any security.
>
> It seems to me that either I need to tell Horde not to try a TLS  
> connect or setup whatever Horde is connecting to at this point to  
> use TLS.
>
> I tried to disable a TLS connection in Horde, so in the Horde Mailer  
> config, I have
> "Use a SMTP server (HIGHLY RECOMMENDED)"
> host: localhost
> port: (empty)
> encyption: none  (I have also tried tls and ssl)
> authenticate to SMTP server: no

This has nothing to do with connecting TO your IMAP server. This is  
for your outgoing mail.


> The password for the http authentication, the local user, are all  
> the same. sasldblistusers2 shows the user. My question here is what  
> format the users should have:
> username at localhost
> username at hostname
> username at hostname.domain.tld
> username at domain.tld

I am confused as to exactly what authentication backend you are using  
in Horde. As far as the general question about thr format of the  
users, that depends entirely on what the authentication backend is  
expecting. There is no one right answer.


> The mailbopx was created using cyradm and the permissions look like this:
> localhost.localdomain> listacl user.myuser
> user.myuser lrswipkxtecda
>
> I have successully tested the username using telnet to connect to  
> ports 110(POP3) and 143 (IMAP), as well as with testsaslauthd.

Port 143 is the TLS port for IMAP, so it seems that your server *does*  
support this?

>
> In the Horde permissions imp is configured so "All Authenticate  
> Users" have all permissions.
>
> I have enable the Horde test scripts and can login to localhost  
> using both the IMAP and POP3 and setting "Use Secure Connection" to  
> both No and Yes.
>
> saslauthd, cyrus, postfix, imapd are running
> ps -ef | grep cyrus
> cyrus    19814     1  1 15:00 ?        00:00:00 /usr/lib/cyrus/bin/master -d
> cyrus    19818     1  0 15:00 ?        00:00:00 idled
>
> ps -ef | grep authd
> root     19884     1  0 15:04 ?        00:00:00 /usr/sbin/saslauthd  
> -a pam -n 5
> root     19885 19884  0 15:04 ?        00:00:00 /usr/sbin/saslauthd  
> -a pam -n 5
> root     19886 19884  0 15:04 ?        00:00:00 /usr/sbin/saslauthd  
> -a pam -n 5
> root     19887 19884  0 15:04 ?        00:00:00 /usr/sbin/saslauthd  
> -a pam -n 5
> root     19888 19884  0 15:04 ?        00:00:00 /usr/sbin/saslauthd  
> -a pam -n 5
>
> ps -ef | grep postfix
> root      1989     1  0 Jun21 ?        00:00:02 /usr/lib/postfix/master -w
> postfix   1996  1989  0 Jun21 ?        00:00:00 qmgr -l -t fifo -u
> postfix  19716  1989  0 14:56 ?        00:00:00 pickup -l -t fifo -u
> postfix  19844  1989  0 15:03 ?        00:00:00 smtpd -n smtp -t  
> inet -u -o stress= -s 2 -o content_filter=spamchk:dummy
> postfix  19845  1989  0 15:03 ?        00:00:00 proxymap -t unix -u
> postfix  19846  1989  0 15:03 ?        00:00:00 anvil -l -t unix -u
>
> ps -ef | grep imap
> cyrus    22211 22202  2 16:31 ?        00:00:00 imapd
>
> For all applications I have "SQL DB schema is ready" and  
> "Application is ready"
>
> Any assistence is appreaciated.
>
> Regards,
> James
>
>
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 9272 bytes
Desc: PGP Public Key
URL: <https://lists.horde.org/archives/horde/attachments/20170625/8a72d003/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 821 bytes
Desc: PGP Digital Signature
URL: <https://lists.horde.org/archives/horde/attachments/20170625/8a72d003/attachment-0001.bin>


More information about the horde mailing list