search for: 2ddf

...ovecot 2.3.10 and coi at the same version. Am I missing something here? Thanks in advance Christian -- R??ner-Network-Solutions Karl-Br?ger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

...ee to comment :-) Christian Thread online: https://www.dovecot.org/list/dovecot/2019-May/115921.html -- R??ner-Network-Solutions Karl-Br?ger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

...09, Mobil: +49 171 9905345 </div> <div> USt-IdNr.: DE225643613, <a href="https://roessner.website" rel="noopener" target="_blank">https://roessner.website</a> </div> <div> PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5 </div> </blockquote> <div> imap_coi_plugin can only be loaded for imap. </div> <div> <br> </div> <div> <br> </div> <div> protocol imap { </div> <div> mail_p...

...bles. How can I express this for sha256? in MD5 this would be %1Mu Many thanks in advance Christian -- R??ner-Network-Solutions Karl-Br?ger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

...same way, %1{sha256:..} and %4{sha256:...}. Thanks. I will try that out. Christian > > Aki -- R??ner-Network-Solutions Karl-Br?ger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

Any progress here? Does anyone know if this will be fixed in 7.1 latest, or should we start looking for different backup solution (in this case I would suggest to remove dump from the source tree - having a backup tool that doesn't work is worse than having none). After upgrading we basically cannot backup our servers. Shouldn't this issue be on

> On 11/05/2020 11:10 Simone Lazzaris <s.lazzaris at interactive.eu> wrote: > > > In data luned? 11 maggio 2020 10:00:38 CEST, lists at mlserv.org ha scritto: > > Hi, > > > > I struggle with directory hashing. I want something like this: > > > > /srv/mail/c/cf37a8dff5e360927ba10ab2 > > > > The final folder is simpel, as it is: >

While trying to speed up nanobsd builds, I mounted /usr/obj on a ramdisk and found my box crashing. Thinking it might be hardware, I tried a separate machine, but with the same results. I have 4G of ram (i386). Am I just running out of some kernel memory ? If so, is there anything I can adjust to prevent this, yet still use mfs in this way ? mdconfig -a -t malloc -s 1800M newfs /dev/md0

Hi If I have the wrong list please feel free to redirect me. I'm running 7.0-RELEASE-p4 and trying to backup to an external USB drive. I'm using the following command dump -a0Lf /backup/diskimages/root /dev/mfid0s1a Where df: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/mfid0s1a 507630 208436 258584 45% / /dev/da1s1d 709513458

Hi, after some time without FreeBSD I installed 7.1 on an IBM Thinkpad T30 (with ZFS root on encrypted geli, works great). Config is: FreeBSD hasking.alashan.nongo 7.1-STABLE FreeBSD 7.1-STABLE #3: Thu Feb 5 21:10:45 CET 2009 root@hasking.alashan.nongo:/usr/obj/usr/src/sys/HASKING i386 I tried using my ath based D-Link DWL G650, which still seems to have some issues in regard to interrupt

Hello, I have a problem with loader. I recently upgraded from 6_rel to 7_rel. Now when I install world there is a problem booting. Here is what I do: cd /usr/src make buildworld make buildkernel KERNCONF=BLACK make installkernel KERNCONF=BLACK At this point I can reboot and all is good. After boot I install the new world: cd /usr/src mergemaster -p reboot into single user mode cd /usr/src make

I hope this isn't an invalid topic for this list. I'm on so many lists and I hate to join another one just to get help on one thing. Apologies if it's not. I am able to use ssh-keygen to generate keys so that I can ssh from my Mac to any of my SuSE systems or ssh from my Mac to any of my FreeBSD systems, without having to enter my password. When I try the same thing from a SuSE system

Hello! A machine I manage remotely for a friend comes under a distributed ssh break-in attack every once in a while. Annoyed (and alarmed) by the messages like: Aug 12 10:21:17 symbion sshd[4333]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:18 symbion sshd[4335]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:20 symbion sshd[4337]: Invalid user mythtv from 85.234.158.180 Aug 12

Hello! A machine I manage remotely for a friend comes under a distributed ssh break-in attack every once in a while. Annoyed (and alarmed) by the messages like: Aug 12 10:21:17 symbion sshd[4333]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:18 symbion sshd[4335]: Invalid user mythtv from 85.234.158.180 Aug 12 10:21:20 symbion sshd[4337]: Invalid user mythtv from 85.234.158.180 Aug 12

In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of