jberrenberg / docker-davmail Goto Github PK

When I connect from Thunderbird to the imap port 1143 exposed by davmail, I get this error ... anyone already faced this issue ?

docker build went fine

I'm starting the container with

docker run --rm -p 1143:1143 -v /home/mdaviot/dav/docker-davmail/davmail.properties:/etc/davmail/davmail.properties davmail     

config default from http://davmail.sourceforge.net/serversetup.html with only changed server url.

from host telnet 127.0.0.1 1143 not working

Hello,
I cannot setup ssl following this site: http://davmail.sourceforge.net/sslsetup.html

Unable to bind server socket for SMTP on port 1025: Exception creating secured server socket : davmail.p12 (No such file or directory)Unable to bind server socket for POP on port 1110: Exception creating secured server socket : davmail.p12 (No such file or directory)Unable to bind server socket for IMAP on port 1143: Exception creating secured server socket : davmail.p12 (No such file or directory)Unable to bind server socket for CALDAV on port 1080: Exception creating secured server socket : davmail.p12 (No such file or directory)Unable to bind server socket for LDAP on port 1389: Exception creating secured server socket : davmail.p12 (No such file or directory)

Is everything alright with your container?
Thanks

Thanks a lot for making this docker setup!

My davmail.properties has the following in the Log setup:

# Loggings settings

# log file path, leave empty for default path
#davmail.logFilePath=/var/log/davmail.log
davmail.logFilePath=/dev/null
# maximum log file size, use Log4J syntax, set to 0 to use an external rotation mechanism, e.g. logrotate
#davmail.logFileSize=1MB
davmail.logFileSize=1MB
# log levels
log4j.logger.davmail=WARN, default.out
log4j.logger.httpclient.wire=WARN, default.out
log4j.logger.org.apache.commons.httpclient=WARN, default.out
log4j.rootLogger=WARN, default.out
log4j.appender.default.out=org.apache.log4j.ConsoleAppender
log4j.appender.default.out.threshold=INFO
log4j.appender.default.out.layout=org.apache.log4j.PatternLayout
log4j.appender.default.out.layout.ConversionPattern=%-5p %c: %m%n

But DEBUG style logs are pouring out of the container, so much that in the last 2 months, it created a 325GB log file. What else can I look at?

Thanks!

When preparing the p12 file with openssl 3 with openssl pkcs12 -export -in cert.pem -inkey key.pem -certfile cert.pem -out davmail.p12, it can no longer be read by davmail, probably because of a too old JDK version.
It produces this error

davmail_1 | 2022-11-12 12:21:32,360 ERROR [main] davmail - Unable to bind server socket for SMTP on port 1025: Exception creating secured server socket : parseAlgParameters failed: ObjectIdentifier() -- data isn't an object ID (tag = 48)Unable to bind server socket for POP on port 1110: Exception creating secured server socket : parseAlgParameters failed: ObjectIdentifier() -- data isn't an object ID (tag = 48)Unable to bind server socket for IMAP on port 1143: Exception creating secured server socket : parseAlgParameters failed: ObjectIdentifier() -- data isn't an object ID (tag = 48)Unable to bind server socket for CALDAV on port 1080: Exception creating secured server socket : parseAlgParameters failed: ObjectIdentifier() -- data isn't an object ID (tag = 48)Unable to bind server socket for LDAP on port 1389: Exception creating secured server socket : parseAlgParameters failed: ObjectIdentifier() -- data isn't an object ID (tag = 48)

The solution is to use the -legacy argument:
openssl pkcs12 -legacy -export -in cert.pem -inkey key.encrypted -certfile cert.pem -out davmail.p12

Would it make sense to switch to a newer JDK?
I specifically filed this bug here, because I think it is a packaging issue.