similar to: Dovecot search message problem

Previously, I needed to downgrade Louis samba packages to Buster's defaults, which would then be upgraded to 4.13 by the dist-upgrade to Bullseye. This was on a Domain Member, so didn't touch my DC's or have to worry about DB format stepping (I hope). apt install samba=2:4.9.5+dfsg-5+deb10u3 python-samba samba-common=2:4.9.5+dfsg-5+deb10u3 samba-common-bin=2:4.9.5+dfsg-5+deb10u3

On 15/02/2023 21:02, Marco Shmerykowsky wrote: > > On 2023-02-15 2:13 pm, Rowland Penny via samba wrote: >> On 15/02/2023 19:05, Marco Shmerykowsky via samba wrote: >>> I ran an 'apt-get update' and a 'apt-get upgrade' >>> samba with the packages referencing Van Belle >>> site for debian bister samba 415. >>> >>> After

Good $daytime, as per the recommendations of Mozilla?s SSL config generator[0], I wanted to set ssl_min_protocol=TLSv1.3 in my dovecot config. This produced the error: imap-login: Error: Failed to initialize SSL server context: Unknown ssl_min_protocol setting 'TLSv1.3' After some digging, I found the function that parses this setting in

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: z Type: application/octet-stream Size: 24104 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20030528/cce0a468/z.obj

At approximately 3:15pm I shut down the office MySQL server to change out some hardware. Shortly after I received a call from one of two customers whose asterisk servers output CDR data to that server. They could not place or receive calls. Shortly after that I received a call from the other customer. I'm below providing output from the message log (At debug level). I don't see much

> Am 22.02.2019 um 22:10 schrieb Voytek Eymont via dovecot <dovecot at dovecot.org>: > > > > On Sat, February 23, 2019 3:47 am, Gerald Galster via dovecot wrote: >> > >> >> try: yum clean all > > > Gerald , thank you > > it shows in the output after 'second step' below: > > # yum clean all > Loaded plugins:

Hello Voytek, the *-devel packages include header files that are only needed if you want to compile something, they are not needed for running a dovecot server. Likewise the *debuginfo packages, they contain information that is helpful for debugging dovecot. Your problem is here: Error: Package: 2:dovecot-lua-2.3.4.1-1.x86_64 (dovecot-2.3-latest) Requires: dovecot = 2:2.3.4.1-1

Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases: 2.3.4.1 https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> Binary packages in https://repo.dovecot.org/ * CVE-2019-3814: If

Due to DMARC issues some people have failed to receive the latest security information, so here it is repeated for both releases: 2.3.4.1 https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.4.1.tar.gz.sig <https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig> Binary packages in https://repo.dovecot.org/ * CVE-2019-3814: If

server is running openssh 4.6p1 on linux x86 (32bit) client is running openssh 4.6p1 on linux x86_64 (64bit) Just connecting from the client to the server and running "top" long enough results in: Disconnecting: Bad packet length 3690378913. This seems like a 32/64 bit problem to me. -- Andreas Steinmetz SPAMmers use robotrap at domdv.de

On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > > 2.3.4.1 > > > >

On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > > 2.3.4.1 > > > >

pull the patches from the port..... On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < dovecot at dovecot.org> wrote: > Oh, so manual compile should NOT work and it's okay or am I missing > something? > > On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote: > >> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo

the patches are already in git master. I've pulled them into the mail/dovecot port. The dovecot guys/gals will release it eventually, but the port works TODAY. On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington <odhiambo at gmail.com> wrote: > I have always been able to compile manually, even from RCs so I believe I > should be able to compile from the tarball as well. >

2.3.4 had the same compile issues.... On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> wrote: > Noted. > > I will wait for dovecot-2.3.4.2 tarball then. > > In all the servers I listed (+2 more), I never use the mail/dovecot port. > > I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have > built in preparation for the

Am 22.02.2019 um 14:43 schrieb Voytek Eymont via dovecot: > > > On Sat, February 23, 2019 12:31 am, Gerald Galster via dovecot wrote: >> Hello Voytek, >> >> >> the *-devel packages include header files that are only needed if you >> want to compile something, they are not needed for running a dovecot >> server. Likewise the *debuginfo packages, they

Hi, We have an alias group named xyz at example.com, this alias group has 3 actual users a at example.com, b at example.com and c at example.com We set vacation rule on the generic sieve rule, the problem is that 3 responses are sent to the original sender. (obviously because the rule is being executed with each user in the alias group) Is it possible to set auto response only once, we tried

Hi, On a debian server after an update to dovecot to 2.3.4.1 imaps mail client stop working. I?ve applied necessary migration for ssl_dh (cf https://wiki.dovecot.org/Upgrading/2.3 <https://wiki.dovecot.org/Upgrading/2.3> ) but that was not enough. The workaround I?ve setup was to remove password protection from the ssl_key file. All tests with ssl_key_password parameter failled (direct

> Am 22.02.2019 um 14:43 schrieb Voytek Eymont via dovecot <dovecot at dovecot.org>: > > > > On Sat, February 23, 2019 12:31 am, Gerald Galster via dovecot wrote: >> Hello Voytek, >> >> >> the *-devel packages include header files that are only needed if you >> want to compile something, they are not needed for running a dovecot >>

Hello, as the tin says. I have several servers running 2.2.27 (Debian stretch) and am adding new ones with 2.3.4.1 (Debian buster). The configs were upgraded where needed but neither 10-mail.conf nor 15-mailboxes.conf were changed. 15-mailboxes is all commented out (I guess the default is auto-create, which isn't documented anywhere I could find) and the only non-comments in 10-mail.conf are