avoid IMAP-Path-Prefix with dovecot

[Thomas_Krcal]

Hy

On a testing server I switched from courier to dovecot Imap server.
As I understood in dovecot there is no need for this IMAP-Path-Prefix like in courier.
So now I still got all folders in INBOX and I have define INBOX to IMAP-Path-Prefix on any testing e-mail on this testing Server.

Is it possible to avoid this IMAP-Path-Prefix with dovecot (..or otherwise)

Thanks

 

[Thomas_Krcal]

Hello.

I think this forced namespace is a big disadvantage in Courier.
A lot of clients have various problems with sync and subfolders.

I think, I could solve this problem for me with dovecot.

I add a custom conf file:
/etc/dovecot/conf.d/20-kkbits.conf

with content:
# Dovecot My own Config
namespace inbox {
separator = .
prefix =
inbox = yes
}

With this I override the namespace that is define in:
/etc/dovecot/conf.d

# Default private namespace setup compatible with Courier-IMAP.
namespace inbox {
separator = .
prefix = INBOX.
inbox = yes
}

I could not easily remove namespace inbox in /etc/dovecot/conf.d because of:
# PLEASE DON'T EDIT ANYTHING IN THIS FILE! ANY CHANGES WILL BE LOST ON UPGRADE.



Is there any conflict or problem in Mailfolders, Panel, Updates or other issues with this method ?

I tested this method in existing Testmailboxes on various clients and I still had no problem.

Thank you

 

[Lloyd_mcse]

Yeah, this is a pain! Especially if you use Horde ActiveSync.

I did the same as you, and haven't had any issues.

 

[Thomas_Krcal]

Thank you !

Did you know, is there pendant setting like the
MAXPERIP
MAXDAEMONS
from courier

 

[Thomas_Krcal]

And to complete this thread:

Now I expanded the File
/etc/dovecot/conf.d/20-kkbits.conf
with:

protocol imap {
mail_max_userip_connections = 64
}
protocol pop {
mail_max_userip_connections = 64
}

and modivied the namespace sction with:

namespace inbox {
separator = .
prefix =
inbox = yes


mailbox Trash {
auto = no
special_use = \Trash
}
mailbox Drafts {
auto = no
special_use = \Drafts
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
auto = no
special_use = \Sent
}
mailbox Spam {
auto = create
special_use = \Junk
}

}

to get a default like imap-server.

I am appreciate and interested in attention and foreseeable problems.

 

[Lloyd_mcse]

These are set in...

Plesk -> Tools & Settings -> Mail Server Settings

Right under "Max Message Size"

Which controls...

/etc/dovecot/conf.d/92-plesk-service-imap.conf
/etc/dovecot/conf.d//92-plesk-service-pop.conf

containing...

service imap {
service_count = 1
process_limit = 1024
}

and

service pop3 {
service_count = 1
process_limit = 1024
}

And then...

/etc/dovecot/conf.d/92-plesk-userip_connections.conf

with

mail_max_userip_connections = 200

I hope that helps
Kind regards

Lloyd

 

[Thomas_Krcal]

Thank you very much Lloyd !
Until now I did not really checked this Page in Plesk.

And my last Step: To get
SSL on IMAP and POP
I only updated the file:
/etc/dovecot/private/ssl-cert-and-key.pem
with my keyfile

It works for me, but is this the optimal plesk-process to get SSL on Dovecot?

Thanks
Tom !

 

[Lloyd_mcse]

I only updated the file:
/etc/dovecot/private/ssl-cert-and-key.pem
with my keyfile!

It works for me, but is this the optimal plesk-process to get SSL on Dovecot?

No problem mate.

Yeah that's right, it's the simplest.

But you may want to use your own paths and update the ciphers eg

ssl_key = </etc/ssl/private/mail.domain.tld.key
ssl_cert = </etc/ssl/certs/mail.domain.tld.crt

in which case I would update the /etc/dovecot/dovecot.conf with my paths and ciphers and then to make sure it doesn't get changed added it all to..

/etc/dovecot/conf.d/20-ssl.conf

(call it what you like)

eg: 20-ssl.conf

# DH parameters length to use.
ssl_dh_parameters_length = 2048

# SSL protocols to use
ssl_protocols = !SSLv2 !SSLv3

# Prefer the server's order of ciphers over client's.
ssl_prefer_server_ciphers = yes

# Server Cipher List
ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:EDH+aRSA:!aNULL:!eNULL:!RC4:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS

# PEM encoded X.509 SSL/TLS certificate and private key.
ssl_key = </etc/ssl/private/mail.domain.tld.key
ssl_cert = </etc/ssl/certs/mail.domain.tld.crt

I hope that helps.
Kind regards

Lloyd

 

[Thomas_Krcal]

Yes, read somewhere about this,
but in the moment for me there is no need to change the path.

Thank you for all Lloyd