login fail

Friedemann Schorer friedemann at schorers.org
Thu Oct 26 20:25:03 CEST 2017


Just confirmed that creating another user shows the same problem - user 
can login via Kolab Webclient (both with username or email), trying to 
login via telnet fails. Even though I deleted both the original 
"scanner" and "scanner2" users via LDAP browser (JXplorer connected to 
LDAP just fine) I find proof of mapping user "scanner2" to the email 
address "scanner at example.com" which was valid for user "scanner2" 
originally. But they don't exist anymore in LDAP ...

Any hints anyone?


Friedemann

---
Cassandra Claire : I respect your position, Professor, he said. I just 
don't share it.

Am 26.10.2017 18:47, schrieb Friedemann Schorer:
> Hi,
> in order to have my multifunction printer both send and receive emails 
> I added POP3 services to /etc/cyrus.conf:
>> START {
>> # do not delete this entry!
>> recover cmd="ctl_cyrusdb -r"
>> idled cmd="idled"
>> }
>> # UNIX sockets start with a slash and are put into 
>> /var/lib/imap/sockets
>> SERVICES {
>> imaps cmd="imapd -s" listen="127.0.0.1:9993" prefork=5
>> sieve cmd="timsieved" listen="sieve" prefork=0
>> ptloader cmd="ptloader" listen="/var/lib/imap/ptclient/ptsock" 
>> prefork=0
>> lmtpunix cmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1
>> notify cmd="notifyd" listen="/var/lib/imap/socket/notify" proto="udp" 
>> prefork=1
>> pop3 cmd="pop3d" listen="pop3" prefork=3
>> pop3s cmd="pop3d -s" listen="pop3s" prefork=1'
>> }
>> EVENTS {
>> # this is required
>> checkpoint cmd="ctl_cyrusdb -c" period=30
>> # this is only necessary if using duplicate delivery suppression,
>> # Sieve or NNTP
>> duplicateprune cmd="cyr_expire -E 3" at=0400
>> # Expire data older then 69 days. Two full months of 31 days
>> # each includes two full backup cycles, plus 1 week margin
>> # because we run our full backups on the first sat/sun night
>> # of each month.
>> # deleteprune cmd="cyr_expire -E 4 -D 69" at=0430
>> # expungeprune cmd="cyr_expire -E 4 -X 69" at=0445
>> deleteprune cmd="cyr_expire -E 0 -D 0" at=0430
>> expungeprune cmd="cyr_expire -E 0 -X 0" at=0445
>> # this is only necessary if caching TLS sessions
>> tlsprune cmd="tls_prune" at=0400
>> # Create search indexes regularly
>> #squatter cmd="squatter -s -i" at=0530
>> }
> POP3 services can be reached via port 110 and 995 OK.
> Now I tried to add a POSIX user named "scanner" Kolab Webadmin said OK, 
> done - but it won't show up nowhere. And I got to admit, I forgot to 
> write down his randomly generated password.
> OK, let's try something else - I created a Kolab User with the login 
> handle "scanner2" - but I can't login:
>> user at host ~ $ openssl s_client -showcerts -connect schorers.org:995
>> CONNECTED(00000003)
>> [ ... SSL stuff removed ... ]
>> +OK cardhu Cyrus POP3 2.5.11-41-gd53406f3f-Debian-2.5.11.41-0~kolab1 
>> server ready <14367161135700903537.1509035621 at cardhu>
>> USER scanner2
>> +OK Name is a valid mailbox
>> PASS XXXXXXXX
>> -ERR [AUTH] Invalid login
>> quit
>> +OK
> Restarted kolab-saslauthd, kolab-server, postfix and guam services, but 
> to no avail. Access is denied, mail.log shows a SASL error -13
> So, here's some questions:
> - where did that user "scanner" go ???
> - more important: why does login keep failing
> Running Kolab 16 on Debian Etch.
>       any hint appreciated :-D
>                 Friedemann


More information about the users mailing list