Your message dated Mon, 10 Apr 2017 21:49:52 +0200
with message-id <[email protected]>
and subject line Re: Bug#675346: courier-imap reports LOGINDISABLED when
IMAP_TLS_REQUIRED is set in /etc/courier/imapd-ssl
has caused the Debian Bug report #675346,
regarding courier-imap reports LOGINDISABLED when IMAP_TLS_REQUIRED is set in
/etc/courier/imapd-ssl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
675346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675346
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: courier-imap
Version: 4.8.0-3
Severity: important
courier-imap listens only on localhost, as I have courier-imap-ssl installed
for connections from outside, and
it is configured to enforce TLS on all connections. Non-ssl courier-imap is
installed so that I do not need to
configure TLS client behaviour on localhost squirrelmail.
After I upgraded to my current version, courier-imap logins from squirrelmail
on localhost started to fail.
I traced this to courier-imap erroneously reporting LOGINDISABLED.
It turns out that if I set IMAP_TLS_ONLY=0 in /etc/courier/imapd-ssl the
problem goes away. Why should non-ssl
courier-imap behaviour depend on a foreign configuration file?
TO REPRODUCE:
install both courier-imap and courier-imap-ssl
set IMAP_TLS_REQUIRED=1 in /etc/courier/imapd-ssl
service courier-imap restart
telnet localhost 143
(CAPABILITY ~ LOGINDISABLED)
set IMAP_TLS_REQUIRED=0 in /etc/courier/imapd-ssl
service courier-imap restart
telnet localhost 143
(CAPABILITY !~ LOGINDISABLED)
-- System Information:
Debian Release: 6.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.39.1-linode34 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages courier-imap depends on:
ii courier-authlib 0.63.0-3 Courier authentication library
ii courier-base 0.65.0-3 Courier mail server - base system
ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib
ii libfam0 2.7.0-17 Client library to control the FAM
ii libgdbm3 1.8.3-9 GNU dbm database routines (runtime
ii postfix [mail-transport 2.7.1-1+squeeze1 High-performance mail transport ag
courier-imap recommends no packages.
Versions of packages courier-imap suggests:
pn courier-doc <none> (no description available)
ii courier-imap-ssl 4.8.0-3 Courier mail server - IMAP over SS
ii mutt [imap-client] 1.5.20-9+squeeze2 text-based mailreader supporting M
-- Configuration Files:
/etc/courier/imapd changed:
ADDRESS=127.0.0.1
PORT=143
MAXDAEMONS=40
MAXPERIP=20
PIDFILE=/var/run/courier/imapd.pid
TCPDOPTS="-nodnslookup -noidentlookup"
AUTHMODULES="authdaemon"
AUTHMODULES_ORIG="authdaemon"
DEBUG_LOGIN=1
IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT
THREAD=REFERENCES SORT QUOTA IDLE AUTH=LOGIN"
IMAP_KEYWORDS=1
IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1
IDLE"
IMAP_IDLE_TIMEOUT=60
IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"
IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"
IMAP_DISABLETHREADSORT=0
IMAP_CHECK_ALL_FOLDERS=0
IMAP_OBSOLETE_CLIENT=0
IMAP_ULIMITD=65536
IMAP_USELOCKS=1
IMAP_SHAREDINDEXFILE=/etc/courier/shared/index
IMAP_ENHANCEDIDLE=0
IMAP_TRASHFOLDERNAME=Trash
IMAP_EMPTYTRASH=Trash:7
IMAP_MOVE_EXPUNGE_TO_TRASH=0
OUTBOX=.Outbox
SENDMAIL=/usr/local/bin/stripandsend
HEADERFROM=X-IMAP-Sender
IMAPDSTART=YES
MAILDIRPATH=Maildir
IMAP_MAILBOX_SANITY_CHECK=0
-- debconf information:
courier-imap/moveconfig: true
--- End Message ---
--- Begin Message ---
Control: fixed -1 4.15-1.3
Hi,
> It turns out that if I set IMAP_TLS_ONLY=0 in /etc/courier/imapd-ssl
> the problem goes away. Why should non-ssl courier-imap behaviour
> depend on a foreign configuration file?
the way it's implemented upstream, both variants read both files, so
it's actually not a foreign config file. Only the ordering makes the
difference:
The ssl variant first loads imapd and then imapd-ssl, allowing the
latter to override variables of the former (without having to repeat it
all). Confusingly, it also works the other way around: the non-ssl
variant first loads imapd-ssl and allows to override variables via imapd.
So, I guess the solution might have been to set IMAP_TLS_ONLY=0 in
/etc/courier/imapd and IMAP_TLS_ONLY=1 in imapd-ssl. However, that flag
doesn't even exist anymore in 4.15 (jessie) and newer, so I'm closing
this issue.
Kind Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
--- End Message ---
