similar to: Dovecot v2.3.7 - TLS/SSL issue

Displaying 20 results from an estimated 9000 matches similar to: "Dovecot v2.3.7 - TLS/SSL issue"

2018 Apr 03
5
issue with sieve forwarding after upgrade to 0.5.1
Hello, After I upgrade dovecot 2.2.35 to 2.3.1 and pigeonhole 0.4.23 to 0.5.1 when I use sieve to forward a message to other address using "redirect :copy" I get this: (host server1.myserver.com <http://server1.myserver.com/>[private/dovecot-lmtp] said: 451 4.2.0 <chris at mydomain.com <mailto:chris at mydomain.com>> Execution of Sieve filters was aborted due to
2018 Apr 04
2
issue with sieve forwarding after upgrade to 0.5.1
Thank you for your reply. I use FreeBSD so no changes on the OS before and after the dovecot/pigeonhole updates. > On 4 Apr 2018, at 08:54, B. Reino <reinob at bbmk.org> wrote: > > Hello, > > The new systemd service file has NoNewPrivileges set to true. You need to override that to false and then it should work again. > > (if you need help with that ask again..
2018 Apr 19
3
lost connection while sending end of data error
I use dovecot-lmtp and postfix. When I send e-mail to 2 recipients (or more) at the same time and if one of them is over quota (or under quota and the message I send is bigger than his free space) mailq shows: -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 20B03336F22 26099 Thu Apr 19 18:02:47 support at example.com (lost connection with
2019 Jul 12
0
Dovecot release v2.3.7
Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > We are pleased to release Dovecot release v2.3.7. My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) starting up for imap, lmtp, sieve | dovecot[76035]: replicator: Error: file_ostream.net_set_tcp_nodelay((conn:unix:/var/run/dovecot/stats-writer),
2019 Jul 12
9
Dovecot release v2.3.7
Hi! We are pleased to release Dovecot release v2.3.7. Tarball is available at https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz.sig Binary packages are available at https://repo.dovecot.org/ Changes ------- * fts-solr: Removed break-imap-search parameter + Added more events for the new statistics, see ?
2019 Jul 12
9
Dovecot release v2.3.7
Hi! We are pleased to release Dovecot release v2.3.7. Tarball is available at https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.tar.gz.sig Binary packages are available at https://repo.dovecot.org/ Changes ------- * fts-solr: Removed break-imap-search parameter + Added more events for the new statistics, see ?
2019 Jul 12
2
Dovecot release v2.3.7
On 12 Jul 2019, at 21.05, Michael Grimm via dovecot <dovecot at dovecot.org> wrote: > > Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> We are pleased to release Dovecot release v2.3.7. > > My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE r349799): > > | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) starting up for
2019 Oct 20
1
Dovecot v2.3.8 released
On 2019-10-20 11:30, Timo Sirainen via dovecot wrote: >> On 18 Oct 2019, at 13.43, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >>> I am seeing a lot of errors since the upgrade, on multiple client >>> accounts: >>> Info: Connection closed: read(size=7902) failed: Connection reset by >>> peer (UID FETCH running for
2019 Jul 16
0
Dovecot release v2.3.7
Version 2.3.7 appears to break director ring sync. After upgrading, our logs are full of these kinds of messages: Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host lookup failed: Timeout because ring not synced - queued for 30 secs (Ring not synced for 1410 secs, hash=271838221) Jul 14 04:09:20 yyy dovecot: director: Error: director: User xxx host lookup failed: Timeout
2019 Jul 13
0
Dovecot release v2.3.7
LMTP is broken on director: Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 (smtp_params_mail_add_body_to_event): assertion failed: ((caps & SMTP_CAPABILITY_8BITMIME) != 0) Jul 13 13:42:41 lmtp(34824): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xdf06a) [0x7f561203806a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xdf0b1) [0x7f56120380b1] ->
2018 Apr 03
0
issue with sieve forwarding after upgrade to 0.5.1
Here are some logs: Apr 3 23:25:35 server1 dovecot: lmtp(chris at coderz.gr)<47735><AUI6Aj/jw1p3ugAAPz4RRA>: program `/usr/sbin/sendmail' terminated with non-zero exit code 75 Apr 3 23:25:35 server1 dovecot: lmtp(chris at coderz.gr)<47735><AUI6Aj/jw1p3ugAAPz4RRA>: Error: sieve: msgid=<DE90EB45-9B58-4679-9BCE-E2698773519E at cretaforce.gr>: failed to redirect
2018 Jul 21
1
dovecot lmtp and drop privileges to specific user
Is it possible when dovecot LMTP to drop privileges to a specific user instead of the e-mail account user?
2019 Jul 18
4
Dovecot with MySQL over SSL.
Hello! I'm attempting to get Dovecot working with MySQL user database on another machine. I can connect to the MySQL (5.7.26) instance with SSL enabled: ?mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem --ssl-cert=/etc/dovecot/client-cert.pem --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA -u vmail -p However if I use the same values in dovecot-sql.conf.ext, I
2011 Aug 15
3
Queue Breakout Input being Ignored
Hello, Raw stats: Version:1.8.3.2 OS:Centos 5.6 Special setup: postgre database I am having a few queue issues with Asterisk specifically relating to breaking out from queues while on hold. The intent is that while someone is on hold they can press a key (lets say *) to break from the queue and go elsewhere (in this case to leave a message). However In all of my testing I am unable to get
2018 Apr 04
0
issue with sieve forwarding after upgrade to 0.5.1
Hello, The new systemd service file has NoNewPrivileges set to true. You need to override that to false and then it should work again. (if you need help with that ask again.. I'm on the train now so I can't write much comfortably..) Cheers. On April 3, 2018 10:25:22 PM GMT+02:00, Christos Chatzaras <chris at cretaforce.gr> wrote: >Hello, > >After I upgrade dovecot 2.2.35
2014 Mar 17
1
samba4 - force ssl/tls for incoming ldap queries
hi there, is there a way to have sambas internal ldap server reject plaintext connections? something similar to the ssf-settings in openldap's acls? i was already thinking about instructing iptables to drop all connections to port 389 - but that would effectively rule out starttls and force the clients to use ldaps, which has been deprectated a long time ago. thank you & with kind
2006 Apr 11
3
model classes in different folders
Hello, I have the following structure: - app - controllers - helpdesk - call_controller.rb (Helpdesk::CallController < ApplicationController) - models - employee.rb - department.rb (Department < ActiveRecord::Base) - helpdesk - call.rb - call_history.rb (Helpdesk::CallHistory < ActiveRecord::Base) Is it possible to have a relationship between
2019 Jul 23
1
Dovecot v2.3.7.1 & Pigeonhole v0.5.7.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz.sig https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ These releases fix the reported regressions in v2.3.7 & v0.5.7.
2019 Jul 23
1
Dovecot v2.3.7.1 & Pigeonhole v0.5.7.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz.sig https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ These releases fix the reported regressions in v2.3.7 & v0.5.7.
2005 Jun 22
3
combining calls from 2 queues
We have 1 queue called helpdesk and are setting up a second one called isp. The helpdesk queue is for internal support calls and isp for our ISP customer calls. Both of these queues will be directed to the same agents (helpdesk phone extensions). We want to have the separate queues for tracking purposes but the queued calls need to be ordered and answered as if there was only one queue. For