similar to: Dovecot v1.2 share user Maildir problems with %%h

Minor fix. I'm using this in my RPM specfile. John --- ./zaptel-1.0-RC1/Makefile.bigu 2004-07-16 17:09:07.000000000 -0500 +++ ./zaptel-1.0-RC1/Makefile 2004-08-18 16:28:45.000000000 -0500 @@@ -316,10 +318,10 @@ elif [ -d $(INSTALL_PREFIX)/etc/init.d ]; then \ install -m 755 zaptel.init $(INSTALL_PREFIX)/etc/init.d/zaptel;\ \ fi - if [ !

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, out of curiosity I tested to deliver into a shared folder of another owner using Sieve. (Not that I intend to do so, but well ... ) Conf is attached. == Script require ["fileinto"]; fileinto "shared.testusr.test1.test2.test3"; == Dovecot logs: Jun 22 15:36:22 ux-2s11standby dovecot: deliver(user): acl vfile: file

Hello, I know that there was a previous posting regarding this in which the addition of: CFLAGS+=-I../asterisk/include fixed the problem, but I have tried that and am still getting the following when trying to run make: ./mkdep -fPIC -I../asterisk/include/asterisk -I../asterisk -D_GNU_SOURCE -I/usr/include/mysql `ls *.c` cc -fPIC -I../asterisk/include/asterisk -I../asterisk -D_GNU_SOURCE

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, using Dovecot v1.2 changeset: 9126:b745911012bb ACL config: acl = vfile # To let users LIST mailboxes shared by other users, Dovecot needs a # shared mailbox dictionary. For example: acl_shared_dict = file:/var/cache/dovecot/shared-mailboxes telnet localhost imap 0 login .... 1 getacl Sent * ACL "Sent"

Hi, Thanks for giving me a detailed reply on hardware needs steven. I have been looking at the archives in detail and found a few people have had problems with zaptel compilation on suse(kernel-source-2.4.19.SuSE-342 // gcc 3.2.2 ) ... is shifting to red hat the only viable scenario...would be a pain cuz suse comes with sun java desktop system( just bought it !! ) ... any fixes would be a

Hi everyone, I've just compiled Asterisk from CVS in my FreeBSD-stable machine. It went fine. I did had to customised the Makefile though: ASTLIBDIR=$(INSTALL_PREFIX)/usr/local/lib/asterisk ASTVARLIBDIR=$(INSTALL_PREFIX)/var/lib/asterisk ASTETCDIR=$(INSTALL_PREFIX)/usr/local/etc/asterisk ASTSPOOLDIR=$(INSTALL_PREFIX)/var/spool/asterisk ASTLOGDIR=$(INSTALL_PREFIX)/var/log/asterisk

Please, is there any way to migrate passwords from old Samba 4.0 Ad DC to new (Samba 4.20) one? On ldbsearch export on old AD only related item I see is 'unicodePwd' attribute, and it is maybe possible write to new system using ldbmodify - but it is right and simplest solution? And one more question - why don't I get any result from the command (on 4.20 AD DC, provisioned with

I've got a brand new Eicon Diva Server BRI card and I want to configure it with Asterisk. I managed to get asterisk and zaptel to compile and install, I've compiled and installed the drivers for the Diva card and now I need to compile and install the chan_driver for chan_capi. Unfortunately this fails miserably. I get the following messages: I'm using: Kernel 2.6.16.37.4,

On Wed, 14 Aug 2024 05:56:22 +0200 Franta Hanzl?k via samba <samba at lists.samba.org> wrote: > Please, is there any way to migrate passwords from old Samba 4.0 Ad DC > to new (Samba 4.20) one? Yes, add another DC, but you will probably have to do it in stages, Samba 4.0.x went EOL 9 years ago. I think you would have to upgrade to 4.5.x then 4.20.x > On ldbsearch export on old AD

Dne 2024.08.14 10:16, Rowland Penny via samba wrote: > On Wed, 14 Aug 2024 05:56:22 +0200 > Franta Hanzl?k via samba <samba at lists.samba.org> wrote: > >> Please, is there any way to migrate passwords from old Samba 4.0 Ad DC >> to new (Samba 4.20) one? > > Yes, add another DC, but you will probably have to do it in stages, > Samba 4.0.x went EOL 9 years ago.

On Wed, 14 Aug 2024 12:24:12 +0200 Franta Hanzlik via samba <samba at lists.samba.org> wrote: > Dne 2024.08.14 10:16, Rowland Penny via samba wrote: > > On Wed, 14 Aug 2024 05:56:22 +0200 > > Franta Hanzl?k via samba <samba at lists.samba.org> wrote: > > > >> Please, is there any way to migrate passwords from old Samba 4.0 > >> Ad DC to new

Hi, I want to integrate openpam with openssh in our server (which uses QNX632 operating system). I am facing some problems in the "make install" part of openssh. Following are the steps I followed to build zlib, openssl, openpam and openssh. *NOTE*: Since I want the sshd and ssh binaries in my server(using QNX), I had to cross compile the packages for QNX (environment was set to x86)

Good Afternoon Everyone, I am having a problem with compiling the CVS version of *-addons downloaded today. I am also having problems compiling an older version as well but im ignoring that one for now. I believe I have all the correct libraries, and I have done extensive searches everywhere I just wondered if I was missing something really silly, or if this is a problem other people have

On Tue, Sep 27, 2016 at 6:53 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > > On Sep 27, 2016, at 2:18 AM, Carsten Mattner <carstenmattner at gmail.com> > wrote: > > > >> On Mon, Sep 26, 2016 at 11:02 PM, Teresa Johnson <tejohnson at google.com> > wrote: > >> I'll either need to get a reproducer from you and/or try to repro

I am currently running v1.1.20 and was wondering if there is any compelling reason to upgrade to v1.2 or v2.0? For example is there any security updates in v1.2 or v2.0 that aren't included in v1.1.20? The other major thing I would be interested in knowing is there any speed enhancements in the newer versions? I am using basic PAM Auth and Maildir mailboxes on a Linux box. Let me know

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

http://bugzilla.mindrot.org/show_bug.cgi?id=406 Summary: Build openssh-3.4p1 fails, Mac OS X v1.2 Product: Portable OpenSSH Version: -current Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

In RelaseNotes 6.8, at the section "Major changes", the word "TlSv1.2" should be changed to "TLS v1.2" . TlSv1.2 -> TLS v1.2 Now, in this ReleaseNotes, not "CentOS6" but "CentOS 6", And now, not "SMBIOS3.0.0 " but "SMBIOS 3.0.0 ". But now, why not "TLS v1.2" but "TlSv1.2" ?