similar to: Plaintext Authentication from Localhost

Hi: It appears that at least at one time, Dovecot supported plaintext authentication from localhost, even if disable_plaintext_auth = yes. To wit, the example configuration file reads: # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect

Hi all, Ok, up until now, I've only always allowed IMAPS connections to dovecot on port 993. I want to also start allowing clients to user port143+STARTTLS, but I walso want to make sure both ports are locked down to ONLY allow secure connections. So... is disable_plaintext_auth = yes in the main config enough to accomplish this? http://wiki2.dovecot.org/SSL/DovecotConfiguration says:

Hi Following my last posts, i succeed to connect pop3 in localhost but not in mydomain.org (with dovecot 0.99 it worked) I have this error : -ERR Plaintext authentication disabled. Thanks

This release was actually tested with reading my inbox (500+ messages, mbox, Solaris 8) using Outlook and Evolution v0.96 2002-08-08 Timo Sirainen <tss at iki.fi> * Changed to LGPL v2.1 license + STARTTLS support and optional disabling of plaintext authentication (LOGINDISABLED capability) + Support for custom message flags, each folder can have 26 different. + New configuration

I'm trying to setup IMAP, so that it works via secure connections. I have it working fine over SSL, now I wish to get TLS to work. I have set imap and imaps to both listen on *, and have disable_plaintext_auth = yes, which according to the docs, Disable LOGIN command and all other plaintext authentications unless SSL/TLS is used (LOGINDISABLED capability). So the problem is now, that TLS

Hello all, I've set up a new instance of dovecot 2.0.9 to use as a POP3/IMAP proxy. On trying to login I am told '-ERR Plaintext authentication disallowed on non-secure (SSL/TLS) connections'. I have set 'disable_plaintext_auth = no' (see output of doveconf attached). More curious still is that *this happens for SSL connections too*. Something seems very wrong here. Yelp?

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability

Hi folks. New to both dovecot and openldap. Trying to set up virtual domains using the wanderingbarque howto: http://www.wanderingbarque.com/mailserver.html Platform is RH enterprise 3. Only difference is I'm trying to use phamm instead of jamm: http://phamm.rhx.it/ dovecot doesn't seem to want to play nice with my openldap; everything else (postfix, etc) seems to work alright.

Server: Ubuntu 9.04 desktop edition Dovecot 1.1.11 Issue: I have set dovecot.conf with: disable_plaintext_auth = no but everytime I have a client (Windows Live Mail, ubuntu evolution) connect from the Internet, I have the following type of message: Plaintext authentication disallowed on non-secure (SSL/TLS) connections. in my mail.log, I have: Jul 28 15:09:43 "name" dovecot:

I'd like to disable plaintext authentication (e.g. only allow authentication that does STARTTLS or connects on SSL/TLS only ports) only for certain (most) IP addresses. I want to exempt a few addresses (users coming over known VPNs). Fortunately, all this is coming in over a firewall (Sonicwall) in which I can NAT traffic by IP address to go to specific port numbers. So, if I can establish

Hello, as soon as I set "disable_plaintext_auth = yes", AUTH=GSSAPI vanishes from capabilities. ([CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=GSSAPI AUTH=PLAIN AUTH=LOGIN] vs [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED]) Why? I'm wondering especially because at

Hello everyone, Since the upgrade to 1.0.alpha3 I experience a strange problem with plaintext authentication. I successfully login first few (2-5) times after the dovecot restart, and then on a reason I cannot login any more (both via POP3 and IMAP). I tried to find out what could be the reason for this but I failed. Nothing is changed inside the user's home directory or

Dear Sirs, I have Postfix 2.5 with Dovecot 1.0.0 as authentication server. Can I disable SMTP plaintext authentications for WAN clients, but allow it for LAN ones?

Hi I have problem with dovecot 2.2.10 - plaintext auth without SSL is not working. I'm upgrading old server and want that settings "stay same" as on old server. SSL has to be optional. /var/log/maillog *pop3-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=_._._._, lip=_._._._, session=<cxPkm4Ud5gBb7YZ/>* my settings: [root at mail dovecot]#

Thanks I succeed with disable_plaintext_auth = no I think that it's not good for security. I'm looking for security with pop3s. I made a certificate with cacert.org

Hi, I use dovecot (pop) with gentoo but it's not securize. I would like to use pops but i don't how to do this. I think i have to use certificates... This my dovecot.conf : protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * ssl_disable = no login = imap login = pop3 default_mail_env = maildir:%h/.maildir mbox_locks = fcntl dotlock auth =

Hi, I want to use CRAM-MD5 or DIGEST-MD5 (non-plaintext) authentication for master users, but Dovecot 2.2.13 rejects it with the following log: Sep 1 06:18:08 localhost dovecot: auth: passwd-file(masteruser,10.0.1.20,master,<ZA1s9/oBgAAKAAEU>): Master user logging in as u0001 Sep 1 06:18:08 localhost dovecot: auth: cram-md5(u0001 at example.jp,10.0.1.20,<ZA1s9/oBgAAKAAEU>):

I wasn't able to get DIGEST-MD5 authentication working with passwords stored as plaintext until I tweaked password_generate() to make it not use the domain portion of user at domain.com as the realm. Both evolution and kmail send the email address as the username with no realm; when dovecot tries to convert the username to user + realm, the hash is different and so DIGEST-MD5

thank you for guidance, just to recap the issue was about squirrelmail giving a wrong message : "connection dropped by imap server" instead of "invalid user or password" as advised i connected using command line on both my old and new servers, and have posted the details including the output of dovevcot -n. 1) command prompt login. i put wrong password telnet x.x.x.x 143

I've included the non-defaulted bits of my dovecot.conf file at the bottom of this email. As I understand my set-up it's using unix authentication methods (/etc/passwd via pam?). Considering disable_plaintext_auth and auth_mechanisms, what exactly is being passed? I was hoping to get auth_mechanism = digest-md5 but that's not working out very well right now. It seems I can only