Re: PROXY protocol

[Tim Groeneveld]

Hey Nikolaos,

 On Sat, 22 Aug 2015 21:56:17 +1000 Nikolaos Milas wrote 
 
 > ...and everything seems to be working fine. Obviously, the proxy sends  
 > requests to different ports. For example, requests received by the proxy  
 > at port 993 are sent to dovecot's port 23003 etc. 

Have you come across any issues after enabling the haproxy on the 
inet_listeners?

Would love to hear if everything is still going OK. I would love to throw
a similar configuration into production.

Regards,
Tim

Re: IMAP Folder Mail Separator

[Alex]

Hi,

 I have a fedora21 install with dovecot-2.2.18, and when creating a new
 subfolder with thunderbird, the actual folder name is
 "Folder1^Folder2" with a carat as a separator, instead of creating
 Folder2 in the Folder1 directory.

 Is this a thunderbird problem? I don't recall having this problem
 prior to upgrading to fedora21, so thought maybe it's a dovecot
 problem.

 Maybe the separator character is customizable?
>>>
>>>
>>> please post your old and the current configuration:
>>>
>>> doveconf -n
>>>
>>> http://wiki2.dovecot.org/MailboxFormat/Maildir
>>> and
>>> http://wiki2.dovecot.org/Plugins/Listescape
>>>
>>> seems to apply in your situation.
>>
>> Perhaps I'm just not understanding, but I've spent the last few days
>> reading through those links, and I just don't understand. I'm really
>> hoping my doveconf output will help. I've also understand this may be
>> a long-standing thunderbird bug, but it worked up until a few months
>> ago after a dovecot/fedora upgrade.
>>
>> # 2.2.18: /etc/dovecot/dovecot.conf
>> # OS: Linux 4.0.7-300.fc22.x86_64 x86_64 Fedora release 22 (Twenty Two)
>> default_client_limit = 2000
>> mail_gid = mail
>> mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u
>> mail_privileged_group = mail
>> mbox_write_locks = fcntl
>> namespace inbox {
>>inbox = yes
>>location =
>>mailbox Drafts {
>>  special_use = \Drafts
>>}
>>mailbox Junk {
>>  special_use = \Junk
>>}
>>mailbox Sent {
>>  special_use = \Sent
>>}
>>mailbox "Sent Messages" {
>>  special_use = \Sent
>>}
>>mailbox Trash {
>>  special_use = \Trash
>>}
>>prefix =
>> }
>> passdb {
>>driver = pam
>> }
>> passdb {
>>driver = pam
>> }
>> protocols = imap pop3
>> service auth {
>>unix_listener /var/spool/postfix/private/auth {
>>  group = postfix
>>  mode = 0660
>>  user = postfix
>>}
>> }
>> service imap-login {
>>inet_listener imap {
>>  port = 0
>>}
>>inet_listener imaps {
>>  port = 993
>>}
>>process_min_avail = 20
>>service_count = 0
>> }
>> service pop3-login {
>>inet_listener pop3 {
>>  port = 0
>>}
>>inet_listener pop3s {
>>  address = 192.168.1.100
>>  port = 995
>>}
>> }
>> ssl_ca = > ssl_cert = > ssl_key = > userdb {
>>driver = passwd
>> }
>> userdb {
>>driver = passwd
>> }
>>
>> Please let me know what other information I can provide to help
>> troubleshoot this.
>>
>> Thanks,
>> Alex
>
> I think this link will prove useful.
>
> http://wiki2.dovecot.org/MboxChildFolders

Yes, that was the solution. Add 'separator = "$"' to the 'namespace
inbox {' section of dovecot.conf. Many suggestions were provided,
including one that said it was a long-standing bug with Thunderbird.
This happened after an upgrade, so I knew it wasn't that bug. I was
surprised to find so much outdated dovecot documentation.

Thanks very much to Edgar and the group for helping me resolve this.

Thanks,
Alex

Shortcomings of Maildir++ layout

[Hadmut Danisch]

Hi,

I am trying to deal with the problem, that under regular mbox format a
path can lead to either a file or a directory, but not both, while under
IMAP, a path is usually both, a message folder containing subfolders.

I found dovecot's approach to this problem, the Maildir++ layout
described under http://wiki2.dovecot.org/MboxChildFolders , and was
astonished to see, what problems come with Maildir++ and how complicated
dovecot tries to deal with them.


I wonder why dovecot is not using a much easier approach and just uses a
configurable prefix and/or suffix like .dir or  for directory names,
e.g.


INBOX   ->   ~/mail/inbox

abc   ->~/mail/abc

abc/def ->   ~/mail/abc.dir/defor ~/mail/___abc___/def


which would make all that trouble with .subscriptions and .index much
more easier. In my eyes the Maildir++ layout is overcomplicated because
of the heap of workarounds to the self-created problems.


regards
Hadmut