- dovecot - dovecot.org

[Dovecot] Delete user data from Dovecot server
by Thiago Henrique 18 Aug '10

18 Aug '10

Hello, I'm testing Dovecot 2.0. I plan to use Dovecot 2.0 with thousands of domains per server. My user base is under virtual MySQL. when I add a user in the database, it is automatically created in the structure of Dovecot at first login. Is there a easy way to delete a user ? Thank you. -- Atenciosamente, Thiago Henrique (21)2233-5950 ramal 27 Infra Estrutura Linux Hostnet Internet - www.hostnet.com.br Digirati Telecomunicações - www.digirati.com.br

3 2

[Dovecot] reverting back to 1.2.12
by Dennis Clarke 18 Aug '10

18 Aug '10

ver 1.2.13 is also tossing these : Aug 18 03:37:49 dovecot: Warning: I/O leak: 805c600 (27) Aug 18 03:37:49 dovecot: Warning: I/O leak: 805c600 (25) Aug 18 03:37:49 dovecot: Warning: I/O leak: 805c600 (23) I have reverted back to 1.2.12 which "just works". I will go back and recompile 1.2.13 and 2.0.0 again. Maybe the addition of postgressql libs linked in or the use of GCC is the issue on Solaris. Not sure but 1.2.12 to 1.2.13 did not go smoothly at all. Dennis

1 0

[Dovecot] pigeonhole
by Xavier Pons 18 Aug '10

18 Aug '10

Hi, I'm trying to compile the last mercurial release of dovecot-pigeonhole 2.0 and get this error: 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/kerberos/include -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a ./debug/.libs/libsieve_ext_debug.a /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-storage/.libs/libdovecot-storage.so /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-lda/.libs/libdovecot-lda.so /root/dovecot/dovecot-hg/dovecot-2.0/src/lib-dovecot/.libs/libdovecot.so -ldl -lrt -Wl,--rpath -Wl,/usr/lib/dovecot ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_stringlist_get_length' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_stringlist_read_all' ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `sieve_single_stringlist_create_cstr' collect2: ld returned 1 exit status make[4]: *** [sievec] Error 1 any idea? thanks Xavier

4 6

[Dovecot] 2.0 and vpopmail
by Jason 'XenoPhage' Frisvold 18 Aug '10

18 Aug '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Does 2.0 require a specific version of vpopmail? I'm getting this on my build attempt : /usr/src/redhat/BUILD/dovecot-2.0.0/src/auth/passdb-vpopmail.c:185: undefined reference to `vauth_load_module' Yes, it's an RPM, that's how I roll. I'm not finding vauth_load_module anywhere on my system.. I'm running vpopmail 5.4.30 which is, I believe the latest stable release.. Thanks, - --------------------------- Jason 'XenoPhage' Frisvold xenophage(a)godshell.com - --------------------------- "Any sufficiently advanced magic is indistinguishable from technology." - - Niven's Inverse of Clarke's Third Law -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkxp/6YACgkQ8CjzPZyTUTT0tACgi5WLR2IcGvhmvmIGlmZpeg1P tUQAn2zx6HuIR3QHIGt/aYCP7nRNBvJ7 =yYrj -----END PGP SIGNATURE-----

2 2

[Dovecot] Using dovecot with vpopmail and mysql auth?
by Aaron Greengrass 18 Aug '10

18 Aug '10

Hi, Does anyone happen to know the right strings to do authentication against mysql storing vpopmail data, vs using the vpopmail auth module? I'm trying to get up to both vpopmail 5.5, and dovecot 2.0, and dovecot-auth seems to reliably segfault on the 5.5 vpopmail module. I've tried downgrading vpopmail as well, with less than stellar results. I saw an old article about doing exactly that -- switching from the vpop module, while still using it's DB, but it is both a) old, and b) confusing. Any help you can offer -- or urls in a pinch -- would be appreciated.

1 1

[Dovecot] Very complex Master User Examples using MySQL
by Marc Perkel 17 Aug '10

17 Aug '10

For those who are interested I have posted in the Wiki examples of using master users in very interesting ways. In these example we will create 3 kinds of master users. The first will be users who can read all email for all domains. The next example will be users who can read all email for their domain only. The third example will be users who can read email of domains listed in a separate ownership table. http://wiki2.dovecot.org/Authentication/MasterUsers Go to Advanced SQL Examples at bottom Let me know what you think. In order to actually make this work you'll have to apply this patch Timo just posted: http://hg.dovecot.org/dovecot-2.0/rev/3ba227176cde

1 0

[Dovecot] dovecot 2.0 convert script
by Marc Perkel 17 Aug '10

17 Aug '10

Since my old config had this: protocols = imap imaps pop3 pop3s ssl_cert_file = /usr/share/ssl/certs/imapd.pem ssl_key_file = /usr/share/ssl/certs/imapd.pem then the convert script should have added ssl = yes Just trying to document all the little issues as I find them.

4 5

[Dovecot] Tricky Master User Query - need MySQL help
by Marc Perkel 17 Aug '10

17 Aug '10

OK - I want to do something very tricky with master users and if I get it to work I'm adding it to the wiki for everyone to use. So far I have a MySQL database that servers multiple domains. I can set a flag making someone a domain owner that allows that person to become master of that domain. Here's the query for that. password_query = SELECT user_name, domain_name, password FROM users WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1' AND '%d'='%{login_domain}' So - here's where we get tricky. I have another table called "ownership" where I have 2 fields which is a pairing of email addresses (login_id) and domains owned (owned_object). Data might look like this: joe(a)blow.com domain1.com joe(a)blow.com domain2.com Since joe(a)blow.com owns both domain1.com and domain2.com I want him to be able to log in as anyone in those 2 domains as a master user. Examples: tom@domain1.com*joe@blow.com harry@domain2.com*joe@blow.com So the idea is to create a MySQL query so that if the master user matches the domain part of the login user then it returns true and allows the login. What MySQL query will do that?

1 0

[Dovecot] Master Login using MySQL problem - %{login_domain}
by Marc Perkel 17 Aug '10

17 Aug '10

Hi Timo, Been trying to track this problem down further. The problem seems to be related to verifying the master user failing. My passdb looks like this: passdb { driver = sql args = /etc/dovecot/dovecot-domain-owner-sql.conf master = yes pass = yes } dovecot-domain-owner-sql.conf contains: user_query = SELECT user_name, domain_name FROM users WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1' password_query = SELECT user_name, domain_name, password FROM users WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1' AND '%d'='%{login_domain}' In this example - bill(a)plf.net is an ordinary user. tom(a)plf.net is a domain owner. Tom wants to read bills email. The login is: bill@plf.net*tom@plf.net This results in tom(a)plf.net being classified as an unknown user. Aug 17 08:38:30 auth: Debug: sql(tom(a)plf.net,127.0.0.1): query: SELECT user_name, domain_name, password FROM users WHERE user_name = 'tom' AND domain_name = 'plf.net' AND owns_domain='1' AND 'plf.net'='' Aug 17 08:38:30 auth: Info: sql(tom(a)plf.net,127.0.0.1): unknown user Aug 17 08:38:32 auth: Debug: client out: FAIL 15 user=tom(a)plf.net Aug 17 08:38:32 imap-login: Info: Aborted login (auth failed, 1 attempts): user=<tom(a)plf.net>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=0, secured Note that the query used to determine that tom(a)plf.net is valid is the password_query and not the user_query resulting in unknown user. I think that's where the problem is.

3 7

[Dovecot] Managesieve and Dovecot 2.0: clients incompatible?
by Jerrale G 17 Aug '10

17 Aug '10

I successfully converted my 1.2.x config and am trying to use managesieve. This configuration is really for 1.2.x even though it says for 2.0: http://wiki2.dovecot.org/ManageSieve/Configuration Trying to assign the port number is not by using "listen". Anyway, I just reverted, on the client, to using the default port 2000. The managesieve client now hangs trying to login and eventually times out. Is the new pigeonhole managesieve incompatible with clients that worked with managesieve 0.11.11? There is no output in the log concerning managesieve from pigeonhole. I guess I could put log=/path/to/a/file in the managesieve part and see what happens. In the old dovecot 1.2, we would get a "managesieve-login" in the log when a client even TRIED to login; now, nothing! -- Jerrale G. SC Senior Admin

2 1