search for: leenoox

Displaying 8 results from an estimated 8 matches for "leenoox".

2007 Jul 27
1
Issues upgrading to 1.1alpha1
I'm trying to upgrade from 1.0.2 to 1.1alpha1. I can build and start dovecot correctly. dovecot -n says: # 1.1.alpha1: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_cert_file: /etc/postfix/server.pem ssl_key_file: /etc/postfix/server.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap):
2007 Jun 20
3
dovecot -n segfault
# uname -a Linux ns2 2.6.18-4-sparc64 #1 Mon Mar 26 11:16:07 UTC 2007 sparc64 GNU/Linux # dovecot -n # 1.0.1: /usr/local/etc/dovecot.conf Segmentation fault uhu? ciao Luca
2007 Jan 21
2
Wrong configure.in entry in CVS branch_1_0
This line in configure.in src/plugins/mail-log/Makefile refers to a non existing direcory in the branch_1_0 tree, which breaks build. ciao Luca
2006 Jun 29
0
Managesieve daemon
Hello, some time ago there was dicussion on the list about development of a managesieve daemon to allow users to manage their own scripts. After putting the pieces togheter and having sieve working in the lda with Dovecot I solved the management issue by using Horde's Ingo + FTP to manage scripts for virtual users. This is quite ugly (technically speaking) but works and it is integrated with
2006 Aug 02
3
configure.in bug?
Hello, I have no autotools knowledge but I had to remove square brackets in configure.in shipped with dovecot AC_CONFIG_HEADERS([config.h]) and dovecot-sieve AC_CONFIG_HEADERS([dsieve-config.h]) to be able to build them. thanks
2007 Apr 18
0
Phones working with 1.2.17, not with 1.4.2
Hello, I've got various phones (mostly SPA-922) behind NAT registered to Asterisk. I've set nat=yes and canreinvite=no, and everything seemed to work great with 1.2.17. After upgrading to 1.4.2 using users.conf and macro-stdexten my spa-922 can't call other extensions. -- Executing [23@default:1] Macro("SIP/22-b72006f0", "stdexten|23| SIP/23") in new stack
2006 Oct 23
1
valid_chroot_dirs question
Hello, I've got a dovecot setup using PAM and real system users. In this setup I also use pure-ftpd to give local users ftp access to their $HOMEs. To have pure-ftpd chroot into the user home i replaced /home/user with /home/user/./ in /etc/passwd. Unfortunately this breaks Dovecot this way: Oct 23 18:18:20 localhost dovecot: Invalid chroot directory '/home/foo' (user foo) (see
2007 Aug 07
1
Dovecot 1.1alpha2 - (imap) killed with signal 10
As promised, here is the bug report: # dovecot -n # 1.1.alpha2: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_cert_file: /etc/postfix/server.pem ssl_key_file: /etc/postfix/server.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3):