modernizing dovecot.conf
Happy Holidays, And if you like me are working throughout so more senior engineers get their holidays, my condolences hah
Taking the time to bring our dovecot.conf into the 2021/22 era .since its quiet time of year, Do I read it right that where we have things like service imap { process_limit = 1024 executable = imap imap-postlogin
are not needed now ? and process limit is a global option?
things like pop3/imap_client_workarounds = fooy are now global options, not to be in protocol { } sections ?
I am reading the example conf files and see these outside the protocol sections where they have in the past lived, this is what makes me think they are now global and not needed in sub sections. but I may be missing some linking going from file to file , we have forever updated our single config file, just fixing whatever breaks when major versions break something, easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-)
On 2021-12-30 03:34, Laura Steynes wrote:
easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-)
you dont have spare times
doveconf -n
no need to read more
if something should change to the better, it would be better default config, that could lead to less questions on why and how to get xxx to work, currect is not that much helpfull for setup new things with unless we all are developpers sadly, and now that dovecot is not enterprise anymore there is less support there aswell :(
That prints out what I have now, inside protcol sections, which differs from the config examples, so is of no use to my questions, thank you for trying anyway
On Thu, Dec 30, 2021 at 1:13 PM Benny Pedersen <me@junc.eu> wrote:
On 2021-12-30 03:34, Laura Steynes wrote:
easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-)
you dont have spare times
doveconf -n
no need to read more
if something should change to the better, it would be better default config, that could lead to less questions on why and how to get xxx to work, currect is not that much helpfull for setup new things with unless we all are developpers sadly, and now that dovecot is not enterprise anymore there is less support there aswell :(
Because gmail is dumb. good mail client interfaces see reply-all with a mailing list as reply to list only
I'll await someone more knowledgeable to answer my original questions I think
On Thu, Dec 30, 2021 at 2:27 PM Benny Pedersen <me@junc.eu> wrote:
On 2021-12-30 04:58, Laura Steynes wrote:
That prints out what I have now, inside protcol sections, which differs from the config examples, so is of no use to my questions, thank you for trying anyway
this is maillists, why did you reply privately aswell ?, more info ?
HPNY all
On 2021-12-30 05:40, Laura Steynes wrote:
Because gmail is dumb. good mail client interfaces see reply-all with a mailing list as reply to list only
so you are just a gmail victim ? :=)
I'll await someone more knowledgeable to answer my original questions I think
knowledge ?
would imap protocol work on gmail ?, can roundcube use gmail imap protocol ?, would it break leggs or bones ?
if you waiting, start with a question with imho you still have not asked
On 12/29/2021 9:53 PM, Benny Pedersen wrote:
On 2021-12-30 05:40, Laura Steynes wrote:
Because gmail is dumb. good mail client interfaces see reply-all with a mailing list as reply to list only
so you are just a gmail victim ? :=)
I have no experience on this with gmail. I haven't subscribed to any mailing lists with my gmail account.
Thunderbird changed a while back so it ignores a Reply-To header sent by a mailing list and replies to the sender of the email... so if you just press Ctrl-R you will not be sending to the mailing list. It is possible to get the old behavior back by disabling the "mail.override_list_reply_to" setting in the Thunderbird config editor. I can't remember which version made this change.
I'll await someone more knowledgeable to answer my original questions I think
knowledge ?
would imap protocol work on gmail ?, can roundcube use gmail imap protocol ?, would it break leggs or bones ?
Yes, roundcube can access gmail. This is the config I needed to put in roundcube's config file:
$config['default_host'] = 'imaps://imap.gmail.com'; $config['default_port'] = 993;
My mail server cannot connect to imap.gmail.com on port 143, so I had to change it to 993. I tested this by making a copy of my roundcube install on another URL and reconfiguring the copy.
Thanks, Shawn
On 12/30/21 10:34, Laura Steynes wrote:
Do I read it right that where we have things like service imap { process_limit = 1024 executable = imap imap-postlogin are not needed now ? and process limit is a global option?
things like pop3/imap_client_workarounds = fooy are now global options, not to be in protocol { } sections ?
All options are in a sense global. imap_client_workarounds would only affect imap anyway, so the question of putting it the protocol imap {} section or outside is inconsequential.
You would want to put an option in a section when it _would_ affect everything, but you don't want it to. You can also group all imap-only options in a protocol imap {} section if that seems neater to you, and doesn't break anything.
You can override a global option in a service XXX {} or protocol XXX {} section, and the global may be explicitly specified, or the default.
participants (4)
-
Benny Pedersen
-
Gedalya
-
Laura Steynes
-
Shawn Heisey