Re: managesieve script 'redirect' fails @ "Error: sieve: ... aborted due to temporary failure; Error: smtp-server: ... failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong ve
On 9/27/20 2:07 PM, PGNet Dev wrote: > so the problem appears not to be the result of a general sieve-processing > fail, > but rather tied to the the redirect action/transaction For anyone interested, having dovecot sieve submit to its own submission proxy appears to be causal. Specifically, setting submission_host = internal.mx.example.com:60025 to submit to @ an UNencrypted port, or submission_host = internal.mx.example.com:60465 to submit @ an ENcrypted port results in the errors I've seen. direct submission to the dovecot submission proxy certainly works, an in the non-sieve-triggering tests above^. also, in brief mention here, Sieve and SMTP submission https://doc.dovecot.org/configuration_manual/sieve/sieve_and_smtp_submission/ an alternative is to set sendmail_path, using the sendmail binary. in this setup, that's postfix's sendmail; so, here, that's sendmail_path = "/usr/sbin/sendmail.postfix" once changed, the sieve filter redirection works. notably, using submission_host = internal.mx.example.com:465 , submitting to postfix's listener _also_ fails. that _suggests_ that the problem's in dovecot's submission code, as used by sieve
custom userdb server, Exim, and proxying
Hi all, We have Exim using Dovecot for authentication. Dovecot, in turn, consults a custom internal server that answers Dovecot’s userdb queries. When IMAP connections arrive, for some users we want to forward those connections--without authentication--to an external IMAP server. For these users, we return “proxy_maybe” and “nopassword” in the authn response from our userdb server. This tells Dovecot to proxy the connection to a new server without trying to authenticate. Exim, though, doesn’t grok “proxy_maybe”, so it just sees “nopassword”. In response, it just skips SMTP authentication entirely. We could address this if our custom service could know whether the authn is for Exim or not. Exim does send a “service=smtp” in its request to /var/run/dovecot/auth-client, but thus far I don’t see that that’s being passed on to the userdb server. Is there any way I can configure Dovecot so that our userdb server can detect when it’s Exim doing the authentication? Alternatively we could just authenticate on the proxy (i.e., stop sending “nopassword”), but that will entail a new requirements for passwords to be in sync; ideally we’d like to avoid that. Any insight from this group would be much appreciated. Thank you! cheers, -Felipe Gasper
RE: Providers running dovecot?
>> I am looking for providers of free e-mail addresses known to run >> Dovecot (or a variant thereof) for IMAP access. > >Possibly Posteo. Not free IIRC, but very inexpensive (~1EUR/month). I already offered him a free account to test with, and some GB's of testing mail. But him seem to have disappeared already ;)
Dsync issues since 2.3.11.3.
Hello! I've started seeing intermittent dsync failures since upgrading Dovecot to 2.3.11.3-3 (CentOS 8 using the official Dovecot repo). Sep 27 17:49:04 host dovecot[130]: dsync-local(user@host)<5GWFD2CmcF+TJwAAsNnMGQ>: Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 66543 no longer in transaction log (highest=66547, last_common_uid=46346, nextuid=46347)) Sep 27 17:49:04 host dovecot[130]: dsync-local(user@host)<5GWFD2CmcF+TJwAAsNnMGQ>: Error: Remote command returned error 75: ssh doveadm dsync-server -u user@host It seems to happen at random times to random users. My setup has 2 servers - users are connecting to the main server and the secondary server is just for backup - noone is actually connecting to it. Any suggestions? Thanks! Reio
