similar to: gssapi considered as PLAIN?

Hi Timo, As http://wiki2.dovecot.org/Authentication/MasterUsers states, currently the first way for master users to log in as other users only supports PLAIN SASL mechanism, and because DIGEST-MD5 uses user name to calculate MD5 digest, the second way can't support DIGEST-MD5. I enhance the code to support DIGEST-MD5 too for the first way, please review the attached patch against

Hi, I can no longer connect to Dovecot (IMAP). The connection is terminated by Dovecot after Client Helo. My server: Dovecot 2.3.3 Debian buster/sid Architecture: ppc My problems started in late August after upgrading Dovecot. SSL settings: ssl_dh = </etc/ssl/dh2048.pem ssl_min_protocol = TLSv1.2 ssl_cipher_list =

Hi, I am new to this list and to dovecot. Forgive me if I ask long discussed items. I managed to install postfix and dovecot 1.0.rc15 on a Debian Sarge server out of the backports. It works so far, I can send emails via smtp to postfix, they are stored in the virtual mailboxes of some users, and I can get them via IMAP from dovecot. However, in dovecot.conf I configured mechanisms =

I'm trying to enable the IMAP COMPRESS plugin listed here: http://wiki2.dovecot.org/Plugins/Compress I have added zlib globally and imap_zlib to the imap protocol. This is the output from doveconf -n with regards to mail_plugins: --cut-- mail_plugins = zlib protocol imap { mail_plugins = zlib imap_zlib } --cut But it seem like the feature is not announced when connecting to the IMAP

azurit at pobox.sk and Tom Sommer asks: > How this ID extension can be enabled in Dovecot? From which version is > it supported? Accordind to Dovecot CAPA's response, it is already enabled * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED] Ready. However, as a previous poster noted, Dovecot doesn't do anything with it other than

I believe I have the configuration set to use START TLS on IMAP4 (143) and POP3 (110) ports. ?However, it does not seem to be working. ?Yet "STARTTLS" is listed as a capability (which tells me I probably do have it configured right). In the session below, 172.30.0.24 is the mail server I'm putting up. 64.26.60.229 is an outside mail service. A similar thing happens on POP3. The

I'm trying to adapt http://wiki2.dovecot.org/HowTo/ImapcProxy to our Exchange Server, which has LOGINDISABLED on Port 143, and I offering LOGIN on Port 993. How do I go about this? Simply changing imapc_port to: imapc_port = 993 doesnt work: Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS

On Tue, 11 Aug 2015, Dr J Austin wrote: > > > On Tue, 11 Aug 2015, Alexander Dalloz wrote: > >> Am 11.08.2015 um 22:28 schrieb Dr J Austin: >>> >>> Hi Alexander >>> >>> [root at maui:/var/log]$ watch 'tail -n40 maillog >>> >>> does not quiver when I try to connect >> >> That's suspicious. >>

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

On Tue, 11 Aug 2015, Alexander Dalloz wrote: > Am 11.08.2015 um 22:28 schrieb Dr J Austin: >> >> Hi Alexander >> >> [root at maui:/var/log]$ watch 'tail -n40 maillog >> >> does not quiver when I try to connect > > That's suspicious. > > Let's exclude it is the client which causes the problem: Connect directly to > the IMAPS

I have two questions: 1. What method/tool (other than a MuA) can I use to test my Dovecot setup from Windows CLI when ssl is enabled? I have tried connecting to to the pop3/imap4 services from a Windows PC but here is what I get: [pop3] +OK Dovecot-2.0-sis ready. user wash at domain.co.ke -ERR Plaintext authentication disallowed on non-secure (SSL/TLS) connections. [imap4] OK [CAPABILITY

On Mon, 2015-09-07 at 23:15 +0200, Benny Pedersen wrote: > change password before debug logs > > then run debug > > change password > > paste it > > is safe Here's the in rawlog: 1441680001.046492 B00001 AUTHENTICATE GSSAPI 1441680001.051720 YIICZQYJKoZIhvcSAQICAQBuggJUMIICUKADAgEFoQMCAQ6iBwMFACAAAACjggFlYYIBYTC

Hi I have a question regarding the IMAP CAPABILITY command behavior of Dovecot 2.0.rc3. While connecting to a Dovecot 1.2.4 server and requesting the supported capabilities, Dovecot returns all capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE

Hi, I have been using CentOS 5.5 with Dovecot 1.0.7. My client apps login with TLS/SSL using an postgres database for username and password authentication. I developed a plugin that added an additional IMAP command. I want to eventually migrate to release 2.0 but have decided to make this a two step process. I have started with 1.2.17 as I hope this would be a smaller step along the way. I have

# dovecot -n |grep -i sort (nothing) Maybe to full list is only available after authentication? # telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. a login XXXXXXXXXXX YYYYYYYYYYYYYYYY a OK [CAPABILITY

Hi, I'm not sure whether the client or the server is at fault (probably the client), but it's clearly a regression for me. I'm using the LCG Profimail (http://lonelycatgames.com/?app=profimail) application for my Symbian smartphone which has quite decent IMAP capabilities. Amongst others it can do IMAP IDLE (which has to be statically enabled in the server settings, so it's not

Hi ! I have an old Courier IMAP and in front of it, I have put a proxy cache with Dovecot/imapc. I use Debian Wheezy (stable) which package Dovecot in version 2.1.7. I have tested the upgrade to Debian Jessie (testing) which package Dovecot in version 2.2.9 but an assertion is thrown : dovecot: imap(xxx): Panic: file imapc-list.c: line 499 (imapc_list_delete_unused_indexes): assertion failed:

Hi, one Fedora user complains about not some troubles after update to dovecot 1.2. He suspects wrong capability information given by dovecot 1.2 In dovecot.conf he uses imap_capability= option. While response to 'A CAPABILITY' respects imap_capability value, the capability info in hello message does not. for imap_capability=IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA

Hello, I'm running dovecot 1.2.15 and I'm having a problem proxying a user to another host, when this user is logged in with a masteruser. I have two dovecot servers configured to serve half of the users locally and to proxy the other half to the other host. Proxying is done using the masteruser feature (username*proxy) and it works as expected as the following test shows: # nc

On 9.4.2019 9.41, Ludwig Wieland via dovecot wrote: > Hello, > > My Dovecot Master can login but not not select INBOX ! > What's wrong ? > > best regards > Luda > > > > 1) USER can select INBOX: OK > --------------------------------------------------- > telnet localhost imap > Trying ::1... > Connected to localhost. > Escape character is