- dovecot - dovecot.org

[Dovecot] IMAP client dependence on dovecot mail storage fromat?
by Kārlis Repsons 09 Jan '10

09 Jan '10

Hi, After setting up a maildir tree with :LAYOUT=fs and accessing it with KMail and Thunderbird, various mail client-specific problems appeared, but, as I didn't try with maildir++, I would like to confirm here: does that matter for an IMAP client much if I store mail on server as ":LAYOUT=fs" or maildir++? Can it see differences? I would like to think, that IMAP protocol should provide for all transactions in a standard way and its dovecot's/server's sole business how it stores mail locally. However... These results seem not very good: KMail: try creating a folder "sub" in "parrent" and you'll get "parrent.sub" along with "parrent" on server side. There, however, are no problems with Latvian unicode chars. Thunderbird: it can create a new folder in "parrent" as desired, but it can't display Latvian unicode chars (being such at server side) on client, while, if I try creating a new folder with Thunderbird with these chars, on server it will look somewhat like base64! So I'm really confused. All together these things are pretty frustrating, sure, but I'd like to understand whats the real problem here!

1 1

Re: [Dovecot] Oracle SQL driver
by Alexander Bukharov 09 Jan '10

09 Jan '10

Added free() for the used VARCHAR pointer.

1 0

[Dovecot] Sieve > Pigeonhole > external storage with LDAP or other data source available to dovecot
by Martin F. Foster 09 Jan '10

09 Jan '10

I am looking at porting and generalizing an old in-house patch that I'm using for the CMU Sieve plugin. It allows sieve script to test & lookup arguments from LDAP. Before getting too involved in this, I'd like to discuss my goals here in the hopes that someone else also thinks this would be useful. Many heads may make better design? Goal: ------ Allows scripts which are still stored on the filesystem to lookup parameters stored in an LDAP directory. Useful if you provide a global sieve script to implement functions such as "vacation", forwarding to small groups (not a MLM), wish to toggle whether a message is kept in the mailbox after being forwarded, etc. <example> # determine if we always auto-respond, or if we respond with a more vacation-ish setting of every 30d # # sample LDAP entry: # uid: testuser(a)domain.com # mailResponderMode: vacation # mailResponderText: "I'm on vacation, far far from the Internet" (base64 encoded string...) # "always" reply mode, sanitized to once a day if ldap "mailResponderMode" "reply" { vacation :days 1 "ldap@mailResponderText"; } # traditional "vacation" mode, say reply once every 30d if ldap "mailResponderMode" "vacation" { vacation :days 30 "ldap@mailResponderText"; } </example> This introduces: 1. a new command "ldap", to lookup attributes and their values in an LDAP directory using the user's context 2. an extention to the vacation command that looks up the vacation reply text that is triggered by supplying "ldap@ldapAttribute" as the text. 3. other actions not shown above which extends redirect and a few other commands to lookup data from LDAP Related work: 1. Pigeonhole low priority TODO would like to implement alternate script storage, eg: LDAP & SQL. I'm not immediately interested in alternate types of script storage, but for what I want to acheive, I need to sanely access at least an LDAP directory. 2. draft-ietf-sieve-external-lists (http://tools.ietf.org/html/draft-ietf-sieve-external-lists-01) proposes a mechanism to pull mailing list addresses from external storage mechanisms such as LDAP, ACAP or relational databases. I'm interested in this, but would like to extend this functionality beyond just lists as the example above demonstrates. 3. there are security and resource consumption issues with doing this, suggesting that limits should be set, or the use may have to be restricted to global scripts eg: sieve_before or sieve_after The question: - do others on this list see value in the functionality described above? If there's some consensus that this would be useful, I'll flesh out howI think a generalized version of this old patch may behave, then (!) work on an implementation as a plugin to dovecot's sieve. cheers, -Martin Foster martin_foster(a)pacific.net.au martin.foster(a)pacnet.com

4 3

[Dovecot] stripping attachments
by Frank Cusack 08 Jan '10

08 Jan '10

there is a windows tool that strips attachments from emails on the server. i think it works for exchange. is there a tool or a way to do this for imap? i don't mean a mail filter that would strip them before the user sees them, i mean that the user could actively cooperate to reduce mail storage space, yet keep the original email on the server sans attachment.

2 1

[Dovecot] dovecot-1.2-sieve-0.1.3 compile error
by El Bundy 08 Jan '10

08 Jan '10

Hi, when I try to compile dovecot-1.2-sieve-0.1.3 on my NAS I get the error below and I have no idea why and who to fix this. I have a Qnap TS239pro NAS with a Intel Atom CPU running Linux. I installed and configured the ipkg dovecot packet (1.2.beta1). Getting mails via fetchmail and send them with deliver to the IMAP. Not I want to include sieve to filter mails as this is not part of the packet I need to compile this by my own. I installed all needed packets and download dovecot-1.2.beta1 and dovecot-1.2-sieve-0.1.3. I do configure and make for dovecot and ./configure --with-dovecot=../dovecot-1.2.beta1 and make for dovecot-1.2-sieve-0.1.3. All run without any problem till the error below. Any idea how to fix this is welcome. /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 -o libsieve.la rfc2822.lo sieve-limits.lo sieve-message.lo sieve-lexer.lo sieve-script.lo sieve-ast.lo sieve-binary.lo sieve-parser.lo sieve-address.lo sieve-validator.lo sieve-generator.lo sieve-interpreter.lo sieve-code-dumper.lo sieve-binary-dumper.lo sieve-result.lo sieve-error.lo sieve-objects.lo sieve-comparators.lo sieve-match-types.lo sieve-address-parts.lo sieve-match.lo sieve-commands.lo sieve-code.lo sieve-actions.lo sieve-extensions.lo cmp-i-octet.lo cmp-i-ascii-casemap.lo mcht-is.lo mcht-contains.lo mcht-matches.lo tst-truefalse.lo tst-not.lo tst-anyof.lo tst-allof.lo tst-address.lo tst-header.lo tst-exists.lo tst-size.lo cmd-require.lo cmd-stop.lo cmd-if.lo cmd-keep.lo cmd-redirect.lo cmd-discard.lo ext-fileinto.lo ext-reject.lo ext-envelope.lo ext-encoded-character.lo sieve.lo ./plugins/vacation/libsieve_ext_vacation.la ./plugins/subaddress/libsieve_ext_subaddress.la ./plugins/comparator-i-ascii-numeric/libsieve_ext_comparator-i-ascii-numeric.la ./plugins/relational/libsieve_ext_relational.la ./plugins/regex/libsieve_ext_regex.la ./plugins/copy/libsieve_ext_copy.la ./plugins/imap4flags/libsieve_ext_imap4flags.la ./plugins/include/libsieve_ext_include.la ./plugins/body/libsieve_ext_body.la ./plugins/variables/libsieve_ext_variables.la ./plugins/enotify/libsieve_ext_enotify.la rm -fr .libs/libsieve.lax mkdir .libs/libsieve.lax rm -fr .libs/libsieve.lax/libsieve_ext_vacation.a mkdir .libs/libsieve.lax/libsieve_ext_vacation.a (cd .libs/libsieve.lax/libsieve_ext_vacation.a && ar x /opt/qnap_install/dovecot-1.2-sieve-0.1.3/src/lib-sieve/./plugins/vacation/.libs/libsieve_ext_vacation.a) libtool: link: ERROR: object name conflicts: .libs/libsieve.lax/libsieve_ext_vacation.a//opt/qnap_install/dovecot-1.2-sieve-0.1.3/src/lib-sieve/./plugins/vacation/.libs/libsieve_ext_vacation.a make[4]: *** [libsieve.la] Error 1 make[4]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/qnap_install/dovecot-1.2-sieve-0.1.3/src/lib-sieve' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/qnap_install/dovecot-1.2-sieve-0.1.3/src/lib-sieve' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/qnap_install/dovecot-1.2-sieve-0.1.3/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/share/MD0_DATA/.qpkg/Optware/qnap_install/dovecot-1.2-sieve-0.1.3' make: *** [all] Error 2 /opt/ is a link to /share/MD0_DATA/.qpkg/Optware/ Bye El -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Dovecot] shared namespace problem
by Patrick Kaiser 08 Jan '10

08 Jan '10

Hi List, I've got a problem, setting up shared namespaces. I am trying to setup a Mailbox (Maildir) which is accessible for some users. (For example mailbox "sales" and only sales representive have access to it) Mailboxes can be found under /var/vmail/<username>, whereas <username> looks like foo.bar or peter.griffin ;) Now, if I connect via telnet, loggin in as foo.bar and run a03 SETACL foobar peter.griffin lwrxk everything seems fine. Under /var/vmail/foo.bar is a acl-file dovecot-acl-list Under /var/vmail/foo.bar/.foobar is a acl-file dovecot-acl The contents looks ok. Also there is a generated file /var/vmail/shared-mailboxes.db. But if i now loggin in as peter.griffin and setup command a03 LIST "" "*" or a03 LIST "" "#shared" I can not find any shared mailbox. Above you can find my actual configuration. I've tried several versions of location: under shared namespace, but without success. Hope someone has a clue and point me into the right direction. Thanks for your help. Friendly Regards, Patrick dovecot -n : # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian squeeze/sid ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_uid: 1001 mail_gid: 1001 mail_location: maildir:/var/vmail/%n mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): acl imap_acl mail_plugins(imap): acl imap_acl mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_log_max_lines_per_sec: 0 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: shared/%%u location: maildir:/var/vmail/%%u/shared:INDEX=/var/vmail/%%u/shared list: children lda: postmaster_address: postmaster(a)example.com hostname: mail.cronon-ag.de mail_plugins: acl mail_plugin_dir: /usr/lib/dovecot/modules/lda sendmail_path: /usr/lib/sendmail auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login digest-md5 passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: acl: vfile acl_shared_dict: file:/var/vmail/shared-mailboxes.db -- Name : Patrick Kaiser Email : patrick.kaiser(a)argonius.de Website : http://www.argonius.de GPG Key : http://www.argonius.de/key.pub

1 0

[Dovecot] Dovecot Sieve: Vacation Recipient
by Lukas Kolbe 08 Jan '10

08 Jan '10

Hi! I tried to use the sieve vacation plugin, but we're facing a little problem: our user's addresses are <uid>@<domain>, and if they want to use imap and sieve, they can have a forward to <uid>@imap.<domain>. The return-path, and hence the address the vacation message is sent to, is then <uid>@<domain> and not the original sender of the message. Is there any way to circumvent this? Sending a vacation back to oneself doesn't really make sense here :) Oh, and happy new year and thank you all for this great piece of software! -- Lukas

2 2

Re: [Dovecot] auth, partially resolved
by Steffen Kaiser 08 Jan '10

08 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 7 Jan 2010, Spyros Tsiolis wrote: >> signed certificate: >>> >> /C=GR/ST=Kerkyra/L=Kerkyra/O=Tourist Enterprizes/OU=IMAP >>> >> server/CN=webmail.domain.gr/emailAddress=postmaster(a)webmail.domain.gr >> >> You access the cert of webmail.domain.gr via a host named >> localhost. >> If Horde runs on the same host, just disable SSL :-) > > . . .because SSL is for remote hosts (clients) on the network anyway > right ? Well, there might be scenarios, when a local user other than root may sniff the connection on localhost, but I think you have no such one. So to encrypt a connection from localhost to localhost is a waste of ressources. In case of Dovecot you'll need one extra file descriptior (and depending on your settings one extra process as well), plus the CPU time to actually do the encryption. > Yeah. The certificate is there. Under "/etc/ssl/certs". > I was thinking that maybe because the system (and the certificate > issuer, horde and dovecot are on the same box. You ask me somewhere > about that) is all-in-one, I need to import the certificate somewhere ? see above for the reason. > The dovecot wiki says that importing the certificate is only applicable > to the client-side (evolution, thunderbird and so on). The webmail-frontend _is_ your client in the view of Dovecot. But since the cert is in /etc/ssl/certs, it should work, but if you validate the cert, the webmail may bark, because you access the SSL-cert with the CN "webmail.domain.gr" by another name "localhost". This is a sign of a man-in-the-middle attack, actually. BTW: Do your SSL IMAP/POP clients also use the name "webmail.domain.gr"? Otherwise they will get a warning as well, maybe each time they connect. Regards, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBS0bzDb+Vh58GPL/cAQJx9Af/egq1HW/M92tmivrAcBFCvyO6pL6cZcwr PDVfWTsQsHAhWOYNTfAuAe0kouFTnjCpGcTXKPAA3VCWvRWR37/RGseeAmKfRmEW BYfKPrkf6ltq+hfREi81rHIme0xIry5UG1oB2/1WfPHmWTckVWNRL0aRIZGM+ZR5 v40MuesoaMyY0EngEnaIfDbswG+vNWF60XZ71knAfVtl12LOe+twzLDEJ3M13SaV zw7qOGj4iUtZgML4LC042dGuF22yKAXElwp26oZVhk522J1VtdMuhi9Bma7YnVfU CfhUWqa3q+jL60fAKhWCP8IoRxxYJ/vsrWFjZaEamjCMCLx3FgeebQ== =IS0t -----END PGP SIGNATURE-----

1 0

[Dovecot] First time Dovecot user, really impressed so far. What is best IMAP enabled webmail package to go with Dovecot?
by Stan Hoeppner 08 Jan '10

08 Jan '10

Greetings everyone, I'm new to the list as of today. I just installed Dovecot a couple of days ago for the first time, Debian Lenny Dovecot v1.0.15-2.3. So far I'm pretty impressed. I'm using mbox format with Dovecot auto-deciding to place mail in user home directories, which is great. It works very well with the Win32 Thunderbird 3 client over a small basic 100FDX switched net. I've got one list mail folder with 10,600 messages and server side body searching that folder via T-Bird is very quick, on the order of 5 seconds. It would probably be quicker if Dovecot threaded the search to use both CPUs, but pegging just the one CPU the search is still very darn quick. And this is on a dual P2-550 class machine with only 384MB RAM and a single 500GB 7200RPM SATA drive. I'd like to install a webmail package on the same host. I used Squirrelmail for this purpose many years ago and I wasn't wholly impressed with the user interface. I'm also not impressed by the fact that I regularly receive spam from compromised Squirrelmail hosts/accounts. I really like the look/feel of the Scalix Web Access AJAX based interface, but I can't/won't use Scalix as it's not supported on Debian, it has more features than I need, and the system requirements are a bit steep. So, what's the best FOSS IMAP enabled web mail front end with a modern look/feel? I'd like to run it on lighttpd, which I'm already using, not apache. Thanks in advance for any advice. My apologies if my first post is a little OT, but I figured there's probably no better place to ask about the best webmail front end for Dovecot than here. -- Stan

14 24

[Dovecot] Does Dovecot Sieve plug-in support Dovecot 2.0?
by wenjie zheng 08 Jan '10

08 Jan '10

Does Dovecot Sieve plug-in support Dovecot 2.0? We have a few servers running Dovecot 2.0 beta1, but the Dovecot Sieve plug-in (version 0.1.4) won't compile against it. Is this on the Sieve TODO list? If so, when do you see it will happen? Thanks Wenjie

4 10