Re: [Dovecot] purge maildir folder after sa-learn
Hi, 2010/5/28 Phil Howard ttip...@gmail.com: So basically, just moving mail files out (to a learn queue or whatever), from either new or cur is safe for Dovecot? That would be simpler. works like a charm for me. Florian
Re: [Dovecot] cur folder e-mails are not shown...
What doi you think? select inbox... * OK [UNSEEN 11997] First unseen. * OK [UIDVALIDITY 1271457928] UIDs valid * OK [UIDNEXT 12341] Predicted next UID b OK [READ-WRITE] Select completed. And about the command you said. There are lots! ... * 12337 FETCH (UID 12337 FLAGS (Junk) INTERNALDATE 29-May-2010 15:21:01 +0200) * 12338 FETCH (UID 12338 FLAGS () INTERNALDATE 29-May-2010 15:21:23 +0200) * 12339 FETCH (UID 12339 FLAGS (\Deleted \Seen) INTERNALDATE 29-May-2010 15:22:37 +0200) * 12340 FETCH (UID 12340 FLAGS (\Recent) INTERNALDATE 29-May-2010 15:25:40 +0200) Gonzalo Aguilar Delgado Consultor CRM - Ingeniero en Informática M. +34 607814276 El vie, 28-05-2010 a las 16:48 +0100, Timo Sirainen escribió: On Fri, 2010-05-28 at 12:55 +0200, Gonzalo Aguilar Delgado wrote: I realized that I have only e-mails from last 13 days. I see that I have lots more in the cur folder inside my Maildir folder. Check how many messages you have by talking IMAP protocol directly: http://wiki.dovecot.org/TestInstallation After selecting INBOX, see what x fetch 1:* (uid flags internaldate) says. attachment: yo-48x48-bw.jpg
Re: [Dovecot] doveadm: Error: dlopen(/path/2/lib10_doveadm_expire_plugin.so) failed
On 29.5.2010, at 0.34, Pascal Volk wrote: dunno why, but I've executed doveadm with the -D option. Debug output contains: doveadm(root): Error: dlopen(/path/2/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so) failed: /path/2/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_lookup This is normal. You don't have expire plugin loaded, so it also can't use doveadm_expire plugin.
Re: [Dovecot] cur folder e-mails are not shown...
Since you didn't claim you actually are missing mail, just seeing more Nope. As I suffer the same problem from Evolution and ThunderBird They could be deleted (actually marked for deletion, physically removed upon expunge). Those would have a T flag in the file name after the comma. Your MUA Evolution shows them in the Trash (virtual) folder. I tried all this but nothing shown. It's like cur folder is not shown. They could have been flagged Junk, and only be displayed in the Junk (virtual) folder. Junk folder is almost empty since I have SpamAsassin in place You could have a search active, hiding some mail. I checked this also. But's not. You could have specifically hidden them. See the View menu. I checked show all. But only a few appears. The one deleted by spam filter in the client. What else can be?
[Dovecot] strange sieve situation
Hi there, I've been working on rolling out the deliver service so we can
implement sieve. Dovecot 1.2.11, Postfix 2.6.6, FreeBSD 8, installed by
ports. Clustered environment, NFS backend.
Everything is working great for the most part, I'm using it to sort a copy
of my personal email on a test server. However, I noticed two emails were
not properly sorted.
I had added a rule (using Ingo, nice little piece of software) to redirect
the nightly FreeBSD security output emails into a folder servers.
However, nothing had triggered that rule, and the Maildir/.servers
directory had not yet been created.
Then, three of the security outputs came in at one time:
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve:
msgid=20100529070108.f2f0b7f...@mail-out04.xecu.net: failed to store
into mailbox 'servers': Mailbox already exists
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve:
msgid=20100529070109.d8f5e159...@mail-out01.xecu.net: failed to store
into mailbox 'servers': Mailbox already exists
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve:
msgid=20100529070109.d8f5e159...@mail-out01.xecu.net: stored mail into
mailbox 'INBOX'
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve: execution
of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve
failed, but implicit keep was successful
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve:
msgid=20100529070110.17a781b5...@mail-out02.xecu.net: stored mail into
mailbox 'servers'
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve:
msgid=20100529070108.f2f0b7f...@mail-out04.xecu.net: stored mail into
mailbox 'INBOX'
May 29 03:01:48 mg8 dovecot: deliver(andyt...@xecu.net): sieve: execution
of script /mail/var/mail2/xecunet/andytest.xecu.net//.dovecot.sieve
failed, but implicit keep was successful
That's the order they appeared in my logfile. I'm assuming they were all
sent to deliver at the same time, they all thought they needed to make the
directory, the one with msgid
20100529070110.17a781b5...@mail-out02.xecu.net was able to make the
directory and get delivered, whereas the other two freaked out because
they couldn't make the directory they thought needed to be made, and just
sent the mail to the inbox.
That's a reasonable approach, although I wonder if deliver/sieve could be
(or perhaps has been in 2.0) adjusted to more intelligently handle that
edge case.
Also, I'm wondering about dovecot_destination_recipient_limit = 1. I
have that set in my main.cf, but I'm not 100% positive it's taking effect.
# grep dovecot /usr/local/etc/postfix/main.cf
dovecot_destination_recipient_limit = 1
virtual_transport = dovecot
# grep dovecot /usr/local/etc/postfix/master.cf
dovecot unix - n n - - pipe
flags=DRhu user=mailman argv=/usr/local/libexec/dovecot/deliver -f ${sender}
-d ${recipient}
# postconf | grep dovecot
smtpd_sasl_type = dovecot
virtual_transport = dovecot
# postconf | grep destination_recipient_limit
default_destination_recipient_limit = 50
lmtp_destination_recipient_limit = $default_destination_recipient_limit
local_destination_recipient_limit = 1
relay_destination_recipient_limit = $default_destination_recipient_limit
smtp_destination_recipient_limit = $default_destination_recipient_limit
virtual_destination_recipient_limit = $default_destination_recipient_limit
Is dovecot_destination_recipient_limit being converted into local_ ?
Thanks,
Andy
---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
Re: [Dovecot] purge maildir folder after sa-learn
Phil Howard wrote: On Wed, May 26, 2010 at 06:13, Timo Sirainen t...@iki.fi wrote: On Wed, 2010-05-26 at 09:56 +0200, Florian Effenberger wrote: rm -f /path/to/Maildir/.spam-learn/* Oh, I really ment .spam-learn/cur/* (and maybe .spam-learn/new/* if you make it learn from both and it doesn't move mails to cur/). Can I simply delete the files, don't I destroy any indices or slow down Dovecot operation because of index rebuilding? Keep Dovecot's index files around so that they won't get deleted while Dovecot is trying to read/write them. You won't slow down anything by manually deleting maildir files. So basically, just moving mail files out (to a learn queue or whatever), from either new or cur is safe for Dovecot? That would be simpler. That's what I do. I move them either to a (shared) ham or spam folder, and run the script posted earlier, which processes and deletes them. -- -Eric 'shubes'
Re: [Dovecot] doveadm: Error: dlopen(/path/2/lib10_doveadm_expire_plugin.so) failed
On 05/29/2010 03:47 PM Timo Sirainen wrote: On 29.5.2010, at 0.34, Pascal Volk wrote: … undefined symbol: expire_set_lookup This is normal. You don't have expire plugin loaded, so it also can't use doveadm_expire plugin. OK, good to know. The 'undefined symbol' part looked a little bit buggy for me. So i reported it. Regards, Pascal -- The trapper recommends today: cafefeed.1015...@localdomain.org
Re: [Dovecot] doveadm: Error: dlopen(/path/2/lib10_doveadm_expire_plugin.so) failed
On 30.5.2010, at 0.50, Pascal Volk wrote: On 05/29/2010 03:47 PM Timo Sirainen wrote: On 29.5.2010, at 0.34, Pascal Volk wrote: … undefined symbol: expire_set_lookup This is normal. You don't have expire plugin loaded, so it also can't use doveadm_expire plugin. OK, good to know. The 'undefined symbol' part looked a little bit buggy for me. So i reported it. Yeah, doveadm just tries to load all doveadm plugins and ignores the ones that it can't.
[Dovecot] dovecot-2.0-pigeonhole/ManageSieve: wrong service name
Hi Stephan,
ManageSieve uses the wrong™ service name for the authdb lookup.
With dovecot-1.2-managesieve the service name was changed from
'managesieve' to 'sieve'. So I altered my table layout in order to make
the query SELECT userid AS user, password FROM dovecotpassword('%Ln',
'%Ld') WHERE %Ls work again.
When I try to login on the sieve port 4190/tcp, I find this in my
dovecot.log:
auth: Error: pgsql: Query failed, retrying: ERROR: column managesieve
does not exist
auth: Error: LINE 1: ..., password FROM dovecotpassword('user',
'example.org') WHERE managesiev...
Regards,
Pascal
--
The trapper recommends today: defaced.1015...@localdomain.org
