[imapfilter-devel] Bug report: "no candidate passwords for encryption found" error message when port is used for an account
David Segonds
david at segonds.org
Sat Nov 15 15:43:06 EET 2003
On Sat, Nov 15, 2003 at 02:05:14PM +0200, Lefteris Chatzibarbas wrote:
> On Fri, Nov 14, 2003 at 03:07:35PM -0600, David Segonds wrote:
> > account account1 david:xxxxxx at xxxxx.xxxxx.net
> ^^^^^^
> This is the problem. You should not supply a password for the account
> in the configuration file. It makes only sense to define encrypted
> passwords with the password editor, for those accounts that do not have
> a password already defined in the configuration file.
Granted. Another mistake on my part. Must have not been awake. :)
As I am probably not the only one to make this type of mistake, it would
be nice to have an error message that points out the problem with a line
number and asking to remove the password.
> account account1 david at xxxxx.xxxxx.net
Yes, with a line like this, it works but with:
account account1 david at xxxxx.xxxxx.net:143
It fails. This is what I had in the original one. Here is the last series of
tests:
=-=-=-=-=
daemon = 60
logfile = /home/david/.imapfilter.log
set timeout = 120
expunge = no
subscribe = yes
namespace = yes
errors = yes
account account1 david at xxxxx.xxxxx.net:143
folder inbox1 INBOX
filter spam
subject "{Spam?}"
action move spam
job spam inbox1
=-=-=-=-=
=-=-=-=-=
$ imapfilter -p -c imapfilterrc
imapfilter: no candidate passwords for encryption found
=-=-=-=-=
Sincerely,
David.
--
David Segonds - PGP 0x1F7A3E7A
More information about the Imapfilter-devel
mailing list