I'm not sure when this problem first occurred - it is many months since I last editted a sieve filter. I am certainly several versions of Thunderbird and, probably, a few versions of Dovecot on from when I last editted a sieve filter. However, I do know that I have done so in the past. I have just built Dovecot 2.2.13 and Pigeonhole 0.4.3, installed and running on Slackware 14.1 x64. I am running an up-to-date version of Thunderbird (31.0) on Arch Linux x64. The sieve filters are definitely being applied to incoming mail, and working perfectly well. However, when I attempt to edit the Sieve Filters (from Thunderbird Tools->Sieve Message Filters...), the Sieve Filters tab is displayed, but not populated (eg, the Server Sieve Capabilities are not displayed, and there is an endless 'hourglass' displayed in the main mailfilters pane. Does anyone recognise the symptoms and can advise how to resolve the problem, or suggest what logs I should examine/post in order to identify the cause? -- ------------------------------------------------------------------- Peter Bell Mob: +63 (0) 9287 340 343 Tagum City, Philippines. Tel: +63 (0) 84 216 9037 email/msn: peter at bellfamily.org.uk Tel: +63 (0) 84 308 0002
Am 19.08.2014 um 16:20 schrieb Peter Bell:> I am running an up-to-date version of Thunderbird (31.0) on Arch Linux x64. > > The sieve filters are definitely being applied to incoming mail, and working perfectly well. > > However, when I attempt to edit the Sieve Filters (from Thunderbird Tools->Sieve Message Filters...), the Sieve > Filters tab is displayed, but not populated (eg, the Server Sieve Capabilities are not displayed, and there is an > endless 'hourglass' displayed in the main mailfilters pane. > > Does anyone recognise the symptoms and can advise how to resolve the problem, or suggest what logs I should > examine/post in order to identify the cause?the extension as i tried to use it the last time pretty clear is not compatible with recent thunderbird versiond -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20140819/350139e6/attachment.sig>
On 08/19/2014 04:20 PM, Peter Bell wrote:> Does anyone recognise the symptoms and can advise how to resolve the > problem, or suggest what logs I should examine/post in order to identify > the cause?Are you using the latest nightly build of the sieve addon? All "stable" releases are outdated. Regards, Thomas Herrmann -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4246 bytes Desc: S/MIME Cryptographic Signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20140819/763686d5/attachment.p7s>
you need the updated beta sieve plugin 0.2.3d https://github.com/thsmi/sieve/blob/master/nightly/0.2.3/sieve-0.2.3d.xpi see https://github.com/thsmi/sieve/issues/26 for the reason why it is not available via mozilla plugins site this should fix the problem in thunderbird. (I use it myself having had the same issue) Regards, Tim On 19/08/2014 15:20, Peter Bell wrote:> I'm not sure when this problem first occurred - it is many months > since I last editted a sieve filter. I am certainly several versions > of Thunderbird and, probably, a few versions of Dovecot on from when I > last editted a sieve filter. However, I do know that I have done so > in the past. > > I have just built Dovecot 2.2.13 and Pigeonhole 0.4.3, installed and > running on Slackware 14.1 x64. > > I am running an up-to-date version of Thunderbird (31.0) on Arch Linux > x64. > > The sieve filters are definitely being applied to incoming mail, and > working perfectly well. > > However, when I attempt to edit the Sieve Filters (from Thunderbird > Tools->Sieve Message Filters...), the Sieve Filters tab is displayed, > but not populated (eg, the Server Sieve Capabilities are not > displayed, and there is an endless 'hourglass' displayed in the main > mailfilters pane. > > Does anyone recognise the symptoms and can advise how to resolve the > problem, or suggest what logs I should examine/post in order to > identify the cause? >