RE: Handling imap from outlook 365
Mr. Krein, Have you set [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\setup] "DisableOffice365SimplifiedAccountCreation"=dword:0001 and then chosen manual setup? That lets us specify 'fred' as the username. Ken From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of todd.kr...@ooma.com Sent: Thursday, September 08, 2022 5:49 PM To: dovecot@dovecot.org Subject: Handling imap from outlook 365 I apologize if this has been answered before, but… Microsoft Outlook 365 doesn’t allow a user to specify the account name for an imap acout, only the email address. Thus f...@smith.com tries to log in as “f...@smith.com” rather than “fred”. Has anyone seen a way to fix this (Microsoft help boards are silent), perhaps by stripping the “@smith.com” during the logon procedure? Thanks, Todd Todd Krein | VP Hardware o:650.566.6657 m:408.857.0556 ooma.com ___ Ooma Confidential and Proprietary (including attachments if any)
Dead links at https://wiki.dovecot.org/Migration/MailFormat
Hi, These links: http://dag.wieers.com/rpm/packages/pine/pine-4.64-3.el4.rf.i386.rpm http://staff.washington.edu/chappa/pine/info/maildir.html on this page https://wiki.dovecot.org/Migration/MailFormat at the Dovecot wiki do not lead to useful results. The dag.wieers.com link seems to redirect to a server at packages.sw.be that does not exist (or does not answer today). Not archived at Wayback Machine as far as I can tell. The washington.edu link returns a 404. This page does appear to be archived by the Wayback Machine, but many of the captures reported by the Wayback Machine actually return no results. I have not checked every capture. I did find a capture from 4 Oct 2008 that does have content. This is the link to that capture. https://web.archive.org/web/20081004145454/http://staff.washington.edu/chappa/pine/info/maildir.html Perhaps someone who attends to the Dovecot Wiki will find this information helpful in updating that page in a useful way. Regards, Ken
Unseen field reported by imap status command returns wrong count for shared mailboxes on dovecot cluster
Hello,
We recently migrated our mail server to a dovecot cluster of 5nodes, a
dovecot proxy, 2directors and 2dovecot backends.
All dovecot nodes run version 2.19.1. We use a glusterfs mounted volume
on the backends forthe mail storage.
We noticed that when issuing the IMAP command to check forUNSEEN
messages formails on the shared namespace instead of seeing the value of
the unseen messages of the user that the mailbox has been shared to,
the value of the unseen messages of the owner of the mailbox is returned.
This behavior causes thunderbird when getting new messages forshared
mailboxes, to show briefly all messages of the mailbox as unseen forthe
user before showing the correct unseen count forthe shared mailbox.
The mail location of the shared mailboxes is defined with imapc storage
type as described inthe documentation.
Is this a dovecot bug? Can we configure a different dovecot
configuration setting so that imap status command reports the correct
unseen field count when mail location is an imapc storage location?
An examples is given below when running doveadm command from one the 2
dovecot directors:
When issuing the status command we see that the unseen count is 2:
root@doved0-rmt0-cn1:/etc/cron.d# doveadm mailbox status -u npyrgiotis
all shared.sysadmins doveadm(npyrgiotis): Info:
remote(10.101.0.71:8080):
doveadm(npyrgio...@domie02.com)<19078><9l8IJTb+GWOGSgAAEU9A+w>:
imapc(10.101.0.75:143): Connected to 10.101.0.75:143 (local
10.101.0.71:33476) shared.sysadmins messages=2 recent=0 uidnext=3
uidvalidity=1662640492 unseen=2 highestmodseq=3 vsize=3950
guid=c92f64f79f0d1ed01e6d5b314f04886c firstsaved=1662643853
shared.sysadmins
messages=2recent=0uidnext=3uidvalidity=1662640492unseen=2highestmodseq=3vsize=3950guid=c92f64f79f0d1ed01e6d5b314f04886c
firstsaved=1662643853
But when fetching the emails of the mailboxes we can see that the \Seen
flag is set for both emails
root@doved0-rmt0-cn1:/etc/cron.d# doveadm fetch -u npyrgiotis flags
mailbox shared.sysadmins ALL doveadm(npyrgiotis): Info:
remote(10.101.0.71:8080):
doveadm(npyrgio...@domie02.com)<19074>:
imapc(10.101.0.75:143): Connected to 10.101.0.75:143 (local
10.101.0.71:38750) flags: \Seen flags: \Seen
Below i post the dovecot configuration of one of the two dovecot backends:
# 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.19 (4eae2f79)
# OS: Linux 5.10.0-17-amd64 x86_64 Debian 11.4
# Hostname: doveb0-rmt0-cn1
auth_cache_negative_ttl = 5mins
auth_cache_size = 50M
auth_debug = yes
auth_default_realm = example.com
auth_master_user_separator = *
auth_mechanisms = plain login
auth_verbose = yes
auth_worker_max_count = 16
disable_plaintext_auth = no
first_valid_uid = 499
hostname = smtp.example.com
imapc_features = fetch-bodystructure fetch-headers rfc822.size search
modseq acl delay-login
imapc_host = 10.101.0.75
imapc_password = # hidden, use -P to show it
imapc_sasl_mechanisms = plain login
imapc_ssl = starttls
imapc_ssl_verify = no
last_valid_uid = 499
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
login_greeting = You have successfully logged into example.com IMAP server
login_trusted_networks = 10.101.0.73 10.101.0.74
mail_always_cache_fields = flags hdr.* date.received date.sent
mail_cache_fields = flags date.received guid size.physical size.virtual
imap.bodystructure body.snippet
mail_debug = yes
mail_fsync = always
mail_plugins = " notify mail_log zlib acl"
mail_privileged_group = mail
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
mdbox_rotate_size = 200M
mmap_disable = yes
namespace example {
list = children
location = imapc:~/shared/%%n:INDEXPVT=~/shared-pvt/%%n
prefix = shared.%%n.
separator = .
subscriptions = no
type = shared
}
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 Spam.Virus {
auto = subscribe
}
mailbox Spam {
auto = subscribe
}
mailbox Trash {
special_use = \Trash
}
prefix =
separator = .
subscriptions = yes
type = private
}
passdb {
args = password=#hidden_use-P_to_show#
driver = static
master = yes
override_fields =
allow_real_nets=127.0.0.0/8,local,10.101.0.73,10.101.0.74
userdb_acl_user=%{auth_user} userdb_namespace/example/disabled=yes
result_success = continue
}
passdb {
args = password=#hidden_use-P_to_show#
driver = static
override_fields = allow_real_nets=127.0.0.0/8,local,10.101.0.73,10.101.0.74
result_success = continue
}
passdb {
args = /etc/dovecot/dovecot-ldap-users.conf.ext
driver = ldap
}
passdb {
args = /etc/dovecot/dovecot-ldap-groups.conf.ext
driver = ldap
}
plugin {
acl = vfile:/etc/dovecot/global-acls/%d/master-dov
Re: mbox to maildir migration, same server?
https://wiki.dovecot.org/Migration/MailFormat
If you have not yet, please read this. Conversion can be done in-place.
While doing the in-place migration, I would strongly suggest keeping the users
out from the server. While it's possible to do while there are users actively
using the server, it is easier when there are no changes going on.
Regards,
Aki
> On 08/09/2022 20:43 EEST kjohn...@eclypse.org wrote:
>
>
> What is the recommended procedure to migrate from mbox to maildir on a server
> already running dovecot? Ideally, this procedure would convert messages in
> an existing mbox INBOX and in ~/mail mboxes (as defined in my dovecot
> configuration) to storage in a ~/Maildir. Some of the INBOXs are rather
> large -- 100's of MB (one of the reasons for migrating).
>
> What I have tried has not worked for me. Below, I describe what I tried, how
> I tested before I tried, what went wrong, and the current setup
> (pre-migration).
>
> What I tried:
> =
>
> stop exim4
>
> service dovecot stop
>
> Make dovecot listen only locally, not to external connections.
>
> /etc/dovecot/local.conf
>
> protocol imap {
> listen = 127.0.0.1:143
> ssl_listen = 127.0.0.1:993
> }
>
> protocol pop3 {
> listen = 127.0.0.1:110
> ssl_listen = 127.0.0.1:995
> }
>
> Modify dovecot configuration for maildir:
> Watch capitalization!
>
> #in 10-mail.conf:
>
> mail_location = maildir:/home/%u/Maildir
>
> namespace inbox {
> separator = /
> }
>
> dovecot -n, to confirm results and perform
> limited syntax checking.
>
> service dovecot start
>
> for each user, in a bash script:
>
> dsync -v -u "$U" mirror "mbox:/home/$U/mail:INBOX=/var/mail/$U"
>
> (if the conversion worked for all users, then reconfigure exim to use maildir
> and restart it; reconfigure dovecot to listen to external interfaces and
> restart.)
>
>
> How I tested:
> =
> Before trying this on the real server, I set up a matching (same versions of
> Debian, Exim, and Dovecot) VM using mbox, with a couple of accounts. One
> using POP3, one using IMAP. The IMAP account was accessed from Claws and
> from Outlook. The test accounts had perhaps a dozen messages on the server.
> I tried the conversion procedure, and everything I tried worked flawlessly.
> (Yes, next time I will move some real inbox files from the live server).
>
>
> What went wrong:
>
> I encountered two types of problems here. The first was several dsync
> warnings (username changed):
>
> dsync(example): Warning: Mailbox changes caused a desync. You may want to run
> dsync again: Remote lost mailbox GUID 21bfa11a81f11763ac15d09efc50 (maybe
> it was just deleted?)
>
> As I understand it, this can result in some or all messages being downloaded
> again by clients. My understanding may be wrong. I also don't understand
> how the mailbox could have changed -- exim4 was stopped, dovecot is only
> listening on 127.0.0.1, and I am the only user who uses a local mail client
> on that system, and this was not my account.
>
> The second problem I encountered seems to match Debian Bug report logs -
> #1011238.
>
> In part of the discussion of that report, the reporter mentions adding -1 to
> the command, as shown:
>
> dsync -v -u "$U" mirror -1 "mbox:/home/$U/mail:INBOX=/var/mail/$U"
>
> While this seemed to eliminate the dsync panic of #1011238, as far as I can
> tell, no old messages were actually moved from the old mbox files to the new
> maildirs. At that point I restored the backup mbox files and undid the
> changes to dovecot and exim4.
>
>
> Current setup:
> ==
> Debian 11.4
> Exim 4.94.2-7
> dovecot 1:2.3.13+dfsg1-2
>
> The current setup with Dovecot was a successful migration from IMAP-UW in
> December 2020.
>
> Output from dovecot -n
> (the list of trusted networks has been removed)
> # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.13 (cdd19fe3)
> # OS: Linux 5.10.0-16-686-pae i686 Debian 11.4
> # Hostname: localhost
> auth_verbose = yes
> mail_location = mbox:~/mail:INBOX=/var/mail/%u
> mail_privileged_group = mail
> 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
> }
> pop3_uidl_format = %08Xv%08Xu
> protocols = " imap pop3"
> ssl_cert = ssl_client_ca_dir = /etc/ssl/certs
> ssl_dh = # hidden, use -P to show it
> ssl_key = # hidden, use -P to show it
> userdb {
> driver = passwd
> }
>
> Thank you to anyone who read this far.
>
> Ken
mbox to maildir migration, same server?
What is the recommended procedure to migrate from mbox to maildir on a server
already running dovecot? Ideally, this procedure would convert messages in an
existing mbox INBOX and in ~/mail mboxes (as defined in my dovecot
configuration) to storage in a ~/Maildir. Some of the INBOXs are rather large
-- 100's of MB (one of the reasons for migrating).
What I have tried has not worked for me. Below, I describe what I tried, how I
tested before I tried, what went wrong, and the current setup (pre-migration).
What I tried:
=
stop exim4
service dovecot stop
Make dovecot listen only locally, not to external connections.
/etc/dovecot/local.conf
protocol imap {
listen = 127.0.0.1:143
ssl_listen = 127.0.0.1:993
}
protocol pop3 {
listen = 127.0.0.1:110
ssl_listen = 127.0.0.1:995
}
Modify dovecot configuration for maildir:
Watch capitalization!
#in 10-mail.conf:
mail_location = maildir:/home/%u/Maildir
namespace inbox {
separator = /
}
dovecot -n, to confirm results and perform
limited syntax checking.
service dovecot start
for each user, in a bash script:
dsync -v -u "$U" mirror "mbox:/home/$U/mail:INBOX=/var/mail/$U"
(if the conversion worked for all users, then reconfigure exim to use maildir
and restart it; reconfigure dovecot to listen to external interfaces and
restart.)
How I tested:
=
Before trying this on the real server, I set up a matching (same versions of
Debian, Exim, and Dovecot) VM using mbox, with a couple of accounts. One using
POP3, one using IMAP. The IMAP account was accessed from Claws and from
Outlook. The test accounts had perhaps a dozen messages on the server. I
tried the conversion procedure, and everything I tried worked flawlessly.
(Yes, next time I will move some real inbox files from the live server).
What went wrong:
I encountered two types of problems here. The first was several dsync warnings
(username changed):
dsync(example): Warning: Mailbox changes caused a desync. You may want to run
dsync again: Remote lost mailbox GUID 21bfa11a81f11763ac15d09efc50 (maybe
it was just deleted?)
As I understand it, this can result in some or all messages being downloaded
again by clients. My understanding may be wrong. I also don't understand how
the mailbox could have changed -- exim4 was stopped, dovecot is only listening
on 127.0.0.1, and I am the only user who uses a local mail client on that
system, and this was not my account.
The second problem I encountered seems to match Debian Bug report logs -
#1011238.
In part of the discussion of that report, the reporter mentions adding -1 to
the command, as shown:
dsync -v -u "$U" mirror -1 "mbox:/home/$U/mail:INBOX=/var/mail/$U"
While this seemed to eliminate the dsync panic of #1011238, as far as I can
tell, no old messages were actually moved from the old mbox files to the new
maildirs. At that point I restored the backup mbox files and undid the changes
to dovecot and exim4.
Current setup:
==
Debian 11.4
Exim 4.94.2-7
dovecot 1:2.3.13+dfsg1-2
The current setup with Dovecot was a successful migration from IMAP-UW in
December 2020.
Output from dovecot -n
(the list of trusted networks has been removed)
# 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.13 (cdd19fe3)
# OS: Linux 5.10.0-16-686-pae i686 Debian 11.4
# Hostname: localhost
auth_verbose = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_privileged_group = mail
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
}
pop3_uidl_format = %08Xv%08Xu
protocols = " imap pop3"
ssl_cert =
Re: Unable to set quota-fs plugin [fixed]
Hi Aki Tuomi, Thanks for your idea, but not, i already tried. Additional information: in my case, mail folders are mounted via nfs, but the same spool, mounted in older dovecot (without systemd) works fine. Jorge Concha C. Área de Sistemas - CEC U. de Chile On 08-09-22 11:53, Aki Tuomi wrote: Maybe SELinux is preventing access? On September 8, 2022 5:38:59 PM GMT+03:00, "Jorge Concha C." wrote: Hello, This solution don't work for me (in Rocky Linux 8 and 9). Do you know other solutions? Or maybe an additional step is necessary? Thanks The issue was in the systemd service file. The option PrivateDevices was setted. It prevents the service to have access to physical devices. I removed this option and from there, quota is reported without errors. Thanks for your support Regards, - Eric Grammatico _/) Jorge Concha C. Area de Sistemas CEC - U. de Chile Aki
Re: Re: Unable to set quota-fs plugin [fixed]
Maybe SELinux is preventing access? On September 8, 2022 5:38:59 PM GMT+03:00, "Jorge Concha C." wrote: >Hello, This solution don't work for me (in Rocky Linux 8 and 9). >Do you know other solutions? >Or maybe an additional step is necessary? > >Thanks > > >> The issue was in the systemd service file. The option PrivateDevices was >> setted. It prevents the service to have access to physical devices. I >> removed this option and from there, quota is reported without errors. >> >> Thanks for your support >> >> Regards, >> >> - >> Eric Grammatico _/) >> > > >Jorge Concha C. >Area de Sistemas >CEC - U. de Chile Aki
Re: Re: Unable to set quota-fs plugin [fixed]
Hello, This solution don't work for me (in Rocky Linux 8 and 9). Do you know other solutions? Or maybe an additional step is necessary? Thanks > The issue was in the systemd service file. The option PrivateDevices was > setted. It prevents the service to have access to physical devices. I > removed this option and from there, quota is reported without errors. > > Thanks for your support > > Regards, > > - > Eric Grammatico _/) > Jorge Concha C. Area de Sistemas CEC - U. de Chile
Re: username changed gu...@example.com -> gumby
On September 8, 2022 4:43:02 PM GMT+03:00, Tom wrote: >On 2022-09-08 02:59, Aki Tuomi wrote: >>> On 08/09/2022 02:00 EEST Tom wrote: >>> As you can see in this snip of the maillog, the domain part of the username >>> is being stripped away: >>> >>> Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn >>> unix:auth-worker (pid=114660,uid=97): auth-worker<2>: >>> passwd(gu...@example.com,10.0.0.70,): Performing userdb >>> lookup >>> Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn >>> unix:auth-worker (pid=114660,uid=97): auth-worker<2>: >>> passwd(gu...@example.com,10.0.0.70,): lookup >>> Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn >>> unix:auth-worker (pid=114660,uid=97): auth-worker<2>: >>> passwd(gu...@example.com,10.0.0.70,): username changed >>> gu...@example.com -> gumby >>> Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn >>> unix:auth-worker (pid=114660,uid=97): auth-worker<2>: >>> passwd(gumby,10.0.0.70,): Finished userdb lookup > >>> How can I get around this issue? I need mailboxes stored by user/domain. >> I don't see how in this config you can even have multiple domains? Using >> passwd ensures that all users are accepted for all domains, because it will >> only look at local username part. > >I'm already using this setup without GSSAPI. Each user can have email >addresses in multiple domains. Validating email addresses is done by FreeIPA >in this case, or LDAP in my prior setup. > >Maybe I need to use another driver. I recommend the LDAP driver. It should make it easier to run various domains. Aki
Re: username changed gu...@example.com -> gumby
On 2022-09-08 02:59, Aki Tuomi wrote: On 08/09/2022 02:00 EEST Tom wrote: As you can see in this snip of the maillog, the domain part of the username is being stripped away: Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn unix:auth-worker (pid=114660,uid=97): auth-worker<2>: passwd(gu...@example.com,10.0.0.70,): Performing userdb lookup Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn unix:auth-worker (pid=114660,uid=97): auth-worker<2>: passwd(gu...@example.com,10.0.0.70,): lookup Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn unix:auth-worker (pid=114660,uid=97): auth-worker<2>: passwd(gu...@example.com,10.0.0.70,): username changed gu...@example.com -> gumby Sep 6 23:12:40 vaj dovecot[114637]: auth-worker(114662): Debug: conn unix:auth-worker (pid=114660,uid=97): auth-worker<2>: passwd(gumby,10.0.0.70,): Finished userdb lookup How can I get around this issue? I need mailboxes stored by user/domain. I don't see how in this config you can even have multiple domains? Using passwd ensures that all users are accepted for all domains, because it will only look at local username part. I'm already using this setup without GSSAPI. Each user can have email addresses in multiple domains. Validating email addresses is done by FreeIPA in this case, or LDAP in my prior setup. Maybe I need to use another driver.
Re: Managesieve not working
Francis Augusto Medeiros-Logeay skrev den 2022-09-08 12:34: Yes, it works. I guess it must be Roundcube, after its update. I need to figure out if the configuration has changed. why ssl on rfc 1918 local non routed networks ? in roundcbe there is example config for no ssl, if this works why not use it then ?
Re: Managesieve not working
Francis Augusto Medeiros-Logeay skrev den 2022-09-08 11:29: Any advice? doveconf -n or i can only give the lotto numbers for next week
Re: Managesieve not working
On 08.09.2022 12:34, Francis Augusto Medeiros-Logeay wrote: Yes, it works. I guess it must be Roundcube, after its update. I need to figure out if the configuration has changed. https://github.com/roundcube/roundcubemail/pull/8670 -- Aleksander Machniak Kolab Groupware Developer[https://kolab.org] Roundcube Webmail Developer [https://roundcube.net] PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
real duplicates of some e-mails / dovecot-2.3.19
Hi, we have the issue, that some(!) e-mails we receive are duplicated when processed by dovecot and stored to the users inbox. The mails are binary identical, same message ID, same size etc. diff sees no difference …. For now we only see that it happens do small mails max. +- 5k in size. And in dose not happen for all mails, but some are spam, some are internal mails some are newsletter which are expected…. and it happens for different users. Dose anyone have/had a similar issue? Any suggestion or idea would be helpful. Thanks . Götz smime.p7s Description: S/MIME cryptographic signature
Re: Managesieve not working
Well, you have configured it to speak SSL. Does openssl s_client -connect
host:port work?
Aki
> On 08/09/2022 12:44 EEST Francis Augusto Medeiros-Logeay
> wrote:
>
>
> Here it is
> # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.7.2 ()
> # OS: Linux 5.4.0-109-generic x86_64 Ubuntu 20.04.4 LTS nfs
> # Hostname: d0ba5bb19b6b
> auth_mechanisms = plain login
> default_vsz_limit = 1 G
> doveadm_password = # hidden, use -P to show it
> doveadm_port = REDACTED
> first_valid_uid = 5000
> haproxy_trusted_networks = 172.18.0.0/16
> last_valid_uid = 5000
> log_path = /var/log/dovecot.log
> mail_gid = vmail
> mail_location =
> maildir:/var/mail/vmail/%d/%n:INDEX=/var/mail/vmail-index/index/%d/%n:CONTROL=/var/mail/vmail-index/control/%d/%n
> mail_plugins = quota notify replication fts fts_solr
> mail_privileged_group = mail
> mail_uid = vmail
> 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 imapsieve vnd.dovecot.imapsieve
> 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 Spam {
> auto = subscribe
> special_use = \Junk
> }
> mailbox Trash {
> special_use = \Trash
> }
> prefix =
> }
> passdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
> plugin {
> fts = solr
> fts_autoindex = yes
> fts_solr = url=http://172.18.0.16:8983/solr/dovecot/
> imapsieve_mailbox1_before =
> file:/var/mail/vmail/mail/sieve/global/report-spam.sieve
> imapsieve_mailbox1_causes = COPY
> imapsieve_mailbox1_name = Spam
> imapsieve_mailbox2_before =
> file:/var/mail/vmail/mail/sieve/global/report-ham.sieve
> imapsieve_mailbox2_causes = COPY
> imapsieve_mailbox2_from = *
> imapsieve_mailbox2_name = Archive
> mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename
> mail_log_fields = uid box msgid size
> mail_replica = tcp:REDACTED
> setting_name = value
> sieve =
> file:/var/mail/vmail/mail/sieve/%d/%n/scripts;active=/var/mail/vmail/mail/sieve/%d/%n/active-script.sieve
> sieve_before = /var/mail/vmail/mail/sieve/global/spam-global.sieve
> sieve_execute_bin_dir = /usr/bin
> sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute
> sieve_pipe_bin_dir = /var/mail/vmail/mail/sieve/global/scripts
> sieve_plugins = sieve_imapsieve sieve_extprograms
> }
> protocols = " imap lmtp sieve pop3"
> replication_max_conns = 300
> service aggregator {
> fifo_listener replication-notify-fifo {
> mode = 0666
> user = vmail
> }
> unix_listener replication-notify {
> mode = 0666
> user = vmail
> }
> }
> service auth-worker {
> user = vmail
> }
> service auth {
> unix_listener /var/spool/postfix/private/auth {
> group = postfix
> mode = 0666
> user = postfix
> }
> unix_listener auth-userdb {
> group = vmail
> mode = 0600
> user = vmail
> }
> }
> service config {
> unix_listener config {
> user = vmail
> }
> }
> service dict {
> unix_listener dict {
> group = vmail
> mode = 0660
> user = vmail
> }
> }
> service doveadm {
> client_limit = 1
> idle_kill = 0
> inet_listener {
> port = REDACTED
> ssl = no
> }
> process_limit = 0
> process_min_avail = 0
> user = vmail
> }
> service lmtp {
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
> group = postfix
> mode = 0600
> user = postfix
> }
> }
> service managesieve-login {
> inet_listener sieve {
> address = 172.18.0.10
> port = 4190
> ssl = yes
> }
> }
> service managesieve {
> process_limit = 1024
> }
> service replicator {
> client_limit = 0
> drop_priv_before_exec = no
> idle_kill = 4294967295 secs
> process_limit = 1
> process_min_avail = 0
> service_count = 0
> unix_listener replicator-doveadm {
> group = vmail
> mode = 0666
> user = dovecot
> }
> vsz_limit = 8 G
> }
> ssl = required
> ssl_cert = ssl_cipher_list = EECDH+AES:EDH+AES+aRSA
> ssl_client_ca_dir = /etc/ssl/certs
> ssl_key = # hidden, use -P to show it
> ssl_prefer_server_ciphers = yes
> userdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
> protocol lmtp {
> mail_plugins = quota notify replication fts fts_solr sieve
> postmaster_address = postmas...@med-lo.eu
> }
> protocol imap {
> mail_plugins = quota notify replication fts fts_solr imap_quota imap_sieve
> }
> protocol sieve {
> managesieve_implementation_string = Dovecot Pigeonhole
> managesieve_max_line_length = 65536
> }
>
> Thanks,
>
> Francis
> > On 8 Sep 2022,
Re: Managesieve not working
> On 08/09/2022 12:29 EEST Francis Augusto Medeiros-Logeay > wrote: > > > Hi, > > I am running dovecot 2.3.7.2 on ubuntu, and have a replication setup. > > I noticed that managesieve doesn't seem to be working. On my backup MX, doing > a telnet to 4190 gets me the proper greetings, but doing the same on my main > server just gave me the normal telnet "Escape character is..." > > I get the following info on the server: > > root@d0ba5bb19b6b:/# doveadm service status managesieve > name: managesieve > process_count: 0 > process_avail: 0 > process_limit: 1024 > client_limit: 1 > throttle_secs: 0 > exit_failure_last: 0 > exit_failures_in_sec: 0 > last_drop_warning: 0 > listen_pending: n > listening: y > doveadm_stop: n > > But when attempting to connect, it doesn't work. > > Any advice? > > Best, > Francis Can you send doveconf -n, please? Aki
