similar to: IMAP COMPRESS not announced while using imap_zlib plugin

I still see the issue below. Is there anyone running separate LMTP logging that could check if they experience the same issue? Best regards Henrik Larsson -------- Original Message -------- Subject: "doveadm log reopen" don't reopen separate lmtp log Date: Sun, 25 Sep 2011 00:23:49 +0200 From: Henrik Larsson <dovecot-user at spambox.dk> To: dovecot at dovecot.org Dear all

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 =

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'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, 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 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

IMAP logins via fetchmail are failing on my mailserver root at grelber:/home/esr# tail -f /var/log/mail.err Nov 24 16:56:48 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/cathy Nov 24 16:56:48 grelber dovecot: IMAP(cathy): Fatal: Namespace initialization failed Nov 24 16:57:39 grelber dovecot: IMAP(cathy):

Obviously I did something wrong, but I don't have SORT and THREAD Capabilities built into my 2.0.7 server (OpenSolaris 5.11 snv_134 i86pc i386 i86xpv Solaris) What do I need to do? * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] VFEmail.net ready. 1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+

> On 02 August 2018 at 16:08 Henrik Larsson <dovecot-user at spambox.dk> wrote: > > > On 15-07-2018 11:42, Henrik Larsson wrote: > > After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, > > managesieve stopped working. > > > > I'm using FreeBSD ports tree, to build these. Only domains have been > > modified in below output. > >

> On 02 August 2018 at 16:22 Henrik Larsson <dovecot-user at spambox.dk> wrote: > > > On 02-08-2018 15:16, Aki Tuomi wrote: > >> On 02 August 2018 at 16:08 Henrik Larsson <dovecot-user at spambox.dk> > >> wrote: > >> > >> > >> On 15-07-2018 11:42, Henrik Larsson wrote: > >> > After upgrading Dovecot to 2.3.2.1

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 '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=CRAM-MD5 AUTH=DIGEST-MD5

After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, managesieve stopped working. I'm using FreeBSD ports tree, to build these. Only domains have been modified in below output. A FreeBSD bug report have also been created. But I'm not sure if this is FreeBSD ports related or Dovecot/Pigeonhole related: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228067 %uname -a FreeBSD

On Mon, 2015-09-07 at 20:37 +0300, Timo Sirainen wrote: > It says "tried to use unsupported auth mechanism". In your later mail > you say that telnet shows AUTH=GSSAPI in capabilities. So that would > mean that the client isn't using AUTHENTICATE GSSAPI but something > else. I'd been considering that perhaps my version of Evolution was too old, so I upgraded from

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'm trying to get Dovecot to use Drupal users password for authenticating IMAP users. But I just cant figure out how to make Dovecot understand the password hash type that Drupal 7 is using. My example user with password Teacher1 looks like this in Drupal database: $S$DZwJa.U8HXT2PvTmwCK13rGEYEvnx5DB6/hlqnfCBum4s4U7MVWU Dovecot retrieves this hash but complains that its not a recognized

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

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

Am Montag, den 15.06.2015, 13:33 -0400 schrieb Steve Matzura: > I think I have it now! Found info about *correctly* defining > namespaces. I now get the following when telnetting in, and it all > looks valid. > > Trying 127.0.0.1... > Connected to 127.0.0.1. > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE >

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

# 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