Re: [Dovecot] v2.0.alpha3 released

2009-12-09 Thread Timo Sirainen
On Tue, 2009-11-24 at 06:44 +0100, Luigi Rosa wrote:
  It's the intended behavior. Dunno if it's the best. Copying example
  config directly to /etc/dovecot/ doesn't seem such a good idea.
 
 It would be nice to put a text file like configuration files go here or
 something like that, or just no action at all. Or maybe a message at the end 
 of
 make install procedure.
 
 Maybe it's me, but if I find an empty directory in /etc after an installation,
 the first think I think is that something went wrong.

How about it installs README file containing:

Configuration files go to this directory. See example configuration files in
/usr/local/share/doc/dovecot/example-config/



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] v2.0.alpha3 released

2009-11-23 Thread Timo Sirainen
On Sat, 2009-11-14 at 09:03 +0100, Luigi Rosa wrote:
 Given this configure command line
 
 ./configure --with-mysql --with-ssl=openssl --sysconfdir=/etc 
 --localstatedir=/var
 
 and given an /etc directory without any dovecot subdirectory (I moved it
 elsewere for testing purposes), is it ok that make install creates 
 /etc/dovecot
 without any file in it, but copy the esxample configuration file only in
 /usr/local/share/doc/dovecot/ ?

It's the intended behavior. Dunno if it's the best. Copying example
config directly to /etc/dovecot/ doesn't seem such a good idea.



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] v2.0.alpha3 released

2009-11-23 Thread Luigi Rosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Timo Sirainen said the following on 23/11/09 23:15:

 and given an /etc directory without any dovecot subdirectory (I moved it
 elsewere for testing purposes), is it ok that make install creates 
 /etc/dovecot
 without any file in it, but copy the esxample configuration file only in
 /usr/local/share/doc/dovecot/ ?

 It's the intended behavior. Dunno if it's the best. Copying example
 config directly to /etc/dovecot/ doesn't seem such a good idea.

It would be nice to put a text file like configuration files go here or
something like that, or just no action at all. Or maybe a message at the end of
make install procedure.

Maybe it's me, but if I find an empty directory in /etc after an installation,
the first think I think is that something went wrong.



Ciao,
luigi

- --
/
+--[Luigi Rosa]--
\

Studio execs often come from different, non-mammalian evolutionary
chains; I think squid rather than fish came onto land and evolved,
mutated, and began running networks and studios and have kept this
fact from us.
   --J. Michael Straczynski
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksLcqAACgkQ3kWu7Tfl6ZSkuQCgxHLOSKq/rkURyF8QSCiI6k4a
kaUAoKngIR74zirf3P4ep8/MKZPAtS7w
=I/40
-END PGP SIGNATURE-


Re: [Dovecot] v2.0.alpha3 released

2009-11-14 Thread Luigi Rosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Timo Sirainen said the following on 10/11/09 04:14:

 http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha3.tar.gz
 http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha3.tar.gz.sig

Given this configure command line

./configure --with-mysql --with-ssl=openssl --sysconfdir=/etc 
--localstatedir=/var

and given an /etc directory without any dovecot subdirectory (I moved it
elsewere for testing purposes), is it ok that make install creates /etc/dovecot
without any file in it, but copy the esxample configuration file only in
/usr/local/share/doc/dovecot/ ?


Ciao,
luigi

- --
/
+--[Luigi Rosa]--
\

TAP: Take Another Plane
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkr+ZEEACgkQ3kWu7Tfl6ZRXTQCgm4wESB7bQbXakla/i5tvstV6
fZkAoJu1oDMOKy+QgrgVSALiZJXqXKrO
=MwjG
-END PGP SIGNATURE-


Re: [Dovecot] v2.0.alpha3 released

2009-11-14 Thread Pascal Volk
On 11/14/2009 09:03 AM Luigi Rosa wrote:
 Given this configure command line
 
 ./configure --with-mysql --with-ssl=openssl --sysconfdir=/etc 
 --localstatedir=/var
 
 and given an /etc directory without any dovecot subdirectory (I moved it
 elsewere for testing purposes), is it ok that make install creates 
 /etc/dovecot
 without any file in it, but copy the esxample configuration file only in
 /usr/local/share/doc/dovecot/ ?

Yes it's OK. :-)
What would happen, if `make install` would copy all the example files
into $SYSCONFDIR/dovecot? It would overwrite your configuration files
with the next `make install` command.


Regards,
Pascal
-- 
The trapper recommends today: beeffeed.0931...@localdomain.org


Re: [Dovecot] v2.0.alpha3 released

2009-11-14 Thread Luigi Rosa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Pascal Volk said the following on 14/11/09 09:28:

 Yes it's OK. :-)
 What would happen, if `make install` would copy all the example files
 into $SYSCONFDIR/dovecot? It would overwrite your configuration files
 with the next `make install` command.

My point if is that if the directory does not exist, it is quite useless to
create it empty.

Either you don't create it and leave the task to sysadmin, or if you create it,
at least put some examples into it.





Ciao,
luigi

- --
/
+--[Luigi Rosa]--
\

Q: And this, I'm particularly proud of - behind the headlights,
  stinger missiles!
James Bond: Excellent, just the thing for unwinding after a rough day
  at the office.
Q: Need I remind you, 007, that you have a license to kill,
  not to break traffic laws.
--007 Goldeneye
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkr+bCIACgkQ3kWu7Tfl6ZSqrQCgzOAmJHHGtlXcCtgUCTeSBaOS
L8kAn3mko7JFlTDTtGpXSj05Sb9gs5hO
=HIiw
-END PGP SIGNATURE-


[Dovecot] v2.0.alpha3 released

2009-11-09 Thread Timo Sirainen
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha3.tar.gz
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha3.tar.gz.sig

Nothing horribly exciting since alpha2, but since I did other releases I
thought I might as well release this one too.

 - Most of the stuff in master.conf is now built into binaries so the
file itself is small. dovecot -n also doesn't show the defaults anymore.

 - Settings now have size and time types. So instead of always wondering
if the units are bytes or kilobytes or megabytes, you can just use e.g.
100k, 100M values. And the same for 100 secs, 100 mins, 100 hours, etc.

 - verbose_proctitle=yes was pretty useless in alpha2 after the
pre/post-login changes. I've now enabled Linux proctitle hack that
allows changing process title (in ps). It now shows e.g. the current
command being executed by imap process. There is also some hope of
getting a proper setproctitle() function to Linux, the patch just got to
-mm code tree today!

 - anvil process now stays alive across SIGHUPs. So doveadm who no
longer forgets users after SIGHUP.

 - remote_ip IP {} and local_ip IP {} changed to remote host|IP {} and
local host|IP {}, i.e. if it's not an IP Dovecot does host name lookup.

 - Using host names is also important to get TLS SNI working. With TLS
SNI support if client supports it, you can serve multiple certificates
with a single IP address.

 - LMTP server adds now Received: header
 - Fixes to LMTP server
 - Fixes to dsync

Some of the larger changes left:

 - plugin API probably needs to be changed, so that it's possible to
handle multiple users by same process but with different plugins
 - config process is too slow
 - rawlog no longer works because of how pre/post-login works now. it
probably needs to be changed into a service and configured something
like:

service imap-rawlog {
  executable = rawlog imap-real /home/%u
  unix_listener imap {
  }
}

service imap {
  unix_listener imap-real {
  }
}

The point would be that when imap-login connects to imap, it actually
connects to rawlog which then connects to imap-real and starts proxying
the connection. A few problems:

1) userdb lookup is done by imap process, so rawlog doesn't know user's
home directory. Perhaps more code could be added so that rawlog requests
imap process to send it back, but maybe that's too much trouble. That's
why I thought just adding a 3rd /home/%u parameter, where rawlog expands
%u to username since that's at least known.

2) Currently it's not possible to remove default internal
unix_listeners, so the above config wouldn't actually work anyway. I
guess there needs to be some new syntax like !unix_listener imap or
something that removes it..

Then again, a nice thing about this is that the rawlog will work with
all types of services, even imap-logins, although that's going to be
almost useless for SSL connections.


signature.asc
Description: This is a digitally signed message part