[imapfilter-devel] Error: attempt to index field 'INBOX'

David DeSimone fox at verio.net
Mon Oct 22 01:31:36 EEST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alejandro Jakubi <jakubi at df.uba.ar> wrote:
>
> I would prefer right now an automatization of the mail processing
> tasks (those that I do currently via Pine filter rules), even if
> partial (because "recipes" are not readily available to implement
> everything).  Later on I will go into learning LUA for adding what is
> left.

I don't think imapfilter has a wiki, so you are probably limited to
searching the archives of this mailing list.

If you look at the January 2007 archives, you should find a post that I
made, where I showed a lot of my code examples and methods that I use
with imapfilter 1.x.  Shows how to avoid some concurrency problems, and
how I like to structure my code to avoid error messages and such.  I
also show how I embed DEBUG statements in my code so that I can test it
interactively, then run it in daemon mode without filling up log files.

> When Pine has the remote INBOX open and imapfilter executes, accessing
> also to this INBOX, Pine produces this error message:
> 
> "[MAIL FOLDER INBOX CLOSED DUE TO ACCESS ERROR]"
> 
> and I have to reopen the remote INBOX.

This is interesting.  I suppose it might be that your particular IMAP
implementation has some restrictions.  My IMAP server is actually part
of Microsoft Exchange, so I know that it freely permits multiple
connections.  If you are using another server such as Cyrus IMAP, it may
have some restrictions concerning what simultaneously-connected clients
can do.

> So, as Pine "does not like" to share the resource, what about
> imapfilter?

Imapfilter is at the mercy of your IMAP server.  If the server returns
an error, imapfilter can't do its work.  But if you are using daemon
mode, it will just try again later.

> Is there a way to query the value of all the options?

It almost does not matter what the default is.  The "safe" thing to do
is to set the option to what you want it to be.  Then you don't have to
worry about what the default is, or whether the default will change from
version to version.

> I am member of this list (I beleived that I could not post otherwise). 
> But I would very grateful if you could continue CC to my address on
> your replies because the messages via the list server arrive here
> rather corrupted (in formating and with missing spaces between some
> words).

That is a strange problem.  It reminds me of when you posted earlier,
saying that imapfilter's man pages are corrupted on your system.  I do
not know why you see so many forms of corruption, but perhaps it is not
really the fault of your system.  Perhaps your terminal emulator is not
working correctly, or does not match the settings of your $TERM
environment variable.  Sometimes, an "stty -tabs" setting can make a
huge difference in apparent corruption.  :)

- -- 
David DeSimone == Network Admin == fox at verio.net
"This email message is intended for the use of the person to whom
 it has been sent, and may contain information that is confidential
 or legally protected.  If you are not the intended recipient or have
 received this message in error, you are not authorized to copy, dis-
 tribute, or otherwise use this message or its attachments.  Please
 notify the sender immediately by return e-mail and permanently delete
 this message and any attachments.  Verio, Inc. makes no warranty that
 this email is error or virus free.  Thank you."  --Lawyer Bot 6000
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFHG9NIFSrKRjX5eCoRAkC4AJ40sMnJ3b3K2eUfTERGjZv2bR1PxwCeKNJ9
oidGNvJUd9oJRX0eitFeqls=
=eok8
-----END PGP SIGNATURE-----




More information about the Imapfilter-devel mailing list