for IMAP on the backend.
Thanks!
On 11/6/19 5:05 PM, Aki Tuomi via dovecot wrote:
As mentioned on earlier email, are you sure you are connecting to port 4190 and
not 143 for ManageSieve?
Aki
On 06/11/2019 17:48 telsch via dovecot wrote:
I need a more detailed hint. Dovecot proxy IMAP
on 143 =)
Aki
On 06/11/2019 16:46 telsch via dovecot wrote:
If i change it to:
passdb {
args = /etc/dovecot-proxy/dovecot-ldap-passdb.conf.ext
default_fields = proxy=y host=server.intra.lan port=143 starttls=yes
master=proxy pass=#hidden_use-P_to_show#
driver = ldap
}
I still got
/STARTTLS.
On 11/6/19 3:19 PM, Aki Tuomi via dovecot wrote:
On 06/11/2019 16:15 telsch via dovecot wrote:
Hello list,
i'm running an internal dovecot instance with working managesieve. But
on my external dovecot-proxy instance i got an internal error. Nothing
logs on internal dovecot.
It seems
Hello list,
i'm running an internal dovecot instance with working managesieve. But
on my external dovecot-proxy instance i got an internal error. Nothing
logs on internal dovecot.
Nov 06 14:55:12 managesieve-login: Error: proxy: Remote sent invalid
response: * OK [CAPABILITY IMAP4rev1 SASL-IR
at least for me it didn't fix. still see in logs:
Error: lzma.read(/var/spool/mail/telsch/storage/m.11800): corrupted
data at 110015
before i upgrade from 2.3.4.1 to 2.3.8 + your patch i noticed i can
access the mails with alpine and roundcube but not with thunderbird.
On 10.10.19
Hello list,
is it save to move the broken m.* files and let dovecot replicate them
again?
dsync(): Error: zlib.read(/var/spool/mail//storage/m.370):
corrupted data at 1486926
dsync(): Error: Mailbox Trash: copy:
i_stream_read(zlib(/var/spool/mail//storage/m.370)) failed:
Actually the mail isn't saved corrupted. The bug is when reading the
mail. So any existing corrupted mails become fixed after upgrading.
Fix here:
https://github.com/dovecot/core/commit/5068b11e594ad7cc1f7cedf2bd9280520e0e534d
Could this also apply to this Timo? We also using attachment_dir
if it's still the same pid, yes:
7584 13.2 1.5 221168 63508 ?R12:48 3:36
dovecot/doveadm-server
On 02.09.19 13:13, Aki Tuomi via dovecot wrote:
Any idea what pid 7584 is?
Aki
On 2.9.2019 14.08, telsch via dovecot wrote:
Hello,
today i got reappearing mails again
Hello,
today i got reappearing mails again, but not from purging. In the logs i
only found this. I've got massive problems by many users because
reappearing mails. If you need more information, i could provide.
Sep 02 12:58:43 doveadm: Warning: Transaction log file
ok thanks for clarification
No, that has always been a mistake and it was fixed in 2.3. Our SSL pages in
documentation & wiki have always recommended concatenating the intermediates
with the cert.
Aki
with v2.2.34 i can use:
ssl_ca =
Hello,
using letsencrypt ssl certs with san works perfectly with 2.2.34, but
after uprading to 2.3.4.1 it couldn't verified (also tried v2.3.7.1).
i connect to imap.myserver.lan
the cn of the cert is myserver.lan and has the san imap.myserver.lan
openssl s_client -connect imap.myserver.lan:993
ok solved my problem by adding master user on backend and self-signed
ssl certs on proxy instance:
default_fields = proxy=y host=imap.myserver.lan port=993 ssl=yes
master=masteruser pass=masterpass
using successfully active/active replica. trying to add a proxy node in
front. this proxy node should do the auth with the same ldap passdb
settings as the replica in addition (later with kerberos). so i add to
10-auth.conf on the proxy:
default_fields = proxy=y host=imap.myserver.lan
14 matches
Mail list logo
