Hi,
Thanks for your support.
So a workaround would involve the migration from the flat to an hierarchical
LAYOUT=fs,
change the hierarchy separator to „/‟ and the namespace separator to a rarely
used symbol
like „§‟. Okay, that actually sounds like a nightmare to me.
> But this would not res
Good -Day,
I'm mailing over these papers as -r-equested:
https://wanologicalsolution.com/aod/ettiuabids197944096
Good to know. Many thanks for your comments. Always
appreciate when someone points out risks.
As to my original question, are any others locating LISTIN
Assuming that the question at hand is :
My best guess at this point is the logs showing "INBOX" and
"INBOX.INBOX" , perhaps there's something about the naming scheme that
is throwing it off, but the "INBOX.INBOX.Drafts" and such are still
being handled.
Thanks again for any direction!
Darr
So it seems that all the crashes are caused by shared users that no
longer exist. There were also mailboxes created by Dovecot at
"/var/run/dovecot/user-not-found/us...@domain.de". After I removed the
corresponding entries from the user_share database (SQL database), the
crashes also seem to ha
Here of course the missing backtrace:
#0 0x7fcb470e517c in acl_mailbox_get_aclobj
(box=box@entry=0x5586bfc958f8) at acl-mailbox.c:31
#1 0x7fcb470d06ed in imap_acl_cmd_myrights (cmd=0x5586bfc0cbe8,
mailbox=0x5586bfc2aef0 "shared/us...@domain.com", box=)
at imap-acl-plugin.c:658
#2 c
after installing the dovecot-dbg package I now get additional error logs
(or maybe I missed them before):
May 16 15:47:21 wv-mail-imap1-1 dovecot:
imap(us...@domain.com): Panic: Module context
acl_storage_module missing
May 16 15:47:21 wv-mail-imap1-1 dovecot:
imap(us...@domain.com): Error: R
ok need some more info but in general ssl setup should be as follows.
FQHN - do have have proper dns reverses setup? - this is an upstream thing
for example :
forwards :
## nslookup mail18.scom.ca
Server: 10.220.0.2
Address:10.220.0.2#53
Name: mail18.scom.ca
Address: 65.39
On 16. May 2022, at 14.09, Sebastian Kroczek wrote:
>
> Hello all,
>
> I updated the server tonight and with it Dovecot from 2.2.27 to
> 2:2.3.19-2+debian11. However, there seems to be a problem with the ACLs,
> because since then fatal errors are logged (see core dump). I suspect that
> some
ok the rights can be a bit confusing at times
assuming you are running virtual users (or not)
try these one at a time, i found that when dovecot starts it will adjust
the permissions on the control files accordingly to what is set in the
examples below, also note postfix can be a variable in
ok duplicsate emails (even across dsync, replication etc) is typically
handled via a global sieve script
I use :
# cat duplicates.sieve
require "duplicate"; # for dovecot >= 2.2.18
if duplicate {
discard;
stop;
}
for the scripts
and setup sieve to work via my dovecot.co
Hello all,
I updated the server tonight and with it Dovecot from 2.2.27 to
2:2.3.19-2+debian11. However, there seems to be a problem with the ACLs,
because since then fatal errors are logged (see core dump). I suspect
that some outdated configuration is causing this behavior, but so far I
cou
Robert's answer is a valid approach pending the size of your server
networks etc.
on another note (because i run multiple servers etc)
I run a common syslog file across all servers which is what you appear
to have now.
from there i like everything in one syslog because i am usually lookin
Am 16.05.2022 um 11:58 schrieb Cristiano Deana:
Hi,
I have a mailserver with dovecot logging to syslog (by default, to
/var/log/maillog) and my MTA (postfix) is doing the same.
I use dovecot's services imap/pop3, auth and lmtp and now logs files are
hard to read because I havve all together MT
Hi,
I have a mailserver with dovecot logging to syslog (by default, to
/var/log/maillog) and my MTA (postfix) is doing the same.
I use dovecot's services imap/pop3, auth and lmtp and now logs files are
hard to read because I havve all together MTA and these services.
Is it possibile to have d
Interesting that your security organization is worried about TLS renegotiation
but do not mind people logging in without TLS... =)
You have
disable_plaintext_auth = no
which allows plaintext auth over non-TLS connection. See
https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuratio
15 matches
Mail list logo
