You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OC_User_IMAP Dovecot (no auth attempts in 0 secs) #59
After upgrading to 0.6.0 and modifying the config.php external users are not able to login. In the maillog only one line gets logged, after entering the credentials. Mar 25 02:31:22 mail dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=46.163.73.154, lip=46.163.73.154, TLS, session=<JmSBKeGE2Owuo0ma>
When switching dovecot to courier Mar 25 03:59:30 mail courier-imaps: couriertls: accept: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca
php 7.3 same error
Same issue here (Login failed; "no auth attemps" in Dovecot log). After an hour of trying different options, and comparing to my Roundcube configuration, I was able to solve it by manually specifying CRAM-MD5 as authentication type by manually editing imap.php from
This is probably because I'm using CRAM-MD5 passwords (the default?) in my Dovecot passdb. Likewise, I have to use
$config['imap_auth_type'] = 'CRAM-MD5';
in my Roundcube configuration.
Bottom line: The Roundcube IMAP class supports a lot of more parameters than just "port" and "timeout", and we need a way to specify them in the user_backends configuration please.
yes, that should be doable...
would you like to do this @tweibert? I would be happy to merge a PR :) (this would greatly accelerate it, because my time as a student is limited and there are lots of other things to do for user_external)
I wish I could do a PR, but I don't do PHP development normally, and I have absolutely no knowledge about the structure of the project. I don't feel fit for the job. Will probably break things instead of fixing them ;)
And when it comes to available time - I wish I had as much today as I had as a student (being a father of two, and a self-employed software dev - no PHP though).
hi everyone
we have a nice new approach for IMAP authentication which hopefully also fixes this issue from @rollbrettler in #122 (Thanks a lot to them!)
now we're looking for as much volunteers as possible to test this out, so please take a look at #122 - further info (also on how to proceed) will be following there...
I know this one is closed, but I am unsure where to mention my issue with your app.
I also see these "no auth attempts" lines, but with version 0.9.1, inside a docker container.
See nextcloud/docker#1086 for my initial ticket, pls advise, thanks a lot.
(I already looked at the dovecot servers, they both only offer "AUTH=PLAIN", btw)
Activity
benbrummer commentedon Mar 25, 2019
When switching dovecot to courier
Mar 25 03:59:30 mail courier-imaps: couriertls: accept: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown caphp 7.3 same error
benbrummer commentedon Mar 25, 2019
#52 (comment) another user with same problem
violoncelloCH commentedon Mar 25, 2019
yes, thank you for reporting!
I would like to keep this issue open to discuss it here
cc @PaulFreund
tweibert commentedon Mar 26, 2019
Same issue here (Login failed; "no auth attemps" in Dovecot log). After an hour of trying different options, and comparing to my Roundcube configuration, I was able to solve it by manually specifying CRAM-MD5 as authentication type by manually editing imap.php from
to:
This is probably because I'm using CRAM-MD5 passwords (the default?) in my Dovecot passdb. Likewise, I have to use
in my Roundcube configuration.
Bottom line: The Roundcube IMAP class supports a lot of more parameters than just "port" and "timeout", and we need a way to specify them in the user_backends configuration please.
benbrummer commentedon Mar 26, 2019
@tweibert thanks this fixed it on my side, too
violoncelloCH commentedon Mar 26, 2019
thank you @tweibert for investigating into this!
I'll try to find the best way to allow to pass additional parameters.
tweibert commentedon Mar 27, 2019
I propose you add a fifth, optional, parameter which is an associative array that is merged into
$params.violoncelloCH commentedon Mar 27, 2019
yes, that should be doable...
would you like to do this @tweibert? I would be happy to merge a PR :) (this would greatly accelerate it, because my time as a student is limited and there are lots of other things to do for user_external)
tweibert commentedon Mar 27, 2019
I wish I could do a PR, but I don't do PHP development normally, and I have absolutely no knowledge about the structure of the project. I don't feel fit for the job. Will probably break things instead of fixing them ;)
And when it comes to available time - I wish I had as much today as I had as a student (being a father of two, and a self-employed software dev - no PHP though).
violoncelloCH commentedon Mar 27, 2019
I see...time is precious (however you could learn new things ;) )
if anyone wants to try (just state so here):
The relevant lines would be https://github.com/nextcloud/user_external/blob/master/lib/imap.php#L20-L40 (where we need to make sure, that additional parameter array from config.php will be passed into the class by the constructor) and then https://github.com/nextcloud/user_external/blob/master/lib/imap.php#L73 (where the parameters are passed to roundcube)...
If you have questions - just ask.
29 remaining items
kevo-gt commentedon Dec 16, 2019
Has anyone found a workaround for this in the meantime before the 0.7.1 release?
matthias-scheler commentedon Dec 16, 2019
Yes, I've posted the work around above:
#59 (comment)
kevo-gt commentedon Jan 22, 2020
Thanks but this did not work for me still. I get the same error on the Dovecot server and then the following error on Nextcloud:
Failed to enable crypto at user_external/lib/imap/imap_rcube.php#999"
and
message":"ERROR: Could not connect via roundcube lib: Could not connect to ssl://X.X.X.X:993: Unknown reason"
Any pointers on what could cause this and how I could fix?
violoncelloCH commentedon Feb 4, 2020
hi everyone
we have a nice new approach for IMAP authentication which hopefully also fixes this issue from @rollbrettler in #122 (Thanks a lot to them!)
now we're looking for as much volunteers as possible to test this out, so please take a look at #122 - further info (also on how to proceed) will be following there...
violoncelloCH commentedon Feb 4, 2020
please take a look at this comment with info on how to proceed: #122 (comment)
stefangweichinger commentedon Apr 23, 2020
I know this one is closed, but I am unsure where to mention my issue with your app.
I also see these "no auth attempts" lines, but with version 0.9.1, inside a docker container.
See nextcloud/docker#1086 for my initial ticket, pls advise, thanks a lot.
(I already looked at the dovecot servers, they both only offer "AUTH=PLAIN", btw)