- dovecot - dovecot.org

[Dovecot] Mail deduplication
by Tim Groeneveld 15 May '13

15 May '13

Hi Guys, I am wondering about mail deduplication. I am looking into the possibility of seperating out all of the message bodies with multiple parts inside mail that is recived from `dovecot` and hashing them all. The idea is that by hashing all of the parts inside the email, I will be able to ensure that each part of the email will only be saved once. This means that attachments & common parts of the body will only be saved once inside the storage. How achievable would this be with the current state of dovecot? Would it even be worth doing? Thanks, Tim

7 19

[Dovecot] quota and dict
by Jeff Gustafson 15 May '13

15 May '13

I have a question about using dict and quotas. I want dovecot to send quota queries to a custom dict server over a socket. I'm doing this because I can't do group quotas based on domain since a customer can have each of their users associated with different domains under a single account. I need to lookup the account ID and group based on that. I'm worried putting everything in mysql will cause way too many writes and lower the performance of our mysql cluster. I have having a little trouble connecting all the dots in the config file. In the userdb example, there is an 'args' parameter that allows a file to specify a uri. I don't see how to do that for dict. I only see file, mysql, and postgresql. Shouldn't I be able to use a dictionary proxy to attach any custom program to a quota dict socket? Tell the quota plug to proxy quota which then points to a socket: plugin { quota = dict:User quota::proxy::quota } dict { quota = proxy:/tmp/test-socket } or should it be: plugin { quota = dict:User quota::proxy:/tmp/test-socket } Neither one create a socket in /tmp. It seems like this should be possible, but I don't see an obvious way to do it. ...Jeff

2 1

[Dovecot] Released Pigeonhole v0.4.0 for Dovecot v2.2.1.
by Stephan Bosch 15 May '13

15 May '13

Hello Dovecot users, I finally release the first version of Pigeonhole v0.4 for Dovecot v2.2. The main reason for the delay was that some unexpected (design) problems occurred with the new doveadm-sieve plugin, which allows synchronizing sieve scripts using doveadm sync. One important change is that I incorporated the extprograms plugin into the main Pigeonhole release. With this plugin it is possible to execute administrator-controlled external programs (shell scripts) from the Sieve interpreter, e.g. for special message delivery, filtering and string manipulation. The list of new features is not that impressive. I've been working on IMAP URLAUTH, IMAP CATENATE and HTTP support for Dovecot. Currently, I'm building an SMTP submission proxy server. After all that I plan to spend more time on Sieve development. One of the most important issues on my list is implementing support for using alternative types of storage (e.g. a database) for Sieve scripts, rather than only a filesystem directory as it is now. Changelog v0.4.0: + Added doveadm-sieve plugin that provides the possibility to sync Sieve scripts using doveadm sync along with the user's mailboxes. + Added the Sieve extprograms plugin to the main Pigeonhole package. It is still a plugin, but it is now included so that a separate compile is no longer necessary and distributors are likely to include it. The extprograms plugin provides Sieve language extensions that allows executing (administrator-controlled) external programs for message delivery, message filtering and string manipulation. Refer to doc/plugins/sieve_extprograms.txt for more information. + Added debug message showing Pigeonhole version at initialization. Makes it very clear that the plugin is properly loaded. + Finished implementation of the Sieve include extension. It should now fully conform to RFC 6609. The main addition is the new :optional tag which makes the include command ignore missing included scripts without an error. + Finished implementation of the Sieve environment extension as much as possible. Environment items "location", "phase" and "domain" now also return a usable value. The release is available as follows: http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.0.tar.gz http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.0.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

10 27

[Dovecot] 2.2.x autobuilds: Debian Stable now Wheezy, which pool for 2.2.x?
by Ron Leach 15 May '13

15 May '13

List, good evening, just installed a new Debian Stable (Wheezy). The Debian Stable repositories now include Dovecot 2.1.7 as standard. I haven't installed that because I wanted to try 2.2.x on this new clean install but unsure which 'pool' to use in the xi.rename-it.nl repository of autobuilds. http://xi.rename-it.nl/debian/pool/ Wheezy became Stable on May 5, just a few days ago. I'm not sure whether to still follow the advice in the wiki for obtaining 2.2.x for Wheezy, which (understandably, because the new Debian Stable release has been so very recent) continues to refer to Wheezy as 'testing'. http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages Presumably, the packages in the 'testing' autobuild system pick up Debian's 'testing' pool libraries (or assume them to exist) and these may no longer be the ones needed for Wheezy because Wheezy is 'Stable', in Debian-speak. Does anyone know, for sure, which autobuild pool to now use for 2.2.x for Wheezy? http://xi.rename-it.nl/debian/pool/stable-auto/ or http://xi.rename-it.nl/debian/pool/testing-auto/ 2.2.x in 'stable-auto' doesn't seem to have changed since before Wheezy was released, whereas 2.2.x has changed in 'testing-auto', and I'm not sure what to make of that. Stephan does suggest that queries be directly written to him, but I posted here because I thought I might not be the only person who was unsure. I'd be grateful for any advice, regards, Ron

3 5

[Dovecot] Idea: POP3 deletion as a flag
by Timo Sirainen 14 May '13

14 May '13

GMail doesn't delete mails when POP3 client issues a DELE command for it. Instead they just become invisible for future POP3 sessions, but they still exist for IMAP/webmail. The same could be implemented pretty easily for Dovecot: - Add a new setting to enable this: pop3_deleted_flag = $POP3Deleted - When DELEting a message, add this flag to the message. - When listing messages, skip all messages that have this flag. - Also hide this flag from IMAP clients(?) Thoughts? Probably 20 lines of new code.

18 44

[Dovecot] ot: mirroring/archiving to a Mac?
by voytek＠sbt.net.au 14 May '13

14 May '13

I have Doveot 2.1.1 on Centos, all's well user mails are kept for 60 days, then, 'aged off' (deleted) a Mac user with two domains and two dozen users asked me: can I set a mail server on my home Mac server, and, 'mirror' the real mail server mailboxes so than I can have an offline mail archive for ever ? I know very little about Macs, can I setup dovceot on Mac? any tips/suggestions/howtos for mirroring/archiving as so?

5 6

[Dovecot] Pigeonhole: Typo in 20-managesieve.conf
by Gedalya 12 May '13

12 May '13

Line 33: #process_count = 1024 Probably you mean process_limit

2 1

[Dovecot] Any way to let dovecot block pop3 attempts?
by Steve Campbell 12 May '13

12 May '13

Is there a way using dovecot facilities to block an IP from attempting POP3 connections (similar to the sendmail access file for smtp connections)? I usually do this at my border firewall, but if there's a quick and dirty way in dovecot to do this, it'd make life a little simpler. Thanks steve campbell

7 10

[Dovecot] Problem with LDA reject message
by Davide 11 May '13

11 May '13

Hi to all, i have a problem with LDA when users are quota-full. My setup is Vpopmail + dovecot + lda; if i send a messagge internally to a user with quota full i receive correctly a messagge but in the header ( i attacch a snip) From - Fri May 10 14:42:27 2013 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <"<>"@mail.cgilfe.it> i receive this strange Return-Path. I the messagge is sent outside other servers reply with this messagge: Subject: failure notice Hi. This is the qmail-send program at mail.cgilfe.it. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <Roberta.Luzzi(a)filcams.cgil.it>: Connected to 80.207.169.234 but sender was rejected. Remote host said: 501 Address Syntax Error in <"<>"@mail.cgilfe.it> this is my .qmail-default file: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/dovecot-lda -d $EXT@$USER | /home/vpopmail/bin/vdelivermail "" bounce-no-mailbox Thanks in advance. -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

Re: [Dovecot] Any way to let dovecot block pop3 attempts?
by Joseph Tam 11 May '13

11 May '13

Steve Campbell writes: > I use Centos and the default dovecot RPM. I seem to recall there was a > way to determine if dovecot was built with "--with-libwrap". Can anyone > shed light on how to determine this, please? Maybe dovecot --build-options Or you can just test it directly by denying a connection to a test host. Joseph Tam <jtam.home(a)gmail.com>

1 0