Re: [Dovecot] anti spam measures
Jakob Curdes wrote: Still no ideas. Sigh. JC Sorry, then I am afraid I do nnot know what the problem is. Good luck. Trever signature.asc Description: OpenPGP digital signature
Re: [Dovecot] ManageSieve and invalid scriptname
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 27 Nov 2008, Miguel Filho wrote: Well as you can see, a file without the .sieve is not welcome :-( I checked the RFC and there is no requirement for a .sieve file extension when considering scriptnames. Well, the RFC specifies the scriptname on wire, but does not (and should not) care, what happens afterwards. You muddle with the internal storage of the managesieve demon. It contains sanity checks to prevent that its operations breaks other programs managing Sieve scripts and the other way around. Is this a misplaced restriction or it really should be enforced for any reason? I hope that this can be tolerable, or I will have to rename a lot of scripts and remove all hardcoded phpscript strings from avelsieve :-( I guess you've configured avelsieve to place the script right into the home directory of the user rather than through ManageSieve, right? Therefore Managesieve detects that this script is alien and keeps its hands off. Either use Managesieve (the protocol) or configure the symlinks in reverse direction (though I suppose it won't work unless Avelsieve overwrites the file): ln -s ~user/.dovecot.sieve ~user/phpscript So Avelsieve will manage, whatever Managesieve places there, and Managesieve does not detect the alien interference. Another strategy would be to: a) test what happens if the target of ~/.dovecot.sieve (~/Maildir/sieve/script.sieve) is a symlink itself. b) remove the name check from the demon. But why are you using two sieve management interfaces? Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJL6jlVJMDrex4hCIRAo/UAJ46ftWtrmSxnrhmYEac/kpUblOLngCeLvzN Y7dXaE1cvNzPw7s/XMQOQ4s= =otoV -END PGP SIGNATURE-
[Dovecot] Panic in 1.1.6 file ioloop.c: line 206
Hi all, I just had a panic with dovecot 1.1.6, two days after replacing 1.0.15 with it in production. Here are the logs immediately preceding the panic, I think they're related. It seems the user connected simultaneously from two different clients, from his own computer and a webmail running on the server, then manipulated mail folders on one side, and logged out. The panic occurred 3 seconds after the logout. Is there a setting I might have missed that could avoid that? TIA, Laurent Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): stat() failed with mbox file /home/user/rAOk-union-DA: No such file or directory Nov 27 19:25:59 balif last message repeated 1 time Nov 27 19:25:59 balif dovecot: [ID 107833 local2.info] IMAP(user): Disconnected: Logged out bytes=436/4810193 Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): file_dotlock_open() failed with file /var/dovecot/index/user/.imap/RAOk-union-DAFC-DCBE-DMCT/dovecot.index.log: No such file or directory Nov 27 19:25:59 balif last message repeated 1 time Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): stat() failed with mbox file /home/user/RAOk-union-DAFC-DCBE-DMCT: No such file or directory Nov 27 19:25:59 balif dovecot: [ID 107833 local2.info] IMAP(user): Disconnected: Logged out bytes=494/314696 Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): file_dotlock_open() failed with file /var/dovecot/index/user/.imap/rAOk-union-directeurs/dovecot.index.log: No such file or directory Nov 27 19:25:59 balif last message repeated 1 time Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): stat() failed with mbox file /home/user/rAOk-union-directeurs: No such file or directory Nov 27 19:25:59 balif dovecot: [ID 107833 local2.info] IMAP(user): Disconnected: Logged out bytes=470/1138733 Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): file_dotlock_open() failed with file /var/dovecot/index/user/.imap/NACRE/dovecot.index.log: No such file or directory Nov 27 19:25:59 balif last message repeated 1 time Nov 27 19:25:59 balif dovecot: [ID 107833 local2.error] IMAP(user): stat() failed with mbox file /home/user/NACRE: No such file or directory Nov 27 19:25:59 balif last message repeated 1 time Nov 27 19:25:59 balif dovecot: [ID 107833 local2.info] IMAP(user): Disconnected: Logged out bytes=2429/174842484 Nov 27 19:25:59 balif dovecot: [ID 107833 local2.info] IMAP(user): Disconnected: Logged out bytes=467/10178 Nov 27 19:26:02 balif dovecot: [ID 107833 local2.crit] Panic: file ioloop.c: line 206: assertion failed: (tv_r-tv_sec = 0 tv_r-tv_usec = 0) Nov 27 19:26:02 balif dovecot: [ID 398108 local2.error] Raw backtrace: 0x24d90 - 0x2851c - 0x286ac - 0x28728 - 0x28de0 - 0x2877c - 0x1f56c - 0x15c40 -- / Leader de Projet Communauté| I'm working, but not speaking for \ G11N http://fr.opensolaris.org | Bull Services http://www.bull.com / FOSUG http://guses.org |
[Dovecot] Autocreate plugin for 1.1 - trying to patch under FreeBSD
Hello all. I try to add Autocreate plugin patch to my FreeBSD host. I think I make all wrong. Could you tell me how to patch it? What I do: cd /usr/ports/mail/dovecot make extract cd cd work/dovecot-1.1.6/src/ fetch http://www.dovecot.org/patches/1.1/autocreate-plugin.c sh -x /tmp/patch.sh + export DOVECOT=~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src + gcc -fPIC -shared -g -Wall -I~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src -I~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src/src/lib -I~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src/src/lib-storage -I~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src/src/lib-mail -I~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src/src/lib-imap -DHAVE_CONFIG_H autocreate-plugin.c -o autocreate_plugin.so autocreate-plugin.c:22:17: error: lib.h: No such file or directory autocreate-plugin.c:23:26: error: mail-storage.h: No such file or directory autocreate-plugin.c:24:28: error: mail-namespace.h: No such file or directory autocreate-plugin.c:28: error: 'PACKAGE_VERSION' undeclared here (not in a function) autocreate-plugin.c:31: warning: 'struct mail_namespace' declared inside parameter list autocreate-plugin.c:31: warning: its scope is only this definition or declaration, which is probably not what you want autocreate-plugin.c:33: warning: 'struct mail_namespace' declared inside parameter list autocreate-plugin.c: In function 'autocreate_mailboxes': autocreate-plugin.c:43: warning: implicit declaration of function 'mail_namespace_find' autocreate-plugin.c:43: warning: assignment makes pointer from integer without a cast autocreate-plugin.c:45: warning: implicit declaration of function 'mail_storage_mailbox_create' autocreate-plugin.c:45: error: dereferencing pointer to incomplete type autocreate-plugin.c:46: error: 'FALSE' undeclared (first use in this function) autocreate-plugin.c:46: error: (Each undeclared identifier is reported only once autocreate-plugin.c:46: error: for each function it appears in.) autocreate-plugin.c:49: warning: implicit declaration of function 'i_snprintf' autocreate-plugin.c: At top level: autocreate-plugin.c:54: warning: 'struct mail_namespace' declared inside parameter list autocreate-plugin.c: In function 'autosubscribe_mailboxes': autocreate-plugin.c:64: warning: assignment makes pointer from integer without a cast autocreate-plugin.c:66: warning: implicit declaration of function 'mailbox_list_set_subscribed' autocreate-plugin.c:66: error: dereferencing pointer to incomplete type autocreate-plugin.c:66: error: 'TRUE' undeclared (first use in this function) autocreate-plugin.c: At top level: autocreate-plugin.c:74: warning: 'struct mail_namespace' declared inside parameter list autocreate-plugin.c: In function 'autocreate_mail_namespaces_created': autocreate-plugin.c:77: warning: passing argument 1 of 'autocreate_next_hook_mail_namespaces_created' from incompatible pointer type autocreate-plugin.c:79: warning: passing argument 1 of 'autocreate_mailboxes' from incompatible pointer type autocreate-plugin.c:80: warning: passing argument 1 of 'autosubscribe_mailboxes' from incompatible pointer type autocreate-plugin.c: In function 'autocreate_plugin_init': autocreate-plugin.c:89: error: 'hook_mail_namespaces_created' undeclared (first use in this function) autocreate-plugin.c: In function 'autocreate_plugin_deinit': autocreate-plugin.c:95: error: 'hook_mail_namespaces_created' undeclared (first use in this function) + cp autocreate_plugin.so /usr/local/lib/dovecot/imap/autocreate_plugin.so cp: autocreate_plugin.so: No such file or directory P.S. cat /tmp/patch.sh # replace * with the correct version: export DOVECOT=~/usr/ports/mail/dovecot/work/dovecot-1.1.6/src gcc -fPIC -shared -g -Wall -I$DOVECOT -I$DOVECOT/src/lib \ -I$DOVECOT/src/lib-storage -I$DOVECOT/src/lib-mail \ -I$DOVECOT/src/lib-imap -DHAVE_CONFIG_H \ autocreate-plugin.c -o autocreate_plugin.so # $PREFIX is the installation directory, e.g. /usr/local or /usr: cp autocreate_plugin.so /usr/local/lib/dovecot/imap/autocreate_plugin.so -- Best regards, Proskurin Kirill
Re: [Dovecot] ManageSieve and invalid scriptname
On Fri, Nov 28, 2008 at 6:16 AM, Steffen Kaiser [EMAIL PROTECTED] wrote: I guess you've configured avelsieve to place the script right into the home directory of the user rather than through ManageSieve, right? Therefore Managesieve detects that this script is alien and keeps its hands off. No, avelsieve is a squirrelmail plugin to create a sieve script. It talks to a ManageSieve daemon, in my case pysieved. pysieved puts the scripts in ~/.sieve and links ~/.dovecot.sieve do the current script in ~/.sieve. So Avelsieve will manage, whatever Managesieve places there, and Managesieve does not detect the alien interference. Avelsieve doesn't manage anything, pysieved does. b) remove the name check from the demon. That is what I'm asking :-D But why are you using two sieve management interfaces? I'm not. I'm testing the ManageSieve patch and preparing to replace pysieved, because it lacks encryption and I need to open direct access to it for my users. Regards, Miguel
[Dovecot] More info from mail_log plugin
HiWe need to track exactly when our users read messages. Unfortunately, I haven't been able to figure out how we can achieve this with Dovecot. Then I saw the mail_log plugin.Is it possible to extend the plugin to also log system flag changes? This would be great, because then we could see in the log files when the Seen flag has been set. Changes in user defined flags would also be interesting to track.I know this would create a lot of log entries, but for us this wouldn't be a problem. Maybe the plugin would default to not tracking flag changes, but could be configured to do so.RegardsBardur Ha Skor _ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-ussource=wlmailtagline
[Dovecot] Dovecot as proxy for M$ Exchange mailboxes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, is there a way to use dovecot as proxy for m$ exchange mailboxes? Currently, our clients not only can login to their mailboxes with their e-mail address but also with their accountid. Both the clients e-mail address and accountid are stored in ldap. Now I need a way to let dovecot rewriting the client's accountid to the respective e-mail address. Is this possible with the proxy-feature of dovecot? Any hints would be appreciated. - -- Freundliche Grüße / Kind regards Axel Schmalowsky Platform Engineer ___ domainfactory GmbH Oskar-Messter-Str. 33 85737 Ismaning Germany Telefon: +49 (0)89 / 55266-356 Telefax: +49 (0)89 / 55266-222 E-Mail: [EMAIL PROTECTED] Internet: www.df.eu Registergericht: Amtsgericht München HRB 150294, Geschäftsführer Tobias Marburg, Jochen Tuchbreiter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJL+JKsuqpduCyZM0RAoFUAJ9mPbv5eI5xP54YhwlmOs40F1RxDQCgir5l jCdaNeXKO8FnOCxaKSI7S4E= =m5WN -END PGP SIGNATURE-
Re: [Dovecot] ManageSieve and invalid scriptname
On Fri, Nov 28, 2008 at 10:02 AM, Steffen Kaiser [EMAIL PROTECTED] wrote: Do the migration pysieved - managesieve like so: + Connect with an user without .dovecot.sieve symlink to managesieved. + Upload a new script. + Check where the script has been filed into. + Then replicate the structure for each user and rename the existing file into phpsieve.sieve (phpsieve is the name of the script) and adjust the ~/.dovecot.sieve symlink to point there. That is what I'm trying to avoid. My original problem is this: sieve-storage: Active sieve script symlink /home/admsis/miguel/.dovecot.sieve is broken: invalid scriptname (points to .sieve/phpscript). 1) The link is correct 2) cmusieve works fine with a link pointing to a file WITHOUT .sieve at the end. When the ManageSieve patch follows the .dovecot.sieve link it complains that the file does not end in .sieve. So, I'm asking if there is a real point doing this restriction or the guilt is pysieved for not creating a file with a .sieve at the end. If the pysieved is guilt, than I will have to rename all scripts already installed :-( Regards, Miguel
Re: [Dovecot] ManageSieve and invalid scriptname
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 28 Nov 2008, Miguel Filho wrote: there is a real point doing this restriction or the guilt is pysieved for not creating a file with a .sieve at the end. There is no guilt here. Both are independed demons for the same service. You could put the same guilt to UW-imap for not storing mails in Maildir, or, when you switch from Cyrus to Dovecot, to any of the two for not use the same storage backend. I count it as safety measurement to probe for the extension. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJL+0+VJMDrex4hCIRAgYjAJ4pyi9SAkFplkMMn/peE7EXcLaT2wCg2BXP bZUt9kUYtkddu7QqYisaCN4= =FmcA -END PGP SIGNATURE-
Re: [Dovecot] Sieve and global scripts
Hi Stephan I will love this feature too. Allan, could you give some example of your wrapper. Thanks, Andres Allan Cassaro escribió: Hi Stephan Bosch, there's any way to make the dovecot deliver agent (with sieve) load a global sieve script before load the user sieve file? I want to create some rules for every one, like: if header contais: IS SPAM, move to SPAM BOX... I made this today with a couple of sed + awk and a wraper for managesieve-login... but, this is definily not the best way to do this... This is possible to do? (Even with change in the code) Regards.
Re: [Dovecot] ManageSieve and invalid scriptname
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 28 Nov 2008, Miguel Filho wrote: So Avelsieve will manage, whatever Managesieve places there, and Managesieve does not detect the alien interference. Avelsieve doesn't manage anything, pysieved does. OK, so you do use two interfaces, managesieve and pysieved ;-) But why are you using two sieve management interfaces? I'm not. I'm testing the ManageSieve patch and preparing to replace pysieved, because it lacks encryption and I need to open direct access to it for my users. Do the migration pysieved - managesieve like so: + Connect with an user without .dovecot.sieve symlink to managesieved. + Upload a new script. + Check where the script has been filed into. + Then replicate the structure for each user and rename the existing file into phpsieve.sieve (phpsieve is the name of the script) and adjust the ~/.dovecot.sieve symlink to point there. E.g. my real users with Maildir + have ~/.dovecot.sieve - Maildir/sieve/horde-ingo.sieve + Maildir base path is ~/Maildir + and Horde uses horde-ingo as script name. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJL93CVJMDrex4hCIRAi4EAKDDZWVuJ9EgUYiO9xOz9fMXoaWAfwCgyOyq 0Gbh/xj4c0Zb3g3pMd7X26k= =bgr0 -END PGP SIGNATURE-
Re: [Dovecot] Dovecot Proxy with MySQL auth
I get the feeling not many people are using Dovecot proxy with MySQL auth. Is there anyone who has done this before? We might end up going with something like NGINX for the proxy instead if we cannot figure out if and how this should work for our type of scenario but it would be nice if we could go with fewer components. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Krejci Sent: Wednesday, November 26, 2008 11:57 AM To: 'Dovecot Mailing List' Subject: [Dovecot] Dovecot Proxy with MySQL auth We are looking at deploying several pop/imap servers to house the mail for 15,000 or more mailbox accounts. We are contemplating on the design and are looking at using MySQL auth (we already have a MySQL environment in place for our user auth to live) and proxy_maybe so each server can proxy for all the others and we just have a network load balancer distribute the incoming connections to all of the Dovecot servers. Each server would have its own local maildir storage for the users local to that server and all of the authentication and target backend pop/imap server data would be stored in the same MySQL database. The problem we are running into is the documentation is not very clear on this type of scenario. http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy At the bottom of this page it gives a query example of SELECT NULL AS password, . but that does not seem to allow for us to use the proxy_maybe if the destination server is localhost (and therefore do not proxy) it does not seem that the above query will actually send the real password for authentication. Is this a misunderstanding on our part or is the use of mysql auth + proxy_maybe not feasible? Assuming the latter we surmised using a separate instance of Dovecot on each machine to act solely as a proxy front end (use proxy instead of proxy_maybe) then on the second instance there is no proxy config and it listens on a separate TCP port like 80143 or whatever. Any input or suggestions would be appreciated. Justin Krejci
Re: [Dovecot] Sieve and global scripts
Hi, Since there already is support for including a global sieve script from within your personal sieve script, wouldn't it be easier to add a default sieve script in your /etc/skel/ dir that includes the global script include? In that way it works out of the box for new users, but configuration can be changed/disabled by the user. Not sure about existing users, though... Regards, Tom Andrés Yacopino schreef: Hi Stephan I will love this feature too. Allan, could you give some example of your wrapper. Thanks, Andres Allan Cassaro escribió: Hi Stephan Bosch, there's any way to make the dovecot deliver agent (with sieve) load a global sieve script before load the user sieve file? I want to create some rules for every one, like: if header contais: IS SPAM, move to SPAM BOX... I made this today with a couple of sed + awk and a wraper for managesieve-login... but, this is definily not the best way to do this... This is possible to do? (Even with change in the code) Regards.
Re: [Dovecot] UIDL question
Please look at http://wiki.dovecot.org/Migration/MailFormat There's a modified version of mb2md.pl there that will keep the existing UIDL info. I look at it, it does indeed generate the ~/Maildir/dovecot-uidlist file with the proper values, however my email client still retrieves a 2nd copy in this test scenario - Download emails from postfix server - Migrate to other server - Download emails from new server (should not happen, due to same uidl), but still does How can i further troubleshoot what the uidl problem is? Sincerely, - Wouter van der Schagt
Re: [Dovecot] UIDL question
On Nov 28, 2008, at 4:54 PM, Wouter van der Schagt wrote: Please look at http://wiki.dovecot.org/Migration/MailFormat There's a modified version of mb2md.pl there that will keep the existing UIDL info. I look at it, it does indeed generate the ~/Maildir/dovecot-uidlist file with the proper values, however my email client still retrieves a 2nd copy in this test scenario - Download emails from postfix server - Migrate to other server - Download emails from new server (should not happen, due to same uidl), but still does How can i further troubleshoot what the uidl problem is? Look at the old UIDLs and look at the new UIDLs. How are they different? My guess is you'll need to set pop3_uidl_format = %v.%u PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] UIDL question
Thank you for the reply, I understand the problem now, however changing the pop3_uidl_format on the target server is not an option since it is a high volume production server. It is currently set to %f because of a previous migration from qmail-pop3d. I don't suppose the pop3_uidl_format setting can be configured on a per popbox basis? Sincerely, - Wouter van der Schagt
Re: [Dovecot] UIDL question
On Nov 28, 2008, at 5:18 PM, Wouter van der Schagt wrote: Thank you for the reply, I understand the problem now, however changing the pop3_uidl_format on the target server is not an option since it is a high volume production server. It is currently set to %f because of a previous migration from qmail-pop3d. I don't suppose the pop3_uidl_format setting can be configured on a per popbox basis? With v1.1 you can add POP3 UIDLs fo dovecot-uidlist. For example if you have mailbox with UIDVALIDITY 1234 and then entries: 123 :file1 124 :file2 You can add their %v.%u UIDL: 123 P1234.123 :file1 124 P1234.124 :file2 i.e. P followed by the UIDL. PGP.sig Description: This is a digitally signed message part
[Dovecot] lda logging directive does'nt work...
Hi all,
I'm using Postfix + Dovecot with system users (/etc/passwd and NIS) +
deliver + cmusieve;
Here are some relevant lines in conf files :
/etc/postfix/main.cf
...
mailbox_command = /usr/lib/dovecot/deliver
...
/etc/dovecot/dovecot.conf
...
protocol lda {
postmaster_address = [EMAIL PROTECTED]
mail_plugins = cmusieve
deliver_log_format = msig=%m : Subject=%s : From=%f :%$
}
...
I just want deliver to log more than default format...like procmail...
but nothing happens...the line 'deliver_log_format' seems to be ignored.
Any idea ?
Re: [Dovecot] UIDL question
With v1.1 you can add POP3 UIDLs fo dovecot-uidlist. For example if you have mailbox with UIDVALIDITY 1234 and then entries: You can add their %v.%u UIDL: 123 P1234.123 :file1 124 P1234.124 :file2 i.e. P followed by the UIDL. That sounds good, however, when i have the following dovecot-uidlist file... 1 1146473021 25449 25360 P1146473021.25360 :1227888318.00.mbox,S=37351:2, 25361 P1146473021.25361 :1227888318.01.mbox,S=35833:2, 25362 P1146473021.25362 :1227888318.02.mbox,S=31107:2, And execute a USER, PASS and UIDL command, i'm getting the %f returned instead of the %v.%u as specified in the dovecot-uidlist file. I'm using the 1.1.4 version of Dovecot. Did i do something wrong? Also the file is updated after i close my telnet session to sometihng that looks like: 3 V1146473021 N25627 1146473021 25449 25538 :1227888318.00.mbox,S=37351:2, 25539 :1227888318.01.mbox,S=35833:2, 25540 :1227888318.02.mbox,S=31107:2, IE: the header is different, if the first is the version number, where can i find more information on the syntax to use in v3? Sincerely, - Wouter van der Schagt
[Dovecot] Dovecot - Vpopmail subdirectories
Hello, I have several thousand domains on a server. I'm doing now migration to Dovecot to replace courier-authlib. Some email accounts are in subdirectories that are automatically created by vpopmail. Example: / var/vpopmail/domains/0/domain.com How do I configure Dovecot? ## # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26.5-sdf103-nfsv4 i686 Gentoo Base System release 1.12.9 ext3 base_dir: /var/run/dovecot/ protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting: Imap ready. first_valid_uid: 89 mail_location: maildir:/var/vpopmail/domains/%d/%n/.maildir auth default: user: vpopmail passdb: driver: vpopmail userdb: driver: static args: uid=89 gid=89 mail=Maildir:/var/vpopmail/domains/%/%d/% n/.maildir ## Best regards, -- Mohamed YACOUBI
Re: [Dovecot] UIDL question
On Sat, 2008-11-29 at 00:15 +0800, Wouter van der Schagt wrote: With v1.1 you can add POP3 UIDLs fo dovecot-uidlist. For example if you have mailbox with UIDVALIDITY 1234 and then entries: You can add their %v.%u UIDL: 123 P1234.123 :file1 124 P1234.124 :file2 i.e. P followed by the UIDL. That sounds good, however, when i have the following dovecot-uidlist file... 1 1146473021 25449 25360 P1146473021.25360 :1227888318.00.mbox,S=37351:2, This mixes v3 syntax with v1 syntax, won't work. 3 V1146473021 N25627 1146473021 25449 This is more like what the header should look like, except for the extra two fields. IE: the header is different, if the first is the version number, where can i find more information on the syntax to use in v3? I'm not sure if I've documented it anywhere. Anyway, the header is simple: 3 Vuidvalidity Nnext-uid Where uidvalidity and next-uid are exactly the same as in v1 (1 uidvalidity next-uid). The records are as you tried to use them originally. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Namespaces and shared folders
giuliano wrote:
I prefer to define everything, even the values that have a default, so
I would define
location (even if mail_location should apply to the default namespace)
and the separator.
Great suggestion. I've changed my namespaces as follows:
namespace private {
separator =
prefix = INBOX.
location = maildir:~/Maildir
inbox = yes
}
namespace public {
separator = /
prefix =
location = maildir:/home/public/shared/Maildir
inbox = no
}
I seem to now have all of my Inbox folders working, and my shared folders
are working for read-only. But when I try to drag a message from my Inbox
into one of the shared folders, I get an Unknown namespace error.
I enabled debug logging and see the following in syslog (and mail.info):
Nov 28 11:41:30 snappy dovecot: imap-login: Login: user=bbell,
method=PLAIN, rip=172.30.1.116, lip=172.30.1.6, TLS
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): Effective uid=1000, gid=1000,
home=/home/bbell
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): Namespace: type=private,
prefix=INBOX., sep=, inbox=yes, hidden=no, subscriptions=no
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): maildir:
data=/home/bbell/Maildir
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): maildir:
root=/home/bbell/Maildir, index=/home/bbell/Maildir, control=, inbox=
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): Namespace: type=public,
prefix=Public/, sep=/, inbox=no, hidden=no, subscriptions=no
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): maildir:
data=/home/public/shared/Maildir
Nov 28 11:41:30 snappy dovecot: IMAP(bbell): maildir:
root=/home/public/shared/Maildir, index=/home/public/shared/Maildir,
control=, inbox=
I'm obviously still doing something wrong. Clues?
--
View this message in context:
http://www.nabble.com/Namespaces-and-shared-folders-tp20727713p20737416.html
Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] UIDL question
On Nov 28, 2008, at 6:43 PM, Wouter van der Schagt wrote: This mixes v3 syntax with v1 syntax, won't work. You're right, after changing it to the v3 syntax i'm getting exactly the same output in both servers after issuing the UIDL command in a telnet session. So far so good. However, a 2nd copy of the files is still being downloaded. Is this because the IP has changed? My steps are. - Download emails from IP.IP.IP.1 - Migrate emails - Confirm manually that UIDL output is the same - If so, download emails from IP.IP.IP.2 And in the last step, im still getting a 2nd copy of all emails. Where is the fault in my reasoning? Do i need to give dovecot a message number that was last downloaded? If the UIDLs are exactly the same, I've no idea why the client would download a duplicate. I haven't heard before that a changed IP would be an issue. Of course that would still be a client-specific issue. Sounds a bit unlikely though. Ccing back to list in case someone else has an idea.. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Namespaces and shared folders
On Nov 28, 2008, at 6:44 PM, bbell2000 wrote:
Great suggestion. I've changed my namespaces as follows:
Rather do it the other way around:
namespace private {
separator =
prefix = INBOX.
prefix =
location = maildir:~/Maildir
inbox = yes
}
namespace public {
separator = /
prefix =
prefix = shared/
Also (assuming v1.1):
subscriptions = no
location = maildir:/home/public/shared/Maildir
inbox = no
}
PGP.sig
Description: This is a digitally signed message part
Re: [Dovecot] Dovecot - Vpopmail subdirectories
Hello, Thank you for this link, but this is not what I want. Dovecot is only used for imap. Currently, authentication works fine, but new fields are created in a subdirectory. Example: /var/vpopmail/domains/0/domain.com Once authenticated, I just want to be in chroot /var/vpopmail/domains/0/domain.com/user and not in /var/vpopmail/domains/domain.com/user I explained that vpopmail which manages the creation of areas and I can not influence the subdirectory. Sincerely, -- Mohamed YACOUBI
Re: [Dovecot] Dovecot - Vpopmail subdirectories
Here is an example of a real configuration file for vpopmail backend,
just adapt for your needs:
dovecot.conf
---
base_dir = /var/run/dovecot/
protocols = imap imaps pop3 pop3s
listen = *
disable_plaintext_auth = no
syslog_facility = mail
ssl_disable = no
ssl_cert_file = /etc/ssl/certs/dovecot.pem
ssl_key_file = /etc/ssl/private/dovecot.pem
login_greeting = Server is ready.
mail_location = maildir:~/Maildir
mail_uid = 89
mail_gid = 89
first_valid_uid = 89
last_valid_uid = 89
first_valid_gid = 89
last_valid_gid = 89
protocol imap {
}
protocol pop3 {
}
auth default {
mechanisms = plain login digest-md5 cram-md5
passdb vpopmail {
}
userdb vpopmail {
}
user = root
}
---
On Fri, Nov 28, 2008 at 2:49 PM, Yacoubi Mohamed [EMAIL PROTECTED] wrote:
Hello,
Thank you for this link, but this is not what I want.
Dovecot is only used for imap.
Currently, authentication works fine, but new fields are created in a
subdirectory.
Example: /var/vpopmail/domains/0/domain.com
Once authenticated, I just want to be in
chroot /var/vpopmail/domains/0/domain.com/user and not
in /var/vpopmail/domains/domain.com/user
You don't need to worry about where vpopmail stored domain's and
user's folders, dovecot will find it.
I explained that vpopmail which manages the creation of areas and I can
not influence the subdirectory.
Sincerely,
--
Mohamed YACOUBI
--
[ ]'s
Aledr - Alexandre
OpenSource Solutions for SmallBusiness Problems
Re: [Dovecot] Namespaces and shared folders
Found the clue I was looking for at http://www.mailinglistarchive.com/dovecot@dovecot.org/msg08557.html. Seems to be working fine now. -- View this message in context: http://www.nabble.com/Namespaces-and-shared-folders-tp20727713p20737738.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] UIDL question
Further investigation revealed that the problem exists with Outlook Express, but not with Mozilla Thunderbird. Thunderbird specifies no new messages. Sincerely, - Wouter van der Schagt
Re: [Dovecot] Sieve and global scripts
Andrés Yacopino schreef: Hi Stephan I will love this feature too. Allan, could you give some example of your wrapper. Thanks, It is on my TODO list. However, doing this correctly is not as trivial as it may seem. There are a few semantical issues to resolve. For instance: should subsequent scripts be called if the one of the earlier ones execute discard? For instance, when a global script throws away the message, why execute the user's script (risking that it inadvertently restores the message)? Jutta Degener took some effort to describe a good way of handling multiple scripts (http://tools.ietf.org/id/draft-degener-sieve-multiscript-00.txt), but this draft document has been stale for quite a while now. Note that the behavior described in that document is completely different from executing multiple scripts in succession using the include extension. I intend to implement it largely as specified in the multiscript document. But even if I implement it to the letter, the necessary changes needed in the interpreter are also not trivial. This feature request has a relatively high priority. But first I need to match cmusieve's functionality (i.e. implement enotify:mailto) and finish all features that are now supported. There are quite a few bits and pieces that need more work. Regards, -- Stephan Bosch [EMAIL PROTECTED]
Re: [Dovecot] ManageSieve and invalid scriptname
Miguel Filho schreef: Hello there, I have been using pysieved and avelsieve and it has been working great. I decided to do test with the ManageSieve patch and got this problem: Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using active sieve script path: ~/.dovecot.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using sieve script storage directory: ~/.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: relative path to sieve storage in active link: .sieve/ Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: Active sieve script symlink /home/admsis/miguel/.dovecot.sieve is broken: invalid scriptname (points to .sieve/phpscript). Well as you can see, a file without the .sieve is not welcome :-( That is correct. I checked the RFC and there is no requirement for a .sieve file extension when considering scriptnames. True, but the ManageSieve server will not use the .sieve extension in the communication with the client. So, as far as the client is concerned, the script is called phpscript. The client can still choose any script name it wants, it is only stored a little differently on the filesystem, which is an implementation concern and has nothing to do with the protocol RFC. http://tools.ietf.org/html/draft-martin-managesieve-12#section-1.6 Is this a misplaced restriction or it really should be enforced for any reason? The .sieve extension is merely added for storage in the file system to distinguish it from other types of files that may reside in the same directory. Otherwise, LISTSCRIPTS would for instance list any file in the storage directory, e.g. also compiled binaries that result from command line execution of sievec. Also note that the .sieve extension itself is not my own invention, because it is specified in section 7 of RFC 5228. As shown recently, this also has a limiting effect on the scope of security holes that involve accessing inappropriate directories. If I had not made this design choice, the recently discovered security hole would have given any user the ability to access any file that is accessible from the uid the server is running with. GETSCRIPT ../victim/mail/inbox.mbox would for instance have been possible with virtual users. So, at all times, only regular files ending with .sieve are considered to be valid sieve scripts. This is also true for the symbolic link that points to the active script. If it points to something else, it is considered to be invalid and no active script is reported in LISTSCRIPTS (a situation that is fixed automatically when a proper script is activated). I hope that this can be tolerable, or I will have to rename a lot of scripts and remove all hardcoded phpscript strings from avelsieve :-( Good news and bad news here. The good news is that you will not need to change Avelsieve in any way. The ManageSieve script name phpscript is implicitly stored as phpscript.sieve. And the other way around: if a script file called phpscript.sieve resides in the sieve storage directory it is reported to Avelsieve as phpscript. That's where the bad news comes in: you still need to rename all existing script files from phpscript to phpscript.sieve for the Dovecot ManageSieve server to notice them. After that, you can reactivate all scripts (Avelsieve should do this implicitly) and all should work. Hmm, maybe I should write a short migration manual. Regards, -- Stephan Bosch [EMAIL PROTECTED]
Re: [Dovecot] Dovecot - Vpopmail subdirectories
Okay, I changed my setup and it works much better. Thank you:) -- Mohamed YACOUBI - Euro Web SARL - http://www.euro-web.fr Location de serveurs dédiés infogérés Infogérance et consulting Hébergement mutualisé sur mesure Serveurs de jeux
Re: [Dovecot] Dovecot as proxy for M$ Exchange mailboxes
How is this proxying Exchange? On 28 Nov 2008, at 07:21, Axel Schmalowsky wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, is there a way to use dovecot as proxy for m$ exchange mailboxes? Currently, our clients not only can login to their mailboxes with their e-mail address but also with their accountid. Both the clients e-mail address and accountid are stored in ldap. Now I need a way to let dovecot rewriting the client's accountid to the respective e-mail address. Is this possible with the proxy-feature of dovecot? Any hints would be appreciated. - -- Freundliche Grüße / Kind regards Axel Schmalowsky Platform Engineer ___ domainfactory GmbH Oskar-Messter-Str. 33 85737 Ismaning Germany Telefon: +49 (0)89 / 55266-356 Telefax: +49 (0)89 / 55266-222 E-Mail: [EMAIL PROTECTED] Internet: www.df.eu Registergericht: Amtsgericht München HRB 150294, Geschäftsführer Tobias Marburg, Jochen Tuchbreiter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJL+JKsuqpduCyZM0RAoFUAJ9mPbv5eI5xP54YhwlmOs40F1RxDQCgir5l jCdaNeXKO8FnOCxaKSI7S4E= =m5WN -END PGP SIGNATURE-
Re: [Dovecot] dovecot 1.1.3 + antispam plugin issues
On Fri, 2008-11-28 at 15:03 +0100, Marcin Rzepecki wrote: Thu, Nov 27, 2008 at 08:28:54PM +0100, Jakob Curdes wrote: HMMM. Same here. DC 1.1.5 with mbox. As I said it affects DC=1.1.3 Maybe it affects mbox? I'm using 1.1.3 now with maildir and have no trouble. Oops, and I tried half of last night to get the mail backend working ... I know something about that ;) Commenting out following code in mbox_read_from_line function (in src/lib-storage/index/mbox/istream-raw-mbox.c) helped and plugin was [...] So that's code from dovecot itself. If that really helped (did you check that the messages really were trained by dspam?) there is some problem between the antispam plugin and the main code. But I think the part you commented out is only the end of the story. Can it be that there is some counting problem when the plugin looks for the inserted message? Timo? Yes, after patching it works good and trains dspam correctly. No i'm still using it with 1.1.3, I've tried to debug newer versions but without success. After commenting this piece of code, dovecot seems to totally ignore plugin when moving messages between Inbox/SPAM ;) I think we really need to ask Timo. Timo? The issue seems to be that getting a given header from a mail fails under certain circumstances. johannes signature.asc Description: This is a digitally signed message part
