[Dovecot] Dovecot / Sieve
Hi, As the new Sieve implementation is using a gratefully stolen copy of deliver.c from dovecot (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copyingchanging it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot in advance, Joan
Re: [Dovecot] Dovecot / Sieve
Joan wrote: As the new Sieve implementation is using a gratefully stolen copy of deliver.c from dovecot (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copyingchanging it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot in advance, I guess that's why it is a FIXME. :) So, point 1 is planned, but I have no idea when Timo is going to make a common interface for this. About point 2, if you mean full integration of Sieve in the main Dovecot tree, I don't think so. I guess it will always be a separately maintained plugin. BTW, why do you bring this up? Did you encounter problems? Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] Dovecot / Sieve
thanks Stefan for the reply. Yes, I have problems, as the gratefully stolen copy in Sieve is not synchronized with the Dovecot one, so the current new Sieve (0.15) does not compile anymore with the current Mercurial/Hg of Dovecot. That is why I was raising those 2 points. Stephan Bosch wrote: Joan wrote: As the new Sieve implementation is using a gratefully stolen copy of deliver.c from dovecot (i.e. a dirty code in mail-raw.c), would it be possible for the Sieve piece 1 - to be using files from dovecot directly rather than copyingchanging it (which is very bad for maintenance) 2 - to be incorporated in the hg/mercurial tree of dovecot ? Thanks a lot in advance, I guess that's why it is a FIXME. :) So, point 1 is planned, but I have no idea when Timo is going to make a common interface for this. About point 2, if you mean full integration of Sieve in the main Dovecot tree, I don't think so. I guess it will always be a separately maintained plugin. BTW, why do you bring this up? Did you encounter problems? Regards,
Re: [Dovecot] antispam plugin and MUA-Junk folders
Many MUAs tag SPAM themselves and move SPAM to a junk folder (Thunderbird uses Junk). It is said to not automatically train these mails, but let have an human revise them. I really think you should turn that off. When it eventually does classify email, you will run into problems because you have two spam filters fighting over control. Currently, I have configured those folders as trash folders for antispam, which means that those messages are essentially lost, because a move into a spam folder will not train them. - The current antispam plugin ignores moves in and out of trash folders completely. I wonder why the move trash - SPAM is ignored? Mostly because you could hit undelete and afaiu it would put them back? I haven't ever really used trash folders, somebody else requested support for those. johannes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot / Sieve
Joan schreef: thanks Stefan for the reply. Yes, I have problems, as the gratefully stolen copy in Sieve is not synchronized with the Dovecot one, so the current new Sieve (0.15) does not compile anymore with the current Mercurial/Hg of Dovecot. That is why I was raising those 2 points. If you are using the Hg version of Dovecot it is always advisable to use the Hg version of Sieve as well: http://hg.rename-it.nl/dovecot-libsieve/ I have a server that regularly builds the various Dovecot(-Sieve) Hg repositories into a Debian package. So, when Sieve does not compile anymore, I'll know within the hour and fix it asap (until then I get bugged with failure e-mails). Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] Dovecot / Sieve
yes in deed. then it worth a note or a link on the download page of dovecot ;-) Stephan Bosch wrote: Joan schreef: thanks Stefan for the reply. Yes, I have problems, as the gratefully stolen copy in Sieve is not synchronized with the Dovecot one, so the current new Sieve (0.15) does not compile anymore with the current Mercurial/Hg of Dovecot. That is why I was raising those 2 points. If you are using the Hg version of Dovecot it is always advisable to use the Hg version of Sieve as well: http://hg.rename-it.nl/dovecot-libsieve/ I have a server that regularly builds the various Dovecot(-Sieve) Hg repositories into a Debian package. So, when Sieve does not compile anymore, I'll know within the hour and fix it asap (until then I get bugged with failure e-mails). Regards,
Re: [Dovecot] Missing IMAP folders after Server reboot
Hi, That's what I'm looking for at the moment. Thanks, Eoin -Original Message- From: dovecot-bounces+ekennedy=sherlings@dovecot.org [mailto:dovecot-bounces+ekennedy=sherlings@dovecot.org] On Behalf Of Scott Silva Sent: 29 May 2009 23:13 To: dovecot@dovecot.org Subject: Re: [Dovecot] Missing IMAP folders after Server reboot on 5-29-2009 6:51 AM Eoin Kennedy spake the following: Hi, Here is the situation, I hope somebody can help me. Our Email server running ubuntu 8.04.1 and dovecot 1.0.10 rebooted, and when it came back up the dovecot config had changed. Prior to the reboot, users stored their emails and folders in /var/mail/~username. Then the config became /var/mail/username for the main Inbox and /home/~username/mail for Folders. Now, none of the folders that users had created in their IMAP account are visible, and their contents are not in the main Inbox file. For example, the Drafts folder was there prior to the reboot, and now it had to be created in /home/username afterwards. These folders were not subfolders of the Inbox, but of the main IMAP root. All users were running Thunderbird as their client. Can they be recovered? I doubt that your mail is gone, somebody just changed where dovecot looks for it. Do you have a backup of your old config file? - Sherling Sons Ltd, Jamestown Road, Inchicore, Dublin 8, Ireland. Company Reg No. 9294 Website: www.sherlingsteel.com
Re: [Dovecot] Missing IMAP folders after Server reboot
Did you try looking for the folders by connecting to IMAP using command line. telnet servername 143 a1 login username pass a2 list * Check if you could see anything.
Re: [Dovecot] Missing IMAP folders after Server reboot
Did you try looking for the folders by connecting to IMAP using command line. telnet servername 143 a1 login username pass a2 list * Check if you could see anything.
Re: [Dovecot] Expire-Plugin segmentation fault (Re: Can expire-tool skip folders with expire time in future errors?)
On Fri, 2009-05-29 at 17:26 +0200, Ralph Seichter wrote:
Timo Sirainen wrote:
Anyway it's not an error. It just means that all the rest of the
mailboxes have future timestamps, and expire-tool has finished its work.
I upgraded to Dovecot 1.1.15, but expire still gives me trouble. I keep
seeing the following error repeatedly now:
dict: db(secondary, ): unable to allocate space from the buffer cache
dict: sdb.open() failed: Cannot allocate memory
Does the attached patch help? If not, increase the 1024*1024 to a larger
value.
diff -r 6e42cd6ae8a7 src/lib-dict/dict-db.c
--- a/src/lib-dict/dict-db.c Thu May 28 14:42:21 2009 -0400
+++ b/src/lib-dict/dict-db.c Sun May 31 19:20:39 2009 -0400
@@ -108,6 +108,7 @@
dict-sdb-set_errfile(dict-sdb, stderr);
dict-sdb-set_errpfx(dict-sdb,
p_strdup_printf(dict-pool, db(secondary, %s), username));
+ dict-sdb-set_cachesize(dict-sdb, 0, 1024*1024, 1);
if ((ret = dict-pdb-open(dict-pdb, dict-tid, uri, NULL,
DB_BTREE, DB_CREATE, 0)) != 0) {
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Assertion failure in maildir-mail.c for gzipped maildir files in 1.1.15
On Fri, 2009-05-29 at 02:11 -0400, David S. Madole wrote: Panic: imap: user=x, Status: file maildir-mail.c: line 85 (maildir_mail_stat): assertion failed: (fd != -1) Thanks, this fixes it: http://hg.dovecot.org/dovecot-1.1/rev/140bd7523890 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Expire Plug-in stopped
On Thu, 2009-05-21 at 17:15 -0500, Matt Rude wrote: When I run the plug-in with the test flag, I receive the following message: /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Info: a...@example.com/Trash: stop, expire time in future: 1242953758 All messages were deleted before the expire plug-in was added. Then they're not tracked and you'll need to wait until the first post-plugin-load message expires. That's 1242953758 = May 31, so they should expire today. Also, when I look up this error on google, I see other peaple who's output shows a real date (not 1242953758), how do I know when this date is? Looks like I committed that change only to v1.1 and forgot to add it to v1.2. Fixed now: http://hg.dovecot.org/dovecot-1.2/rev/f144ef760714 You can also use: date -u -d 1970-01-01 1242953758 seconds signature.asc Description: This is a digitally signed message part
Re: [Dovecot] imap cann't read the mail that foxmail send
On Tue, 2009-05-19 at 10:02 +0800, wallace0615 wrote: I compared the data that using the two way to send, and found the reason: use outlook and foxmail: at the beginning of the eamil data is From zxjteacher_SP_LZU zxjteacher_sp_...@myserver; and if I telnet host 25 to send the mail: at the beginning of the eamil data is From zxjteacher_sp_...@myserver, so I delete zxjteacher_SP_LZU, dovecot read it out. What exactly do you mean by the above? Do you mean the mbox's From line separator is different with them or that you have the mbox From line and also the above line? Copypaste a full example? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
On Mon, 2009-05-18 at 21:23 +0200, e-frog wrote:
Timo Sirainen wrote:
On Sun, 2009-02-22 at 12:49 +0100, e-frog wrote:
Trying 1.2.beta1 with expire plugin currently:
When I set mail_location = maildir:~/.maildir the expire plugin doesn't
delete messages.
Should be fixed in hg now.
My guess is that mail_location is not respected by expire-tool for some
reason and in second
case mailbox auto-detection makes it working?
Yes.
Thanks Timo! It works now as long as there is no namespace for the virtual
plugin defined:
http://hg.dovecot.org/dovecot-1.2/rev/6fd725b94504
http://hg.dovecot.org/dovecot-1.2/rev/531083e6e84a
Then put mail_plugins setting outside protocol {}.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Can expire-tool skip folders with expire time in future errors?
On Tue, 2009-05-26 at 13:03 +0200, Ralph Seichter wrote: I have folders containing messages which have been moved there -- either by the sieve plugin or manually in Thunderbird -- days or even weeks ago. The messages are not removed even with an expire time of somefolder 1. Were the messages moved there before expire plugin was loaded? Those aren't tracked. Also if you change the expire time, it won't change immediately because the old value was already used to set the next expire stamp in the database. What can I do to find out why some folders don't seem to be processed by the expire plugin? Is there any debugging/logging data I can look into? I think it works, but you'll just have to wait for a few weeks to get the database up to date.. signature.asc Description: This is a digitally signed message part
[Dovecot] v1.1.16 released
http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz.sig Fixes a couple of bugs in v1.1.15's changes. Hopefully the last v1.1 release before v1.2.0. - v1.1.15 could have crashed if mailbox-closing command was pipelined after a mailbox-accessing command. - v1.1.15's zlib plugin may have caused crashes when fetching INTERNALDATE. - Maildir: If messages had been deleted externally from new/ directory and mailbox was opened with EXAMINE, Dovecot didn't immediately notice that the messages were deleted. - If message body started with a space, some operations could have assert-crashed. signature.asc Description: This is a digitally signed message part
