Context

Greetings. I'm not an expert in networks and stuff like DNS, SSL/TLS, Postfix, Dovecot, etc. So I was trying to play with the mail server container in my home-brewed lan server with no fancy security stuff. And I disabled as much as I could with a target on plain unsecured password "protection".

Expected Behavior

Setting SSL_TYPE= in docker-compose.yml will allow to use plain unsecured password.

Actual Behavior

Server refuses login attempts, it just aborts connection.

Possible Fix

Update description/wiki to reflect current behavior.

Steps to Reproduce

Just follow the README.md.
Update docker-compose.yml with:

environment:
  - ENABLE_SPAMASSASSIN=0
  - ENABLE_CLAMAV=0
  - ENABLE_FAIL2BAN=0
  - ENABLE_POSTGREY=0
  - ONE_DIR=1
  - DMS_DEBUG=1
  - SSL_TYPE=
  - ENABLE_SRS=0

Your Environment

• Amount of RAM available: ~5G
• Mailserver version used: release-v6.1.0
• Docker version used: 18.09.0, build 4d60db4
• Environment settings relevant to the config:

Steps to get it working

Yes, there is a wiki section on plain text access which I overlooked in the beginning and overrode two dovecot config files 10-auth.conf and 10-ssl.conf with:

ssl = no
disable_plaintext_auth=no

Thoughts

My point is that README.md is the first place the user will see and information there should be as accurate as possible. Currently https://github.com/tomav/docker-mailserver/blob/0fb4a6d082cc0a3c8a5d3ff6193d1032329d11d4/target/start-mailserver.sh#L855-L856
has no default option, so emptying SSL_TYPE does nothing. You have to manually disable SSL.

Off topic

While we're there, I'm not a native English speaker, but I believe there's a typo in SSL_TYPE section: manual => Let's you manually specify... should have Let you or maybe even better Allow you.
Just didn't want to raise a separate issue on such a small matter.