dsync with vurtial folder leads to mess of msg ID
Greetings, I have a setup with two dovecot servers and dsync replication between them. On both of them I have a virtual folders, forexample All with config: mx1# cat /etc/dovecot/virtual/All/dovecot-virtual * -Trash -Trash/* -Junk -Junk/* all All virtual folders are excluded from replication because it leads to broken replication with errors like: virtual.All can't be created. So, I have. replication_dsync_parameters = -d -l 30 -U -x virtual. Unfortently, after a couple of weeks I've noticed that msg id for the same message on the different servers aren't match. For example: mx1# doveadm fetch -u kir...@korins.ky 'uid' mailbox virtual.All header Message-ID 'macports/macports-ports/pull/22284/c1901369...@github.com' uid: 157786 mx1# doveadm fetch -u kir...@korins.ky 'uid' mailbox INBOX header Message-ID 'macports/macports-ports/pull/22284/c1901369...@github.com' uid: 5561 mx1# vs mx2# doveadm fetch -u kir...@korins.ky 'uid' mailbox virtual.All header Message-ID 'macports/macports-ports/pull/22284/c1901369...@github.com' uid: 157766 mx2# doveadm fetch -u kir...@korins.ky 'uid' mailbox INBOX header Message-ID 'macports/macports-ports/pull/22284/c1901369...@github.com' uid: 5561 mx2# as you may see msgid at INBOX are matched, but it isn't true for virtual.All, here 157786 vs 157766 So, here the question: how can I sync msg id inside virtual folder on this setup? -- wbr, Kirill ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: lda or lmtp for sieve?
Thanks for the reassurance. It was a reach, hoping for some straw to grasp regarding the managesieve 4190 failure to bind. On 1/19/24 18:28, Joe Acquisto wrote: I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when discussing sieve. The documentation also mentions that lmtp is preferred over lda, and seems to say in places that sieve will operate without issue in either case. Does it matter to sieve implementation if one uses only lmtp? ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: master-users problem
Hi Barbara,
On 13.12.23 15:08, Barbara M. wrote:
passdb {
args = /etc/dovecot/master-users
Correct me if I am wrong, but IIRC, these files are read after
privileges are dropped... so quick guess: is the file readable by the
service user itself?
If your service runs with "dovecot" as user, try the following:
sudo -u "dovecot" test -r "/etc/dovecot/master-users"; echo $?
where 1 == error and 0 == success.
On many installations and setups, the /etc/dovecot/ directory is owned
by root with 750 permission. So it might make sense to place the file
somewhere else, e.g. beside instead of inside the /etc/dovecot/ dir, so
you do not need to soften the permissions of the more important config
files:
# ls -lah /etc/ | grep dovecot
drwxr-x--- 4 rootroot4.0K Jan 17 22:06 dovecot
-rw-r- 1 dovecot dovecot 76 Jan 8 00:06 dovecot-masterusers-passwd
--
Regards
Andreas Haerter
foundata GmbH
Steinhäuserstr. 20
76135 Karlsruhe
Sitz der Gesellschaft: Karlsruhe
Registergericht: Amtsgericht Mannheim, HRB 714807
Geschäftsführer: Andreas Haerter
USt-IdNr.: DE284122682
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Re: lda or lmtp for sieve?
On 20/01/24 12:28, Joe Acquisto wrote: I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when discussing sieve. The documentation also mentions that lmtp is preferred over lda, and seems to say in places that sieve will operate without issue in either case. Does it matter to sieve implementation if one uses only lmtp? LDA is older, think of LMTP as a more modern replacement. LDA has to launch a separate process and process one message at a time. LMTP maintains a running service and can stream multiple messages in a single connection, therefore LMTP is a lot more efficient. You will see a lot of bad advice on the internet, or old outdated advice. Tutorials that use LDA is an example of old, outdated advice. Sieve itself doesn't care which one you use, but there are other reasons to prefer LMTP. Peter ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: lda or lmtp for sieve?
Does it matter to sieve implementation if one uses only lmtp? No. Works here with only lmtp. -- Christian Kivalo ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: lda or lmtp for sieve?
Nope. That's what I do. With the new Tainting rules in the Exim MTA, LMTP became the easier of the two. On Fri, Jan 19, 2024 at 5:28 PM Joe Acquisto wrote: I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when discussing sieve. The documentation also mentions that lmtp is preferred over lda, and seems to say in places that sieve will operate without issue in either case. Does it matter to sieve implementation if one uses only lmtp? ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
lda or lmtp for sieve?
I noticed that many places in the documentation and in examples gleaned from the wilderness, refer to the LDA protocol when discussing sieve. The documentation also mentions that lmtp is preferred over lda, and seems to say in places that sieve will operate without issue in either case. Does it matter to sieve implementation if one uses only lmtp? ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Documentation flaw: man-page link.
Further along those lines, at the below page, only download and installation is "not broken". https://doc.dovecot.org/admin_manual/pigeonhole_managesieve_server/ joe a. On 1/19/2024 01:37:26, Aki Tuomi via dovecot wrote: On 18/01/2024 15:34 EET Ralph Corderoy wrote: Hi, https://doc.dovecot.org/admin_manual/doveadm_mailbox_commands/ ends with The man-pages also contain good descriptions of doveadm commands. Man-pages can be accessed online at e.g. https://wiki.dovecot.org/Tools/Doveadm That wiki page says Our primary documentation is now at https://doc.dovecot.org, please update your links. But I was at https://doc.dovecot.org to start with and there is no obvious mention of man pages there. This needs tidying up to avoid the loop and ideally provide man pages. -- Cheers, Ralph. Hi! Thanks for pointing this out, we are working on fixing the links. Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
replication timeout
I have two Dovecot mail servers that replicate to each other. Sometimes there are delays in the synchronization, and I notice that the mail log has entries like this: Error: dsync(spokane): I/O has stalled, no activity for 600 seconds (last sent=mailbox, last recv=mailbox_state) Five minutes seems like a long time to sit there waiting with nothing happening. Is there a way to reduce this timeout so that I don't have so many replicaton connections just sitting around doing nothing? (Of course, a way to prevent the I/O stalls would be great too, but with my limited upload bandwidth, they may be unavoidable.) Andy ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Documentation flaw: man-page link.
On 1/19/2024 01:37:26, Aki Tuomi via dovecot wrote: On 18/01/2024 15:34 EET Ralph Corderoy wrote: Hi, https://doc.dovecot.org/admin_manual/doveadm_mailbox_commands/ ends with The man-pages also contain good descriptions of doveadm commands. Man-pages can be accessed online at e.g. https://wiki.dovecot.org/Tools/Doveadm That wiki page says Our primary documentation is now at https://doc.dovecot.org, please update your links. But I was at https://doc.dovecot.org to start with and there is no obvious mention of man pages there. This needs tidying up to avoid the loop and ideally provide man pages. -- Cheers, Ralph. Hi! Thanks for pointing this out, we are working on fixing the links. Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org Oh, yes, Please. I've rarely been more frustrated trying to "bootstrap" myself than in my efforts to get dovecote and sundry working. The "loops" have been greatest contributor. joe a. ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Where can one look to determine if managesieve "loaded"? Such as via logs or other some means? As indicated it did not, AFAICT, bind to 4190 as directed, and no errors appear in logs, via "doveadm log errors". If there were some configuration error or failure in some startup, should there not be something? joe a. On 1/18/2024 18:30:06, Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . . ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Yes, to the specific IP "connection refused", locally or remotely. joe a. On 1/19/2024 10:04:16, Aki Tuomi via dovecot wrote: Did you notice that your server is listening only on specific IPv4 address? Did you try to connect against that? Aki On 19/01/2024 16:43 EET Joe Acquisto wrote: The problem of managesieve server/service not taking hold of port 4190 remains. Perhaps the service is not being loaded/running at all? Pardon any terminology faux pas On 1/18/24 18:30, Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . . ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Did you notice that your server is listening only on specific IPv4 address? Did you try to connect against that? Aki > On 19/01/2024 16:43 EET Joe Acquisto wrote: > > > The problem of managesieve server/service not taking hold of port 4190 > remains. Perhaps the service is not being loaded/running at all? > Pardon any terminology faux pas > > On 1/18/24 18:30, Joe Acquisto wrote: > > Trying to connect to managesieve server configured to port 4190. No go. > > > > Roundcube is configured (thunderbird apparently having nothing > > current), but selecting "Add Filter" (new since re-configured for > > managesieve) produces "unable to connect to server". > > > > Port 4190 does not seem to answer or be "bound" to anything. Telnet to > > 4190 produces "connection refused". > > > > A "one box" solution. > > > > If I had to guess, I would guess, operator error. Otherwise, things > > are looking up. But, I remember a movie that said never to do that . . . > > > > > > ___ > > dovecot mailing list -- dovecot@dovecot.org > > To unsubscribe send an email to dovecot-le...@dovecot.org > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
The problem of managesieve server/service not taking hold of port 4190
remains. Perhaps the service is not being loaded/running at all?
Pardon any terminology faux pas
On 1/18/24 18:30, Joe Acquisto wrote:
Trying to connect to managesieve server configured to port 4190. No go.
Roundcube is configured (thunderbird apparently having nothing
current), but selecting "Add Filter" (new since re-configured for
managesieve) produces "unable to connect to server".
Port 4190 does not seem to answer or be "bound" to anything. Telnet to
4190 produces "connection refused".
A "one box" solution.
If I had to guess, I would guess, operator error. Otherwise, things
are looking up. But, I remember a movie that said never to do that . . .
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
# 2.3.21 (47349e2482): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.21 (f6cd4b8e)
# OS: FreeBSD 13.2-STABLE amd64
# Hostname: thebighonker.lerctr.org
auth_default_realm = lerctr.org
auth_mechanisms = plain login
auth_realms = lerctr.org thebighonker.lerctr.org tbh.lerctr.org
thejonesonair.com thejonesonair.net why.net
default_vsz_limit = 1 G
deliver_log_format = msgid=%m: %$ (subject=%s from=%f size=%w)
doveadm_password = # hidden, use -P to show it
first_valid_gid = 0
first_valid_uid = 0
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = 192.147.25.65, ::
login_access_sockets = tcpwrap
mail_attribute_dict = file:%h/mail/.imap/dovecot-mail-attributes
mail_location = mbox:~/mail:INBOX=~/mail/INBOX:NO-NOSELECT
mail_log_prefix = "%s(%u/%p): "
mail_plugins = " fts fts_solr notify virtual"
mail_privileged_group = mail
mail_server_admin = mailto:l...@lerctr.org
mail_server_comment = LERCTR Mail Server
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 mboxmetadata
servermetadata vnd.dovecot.debug imapsieve vnd.dovecot.imapsieve
namespace archive {
hidden = no
list = no
location = mbox:~/MAIL-ARCHIVE
prefix = ARCHIVE/
separator = /
}
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox INBOX {
auto = create
}
mailbox SENT {
special_use = \Sent
}
mailbox SPAM {
special_use = \Junk
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
mailbox virtual/Flagged {
special_use = \Flagged
}
mailbox virtual/all {
special_use = \All
}
prefix =
separator = /
}
namespace virtual {
hidden = no
list = yes
location = virtual:~/MAIL-VIRTUAL
prefix = Virtual/
separator = /
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
passdb {
args = user=%Ln noauthenticate
driver = static
skip = authenticated
}
passdb {
args = failure_show_msg=yes session=yes max_requests=20
driver = pam
override_fields = domain=lerctr.org
skip = authenticated
}
plugin {
fts = solr
fts_autoindex = yes
fts_solr = url=http://localhost:8983/solr/dovecot/
fts_tika = http://localhost:9998/tika/
imapsieve_mailbox1_before =
file:/usr/local/share/dovecot-pigeonhole/sieve/report-spam.sieve
imapsieve_mailbox1_causes = COPY
imapsieve_mailbox1_name = SPAM
imapsieve_mailbox2_before =
file:/usr/local/share/dovecot-pigeonhole/sieve/report-ham.sieve
imapsieve_mailbox2_causes = COPY
imapsieve_mailbox2_from = SPAM
imapsieve_mailbox2_name = *
imapsieve_url = sieve://thebighonker.lerctr.org
mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename
flag_change append
mail_log_fields = uid box msgid size from subject vsize flags
recipient_delimiter = +-_
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_execute_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve
sieve_extensions = +editheader +vacation-seconds +mboxmetadata
+servermetadata +vnd.dovecot.debug
sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute
sieve_pipe_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve
sieve_plugins = sieve_imapsieve sieve_extprograms
}
postmaster_address = postmas...@lerctr.org
protocols = imap pop3 lmtp sieve
recipient_delimiter = +-_
service anvil {
unix_listener anvil {
group = mail
mode = 0666
}
}
service auth {
unix_listener auth-client {
mode = 0666
}
unix_listener auth-master {
mode = 0666
}
}
service doveadm {
inet_listener http {
port = 8080
ssl = yes
}
}
service indexer-worker {
drop_priv_before_exec = yes
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1
port = 24
}
}
service managesieve-login {
inet_listener sieve {
port =
