similar to: sieve don't build

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 bldg dovecot cvs branch_1_0 on osx, i'm seeing a sensitivity to order in protocol statements. e.g., on launch: THIS WORKS FINE: protocol lda { sendmail_path = /usr/local/exim/bin/exim ... plugin { quota = maildir:storage=10240 # 10 MB quota limit } } but, THIS DOES NOT protocol lda { ... plugin { quota =

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi, i've built dovecot latest cvs on OSX 10.4.7. i'm making a 1st attempt @ trying/failing to get TLS operation up-n-running ... my install's OK: Install prefix ...................... : /usr/local/dovecot File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi, i've dovecot-cvs up on osx. logging in with virtual users is working. so far so good. i'm attempting to build sieve support now. after: % cd /usr/ports/dovecot/dovecot-sieve % glibtoolize -f -c % autoreconf -i -f configure.in: installing `./install-sh' configure.in: installing `./missing' src/Makefile.am:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on dovecot launch, 'dovecot.log' is created as: -rw------- 1 root testuser 271 2006-09-11 07:58 dovecot.log which causes an apparent perms prob with exim using dovecot's LDA ... what/how do i define/change the LOG's ownership/perms with? it seems to ignore the dovecot.conf umask setting, etc. thx. richard - -- /"\ \

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, per the exim docs @: http://exim.org/exim-html-4.62/doc/html/spec_html/ch36.html a cyrus_sasl authenticator driveer is 'included' in exim core. given that Dovecot has become a very attractive alternative for an increasing number of folks, and there's a patch against exim 4.43 here:

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi all, i have two OSX boxes set up for ssh via pubkey auth only. i'm setting up rsync comms for the first time. i have rsyncd running on box A. no-auth rsync from box B to/from box A's rsyncd works as expected. rsync@B to/from rsyncd@A using pubkey-auth'd-ssh trasport: rsync --verbose --stats --recursive -e "ssh -F

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, building OPENSSH v4.3p2 on OSX 10.4.7, all's fine (config, nake, install, exec) out-of-the-box. so, to be clear, this is NOT a blocker, by any stretch ... that said, however ... if, instead of a don't-monkey-with-it build, prior to ./configure, i: autoreconf -i -f then, a subsequent: ./configure \ --prefix=/usr/local/openssh \

Hi, can anybody tell me what the errors mean and why my asterisk server falls from time to time. From time to time means several hours, not regularly. I also can provide a core if someone can debug? Thanks and regards Jan 11 14:34:59 NOTICE[13573] chan_zap.c: Hangup, did not find cref 83, tei 64 Jan 11 14:34:59 WARNING[13573] chan_zap.c: Hangup on bad channel 0/2 on span 8 Jan 11 14:35:03

Hello developers, some informations before I come to the problem: At work we're using Open-SSH 3.4p1 under Solaris 8. I compiled the Open-SSH by myself with gcc-3.1. In the gcc is the bounds checking patch included (http://web.inter.nl.net/hcc/Haj.Ten.Brugge/bounds-checking-gcc-3.1-1.01.patch.bz2). With this patch I compiled: - prngd 0.9.25 - zlib 1.1.4 - Open-SSL 0.9.6d Everything

Hi, We had Samba v 3.011 installed on Solaris 2.8. We upgraded to v3.014 and ran into the ACL issue where users can edit their files from Windows XP, but cannot delete or rename them. Is there a new parameter for this, or is it a known bug? If it is a bug, does 3.014a fix it? Thanks, Dom Verlezza TIAA-CREF (704)455-8944 ************************************************************** This

Hello. The problem I have is route nat. Short question: Must "route nat", mentioned in ip-cref documentation comming with iproute2 package, work with 2.6.9 kernel? Long question and description of the problem: There is an appendix C in ip-cref by Alexey Kuznetsov called "Route NAT Status". I''ve followed this configuration with 2.4.2x kernel and everything works.

5.1p1 disconnects after the password prompt when connecting to my router and UPS. 5.1p1 connects fine to other unix hosts, and my Windows client connects fine to 5.1p1 servers. 5.0p1 works fine everywhere. I've tried ssh -T, ssh -t, permutations with ssh -o Compression=no -o TCPKeepAlive=no, etc, to no avail. I've used the default ssh_config file, and it still fails. Can anyone

Hi there, I have a weird problem with OpenSSH 2.9.9p2 on Solaris 8. Whenever I try to use ssh, scp or sftp to connect to the Solaris box, the connection is closed by the server and the following msg logged thru syslog: "sshd[542]: fatal: buffer_get: trying to get more bytes 129 than in buffer 39" I tried from an RH 7.1 client (2.9.9p2), from a Solaris 8 client (2.9.9p2), and an OpenBSD

Hi guys, I have a OpenSSH 3.4p1 installation on a SourceMage box, and I am trying to connect to a OpenSSH 3.3p1 installation on a RedHat 7.x box and any other machine. The client fails with a "Host key verification failed." Any other client connects correctly to the RedHat box, and any other server that I try to connect to from the SourceMage box fails with the same error message.

I have been contacted by some people who are having a problem with transfer files using OpenSSH 4.1p1 with the HPN patch. I've taken a look at their problem and I don't think its a problem with the HPN code so I thought I would bounce it over here to see if anyone here has some insight. In brief the connection is dying without spitting out an error message during the key exchange. Of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi matthias, reading the dovecot wiki page: http://wiki.dovecot.org/Quota that, apparently, you last edited (created?): Quota (last edited 2006-06-13 15:27:38 by MatthiasAndree) i note: " plugin { # 10 MB quota limit quota = maildir:storage=10240 # 1000 messages quota limit quota = maildir:messages=1000 # 10 MB + 1000

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i build mysql (currently v5.0.22) on OSX 10.4.7 w/ threading enabled. i.e., i build the reentrant libs: libmysqlclient_r.dylib rather than the 'usual': libmysqlclient.dylib currently, to make Dovecot 'play nice' and recognize the reentrant libs, I: perl -pi -e

Hello, I recently compiled OpenSSH 4.0p1 with OpenSSL 0.9.7g on my Linux 2.6.11.3 machine. When I try to connect, the connection is immediately closed. When I setup public key authentication, I am able to login using my public key. However password authentication seems to be ignored. I attached debugging output from both the server and client. $ ssh -vvv localhost OpenSSH_4.0p1, OpenSSL 0.9.7g

Hi, I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am connecting from a ssh client (openssh-2.9p2) on an x86 Linux box. This works fine for ssh protocol version 1, but am getting the below error for ssh v2: Disconnecting: Bad packet length -857542839. I am also attaching the complete debug traces from sshd & ssh below. I am not sure if this is an "endian" issue.

I'm using an OpenBSD 2.9 snapshot on i386. "ssh -V" reveals OpenSSH_2.9, yada yada. I generated a keypair using ssh-keygen and accepting defaults. I copied the public key to another box, stuck it in ~/.ssh/authorized_keys with host restriction and then tried to use it. Failed. Removed the host restriction, still failed. Just get asked for password. So I cut out the extra box.