Re: [Dovecot] questions about compiling Sieve plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 30 Apr 2009, MercuryShadow wrote: The installed version is 1.0.rc15-2etch4, installed from the Debian repositories. Uff, maybe you need "non-free" and "contrib" sections in sources.list. I tried on Etch myself with success. Anyway, you can easily try to install any older library, which provides the development files for the particular dependency, because your goal is just to compile Dovecot in order to get lib-sieve compiled. then run debian/rules build Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSf6UD3WSIuGy1ktrAQI/gggAwMNbq+QChm0ge1Yzk5fjZSuv4IrPVmKq usOWAtBoLFFEbC624XhdiVO1iFRCPminF87YxxDpmX0TIYwIIOmFiB4fSLWYNC2n Hy/T209A9ZTbfFEOHFG+F9nW5Tq2Dm5u02bEiHBGD0i4I7zTwvn1/qG/SMUmWxPF F7Mn4BjClWNYiZP2/PaZAcgXIVzeZrCEq4Y+eA6mOat6D9maV83TbY//OvEr4rcF 8BWkvpNrGrxX7FpfS9Y4sU6Ai+SDffLaNHzIr5aZBTpO73hb6Dy3o3/ZBxeBU+vs OZL2prZamqdOe7dYWwB5jc4Py0GIEwtx+LQcLY3xWKcToNUkyKYiiw== =plGl -END PGP SIGNATURE-
Re: [Dovecot] login_max_processes_count and logs
Timo Sirainen wrote: On Thu, 2009-04-30 at 11:32 +0200, Dominique Fournier wrote: Hello, Our server reach today the login_max_processes_count. Dovecot works well and don't accept any new connection. But it doesn't log anything about this problem : we are blind why the connection is refused for the clients. Could you add a log when the connection limit is reached or (maybe better) a log with the occupation for the beginning of each connection ? . Dovecot version 1.0.15 on Debian AMD64 v1.1.9+ logs a warning: All login processes are in use. You may need to increase login_max_processes_count Thanks, I will ask this to Debian. begin:vcard fn:Dominique Fournier n:Fournier;Dominique adr;dom:;;25, av des martyrs;GRENOBLE;;38042 email;internet:dominique.fourn...@grenoble.cnrs.fr title:CNRS / CRIC tel;work:04 76 88 78 59 note:Hotline : 04 76 88 79 54 x-mozilla-html:FALSE url:http://cric.grenoble.cnrs.fr version:2.1 end:vcard smime.p7s Description: S/MIME Cryptographic Signature
[Dovecot] New messages notification - (IMAP PUSH?)
Hello all. I have strange problem. As I understand IMAP use server2client command to tell what new email is arrived. So - all was good, but few weeks ago I notice what my thunderbird not show new messages. I think it was local problem(I switch distro what day) but soon my email clients what uses mostly Outlook-2007-SP1 start to confirm this problem. What can it be and how can I fix it? I use Dovecot on FreeBSD-7.1 #pkg_info | grep dovecot dovecot-1.1.11 dovecot-managesieve-0.10.5 dovecot-sieve-1.1.6 #dovecot -n # 1.1.11: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p3 i386 ufs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-debug.log protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 ssl_ca_file: /usr/local/etc/certs/GlobalSignCA.crt ssl_cert_file: /usr/local/etc/certs/fxclub_org.crt ssl_key_file: /usr/local/etc/certs/fxclub_org.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_greeting_capability(managesieve): no login_process_size: 128 login_processes_count: 20 login_max_processes_count: 512 mail_max_userip_connections(default): 256 mail_max_userip_connections(imap): 256 mail_max_userip_connections(pop3): 20 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_uid: dmail mail_gid: dmail mail_location(default): maildir:/var/spool/dovecot/domains/%d/%n/ mail_location(imap): maildir:/var/spool/dovecot/domains/%d/%n/ mail_location(pop3): maildir:/var/spool/dovecot/domains/%d/%n/ mail_location(managesieve): mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_process_size: 512 mail_plugins(default): quota imap_quota autocreate mail_plugins(imap): quota imap_quota autocreate mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): % sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve auth default: mechanisms: plain login user: dovecot-auth username_format: %Lu verbose: yes worker_max_count: 100 passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: exim master: path: /var/run/dovecot/auth-master mode: 384 user: dmail plugin: quota: maildir quota_rule: *:storage=1024M quota_rule2: Trash:storage=1256M quota_rule3: SPAM:ignore quota_warning: storage=80%% /usr/local/bin/quota-warning.sh 80 quota_warning2: storage=95%% /usr/local/bin/quota-warning.sh 95 autocreate: Trash autocreate2: Sent autocreate3: Spam autosubscribe: Trash autosubscribe2: Sent autosubscribe3: Spam -- Best regards, Proskurin Kirill
[Dovecot] Can't connect to auth server
I'm trying to phase out procmail and move to dovecot-sieve instead. It
ain't proving easy. I'll describe my setup:
- Centos 5.2 box with dovecot 1.1.4 and dovecot-sieve 1.1.6 from ATrpms.
- A single user account is used to store all our email (the account is
called maildb).
- Getmail is being used to fetch the email from various ISP mailboxes.
I want to deliver mail to different folders in maildb's Maildir/
depending on who the email is addressed to (the procmail recipes
currently do that).
- Getmail destination section looks like this:
[destination]
type = MDA_external
path = /usr/libexec/dovecot/deliver
arguments = ("-d", "maildb")
allow_root_commands = true
- When I run getmail I get this error in dovecot.log:
deliver(maildb): May 04 22:15:26 Error: Can't connect to auth server
at /var/run/dovecot/auth-master: No such file or directory
It's true that I don't have a file called auth-master. I guess I
should have but until I started this dovecot-sieve work it was never a
problem. I have no idea what that file should look like. As I
installed from binary RPMs I would have thought one would have come
with the install.
Can anyone help?
Regards,
Phill
Re: [Dovecot] Unexplainable problem with POP3 quotas
2009/5/1 Timo Sirainen :
> On Thu, 2009-04-30 at 17:36 +0200, Marco Marongiu wrote:
>> * send a message slightly smaller than the number of bytes added at
>> step 2 (e.g., 2000); we are still under the 80% limit
>> * log in via POP to make dovecot update maildirsize
>
> This is the problem. Your MDA should enforce the quota usage. There's no
> guarantees that Dovecot updates maildirsize after the Maildir has been
> modified externally. Even when it updates it, it uses a different code
> path ("quota recalculation"), which doesn't trigger quota warnings.
>
> So use Dovecot's deliver and it'll do the quota enforcing and warnings.
Thanks Timo, we just reviewed the information in
http://wiki.dovecot.org/LDA and http://wiki.dovecot.org/LDA/Postfix
and we'll begin to test a new configuration shortly.
I hope to be back with good news soon ;)
Ciao
--bronto
Re: [Dovecot] fts-solr plugin issue (Marked invalid)
OK. Concentrating problem in one question. How to ignore "bad" message and index next one in indexing procedure (fts plugin) ?. Now, one "error 500" from solr and dovecot (# 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.21.7-2.fc8xen i686 Ubuntu 8.04.2 ext3 ) stop and each next search query repeat the story. I've explored fts, and ftp-solr directories in src, without success for now. Timo, you understand code much bettter, can you help me and point to place in code, or probably create some patch, if possible ?. On Fri, 05/01/2009 at 5:56pm, "Nikolai Derzhak" wrote: > Hi. > > We user ftp-solr plugin and have problem with solr-1.3+ > with HTMLStripWhitespaceTokenizerFactory (Solr schema in attachments). > In some maildir's present messages with wrong "Content-Type: " fields in > attachments. > For example: > " > Content-Type: TEXT/mspowerpoint; name="Zapatec_6zap_netvibes_1.ppt" > " > Indexing for this messages is stop with "fts_solr: Indexing failed: 500 > Internal Server Error". > In solr log is: > " > SEVERE: java.io.IOException: Mark invalid > at java.io.BufferedReader.reset(BufferedReader.java:485) > " > (mail list with discussion: http://markmail.org/message/2fnfiwygvehjngyr# > query:SEVERE%3A%20java.io.IOException%3A%20Mark%20invalid%20lucene+page:1+ > mid:2fnfiwygvehjngyr+state:results) > > Look's like dovecot try to index attachments like this. > Also for some messages we have same error. > Dovecot stop indexing of box and each search we have lag and CPU load on > server. > > So we need to make dovecot more "stable" to this error. > For first time , will be good, just ignore problematic messages with error > from solr. > > Let's discuss this issue, because this is general problem. > We ready to explore code where needed , etc. > > Regards, > Nikolai > > Powered by the 6zap. Sign up at http://www.6zap.com for an account that > provides advanced e-mail, calendar and contacts capabilities. Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.
Re: [Dovecot] fts-solr plugin issue (Marked invalid)
On May 4, 2009, at 10:16 AM, Nikolai Derzhak wrote: OK. Concentrating problem in one question. How to ignore "bad" message and index next one in indexing procedure (fts plugin) ?. Now, one "error 500" from solr and dovecot (# 1.1.11: /etc/dovecot/ dovecot.conf # OS: Linux 2.6.21.7-2.fc8xen i686 Ubuntu 8.04.2 ext3 ) stop and each next search query repeat the story. Maybe simply using 1.1.14 would help? I already fixed one Solr issue: http://hg.dovecot.org/dovecot-1.1/rev/678c3252a454 If that's not the problem, it would help to have one of those mails that breaks it.
Re: [Dovecot] fts-solr plugin issue (Marked invalid)
Citando Nikolai Derzhak : > But in sum: when dovecot try to index some mail's, that solr tokenizer not > eat (error 500, Marked invalid), > dovecot stop indexing of box and retry attempts in each next search with same > result. I think u might have a look on solr-connection.c and look to the functions that communicate with Solr and change the error handling. I think this "miss feature" will be useful to me soon. Rui Carneiro -- Portugalmail, Comunicações S.A. www.portugalmail.net PS: Sorry but my current knowledge on this is not very much at the moment.
Re: [Dovecot] fts-solr plugin issue (Marked invalid)
On Mon, 05/04/2009 at 5:36pm, "Rui Carneiro" wrote: > I do not have sure if I understood your problem correctly. > > Are you trying to index attachments from messages? Or Dovecot is indexing > some "bad" parts and you just do not know why? > Read first post, please, with description. But in sum: when dovecot try to index some mail's, that solr tokenizer not eat (error 500, Marked invalid), dovecot stop indexing of box and retry attempts in each next search with same result. > Regards, > Rui Carneiro > -- > Portugalmail, Comunicações S.A. > www.portugalmail.net > > Citando Nikolai Derzhak : > >> OK. Concentrating problem in one question. >> How to ignore "bad" message and index next one in indexing procedure (fts >> plugin) ?. >> Now, one "error 500" from solr and dovecot (# 1.1.11: >> /etc/dovecot/dovecot.conf >> # OS: Linux 2.6.21.7-2.fc8xen i686 Ubuntu 8.04.2 ext3 >> ) stop and each next search query repeat the story. >> I've explored fts, and ftp-solr directories in src, without success for now. >> >> Timo, you understand code much bettter, can you help me and point to place >> in >> code, >> or probably create some patch, if possible ?. Powered by the 6zap. Sign up at http://www.6zap.com for an account that provides advanced e-mail, calendar and contacts capabilities.
Re: [Dovecot] fts-solr plugin issue (Marked invalid)
I do not have sure if I understood your problem correctly. Are you trying to index attachments from messages? Or Dovecot is indexing some "bad" parts and you just do not know why? Regards, Rui Carneiro -- Portugalmail, Comunicações S.A. www.portugalmail.net Citando Nikolai Derzhak : > OK. Concentrating problem in one question. > How to ignore "bad" message and index next one in indexing procedure (fts > plugin) ?. > Now, one "error 500" from solr and dovecot (# 1.1.11: > /etc/dovecot/dovecot.conf > # OS: Linux 2.6.21.7-2.fc8xen i686 Ubuntu 8.04.2 ext3 > ) stop and each next search query repeat the story. > I've explored fts, and ftp-solr directories in src, without success for now. > Timo, you understand code much bettter, can you help me and point to place in > code, > or probably create some patch, if possible ?.
[Dovecot] Problem with BODYSTRUCTURE (wrong charset)
Hi,
I've changed a program that fetches mail via IMAP from an Exchange Server to
use our Dovecot machine.
But now I'm experiencing strange problems with seem to be caused by a wrong
BODYSTRUCTURE answer that causes wrong charset handling. When fetchting the
BODYSTRUCTURE I see this:
Dovecot:
88 UID fetch 32 (BODYSTRUCTURE)
* 1 FETCH (UID 32 BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL
"7bit" 725664 9385 NIL NIL NIL NIL))
88 OK Fetch completed.
Exchange:
90 UID fetch 10 (BODYSTRUCTURE)
* 2 FETCH (BODYSTRUCTURE (("TEXT" "PLAIN" ("charset" "iso-8859-1") NIL NIL
"QUOTED-PRINTABLE" 2784 47 NIL NIL NIL)("IMAGE" "JPEG" ("name" "197254.jpg")
NIL NIL "BASE64" 498806 NIL ("attachment" ("filename" "197254.jpg"))
NIL)("IMAGE" "JPEG" ("name" "197254_1.jpg") NIL NIL "BASE64" 188424 NIL
("attachment" ("filename" "197254_1.jpg")) NIL)("IMAGE" "JPEG" ("name"
"197254_2.jpg") NIL NIL "BASE64" 31878 NIL ("attachment" ("filename"
"197254_2.jpg")) NIL)("TEXT" "PLAIN" ("name" "pix.xml") NIL NIL
"QUOTED-PRINTABLE" 2934 49 NIL ("attachment" ("filename" "pix.xml"))
NIL)("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 0 1 NIL ("attachment"
NIL) NIL) "mixed" ("Message-ID:" ""
"boundary" "000XMAIL000") NIL NIL) UID 10)
90 OK FETCH completed.
Mail contents were:
[...]
To: b...@foo.de
Subject: Pictures
From: bl...@foo.de
CC:
Errors-To: bl...@foo.de
Sender: foo...@foo.de
MIME-Version: 1.0
Content-Type: multipart/mixed;
Message-ID:=;
boundary="000XMAIL000"
Message-Id: <20090504120233.58afc34...@foo.de>
Date: Mon, 4 May 2009 14:02:33 +0200 (CEST)
--000XMAIL000
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: Quoted-Printable
[...]
--000XMAIL000
Content-Type: image/jpeg; name="197254.jpg"
Content-Transfer-Encoding: Base64
Content-Disposition: attachment; filename="197254.jpg"
[...]
--000XMAIL000
Content-Type: text/plain; name="pix.xml"
Content-Transfer-Encoding: Quoted-Printable
Content-Disposition: attachment; filename="pix.xml"
=0D
=0D
[...]
Here is my dovecot -n output:
# 1.1.14: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.21-gentoo-r1 i686 Gentoo Base System release 1.12.11.1 ext3
log_path: /var/log/dovecot
protocols: imap imaps pop3 pop3s
listen: [::]
ssl_cert_file: /etc/ssl/dovecot/server.pem
ssl_key_file: /etc/ssl/dovecot/server.key
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
mail_privileged_group: vmail
mail_location: maildir:/var/mail/%d/%n
mail_executable(default): /usr/libexec/dovecot/imap
mail_executable(imap): /usr/libexec/dovecot/imap
mail_executable(pop3): /usr/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/lib/dovecot/imap
mail_plugin_dir(imap): /usr/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/pop3
auth default:
mechanisms: plain login digest-md5 cram-md5 rpa apop
username_translation: AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz
verbose: yes
debug: yes
debug_passwords: yes
passdb:
driver: passwd-file
args: /etc/passwd.dovecot
userdb:
driver: passwd-file
args: /etc/passwd.dovecot
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 432
user: postfix
group: postfix
master:
path: /var/run/dovecot/auth-master
mode: 432
user: root
group: vmail
So is this a parsing error in dovecot or was the Exchange Server just parsing
incorrect MIME-Headers?! Any hint would be appreciated...
Thanks in advance,
Craig
Re: [Dovecot] Problem with BODYSTRUCTURE (wrong charset)
On Mon, 2009-05-04 at 16:18 +0200, Craig Craig wrote: > Content-Type: multipart/mixed; > Message-ID:=; > boundary="000XMAIL000" The problem is the Message-ID parameter. It's not legal to have ':' before '='. I added a workaround to v1.2+, but v1.1's code is different and I'd rather not change it much anymore. http://hg.dovecot.org/dovecot-1.2/rev/05a98aaf0aaf signature.asc Description: This is a digitally signed message part
[Dovecot] mail_index_sync_map error on 1.1.14
Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. NFS may have been used. Panic: IMAP(user): file mail-index-sync-update.c: line 843 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index- >indexid || map->hdr.indexid == 0) Two different backtraces to this error are: 0 libSystem.B.dylib 0x7fff87b775ea __kill + 10 1 libSystem.B.dylib 0x7fff87bf9fc8 abort + 83 2 imap 0x000100069f3e default_fatal_finish + 70 3 imap 0x000100069f8c i_syslog_fatal_handler + 0 4 imap0x0001000696eb i_info + 0 5 imap 0x000100051d3a mail_index_sync_map + 144 6 imap 0x00010004a22c mail_index_map + 212 7 imap 0x000100046a0f mail_index_refresh + 14 8 imap 0x000100016e4b maildir_sync_header_refresh + 24 9 imap 0x000100016ee6 maildir_sync_quick_check + 61 10 imap 0x00010001796a maildir_sync_context + 91 11 imap 0x000100017d8e maildir_storage_sync_init + 104 12 imap0x00010003eb1b mailbox_sync + 31 13 imap 0x000148a8 cmd_select_full + 224 14 imap0x000149f3 cmd_select + 11 15 imap 0x0001677e client_command_input + 33 16 imap 0x0001693f client_command_input + 482 17 imap 0x00016a3e client_handle_input + 239 18 imap0x00016bc2 client_input + 148 19 imap 0x000100070f83 io_loop_handler_run + 272 20 imap0x000100070348 io_loop_run + 55 21 imap0x0001db95 main + 1635 22 imap0x00011010 start + 52 0 libSystem.B.dylib 0x7fff863125ea __kill + 10 1 libSystem.B.dylib 0x7fff86394fc8 abort + 83 2 deliver 0x00010005f82d default_fatal_finish + 70 3 deliver 0x00010005f8fb i_set_failure_syslog + 0 4 deliver 0x00010005efda i_info + 0 5 deliver 0x00010004867e mail_index_sync_map + 144 6 deliver 0x000100040b70 mail_index_map + 212 7 deliver 0x00010003d353 mail_index_refresh + 14 8 deliver 0x000100044219 mail_index_transaction_commit_v + 988 9 deliver 0x000100032e1c index_transaction_finish_commit + 90 10 deliver 0x0001fc4d maildir_transaction_commit + 130 11 deliver 0x000100032cb9 index_transaction_commit + 63 12 lib10_quota_plugin.so 0x00010021efd9 quota_get_mail_user_quota + 1907 13 deliver 0x0001000354ac mailbox_transaction_commit + 48 14 deliver 0x00011844 deliver_save + 572 15 deliver 0x00013244 main + 6266 16 deliver 0x00010948 start + 52
[Dovecot] index_mailbox_set_recent_uid error on 1.1.14
Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. Pretty sure NFS was not used. Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: seq_range_exists(&ibox->recent_flags, uid) The backtrace is: 0 libSystem.B.dylib 0x7fff85025166 __kill + 10 1 libSystem.B.dylib 0x7fff850a80e0 abort + 83 2 imap 0x000100069f3e default_fatal_finish + 70 3 imap 0x000100069f8c i_syslog_fatal_handler + 0 4 imap0x0001000696eb i_info + 0 5 imap 0x00010003b86b index_mailbox_set_recent_uid + 74 6 imap 0x00010003b8cb index_mailbox_set_recent_seq + 58 7 imap 0x000100018f5d maildir_sync_index + 2163 8 imap 0x000100017ba5 maildir_sync_context + 662 9 imap 0x000100017d8e maildir_storage_sync_init + 104 10 imap 0x0001c037 imap_sync_init + 132 11 imap 0x0001c289 cmd_sync_delayed + 477 12 imap 0x00016ae8 client_handle_input + 409 13 imap0x00016bc2 client_input + 148 14 imap 0x000100070f83 io_loop_handler_run + 272 15 imap0x000100070348 io_loop_run + 55 16 imap0x0001db95 main + 1635 17 imap0x00011010 start + 52
Re: [Dovecot] questions about compiling Sieve plugin
Here are the three lines in my sources.list: deb http://http.us.debian.org/debian/ etch main deb-src http://http.us.debian.org/debian/ etch main deb http://security.debian.org/ stable/updates main contrib non-free "contrib" and "non-free" appear to be present already. Steffen Kaiser-9 wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thu, 30 Apr 2009, MercuryShadow wrote: > >> The installed version is 1.0.rc15-2etch4, installed from the Debian >> repositories. > > Uff, maybe you need "non-free" and "contrib" sections in sources.list. > I tried on Etch myself with success. > >>> Anyway, you can easily try to install any older library, which provides >>> the development files for the particular dependency, because your goal >>> is >>> just to compile Dovecot in order to get lib-sieve compiled. >>> >>> then run debian/rules build > > Bye, > > - -- > Steffen Kaiser > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > > iQEVAwUBSf6UD3WSIuGy1ktrAQI/gggAwMNbq+QChm0ge1Yzk5fjZSuv4IrPVmKq > usOWAtBoLFFEbC624XhdiVO1iFRCPminF87YxxDpmX0TIYwIIOmFiB4fSLWYNC2n > Hy/T209A9ZTbfFEOHFG+F9nW5Tq2Dm5u02bEiHBGD0i4I7zTwvn1/qG/SMUmWxPF > F7Mn4BjClWNYiZP2/PaZAcgXIVzeZrCEq4Y+eA6mOat6D9maV83TbY//OvEr4rcF > 8BWkvpNrGrxX7FpfS9Y4sU6Ai+SDffLaNHzIr5aZBTpO73hb6Dy3o3/ZBxeBU+vs > OZL2prZamqdOe7dYWwB5jc4Py0GIEwtx+LQcLY3xWKcToNUkyKYiiw== > =plGl > -END PGP SIGNATURE- > > -- View this message in context: http://www.nabble.com/questions-about-compiling-Sieve-plugin-tp23285989p23374070.html Sent from the Dovecot mailing list archive at Nabble.com.
Re: [Dovecot] mail_index_sync_map error on 1.1.14
On Mon, 2009-05-04 at 12:21 -0500, Mike Abbott wrote: > Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit > Intel. NFS may have been used. > > Panic: IMAP(user): file mail-index-sync-update.c: line 843 > (mail_index_sync_map): assertion failed: (map->hdr.indexid == index- > >indexid || map->hdr.indexid == 0) Can you get the values of map->hdr.indexid and index->indexid? Anyway it looks like dovecot.index file was recreated by another Dovecot that didn't know about the existing index files (which shouldn't really be happening normally) and the syncing code didn't handle that very well. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] index_mailbox_set_recent_uid error on 1.1.14
On Mon, 2009-05-04 at 12:21 -0500, Mike Abbott wrote: > Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit > Intel. Pretty sure NFS was not used. > > Panic: IMAP(user): file index-sync.c: line 39 > (index_mailbox_set_recent_uid): assertion failed: > seq_range_exists(&ibox->recent_flags, uid) Did it log anything else? I know this can happen in some error conditions that I haven't bothered to look into yet. signature.asc Description: This is a digitally signed message part
[Dovecot] Maildir bugs
I just found out that when using deliver or saving mails with IMAP APPEND command there was all kinds of race condition bugs that could cause e.g.: dovecot-uidlist: Duplicate file entry at line 18: 1241457213.M690227P32531.host,W=3359:2,T (uid 170019 -> 170020) And who knows what else. If you've run into those problems, these patches should help: http://hg.dovecot.org/dovecot-1.1/rev/6bbe27c32cb8 http://hg.dovecot.org/dovecot-1.1/rev/003bebac2c76 http://hg.dovecot.org/dovecot-1.1/rev/96c8632775df They are pretty large though, hopefully won't break anything. But at least my stress tests can no longer break it. I'll probably release v1.1.15 RC in a few days so at least some people can try to break it before the final v1.1.15 :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] New messages notification - (IMAP PUSH?)
Proskurin Kirill wrote: Hello all. I have strange problem. As I understand IMAP use server2client command to tell what new email is arrived. So - all was good, but few weeks ago I notice what my thunderbird not show new messages. I think it was local problem(I switch distro what day) but soon my email clients what uses mostly Outlook-2007-SP1 start to confirm this problem. What can it be and how can I fix it? Do the messages not show up at all? Or do they not show as new? If you have two mail clients running at the same time, one will miss out on the 'new message' notices. -- Curtis Maloney cmalo...@cardgate.net
Re: [Dovecot] New messages notification - (IMAP PUSH?)
Curtis Maloney wrote: Proskurin Kirill wrote: Hello all. I have strange problem. As I understand IMAP use server2client command to tell what new email is arrived. So - all was good, but few weeks ago I notice what my thunderbird not show new messages. I think it was local problem(I switch distro what day) but soon my email clients what uses mostly Outlook-2007-SP1 start to confirm this problem. What can it be and how can I fix it? Do the messages not show up at all? Or do they not show as new? If you have two mail clients running at the same time, one will miss out on the 'new message' notices. They not show at all. Then I click at IMAP folder - they start to show at that folder. I have about 40 IMAP folders - and it is hard to push at every folder minute after minute. ;-) I not change anything at config and really don`t know why this problem appears. And I don`t know how to test it by IMAP commands. -- Best regards, Proskurin Kirill
