[Dovecot] Dovecot 1-2-6 and management-sieve
Hello, I try to patch the dovecot-Sources to use the management-sieve. I've downloaded the Sources, unpacked them, do a gzip -dc dovecot-1-2-managesieve-patch-52abc11d7f48.tar.gz |patch -p1. I get a Error rom the patch: patching file README.managesieve patching file dovecot-example.conf patching file src/master/child-process.c patching file src/master/child-process.h patching file src/master/listener.c patching file src/master/login-process.c patching file src/master/mail-process.c patching file src/master/main.c patching file src/master/master-settings-defs.c patching file src/master/master-settings.c patching file src/master/master-settings.h patch unexpectedly ends in middle of line What do I wrong? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email d...@marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
Re: [Dovecot] Bad_MIME on vacation messages
Installed postfix and problem solved.. so something screwy with the qmail install On Mon, Oct 12, 2009 at 1:19 PM, Stephen Vaughan stephenvaug...@gmail.comwrote: My .dovecot.sieve is just one that I've coped straight off the dovecot wiki, it has to be qmail doing some weird things. I'm tempted to just install postfix and see if that will fix it. On Sat, Oct 10, 2009 at 1:30 AM, Charles Marcus cmar...@media-brokers.com wrote: On 10/7/2009, Stephen Vaughan (stephenvaug...@gmail.com) wrote: We are using Dovecot Sieve 0.1.12, the auto reply message contains ^M characters at the end of a few lines, they are only visable through vi, example: So, the solution is to find out what is breaking the headers (adding the ^M characters). You keep assuming it is a dovecot problem, but I don't think it is. You've never posted your vacation or sieve scripts or dovecot -n output (that I can see), so that would be a good place to start. My best guess is its either a bad sieve script or something weird qmail is doing. -- Best regards, Charles -- Best Regards, Stephen Sent from Sydney, Nsw, Australia -- Best Regards, Stephen Sent from Sydney, Nsw, Australia
Re: [Dovecot] Dovecot 1-2-6 and management-sieve
On 10/12/2009 03:44 PM Daniel Spannbauer wrote: Hello, I try to patch the dovecot-Sources to use the management-sieve. I've downloaded the Sources, unpacked them, do a gzip -dc dovecot-1-2-managesieve-patch-52abc11d7f48.tar.gz |patch -p1. I get a Error rom the patch: patching file README.managesieve patching file dovecot-example.conf patching file src/master/child-process.c patching file src/master/child-process.h patching file src/master/listener.c patching file src/master/login-process.c patching file src/master/mail-process.c patching file src/master/main.c patching file src/master/master-settings-defs.c patching file src/master/master-settings.c patching file src/master/master-settings.h patch unexpectedly ends in middle of line What do I wrong? You are trying to apply the file series as patch, but this is not a patch. Extract the gziped archive and apply only the managesieve.patch. Regards, Pascal -- The trapper recommends today: cafefeed.0928...@localdomain.org
Re: [Dovecot] Dovecot 1-2-6 and management-sieve
Pascal Volk schrieb: On 10/12/2009 03:44 PM Daniel Spannbauer wrote: Hello, I try to patch the dovecot-Sources to use the management-sieve. I've downloaded the Sources, unpacked them, do a gzip -dc dovecot-1-2-managesieve-patch-52abc11d7f48.tar.gz |patch -p1. I get a Error rom the patch: patching file README.managesieve patching file dovecot-example.conf patching file src/master/child-process.c patching file src/master/child-process.h patching file src/master/listener.c patching file src/master/login-process.c patching file src/master/mail-process.c patching file src/master/main.c patching file src/master/master-settings-defs.c patching file src/master/master-settings.c patching file src/master/master-settings.h patch unexpectedly ends in middle of line What do I wrong? You are trying to apply the file series as patch, but this is not a patch. Extract the gziped archive and apply only the managesieve.patch. Ah, ok. Thanks. I should look at what im downloaded :) Tanks a lot Regards Daniel Regards, Pascal -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email d...@marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
Re: [Dovecot] bsdauth with cache_key failed
On Sun, 2009-10-11 at 19:44 +0200, Pascal Volk wrote: Oct 8 10:04:12 pegasus dovecot: auth(default): Panic: file passdb.c: line 201 (passdb_init): assertion failed: (passdb-passdb-default_pass_scheme != NULL || passdb-passd b-cache_key == NULL) Oct 8 10:04:12 pegasus dovecot: dovecot: child 8407 (auth) killed with signal 6 (core not dumped) hi, the attached patch has solved this issue on my OpenBSD system. + module-default_pass_scheme = PLAIN; I think the passwords come in CRYPT format, not PLAIN? I added that. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] @2.0, autocreate fails. Permission lookup failed?
On Sat, 2009-10-10 at 22:06 -0700, PGNet Dev wrote: with similar confs in v1.2, autocreate works as expected, creating all subdirs correctly. in v2.0, @ imap login (with TBird, atm), only Trash folder is created, but nothing else, I think you're missing autocreate from mail_plugins setting. And Trash is probably created by your client. Oct 10 22:01:11 IMAP(testu...@my.domain.com): Info: Namespace : Permission lookup failed from /data/mail/Domains/my.domain.com/Accounts/testuser/Trash This message could perhaps be improved.. It anyway means that Dovecot wanted to find out what permissions to use for Trash mailbox, but the Trash directory didn't yet exist so.. Oct 10 22:01:11 IMAP(testu...@my.domain.com): Info: Namespace : Using permissions from /data/mail/Domains/my.domain.com/Accounts/testuser: mode=0700 gid=-1 It fallbacked to using the default permissions from testuser directory. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] clarify 'type', 'executable' 'path' in 2.0 master.conf?
On Sat, 2009-10-10 at 13:57 -0700, PGNet Dev wrote: On Sat, Oct 10, 2009 at 1:55 PM, Timo Sirainen t...@iki.fi wrote: You didn't list auth, which is also there. you're correct. so, auth, auth-source, config, log, anvil is all the types? Yeah. signature.asc Description: This is a digitally signed message part
[Dovecot] Autocreate plugin for some domains
Thanks In my mail server are hosted multiple domains, I need to create folders automatically only to users of certain domains, it is feasible to use the plugin Autocreate only for certain domains? Thanks Jose Luis _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us
Re: [Dovecot] Autocreate plugin for some domains
On Mon, 2009-10-12 at 14:59 -0500, Jose Luis Marin Perez wrote: In my mail server are hosted multiple domains, I need to create folders automatically only to users of certain domains, it is feasible to use the plugin Autocreate only for certain domains? What do you use as userdb? From userdb you can add/override any settings. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Autocreate plugin for some domains
On 10/12/2009 09:59 PM Jose Luis Marin Perez wrote: Thanks In my mail server are hosted multiple domains, I need to create folders automatically only to users of certain domains, it is feasible to use the plugin Autocreate only for certain domains? Thanks Please don't hijack threads. See: http://dovecot.org/list/dovecot/2009-July/041704.html Regards, Pascal -- The trapper recommends today: beeffeed.0928...@localdomain.org
Re: [Dovecot] Autocreate plugin for some domains
Dear Sirs Thanks for your reply, this is the configuration of dovecot: # 1.1.16: /usr/local/etc/dovecot.conf # OS: Linux 2.6.9-67.0.15.plus.c4smp i686 CentOS release 4.6 (Final) log_path: /var/log/dovecot.log listen: *:10143 ssl_listen: *:10943 disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 89 last_valid_uid: 89 first_valid_gid: 89 last_valid_gid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mail_plugins: quota namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: passdb: driver: checkpassword args: /usr/vpopmail/bin/vchkpw /usr/local/bin/vchkpw-wrapper.sh userdb: driver: prefetch args: uid=89 gid=89 home=/usr/vpopmail/domains/%d/%u plugin: quota: maildir quota_rule: ?:storage=0 quota_rule2: Trash:ignore Thanks Jose Luis From: t...@iki.fi To: jolumape...@hotmail.com Date: Mon, 12 Oct 2009 16:03:18 -0400 CC: dovecot@dovecot.org Subject: Re: [Dovecot] Autocreate plugin for some domains On Mon, 2009-10-12 at 14:59 -0500, Jose Luis Marin Perez wrote: In my mail server are hosted multiple domains, I need to create folders automatically only to users of certain domains, it is feasible to use the plugin Autocreate only for certain domains? What do you use as userdb? From userdb you can add/override any settings. _ Explore the seven wonders of the world http://search.msn.com/results.aspx?q=7+wonders+worldmkt=en-USform=QBRE
Re: [Dovecot] @2.0, autocreate fails. Permission lookup failed?
hi, On Mon, Oct 12, 2009 at 12:49 PM, Timo Sirainen t...@iki.fi wrote: I think you're missing autocreate from mail_plugins setting. Right place to look, it turns out. Turns out that the encoding on imap.conf had been -- somoehow -- switched to Windows Latin. Odd, as I have no Win boxes around. Anyway, no errors were fired, but something in the line-endings difference caused either the mail_plugins setting, or the whole imap.conf file, to not parse correctly. Switched back to UTF encoding, all's well. And Trash is probably created by your client. You're correct. Didn't realize that it did so ... Oct 10 22:01:11 IMAP(testu...@my.domain.com): Info: Namespace : Permission lookup failed from /data/mail/Domains/my.domain.com/Accounts/testuser/Trash This message could perhaps be improved.. It anyway means that Dovecot wanted to find out what permissions to use for Trash mailbox, but the Trash directory didn't yet exist so.. Oct 10 22:01:11 IMAP(testu...@my.domain.com): Info: Namespace : Using permissions from /data/mail/Domains/my.domain.com/Accounts/testuser: mode=0700 gid=-1 It fallbacked to using the default permissions from testuser directory. Thanks for clearing that up. Still, the Trash directory _did_ exist -- created, as you pointed out, by my client. Once I get stuff cleaned up here, I'll check all this again ... Thanks.
Re: [Dovecot] Autocreate plugin for some domains
Dear Sirs, I use as userdb, the following: userdb: driver: prefetch args: uid=89 gid=89 home=/usr/vpopmail/domains/%d/%u Dovecot -n # 1.1.16: /usr/local/etc/dovecot.conf # OS: Linux 2.6.9-67.0.15.plus.c4smp i686 CentOS release 4.6 (Final) log_path: /var/log/dovecot.log listen: *:10143 ssl_listen: *:10943 disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 89 last_valid_uid: 89 first_valid_gid: 89 last_valid_gid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mail_plugins: quota namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: passdb: driver: checkpassword args: /usr/vpopmail/bin/vchkpw /usr/local/bin/vchkpw-wrapper.sh userdb: driver: prefetch args: uid=89 gid=89 home=/usr/vpopmail/domains/%d/%u plugin: quota: maildir quota_rule: ?:storage=0 quota_rule2: Trash:ignore How could create folders to users in certain domains by autocreate plugin? Thanks Jose Luis Subject: Re: [Dovecot] Autocreate plugin for some domains From: t...@iki.fi To: jolumape...@hotmail.com CC: dovecot@dovecot.org Date: Mon, 12 Oct 2009 16:03:18 -0400 On Mon, 2009-10-12 at 14:59 -0500, Jose Luis Marin Perez wrote: In my mail server are hosted multiple domains, I need to create folders automatically only to users of certain domains, it is feasible to use the plugin Autocreate only for certain domains? What do you use as userdb? From userdb you can add/override any settings. _ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vistamkt=en-USform=QBRE
[Dovecot] Homedir for sieve/LDAP
I'm somewhat confused regarding Home Directories needed by sieve and setting them for an LDAP userdb. We have system users, passdb ldap, userdb ldap, but home directories are not mounted on the mail server. Now apparently, sieve needs the home directory for .dovecot.lda-dupes. Is there an easier way to give lda/sieve a home directory than setting something along the lines of user_attrs = ...,uid=home=/import/mail/%$/home in dovecot-ldap.conf?
Re: [Dovecot] Homedir for sieve/LDAP
On Tue, 2009-10-13 at 00:02 +0200, Edgar Fuß wrote: We have system users, passdb ldap, userdb ldap, but home directories are not mounted on the mail server. It doesn't matter if Dovecot's home directories are different from the users' primary home directories. It's probably even better if they're different. http://wiki.dovecot.org/VirtualUsers#homedirs should apply to your use case as well. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Homedir for sieve/LDAP
On Tue, 2009-10-13 at 00:02 +0200, Edgar Fuß wrote: Is there an easier way to give lda/sieve a home directory than setting something along the lines of user_attrs = ...,uid=home=/import/mail/%$/home in dovecot-ldap.conf? You could also avoid using uid for that and use instead: .., =home=/import/mail/%u/home signature.asc Description: This is a digitally signed message part
[Dovecot] v2.0.alpha1 released
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz
http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha1.tar.gz.sig
So here's the first alpha version of Dovecot v2.0. There are still a
couple of things left to do, but in general it should work for most
people. I started using it for my own mails a few days ago and it seems
to work without errors.
Largest changes since v1.2:
* Global ACLs are now looked up using namespace prefixes. For example
if you previously had INBOX. namespace prefix and a global ACL for
INBOX.Sent, it's now looked up from INBOX.Sent file instead of
Sent as before.
+ Redesigned master process. It's now more modular and there is less
code running as root.
+ Configuration supports now per-local/remote ip/network settings.
+ dsync utility does a two-way mailbox synchronization.
+ LMTP server and proxying.
+ Added mdbox (multi-dbox) mail storage backend.
+ doveadm utility can be used to do all kinds of administration
functions. Old dovecotpw and *view utilities now exist in its
subcommands.
Some things left to do:
- Do something about backwards compatibility with v1.x. Either make it
read v1.x config files or provide some config conversion utility.
- dsync still has some bugs
- config process is a bit too slow. config handling in general could use
some caching all around. no need to ask configuration for each login
unless there are per-remote-ip settings.
- some kind of an optional connection policy server could be useful.
mainly to finally implement tcp-wrappers support.
- mail_uid, mail_gid, mail_chroot settings don't really work now. I
think this actually needs a bit larger change, which is probably a good
idea in any case:
After successfully authenticating, login process needs to get imap/pop3
process executed. Currently this is done by transferring the connection
fd to master process, doing userdb lookup and then forking and execing
the imap/pop3 process.
The new behavior I'm thinking is that after auth, login process would
connect to imap/pop3 unix socket in the login/ directory. That would
cause master process to fork a new imap/pop3 process (running as root).
Login process would send the necessary auth information via the unix
socket, possibly transfer also the fd, and imap/pop3 would do the userdb
lookup and then drop privileges.
This change has some pros:
- Master process will no longer temporarily hold some extra fds and use
extra memory during auth lookups. If auth process is hanging these could
cause problems.
- Master process will no longer have any special auth handling code and
I can remove type=auth-source and type=auth services.
- Of course fixes the mail_* setting issue, because all of this is now
done by imap/pop3 process, which knows about these settings.
- Creating support for multiple imap/pop3 post-login connections in a
single process should be pretty easy to implement with this. The
imap/pop3 unix socket just needs to be listened by a new process in the
middle that keeps track of what imap/pop3 processes exist and can
redirect the new connections to those.
But also some cons:
- drop_priv_before_exec=yes no longer works, unless the uid/gid is
hardcoded to the service {} block.
- Each imap/pop3 process needs to do a connect() to auth server at
startup, adding a bit to the latency.
signature.asc
Description: This is a digitally signed message part
[Dovecot] dovecot-2.0-managesieve make fails @ '...libdovecot-login.so: undefined reference to `login_process_preinit''
building, dovecot-2.0, HEAD:10054:5cb162da8708 dovecot-2.0-sieve, 1051:1d194d46d6e6 both build fine. @, dovecot-2.0-managesieve, 159:2236331aa0a3 cd /usr/local/src/dovecot-2.0-managesieve/ ./configure \ --with-dovecot=/usr/local/src/dovecot-2.0 \ --with-dovecot-sieve=/usr/local/src/dovecot-2.0-sieve make fails @, ... gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/src/dovecot-2.0 -I/usr/local/src/dovecot-2.0/src/lib -I/usr/local/src/dovecot-2.0/src/lib-auth -I/usr/local/src/dovecot-2.0/src/lib-master -I/usr/local/src/dovecot-2.0/src/login-common -I../../src/lib-managesieve -I/usr/local/src/dovecot-2.0-sieve -I/usr/local/src/dovecot-2.0-sieve/src/lib-sieve -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/local/ssl/include -MT managesieve-proxy.o -MD -MP -MF .deps/managesieve-proxy.Tpo -c -o managesieve-proxy.o managesieve-proxy.c mv -f .deps/managesieve-proxy.Tpo .deps/managesieve-proxy.Po /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/local/ssl/include-o managesieve-login client.o client-authenticate.o managesieve-proxy.o /usr/local/src/dovecot-2.0-sieve/src/lib-sieve/libsieve.la /usr/local/src/dovecot-2.0/src/login-common/libdovecot-login.la ../../src/lib-managesieve/libmanagesieve.a ../../src/lib-sievestorage/libsievestorage.a /usr/local/src/dovecot-2.0/src/lib-dovecot/libdovecot.la -lrt libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/local/ssl/include -o .libs/managesieve-login client.o client-authenticate.o managesieve-proxy.o /usr/local/src/dovecot-2.0-sieve/src/lib-sieve/.libs/libsieve.a /usr/local/src/dovecot-2.0/src/login-common/.libs/libdovecot-login.so -L/usr/local/ssl/lib -lssl -lcrypto -lz ../../src/lib-managesieve/libmanagesieve.a ../../src/lib-sievestorage/libsievestorage.a /usr/local/src/dovecot-2.0/src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,-rpath -Wl,/usr/local/lib/dovecot /usr/local/src/dovecot-2.0/src/login-common/.libs/libdovecot-login.so: undefined reference to `login_process_preinit' collect2: ld returned 1 exit status make[3]: *** [managesieve-login] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot-2.0-managesieve/src/managesieve-login' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-2.0-managesieve/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-2.0-managesieve' make: *** [all] Error 2
[Dovecot] @2.0 IMAP login, Error: ...//lib20_fts_plugin.so: undefined symbol: fts_next_hook_mailbox_allocated
hi,
@ imap login to 2.0/head,
Oct 12 21:06:53 master: Info: Dovecot v2.0.alpha1 starting up (core
dumps disabled)
Oct 12 21:07:16 imap-login: Info: Login:
user=testu...@my.domain.com, method=PLAIN, rip=192.168.1.100,
lip=192.168.1.101, TLS
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Loading modules
from directory: /usr/local/lib/dovecot
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Module loaded:
/usr/local/lib/dovecot/lib10_quota_plugin.so
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Module loaded:
/usr/local/lib/dovecot/lib11_imap_quota_plugin.so
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Info: Module loaded:
/usr/local/lib/dovecot/lib20_autocreate_plugin.so
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Error:
dlopen(/usr/local/lib/dovecot/lib20_fts_plugin.so) failed:
/usr/local/lib/dovecot/lib20_fts_plugin.so: undefined symbol:
fts_next_hook_mailbox_allocated
Oct 12 21:07:16 IMAP(testu...@my.domain.com): Fatal: Couldn't load
required plugins
also, after install, i note,
cd /usr/local/lib
ls dovecot/{imap,lda,pop3}
dovecot/imap:
lib15_notify_plugin.so
dovecot/lda:
lib15_notify_plugin.so lib90_sieve_plugin.a lib90_sieve_plugin.la
lib90_sieve_plugin.so
dovecot/pop3:
lib15_notify_plugin.so
shouldn't, e.g., dovecot/imap have auto-populated symlinks to
autocreate, fts, etc plugins? or for 2.0 do they need to be manually
created?
thx.
