similar to: Dovecot did not accept Login from Host

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

Hi, I have Dovecot listening on both IPv4 and IPv6, and can connect on both interfaces, but cannot authenticate over IPv6, using exactly the same credentials as IPv4. I assumed that the same authentication mechanisms would be used, regardless of the protocol being used - are there differences somewhere? For example: ~$ telnet server1.teststable.simplyspamfree.com 143 Trying

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 got trouble with master login thunderbird anounces no INBOX there at master login also telnet looks strange normal user login 1 login ...... 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN

# 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, dovecot 1.2.2 with a second namespace called "Public", mapped to "/export/vmailboxes/public", LIST returning \HasNoChildren: root at testvm06:~# cat /export/vmailboxes/public/dovecot-acl user=cite lrwstiekxa authenticated lrs anyone lrs root at testvm06:~# ls -l /export/vmailboxes/public/.announcements/dovecot-acl lrwxrwxrwx 1 root root 14 Aug 6 03:50

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 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, 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, In Dovecot 2.0 the QUOTA capability is not announced until after the user has logged in. This breaks quota-support in some webmail clients (Roundcube, Atmail, probably more). After searching the lists, I see that this was fixed as a bug back in 1.0, but I guess it crept back in. :-) 1.0.7: * OK Dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND

Here's my conf: # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-71.el6.x86_64 x86_64 CentOS release 6.6 (Final) auth_mechanisms = plain login digest-md5 cram-md5 disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 mail_gid = 89 mail_location = maildir:/coraid-s2l2/domains mail_uid = 89 maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto

On an Ubuntu Server 12.04 system with Dovecot 2.0.19 I am having some trouble with the Dovecot passwords. I am finding this in the logs when I unsuccessfully try to log in: Jul 07 08:13:25 auth-worker: Debug: pam(user at someDomain.com,212. 179.241.14): lookup service=dovecot Jul 07 08:13:25 auth-worker: Debug: pam(user at someDomain.com,212.179.241.14): #1/1 style=1 msg=Password: Jul 07 08:13:27

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:

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

I have very strange problem with masteruser. See two logs below: # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Welcome to our post server! x login nevorotin password x OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT

Hi, why I don't see SORT capability on my dovecot server? # 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. 1 capability * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE

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

Hi I have a problem with STARTTLS, with imaps all ok. I have tried to connect to server with different clients (thunderbird, the bat, mulberry) and had same result. Thunderbird log for example: 0[284708]: 25c0e08:192.168.4.200:NA:SetupWithUrl: clearing IMAP_CONNECTION_IS_OPEN 1920[25c77c8]: ImapThreadMainLoop entering [this=25c0e08] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:ProcessCurrentURL:

On Tue, 04 Apr 2017 11:07:26 +0000 Luca Bertoncello <lucabert at lucabert.de> wrote: > Hi all, > > i've got a strange behaviour with a BlackBerry Classic Phone (BBOS > 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to > fetch mails. > > Before burying myself into debugging sessions, i try to get an > understanding if the following is a Client-