similar to: 1.0 beta1 testing

Displaying 20 results from an estimated 2000 matches similar to: "1.0 beta1 testing"

2009 Oct 06
10
Binary locations
Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) So the binaries are: 1) These probably belong to bin/ or sbin/ or both: - authtest - dovecotpw - doveadm 2) Binaries that you might want to call from mail_executable setting: - rawlog - gdbhelper 3) Index file dumping
2017 May 31
2
[Dovecot-news] v2.2.30.1 released
Am 31.05.2017 um 16:35 schrieb Timo Sirainen: > On 31 May 2017, at 16.53, Reindl Harald <h.reindl at thelounge.net > <mailto:h.reindl at thelounge.net>> wrote: >> >> LTO build is as broken as 2.2.30 >> >> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s >> "../lib10_quota_plugin.la"
2015 Mar 13
2
v2.2.16 released
On 12 Mar 2015, at 21:09, Reindl Harald <h.reindl at thelounge.net> wrote: > > /usr/lib64/dovecot/stats/libstats_mail.so > > why in the world a new sub-directory containing just one so-file enforcing pakcage buildsers to change SPEC files? So that external plugins can add more files in there and extend the available statistics.
2008 Aug 19
3
How Can I Tell How Dovecot Was Installed?
I'm trying to help someone with Dovecot, and it looks like this one is a few versions behind. They say that they're not sure if it was installed Via an RPM or a source tarball. Dovecot is use MySQL. This is a RHEL5 server. There are RPMs listed as installed (rpm -qa) but I don't know how I can tell what was used to install the currently used set up. (also asking on the Postifix list)
2008 Oct 23
4
First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every
2008 Oct 23
4
First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
Hello Dovecot users, Finally, after little more than a year, I finished the first release of the new Sieve implementation for Dovecot. The main reason for rewriting the Sieve engine is to provide more reliable script execution and to provide better error messages to users and system administrators. Also, since the Sieve language evolves quickly, with new language extensions published every
2005 Dec 14
1
Best way to upgrade from 1.0a4 to 1.0a5
Hello all, I have 1.0 Alpha 4. Is it better to shut down sendmail, uninstall dovecot 1.0a4 then install 1.0a5, or just install 1.0a5 over the top of 1.0a4? Thanks, Cliff
2007 Oct 18
2
more problems with dovecot-1.1 beta3
Hi, Thank you for pointing me about -xc99 flag, I have compiled and installed dovecot inplace of version 1.0.5 without any special actions on the upgrade. And after starting it immediately got in it's log file messages like: --- dovecot: Oct 16 23:10:18 Error: IMAP(seriv): file_set_size() failed with index cache file /var/spool/imap/seriv/.imap/.git-altlinux-ru/dovecot.index.cache: Invalid
2007 Aug 03
2
dovecot-1.0.3 & apacheds ldap
I have problem with dovecot-1.0.3 and apacheds ldap server. If I change just uris in dovecot-ldap.conf to point to fedora-ds server, everything works O.K. I've tried with apacheds ldap server versions 1.0.2 and 1.5.0 command line search with parameters taken from dovecot.debug log gives me all needed attributes. Comments and help welcome. Here is my data: --- # /opt/dovecot/sbin/dovecot -n #
2007 Jul 25
3
dovecot-1.1 + dovecot-sieve-1.1 deliver backtraces
Hi, I am trying dovecot-1.1 with dovecot-sieve-1.1. First, dovecot -n do not report about deliver settings. They are: --- protocol lda { postmaster_address = postmaster at parkheights.dyndns.org hostname = parkheights.dyndns.org mail_plugins = cmusieve mail_plugin_dir = /usr/lib64/dovecot11/modules/lda sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot11/auth-master
2013 Apr 16
2
Dovecot 2.2.0 compile error
Hi, i tried to compile dovecot 2.2.0 and i end up with this error: make[6]: Entering directory `/mnt/data/Develop/Openwrt/trunk_git/build_dir/target-mips_r2_uClibc-0.9.33.2/dovecot-2.2.0/src/util' /bin/sh ../../libtool --tag=CC --mode=link mips-openwrt-linux-uclibc-gcc -std=gnu99 -Os -pipe -mips32r2 -mtune=mips32r2 -fno-caller-saves -mno-branch-likely -fhonour-copts
2007 Mar 29
2
dovecot mmap() complaints: No such device
I'm trying to use dovecot-deliver with sieve plugin, delivering to Maildirs. Everything seems working O.K., but I'm getting the following lines in /var/log/maillog: --- Mar 29 00:06:00 alt64 dovecot: imap-login: Login: user=<seriv>, method=PLAIN, rip=66.80.117.2, lip=192.168.10.8, TLS Mar 29 00:06:00 alt64 dovecot: IMAP(seriv): mmap() failed with index file
2007 Mar 19
3
PHP implementation of dovecotpw passwords
I am looking for PHP functions that implement passwords that much the dovecotpw implementation. I downloaded one from PEAR, Crypt_HMAC, but the passwords it generates look nothing like the dovecotpw passwords, which could be my fault because I know nothing about the field. Is there a guide or some library that implements them to match dovecotpw?
2008 Jul 24
3
how to store flags \Seen into read-only mailbox?
Hi, I'm trying to use dovecot for storing mailing lists and read-only access for users. The OS is Solaris, authentication for all readers of these lists are from Ldap through PAM, and one local user "listuser" will receive all mail and store them into it's folders (Maildirs). These maildirs are readable (read-only) for all others and they are shared by setting --- mail_location:
2010 Feb 14
3
salted passwords
The idea of salted hash algorithms is to generate a different hash even if the same text is entered. That can be easily seen with dovecotpw: using NON-salted SHA256, same hash is generated for a given password [root at correio ~]# dovecotpw -s SHA256 -p 123 {SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM= [root at correio ~]# dovecotpw -s SHA256 -p 123
2006 Sep 28
2
which e-mail client can work with recent dovecot?
Hi, I'm trying to use dovecot-1.0.rc7. Before I've used dovecot-1.0 from nightly cvs build of August 08, 2006. It worked perfectly, on Linux 64-bit, you can see spec and patches at http://www.sisyphus.ru/srpm/dovecot/ When I tried to upgrade to rc7 and to recent nightly cvs builds with the same configuration and patches (provided necessary adaptations), it builds O.K, but can not move
2007 Jan 23
1
dovecotpw/sql crypt scheme core dump with rc17-19
Platform is Solaris 8 on a 280R. I'm setting up a new installation of Dovecot, and I ran into some troubles that I've partly tracked down. I setup auth/user dbs with LDAP initially, and things worked well. Passwords are stored as "{crypt}zxcv..." in LDAP. I setup SQL, and began getting this: dovecot: Jan 23 16:37:47 Error: child 8718 (auth-worker) killed with signal 11
2008 Sep 12
5
cram-md5 and users maintaining their own passwords?
Is there any other mechanism than using passwd files with md5-hashed passwords created by dovecotpw that will support cram-md5 authentication? Has anyone created setups where the passwd databases reside in the individual users home directories? Is it possible to persuade dovecotpw to update the passwd databases automatically. Having to use a text editor to paste in the passwords sets a high
2008 Jul 01
2
"select NULL as password..." failing after upgrade to dovecot-1.1
Hi, I've upgraded mail server to dovecot-1.1, on solaris-10 with mysql user database. I used sql query "SELECT NULL as password, login as user, concat('/mail/var/dovecot/',login) AS userdb_home, 501 AS userdb_uid, 501 AS userdb_gid FROM users WHERE login='%n' AND password=old_password('%w')" with dovecot-1.0.15 and it worked perfectly. But since upgrade
2006 Jun 12
1
./configure and /or Makefile problem
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 This is on OpenBSD 3.x. I'll fully admit not being a savvy programmer and therefore unable to suggest a decent resolution. It seems that _something_ in either the main "configure" script or one of the Makefile.in templates is causing the Makefiles in src/auth and src/util to add two variables named "AUTH_CFLAGS" and