Displaying 13 results from an estimated 13 matches for "pallissard".
2017 Jun 07
2
doveadm ssl error when upgrading from 2.2.27 to 2.2.29
...g openssl 1.1.0.f and an ec cert/key with the following curve.
ASN1 OID: prime256v1
NIST CURVE: P-256
Does anyone know anything about this off the top of their head? If not I'll try to git-bisect 2.2.27 -> 2.2.28 and see if I can find any offending commits later on this week.
--
Matt Pallissard
2017 Jun 09
2
doveadm ssl error when upgrading from 2.2.27 to 2.2.29
On Thu, Jun 08, 2017 at 11:06:01AM +0300, Aki Tuomi wrote:
>
>
> On 07.06.2017 15:16, Pallissard, Matthew wrote:
> > I'm starting to see the following error when upgrading from 2.2.27 to 2.2.29.
> >
> > doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher...
2020 Apr 30
2
sender rewriting scheme
Hello,
I would like to know if dovecot/pigeonhole provide a way to do sieve
redirection with sender rewriting scheme (srs)?
I apologize in advance if that e-mail address isn't meant for assistance,
but I've asked on the official irc channel on freenode and was told to
direct my query to dovecot at dovecot.org, I hope you won't mind.
Thanking you in advance
Best Regards
2017 Apr 19
3
help
Dear Team
I have faced issue with email downloading in the email client by using pop3 SSL port 995 in dovecot v2.1.17 for outlook client 2016 on production environment.
As per my troubleshooting on my test environment, I have upgraded dovecot version v2.2.28, and changed paramer "ssl_dh_parameters_length = 2048" and "verbose_ssl = yes", The issue seems to be resolved in
2017 Aug 19
2
doveadm client not compatible with this server (mixed old and new binaries?)
I'm getting the error "doveadm(10.0.0.10): Error: ddoveadm client not
compatible with this server (mixed old and new binaries?)" on the source
server (10.0.05) when trying to sync with a new destination server and I
feel the error seems very obvious and self-explanatory except for one
small thing - both servers claim to be the same version
dovecot -n reports:
Source
2017 May 18
1
Sieve GLOBAL + Sieve LOCAL
Doesn't 'keep' imply 'stop'? What if your users want the email in a different folder that the INBOX?
Leave the 'else' clause off.
Bill
On 5/17/2017 4:07 PM, dovecot at pallissard.net wrote:
>> But what I would need is execute a global sieve_before for all users to
>> apply some spam selection rules. Did anybody easily achieved it?
> Is this what you are looking for? This is how I enforce spam rules prior to users' custom scripts.
>
> #in dovecot con...
2017 May 16
2
Sieve GLOBAL + Sieve LOCAL
Hello List,
I am using dovecot:
ii dovecot-antispam 2.0+20130822-2 amd64
Dovecot plugins for training spam filters
ii dovecot-core 1:2.2.10-1 amd64
secure POP3/IMAP server - core files
ii dovecot-imapd 1:2.2.10-1 amd64
secure POP3/IMAP server - IMAP daemon
ii
2017 Apr 19
0
help
> What can i do to resolve this issue in dovecot v2.1.17 in Production environment? Kindly help
Why don't you upgrade production and modify the settings as you did in test?
Matt Pallissard
On Wed, 2017-04-19 at 13:20 +0000, Bhushan Bhosale wrote:
> Dear Team
>
> I have faced issue with email downloading in the email client by using pop3 SSL port 995 in dovecot v2.1.17 for outlook client 2016 on production environment.
>
> As per my troubleshooting on my test environ...
2017 May 17
0
Sieve GLOBAL + Sieve LOCAL
...plugin {
sieve_before = /var/lib/dovecot/sieve/global/default.sieve
}
#In /var/lib/dovecot/sieve/global/default.sieve
require ["fileinto"];
if header :contains "X-Spam-Flag" "YES" {
fileinto "Spam";
stop;
} else {
keep;
}
--
Matt Pallissard
2017 Jun 07
0
doveadm sync SSL error when upgrading from 2.2.27 -> 2.2.29
...#39;m using a cert/key with the following curve.
ASN1 OID: prime256v1
NIST CURVE: P-256
Downgrading to 2.2.27 resolves the issue. Does anyone know about this off the top of their head? If not I'll try to git-bisect 2.2.27->2.2.28 for any offending commits later on this week.
--
Matt Pallissard
2017 Jun 08
0
doveadm ssl error when upgrading from 2.2.27 to 2.2.29
On 07.06.2017 15:16, Pallissard, Matthew wrote:
> I'm starting to see the following error when upgrading from 2.2.27 to 2.2.29.
>
> doveadm(ip.add.re.ss): Error: doveadm client disconnected before handshake: SSL_accept() failed: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
>
> Down...
2017 Aug 23
0
doveadm client not compatible with this server (mixed old and new binaries?)
...ere was still an old process hanging around.
Fully stopping the service, checking that there were no dovecot processes running, then starting it up again resolved the issue.
If that fails, turning off SSL within your doveadm/plugin blocks temporarily may reveal other errors.
Good luck.
--
Matt Pallissard
On Sat, Aug 19, 2017 at 09:47:35PM +0100, Kevin Golding wrote:
> I'm getting the error "doveadm(10.0.0.10): Error: ddoveadm client not
> compatible with this server (mixed old and new binaries?)" on the source
> server (10.0.05) when trying to sync with a new destination ser...
2020 May 01
0
sender rewriting scheme
...ou'd like individual users to be able to set it up on their own, you can probably handle that in sieve. Sieve supports modifying the headers.
https://doc.dovecot.org/configuration_manual/sieve/configuring_auto_forward_sender_address/
Someone else on this list may know better than I.
Matt Pallissard
On 2020-04-30T17:50:37 +0200, Mathieu Gosset wrote:
> Hello,
>
>
>
> I would like to know if dovecot/pigeonhole provide a way to do sieve
> redirection with sender rewriting scheme (srs)?
>
> I apologize in advance if that e-mail address isn't meant for assistance,
>...