UPDATE: Dovecot 1.1.1

Here is an update to Dovecot 1.1.1. This is not the version that will be commited as I'm waiting for 1.1.2, but I would like to have some initial testing of the update as is and to also check things like Kerberos and Sieve which I do not use. Index: Makefile

Re: webkit-gtk2 and midori port

On Sat, Jun 28, 2008 at 08:38:52PM -0400, James Turner wrote: Attached are two new ports, one for webkit-gtk2 and the other midori. Both were built and tested on amd64. Webkit doesn't have a formal release but the attached port is for the latest nightly dated today. I've been using midori as

DJBware ports

Hi guys, I'm willing to port all DJB's public domain software, including djbdns, qmail, daemontools, etc. If made, It can be easily accepted on ports or, for historical reasons, i will not be imported? Regards, -- Eduardo Alvarenga

Re: Ports with possible 64-bit problems

On Mon, Jun 30, 2008 at 8:31 AM, Christian Weisgerber [EMAIL PROTECTED] wrote: A grep over a recent set of amd64 bulk build logs shows these ports generating warnings that indicate possible 64-bit problems: I'm looking at the Erlang port's build logs, and I see some warning: cast from pointer

Re: DJBware ports

Eduardo Alvarenga wrote: Hi guys, I'm willing to port all DJB's public domain software, including djbdns, qmail, daemontools, etc. If made, It can be easily accepted on ports or, for historical reasons, i will not be imported? I'm not a porter, I don't have final say in this at all, but:

Will you update amavisd-new to 2.6.1 in -current?

Hi, Amavisd-new released 2.6.1 several days ago, support DKIM. Will you update it in -current? -- Best Regards. Zhang Huangbin - Mail Server Solution for Red Hat(R) Enterprise Linux CentOS 5.x: http://iRedMail.googlecode.com/

grip

Grip is one of the ports that's listed as having 64-bit issues. The current stable version is 3.2.0, but the development version (3.3.1) was released over three years ago. Should I just fix it, or update it to 3.3.1 and fix it?

Sarg problem on 4. 3 AMD64

Hi everyone, I got this error on Sarg running on 4.3 amd64: SARG: sarg version: 2.2.3.1 Jan-02-2007 SARG: Maximum file descriptor: cur=128 max=1024, changed to cur=2 max=2 SARG: Reading access log file: /var/squid/logs/access.log SARG: (util) tbuf=30Jun2008, reading: 0.00% SARG: