[Dovecot] Proxy setup upgrade from 1.0.3 to 1.1.7
Hi guys!
I hope somebody can help me with my problem:
We have a server running dovecot and proxying IMAPS connections to our
internal network. This worked so far very good until we upgraded the
server to a new SUSE Linux version and with it dovecot from version
1.0.3 to 1.1.7.
My guess is that something changed in the way dovecot reads the user
file as the configuration stayed the same:
dovecot.conf:
base_dir = /var/run/dovecot/
protocols = imaps
disable_plaintext_auth = yes
ssl_cert_file = /pathtocertificate
ssl_key_file = /pathtocertificate
ssl_disable = no
ssl_listen = 80.149.64.98:993
log_path = /var/log/dovecot.log
login_dir = /var/run/dovecot/login
login_process_per_connection = yes
login_processes_count = 3
login_greeting = main.xbdx.de IMAP What can we do for you?
imap_client_workarounds = tb-extra-mailbox-sep
mail_debug = no
auth_debug = yes
auth_cache_size = 4096
auth_cache_ttl = 7200
auth_worker_max_count = 30
auth default {
userdb static {
args = uid=5000 gid=5000
}
passdb {
driver = passwd-file
args = /etc/dovecot/dovecot.passdb
}
socket listen {
client {
path = /var/spool/postfix/private/auth
mode = 0660
user = postfix
group = postfix
}
}
mechanisms = plain login
user = root
count = 1
}
dovecot.passdb:
testuser1:::host=internalip port=143 nodelay=y nologin=y proxy=y
testuser2:::host=internalip port=143 nodelay=y nologin=y proxy=y
dovecot.log:
dovecot: Oct 06 10:37:26 Info: Dovecot v1.1.7 starting up
dovecot: Oct 06 10:37:26 Info: auth(default): passwd-file
/etc/dovecot/dovecot.passdb: Read 2 users
dovecot: Oct 06 10:37:27 Info: auth(default): new auth connection: pid=8135
dovecot: Oct 06 10:37:27 Info: auth(default): new auth connection: pid=8136
dovecot: Oct 06 10:37:27 Info: auth(default): new auth connection: pid=8137
dovecot: Oct 06 10:37:39 Info: auth(default): new auth connection: pid=8139
dovecot: Oct 06 10:37:39 Info: auth(default): client in: AUTH 1
PLAIN service=imapsecured lip=80.149.64.98rip=217.91.33.32
lport=993 rport=61752 resp=hidden
dovecot: Oct 06 10:37:39 Info: auth(default):
cache(adrian.wojcicki,217.91.33.32): miss
dovecot: Oct 06 10:37:39 Info: auth(default):
passwd-file(testuser1,217.91.33.32): lookup: user=testuser1
file=/etc/dovecot/dovecot.passdb
dovecot: Oct 06 10:37:39 Info: auth(default):
passwd-file(testuser1,217.91.33.32): Password mismatch
dovecot: Oct 06 10:37:41 Info: auth(default): client out: FAIL 1
user=testuser1host=internalip port=143nologin proxy
pass=hidden
dovecot: Oct 06 10:37:41 Info: imap-login: Aborted login (auth failed, 1
attempts): user=testuser1, method=PLAIN, rip=217.91.33.32,
lip=80.149.64.98, TLS
Thanks!
Adrian
Re: [Dovecot] Proxy setup upgrade from 1.0.3 to 1.1.7
That helped, it works again. Thanks! Timo Sirainen schrieb: On Oct 6, 2009, at 5:54 AM, Adrian Wojcicki | Unternehmensberatung Wojcicki wrote: We have a server running dovecot and proxying IMAPS connections to our internal network. This worked so far very good until we upgraded the server to a new SUSE Linux version and with it dovecot from version 1.0.3 to 1.1.7. My guess is that something changed in the way dovecot reads the user file as the configuration stayed the same: .. testuser1:::host=internalip port=143 nodelay=y nologin=y proxy=y .. dovecot: Oct 06 10:37:39 Info: auth(default): passwd-file(testuser1,217.91.33.32): Password mismatch Yes, nowadays you need to add nopassword=y also. http://wiki.dovecot.org/Upgrading/1.1 also mentions other things that could affect you.
Re: [Dovecot] Connection problems using dovecot proxy
Timo Sirainen wrote: On Thu, 2008-04-24 at 16:02 +0300, Timo Sirainen wrote: On Wed, 2008-04-23 at 16:00 +0200, Adrian Wojcicki | Unternehmensberatung Wojcicki wrote: Now, while this setup works using Thunderbird, iPhone, etc. I have problems connecting using a Samsung Qbowl. It simply aborts with a connection error. .. Could somebody point me into a direction where to look next? There isn't really anything else you can do except to look at the network traffic using e.g. wireshark or ngrep to see what exactly is different when using the proxy vs. when connecting directly. Actually just noticed another mail about a proxy problem, does this patch fix it: http://hg.dovecot.org/dovecot-1.0/rev/48bfe0940a07 Had no time the last couple of days but could spare some time to try it again today. That was the error with the phone; it didn't accept the two-line reply. The patch solved the problem. Thanks!
[Dovecot] Connection problems using dovecot proxy
Hi Maybe somebody could help me with the following problem: I have set up a dovecot imap proxy in the dmz and a dovecot imap server in the intranet. Both in version 1.05. Now, while this setup works using Thunderbird, iPhone, etc. I have problems connecting using a Samsung Qbowl. It simply aborts with a connection error. Using the same setup but bypassing the proxy and connecting to the imap server directly does work for the phone. Logs on both servers don't show any errors. There is simply a Info: IMAP(test): Connection closed at the end. I enabled the rawlogs on the imap server but they don't long anything (They do log access from other imap clients but nothing from the phone). Could somebody point me into a direction where to look next? LOGS: Dovecot proxy: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_cert_file: pathToCert ssl_key_file: pathToCert disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_debug: yes auth default: cache_size: 4096 cache_ttl: 7200 debug: yes passdb: driver: sql args: /etc/dovecot/sql.conf userdb: driver: static args: static uid=5000 gid=5000 home=/dev/null dovecot: Apr 23 15:42:45 Info: auth(default): client in: AUTH 1 PLAIN service=IMAPlip=192.168.3.200 rip=80.187.64.167 resp=hidden dovecot: Apr 23 15:42:45 Info: auth(default): cache(test,80.187.64.167): hit dovecot: Apr 23 15:42:45 Info: auth(default): cache(test,80.187.64.167): NULL password access dovecot: Apr 23 15:42:45 Info: auth(default): client out: OK1 user=test host=192.168.0.205 destuser=test nologin proxy pass=hidden dovecot: Apr 23 15:42:45 Info: imap-login: proxy(test): started proxying to 192.168.0.205:143: user=test, method=PLAIN, rip=80.187.64.167, lip=192.168.3.200 dovecot: Apr 23 15:42:45 Info: imap-login: proxy(test): disconnecting 80.187.64.167 Dovecot server: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:/home/%u/.maildir mail_debug: yes mail_executable: /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap auth default: debug: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=1001 gid=100 home=/home/%u dovecot: Apr 23 15:42:45 Info: auth(default): client in: AUTH 1 PLAIN service=IMAPlip=192.168.0.205 rip=192.168.2.1 resp=hidden dovecot: Apr 23 15:42:45 Info: auth(default): passwd-file(test,192.168.2.1): lookup: user=test file=/etc/dovecot/passwd dovecot: Apr 23 15:42:45 Info: auth(default): client out: OK1 user=test dovecot: Apr 23 15:42:45 Info: auth(default): master in: REQUEST 6 11785 1 dovecot: Apr 23 15:42:45 Info: auth(default): master out: USER 6 testuid=1001gid=100 home=/home/test dovecot: Apr 23 15:42:45 Info: imap-login: Login: user=test, method=PLAIN, rip=192.168.2.1, lip=192.168.0.205 dovecot: Apr 23 15:42:45 Info: IMAP(test): Effective uid=1001, gid=100, home=/home/test dovecot: Apr 23 15:42:45 Info: IMAP(test): maildir: data=/home/test/.maildir dovecot: Apr 23 15:42:45 Info: IMAP(test): maildir: root=/home/test/.maildir, index=/home/test/.maildir, control=, inbox= dovecot: Apr 23 15:42:45 Info: IMAP(test): Connection closed
