Aborted login (auth failed)

[Christof Bodner]

Hi,

My SSL auth got invalid, so I updated my SSL configuration (Apache works)

This ist the log:
---
Apr 22 11:01:55 rosi dovecot: imap-login: Debug: SSL: elliptic curve
secp384r1 will be used for ECDH and ECDHE key exchanges
Apr 22 11:01:55 rosi dovecot: imap-login: Debug: SSL: elliptic curve
secp384r1 will be used for ECDH and ECDHE key exchanges
Apr 22 11:01:55 rosi dovecot: auth: Debug: auth client connected (pid=3466)
Apr 22 11:01:55 rosi dovecot: auth: Debug: client in:
AUTH#0111#011PLAIN#011service=imap#011secured#011session=a5AlFA8x3gAB#011lip=::1#011rip=::1#011lport=143#011rport=48350#011resp=
Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1):
lookup service=dovecot
Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1):
#1/1 style=1 msg=Password:
Apr 22 11:01:57 rosi dovecot: auth-worker(3460): pam(test,::1):
pam_authenticate() failed: Authentication failure (password mismatch?)
Apr 22 11:01:59 rosi dovecot: auth: Debug: client passdb out:
FAIL#0111#011user=test
Apr 22 11:01:59 rosi dovecot: imap-login: Aborted login (auth failed, 1
attempts in 4 secs): user=, method=PLAIN, rip=::1, lip=::1,
secured, session=
---
A login via SSH is working, What could be the reason for the login fail?

This is my config:
---
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-85-generic x86_64 Ubuntu 14.04.4 LTS
auth_debug = yes
auth_verbose = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
namespace {
  hidden = yes
  inbox = yes
  list = no
  location = mbox:~/mail:INBOX=/var/mail/%u
  prefix = "#mbox/"
  separator = /
  type = private
}
passdb {
  driver = pam
}
plugin {
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
}
protocols = " imap pop3"
service auth {
  unix_listener /var/spool/postfix/private/auth {
mode = 0666
  }
sl_ca = http://www.oe8.oevsv.at>Landesverband Kärnten
  Christof Bodner, OE8BCK
  Bertha-von-Suttnerstraße 6/4
  9500 Villach

email: mailto:oe8...@oevsv.at
Tel.:  +43-650-7215383
-
GnuPG public key: 0x7204CB8C
Fingerprint 4065 0716 9A15 E26B 2286 9F04 FD3B 74E9 7204 CB8C
-

lda_original_recipient_header overrides RCPT TO?

[Gedalya]

Hi all,

The example config says:

# Header where the original recipient address (SMTP's RCPT TO: address) is taken
# from if not available elsewhere. With dovecot-lda -a parameter overrides this.
# A commonly used header for this is X-Original-To.
#lda_original_recipient_header =

I'm using dovecot 2.2.19

The "if not available elsewhere" bit seems to hold true for LDA, but not for 
LMTP.
That is to say, if the value I want used is passed with LDA using the -a 
option, and another one I want ignored is passed in the header specified in 
this option, it works correctly and I have the address detail in sieve. However 
when using LMTP and the desired value is passed as RCPT TO, and this option is 
defined, and such a header exists -- its value seems to take effect, and is 
matched by sieve as the envelope address.

recipient delimiter translation with exim

[Gedalya]

In case anyone is interested:

Say I want to allow multiple recipient delimiters, possibly more than one 
character long, and dovecot is configured to use the + sign.
In my case I decided to also allow the following: ".-" "__" and ".."

My last router in exim is mysql_user and the one before that is mysql_alias. I 
added the following before mysql_alias:

suffix_translate:
  debug_print = "R: suffix_translate for $local_part@$domain"
  driver = redirect
  domains = +virtual_domains
  local_part_suffix = .-* : __* : ..*
  data = 
${quote_local_part:$local_part${sg{$local_part_suffix}{\N^(\.-|__|\.\.)\N}{+}}}@$domain
# the following is an "optimization" or just a way to make the debug output 
less tedious. It prevents
# exim from going all the way back to the first router with the new address
  redirect_router = mysql_alias

In the dovecot_lmtp transport, I added the rcpt_include_affixes option.

With LDA, use the -a flag as follows:
-a $local_part$local_part_suffix@$domain

With LMTP, using the envelope_to_add option and configuring dovecot to use it 
with the lda_original_recipient_header option, I get an Envelope-To header 
populated with the original recipient, and dovecot uses that one for some 
reason. See my other message posted on this list.

Re: Aborted login (auth failed)

[Steffen Kaiser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 22 Apr 2016, Christof Bodner wrote:


Apr 22 11:01:55 rosi dovecot: auth: Debug: client in:
AUTH#0111#011PLAIN#011service=imap#011secured#011session=a5AlFA8x3gAB#011lip=::1#011rip=::1#011lport=143#011rport=48350#011resp=
Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1):
lookup service=dovecot
Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1):
#1/1 style=1 msg=Password:
Apr 22 11:01:57 rosi dovecot: auth-worker(3460): pam(test,::1):
pam_authenticate() failed: Authentication failure (password mismatch?)


it says failure, are you sure that PAM uses the same backends for Dovecot 
and SSH?



A login via SSH is working, What could be the reason for the login fail?


- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBVxoSrHz1H7kL/d9rAQJ54Qf8DumBO/FuQcky+kO9rln2I7mS8FNdXepU
B6CRjP8JABmxIz6m48ntgPbUZVEztA9ApAfCw6iRLPaCf/NFnia3m1vQeyku49K9
jujF5beVlOsg+HFuttZ4mgTZs2cMnSJaVhzs2NHZtdCMKLzgrC0x5+rm62/VUKsy
EONqpKm8h9lMXhWkFAkA+jpEocgLsdeY0TFcHeCTRirI2dsqNPQ7ifUPg6EtE3pK
ccUL+doe5huZAMtc4JOSZmpGVOvmEmL4ig7Duk+9GmSptZ/7I3jHvOR1yNMaq3sb
buFT5I7FHhP1Avxp6GY/+nTYhPQ+IRu7+aMBdq3vJgWaZyANv7mHLg==
=MsiI
-END PGP SIGNATURE-

push-notification plugin and imap-metadata permissions

[Giovanni S. Fois]

Ultra short version:

Why cant I set the following mailbox metadata key?
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify

Let me explain the context:

I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22

The push-notification plugin is supposed to send out a notification whenever
a mailbox get a new email message.

In order to tell if a mailbox is enabled to send out the notification, the 
plugin
looks out for the following mailbox metadata key:
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify

If the key is set then everything is OK and the notification is sent, otherwise 
the
action is skipped.

If I try to setup the metadata key by hand (telnet as the user over the imap 
port):
setmetadata INBOX (/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify 
"user=myu...@mydomain.com")


I get the error message: "Internal mailbox attributes cannot be accessed"

Digging in the Dovecot 2.2.22 sources i found that:

This string is from lib-imap-storage/imap-metadata.c - line 36 - Dovecot 2.2.22
The message is triggered by the following condition - same file - line 125  - 
Dovecot 2.2.22

if (strncmp(*key_r, MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT,
strlen(MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT)) == 0) {

So the path pvt/server appears to be forbidden.

But, in the file lib-storage/mailbox-attribute.h we can read the following 
comment:

/* User can get/set all non-pvt/ attributes and also pvt/server/
   (but not pvt/server/pvt/) attributes. */

And, after said comment there is the definition of the macro 
MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key)

which has the same basic function of the condition in imap-metadata.c , but in 
this case
the same imap key is seen as accessible.

Now my questions:

Can we use a negated version of MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) 
in imap-metadata?
How can the push-notification plugin work out-of-the-box without changes and 
recompilation?

Thank you for your valuable time and forgive me if I'm posing a dumb question.

Best wishes,
Giovanni S. Fois

Re: push-notification plugin and imap-metadata permissions

[Teemu Huovila]

On 22.04.2016 15:17, Giovanni S. Fois wrote:
> Ultra short version:
> 
> Why cant I set the following mailbox metadata key?
> /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
Why do you want to set it there? Have you tried setting it on some mailbox path?

> 
> Let me explain the context:
> 
> I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22
> 
> The push-notification plugin is supposed to send out a notification whenever
> a mailbox get a new email message.
> 
> In order to tell if a mailbox is enabled to send out the notification, the 
> plugin
> looks out for the following mailbox metadata key:
> /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
> 
> If the key is set then everything is OK and the notification is sent, 
> otherwise the
> action is skipped.
> 
> If I try to setup the metadata key by hand (telnet as the user over the imap 
> port):
> setmetadata INBOX 
> (/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify 
> "user=myu...@mydomain.com")
> 
> I get the error message: "Internal mailbox attributes cannot be accessed"
> 
> Digging in the Dovecot 2.2.22 sources i found that:
> 
> This string is from lib-imap-storage/imap-metadata.c - line 36 - Dovecot 
> 2.2.22
> The message is triggered by the following condition - same file - line 125  - 
> Dovecot 2.2.22
> 
> if (strncmp(*key_r, MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT,
> strlen(MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT)) == 0) {
> 
> So the path pvt/server appears to be forbidden.
> 
> But, in the file lib-storage/mailbox-attribute.h we can read the following 
> comment:
> 
> /* User can get/set all non-pvt/ attributes and also pvt/server/
>(but not pvt/server/pvt/) attributes. */
> 
> And, after said comment there is the definition of the macro 
> MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key)
> which has the same basic function of the condition in imap-metadata.c , but 
> in this case
> the same imap key is seen as accessible.
> 
> Now my questions:
> 
> Can we use a negated version of MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) 
> in imap-metadata?
> How can the push-notification plugin work out-of-the-box without changes and 
> recompilation?
> 
> Thank you for your valuable time and forgive me if I'm posing a dumb question.
Please see instructions at 
http://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mail#Setup_of_the_Dovecot_Push
In case the problem is not resolved, do attach your doveconf -n output to the 
next mail.

br,
Teemu

> 
> Best wishes,
> Giovanni S. Fois

Re: push-notification plugin and imap-metadata permissions

[Giovanni S. Fois]

[cut]

On 04/22/2016 02:57 PM, Teemu Huovila wrote:

Why cant I set the following mailbox metadata key?
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
Why do you want to set it there? Have you tried setting it on some mailbox path?


Do you mean by editing directly the metadata file instead of accessing it with 
an Imap command?
The answer to this question is that I don't have the direct access to the 
physical mailboxes.


Let me explain the context:

I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22

The push-notification plugin is supposed to send out a notification whenever
a mailbox get a new email message.

In order to tell if a mailbox is enabled to send out the notification, the 
plugin
looks out for the following mailbox metadata key:
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify

If the key is set then everything is OK and the notification is sent, otherwise 
the
action is skipped.

If I try to setup the metadata key by hand (telnet as the user over the imap 
port):
setmetadata INBOX 
(/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify 
"user=myu...@mydomain.com")

I get the error message: "Internal mailbox attributes cannot be accessed"

Digging in the Dovecot 2.2.22 sources i found that:

This string is from lib-imap-storage/imap-metadata.c - line 36 - Dovecot 2.2.22
The message is triggered by the following condition - same file - line 125  - 
Dovecot 2.2.22

if (strncmp(*key_r, MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT,
 strlen(MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT)) == 0) {

So the path pvt/server appears to be forbidden.

But, in the file lib-storage/mailbox-attribute.h we can read the following 
comment:

/* User can get/set all non-pvt/ attributes and also pvt/server/
(but not pvt/server/pvt/) attributes. */

And, after said comment there is the definition of the macro 
MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key)
which has the same basic function of the condition in imap-metadata.c , but in 
this case
the same imap key is seen as accessible.

Now my questions:

Can we use a negated version of MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) 
in imap-metadata?
How can the push-notification plugin work out-of-the-box without changes and 
recompilation?

Thank you for your valuable time and forgive me if I'm posing a dumb question.

Please see instructions at 
http://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mail#Setup_of_the_Dovecot_Push
In case the problem is not resolved, do attach your doveconf -n output to the 
next mail.


I have read the instructions, and enabled the metadata options and enabled the lmtp and lda parts as 
stated in the instructions.
I understand that the instructions talk about the Dovecot "http-notify" plugin, which I suppose is 
the old name of the push_notification plugin.
I understand that the Ox Appsuite Mail uses the following imap key 
"/private/vendor/vendor.dovecot/http-notify" instead of the one declared by

the plugin.

I'm not using the OX Appsuite Mail, I just need to get out the notifications out of the plugin 
towards some url of mine which will take care of the message.

In order to get there I need to write said metadata key in the INBOX folders 
metadata .

I know I could write my own plugin or I could recompile the push_notification plugin after changing 
the key.
The problem with this is that my sysadmin wants to install and keep everything updated using only 
original packages.


Attached to this email you will find the output of the dovecot -n command.

I'll be grateful for any hint and suggestion.

Thank you for your time and patience.

Giovanni










# 2.2.23.1 (b1f5a4f): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.13 (93c6eee)
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.10 
auth_debug = yes
auth_default_realm = mydomain.it
auth_master_user_separator = *
auth_mechanisms = cram-md5 digest-md5 plain
auth_realms = mydomain.it
auth_username_format = %l...@mydomain.it
auth_verbose = yes
base_dir = /var/run/dovecot/
disable_plaintext_auth = no
dotlock_use_excl = no
imap_capability = IMAP4rev1 UIDPLUS NAMESPACE QUOTA CHILDREN SORT ID
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
imap_id_log = *
listen = *
mail_attribute_dict = file:%h/Maildir/dovecot-attributes
mail_debug = yes
mail_fsync = always
mail_gid = 
mail_location = sdbox:~/dbox:ALT=/mbx_alt/%5.2h_t2/%12.6h%u
mail_plugins = quota stats notify
mail_uid = 
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character 
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy 
include variables body enotify environment mailbox date index ihave duplicate 
mime foreverypart extracttext vacation-seconds editheader
mmap_disable = yes
namespace inbox {
  inbox = yes
  location = 
  mailbox Draft {
auto = subscribe
special_use = \Drafts
  }
  mailbo

Re: Thunderbird version 45 no longer can login via SSL (UPDATE)

[cjay]

Problem solved.
I had my cipher list too restricted.  I went back to the default:

Was:
MEDIUM:!LOW:!SSLv2

now its:

ALL:!LOW:!SSLv2:!EXP:!aNULL

Thunderbird version 45 is happy now. We are in process of migrating over 
to Office 365, so just have to keep this server happy for a few more 
months.




--
C. J. KeistEmail: cj.ke...@colostate.edu
Systems Group Manager  Solaris 10 OS (SAI)
Engineering Network Services   Phone: 970-491-0630
College of Engineering, CSU
Ft. Collins, CO 80523-1301

All I want is a chance to prove 'Money can't buy happiness'

On 04/21/2016 14:47, CJ Keist wrote:

All,
Just ran into issue with the latest Thunderbird release today,
version 45.0.  This version will no longer login to our dovecot 1.2.17
version. I now this is old version but wanting to know if there is
anyone finding a solution to this?

Right now our work around is to reinstall Thunderbird version 38.7.2

Thanks...

Re: Setting up replication?

[Knute Johnson]

On 4/21/2016 17:53, Edgar Pettijohn wrote:


http://wiki.dovecot.org/MboxLocking


Thanks Edgar, I hadn't seen that page before.  I've tried every 
combination of locking but still get the same errors.


I would love to see somebody's config files that has this working on a 
Ubuntu server.


Thanks,

--

Knute Johnson

Re: Setting up replication?

[Michael Grimm]

Knute Johnson  wrote:

> I disabled replication and don't really know where to go from here. Can 
> anybody give me a hand?

From what I have seen in this thread your configuration looks ok to me.

IIRC, you have two users, only. And, IIRC, the mbox format isn't really suited 
for replication. Thus, I do recommend to migrate to another mailbox format like 
mdbox or sdbox. Migration can be achieved by dsync. You will find examples in 
the archives of this mailing list.

Good luck,
Michael

Re: Aborted login (auth failed)

[Christof Bodner]

Hi,

---
ssh -v -l test 10.0.1.117

debug1: Next authentication method: password
test@10.0.1.117's password:
debug1: Authentication succeeded (password).
Authenticated to 10.0.1.117 ([10.0.1.117]:22).
debug1: channel 0: new [client-session]
---
$ 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] Dovecot (Ubuntu) ready.

a1 LOGIN test 12345
a1 NO [ALERT] Password:
---
Apr 22 20:40:11 rosi dovecot: imap-login: Debug: SSL: elliptic curve 
secp384r1 will be used for ECDH and ECDHE key exchanges
Apr 22 20:40:11 rosi dovecot: imap-login: Debug: SSL: elliptic curve 
secp384r1 will be used for ECDH and ECDHE key exchanges

Apr 22 20:40:11 rosi dovecot: auth: Debug: auth client connected (pid=11154)
Apr 22 20:40:18 rosi dovecot: auth: Debug: client in: 
AUTH#0111#011PLAIN#011service=imap#011secured#011session=012XKBcxmgAB#011lip=::1#011rip=::1#011lport=143#011rport=48794#011resp=
Apr 22 20:40:18 rosi dovecot: auth-worker(11158): Debug: Loading modules 
from directory: /usr/lib/dovecot/modules/auth
Apr 22 20:40:18 rosi dovecot: auth-worker(11158): Debug: Module loaded: 
/usr/lib/dovecot/modules/auth/libdriver_mysql.so
Apr 22 20:40:18 rosi dovecot: auth-worker(11158): Debug: pam(test,::1): 
lookup service=dovecot
Apr 22 20:40:18 rosi dovecot: auth-worker(11158): Debug: pam(test,::1): 
#1/1 style=1 msg=Password:
Apr 22 20:40:20 rosi dovecot: auth-worker(11158): pam(test,::1): 
pam_authenticate() failed: Authentication failure (password mismatch?)
Apr 22 20:40:22 rosi dovecot: auth: Debug: client passdb out: 
FAIL#0111#011user=test#011reason=Password:

---

The PAM configuration is the same:
---
$ cat /etc/pam.d/login
...
# Standard Un*x account and session
@include common-account
@include common-session
@include common-password
...
---
$ cat /etc/pam.d/dovecot
#%PAM-1.0

@include common-auth
@include common-account
@include common-session
@include common-password
---

So I'm quite sure that PAM uses the same backends. Any other ideas?

KR,
Christof

Am 2016-04-22 14:01, schrieb Steffen Kaiser:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 22 Apr 2016, Christof Bodner wrote:


Apr 22 11:01:55 rosi dovecot: auth: Debug: client in:
AUTH#0111#011PLAIN#011service=imap#011secured#011session=a5AlFA8x3gAB#011lip=::1#011rip=::1#011lport=143#011rport=48350#011resp= 


Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1):
lookup service=dovecot
Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1):
#1/1 style=1 msg=Password:
Apr 22 11:01:57 rosi dovecot: auth-worker(3460): pam(test,::1):
pam_authenticate() failed: Authentication failure (password mismatch?)


it says failure, are you sure that PAM uses the same backends for 
Dovecot and SSH?



A login via SSH is working, What could be the reason for the login fail?


- -- Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBVxoSrHz1H7kL/d9rAQJ54Qf8DumBO/FuQcky+kO9rln2I7mS8FNdXepU
B6CRjP8JABmxIz6m48ntgPbUZVEztA9ApAfCw6iRLPaCf/NFnia3m1vQeyku49K9
jujF5beVlOsg+HFuttZ4mgTZs2cMnSJaVhzs2NHZtdCMKLzgrC0x5+rm62/VUKsy
EONqpKm8h9lMXhWkFAkA+jpEocgLsdeY0TFcHeCTRirI2dsqNPQ7ifUPg6EtE3pK
ccUL+doe5huZAMtc4JOSZmpGVOvmEmL4ig7Duk+9GmSptZ/7I3jHvOR1yNMaq3sb
buFT5I7FHhP1Avxp6GY/+nTYhPQ+IRu7+aMBdq3vJgWaZyANv7mHLg==
=MsiI
-END PGP SIGNATURE-


--

-
Landesverband Kärnten
  Christof Bodner, OE8BCK
  Pestalozzistzraße  11/6
  9500 Villach

email: mailto:oe8...@oevsv.at
Tel.:  +43-650-7215383
-
GnuPG public key: 8A265334
Fingerprint CF71 08D2 18B8 A824 37A5  B80E 0888 37E1 8A26 5334
-

Re: push-notification plugin and imap-metadata permissions

[Timo Sirainen]

On 22 Apr 2016, at 15:17, Giovanni S. Fois  wrote:
> 
> In order to tell if a mailbox is enabled to send out the notification, the 
> plugin
> looks out for the following mailbox metadata key:
> /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify
> 
> If the key is set then everything is OK and the notification is sent, 
> otherwise the
> action is skipped.
> 
> If I try to setup the metadata key by hand (telnet as the user over the imap 
> port):
> setmetadata INBOX 
> (/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify 
> "user=myu...@mydomain.com")
> 
> I get the error message: "Internal mailbox attributes cannot be accessed"

Server metadata is set with:

a SETMETADATA "" (/private/vendor/vendor.dovecot/http-notify 
"user=myu...@mydomain.com")

Which should internally map into the INBOX's 
/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify.

Re: UTF-8 encoded folders on filesystem

[Pavel Volkovitskiy]

On Thu, Apr 21, 2016 at 1:30 PM, Timo Sirainen  wrote:

> On 21 Apr 2016, at 10:37, Pavel Volkovitskiy  wrote:
> >
> > I wonder if that possible to have utf-8 encoded folders on filesystem
> with
> > dovecot?
> >
> > ​May be this feature planned already?​
>
> mail_location = ...:UTF-8
>
>
​Thanks!​



-- 
Pavel

Progress messages

[Joel Roth]

Hi Dovecot maintainers,

I'm maintainer of Net::IMAP::Client, a perl IMAP client
library.[1]

I've had two bug reports related to Dovecot's in-progress
messages.[2,3]

While patches have been submitted to resolve both of these
bugs, I would like to minimize the possibilty of future 
breakage. Hence the following questions:

1. Which parts of the RFC are relevant to the in-progress messages?

2. Do you have a list of all of Dovecot's in-progress messages?

3. If, in future, other in-progress messages may be added, 
can you provide a standard syntax that I may use
to strip them from the reply stream.

Finally, please CC replies to me, as I am not joined to the
list.

Thank you for your attention.

Joel



1.  https://metacpan.org/pod/Net::IMAP::Client
2.  https://rt.cpan.org/Public/Bug/Display.html?id=84623
3.  https://rt.cpan.org/Public/Bug/Display.html?id=113489




-- 
Joel Roth
  

Re: Progress messages

[Timo Sirainen]

On 23 Apr 2016, at 01:26, Joel Roth  wrote:
> 
> Hi Dovecot maintainers,
> 
> I'm maintainer of Net::IMAP::Client, a perl IMAP client
> library.[1]
> 
> I've had two bug reports related to Dovecot's in-progress
> messages.[2,3]
> 
> While patches have been submitted to resolve both of these
> bugs, I would like to minimize the possibilty of future 
> breakage. Hence the following questions:
> 
> 1. Which parts of the RFC are relevant to the in-progress messages?
> 
> 2. Do you have a list of all of Dovecot's in-progress messages?
> 
> 3. If, in future, other in-progress messages may be added, 
> can you provide a standard syntax that I may use
> to strip them from the reply stream.

IMAP server is free to send any untagged replies to the client at any time. The 
IMAP clients should parse the wanted information from the received untagged 
replies and ignore the rest. It sounds like your IMAP library is doing exactly 
the opposite by treating any unexpected untagged replies as errors.

Here's an excerpt from the RFC:

   Certain server data MUST be recorded by the client when it is
   received; this is noted in the description of that data.  Such data
   conveys critical information which affects the interpretation of all
   subsequent commands and responses (e.g., updates reflecting the
   creation or destruction of messages).

   Other server data SHOULD be recorded for later reference; if the
   client does not need to record the data, or if recording the data has
   no obvious purpose (e.g., a SEARCH response when no SEARCH command is
   in progress), the data SHOULD be ignored.

> 2.  https://rt.cpan.org/Public/Bug/Display.html?id=84623

Strictly speaking a SEARCH command can return multiple untagged SEARCH replies, 
all of which should be merged together.. Luckily there are no servers actually 
doing it (that I'm aware of) and I'm not planning on changing Dovecot to do 
that either.

> 3.  https://rt.cpan.org/Public/Bug/Display.html?id=113489

This isn't enough. There are other untagged replies that can be sent. Dovecot 
can also send "* NO .." while it's waiting for locks.

I'm also wondering how your client will behave when receiving unsolicited FETCH 
replies caused by other concurrent clients. For example this can happen:

x uid fetch 1:* internaldate
* 1 FETCH (UID 1 INTERNALDATE "22-Apr-2016 20:41:08 +0300")
* 2 FETCH (UID 2 INTERNALDATE "22-Apr-2016 20:41:08 +0300")
* 3 FETCH (UID 3 INTERNALDATE "22-Apr-2016 20:41:08 +0300")
* 2 FETCH (FLAGS (\Seen))
* 4 EXISTS
x OK Fetch completed (0.001 + 0.000 secs).

Looks like Dovecot currently sends all these unsolicited responses after the 
requested replies, but that's not required by RFC. I'm not planning on changing 
it though, except that enabling NOTIFY extension can cause them to happen at 
any time.

Also, I assume your library doesn't try to use message sequence numbers for 
anything and in general doesn't try to keep track of the latest mailbox state? 
Because that would require tracking the EXPUNGE/EXISTS/FETCH replies, which 
could happen as a result of most of the IMAP commands (except EXPUNGE has 
restrictions).

Also a few links about writing IMAP clients:

http://imapwiki.org/ClientImplementation
http://dovecot.org/imap-client-coding-howto.html
http://dovecot.org/client-commandments.txt